https://github.com/home-assistant/core/issues/35137 is related, but it’s possible that’s a separate issue.
I keep running into this same issue and I just switched to connecting them to the SmartThings app and using that to connect to Home Assistant. It’s not local but at least it works!
1 Like
Thanks! For anyone using SmartThings, this might be a viable workaround.
That’s the second app (after Kasa) which handles TP-Link switches just fine. I think we’ve conclusively proven that HA is where the problem lies.
1 Like
I had no issues after updating the firmware on the 110 tp-link switches. Its not long since it was a new firmware released
1 Like
Hmmm. Worth a shot. My HS110 switches are at firmware version 1.2.5, according to Kasa. I don’t see any way to update them on the app.
What’s the latest firmware version and how would I install it?
One thing I’ve found is that they can be stable for long periods, then go into a “funk” where they’re constantly going unavailable. I think this may be why we see comments like “I did xyz and now they work fine.”
Clearly network reliability is a factor, but the Kasa app has no problem during these “funk” times. Presumably HA just doesn’t handle minor connection issues as well as the Kasa and SmartThings apps.
One thing I’ve noticed is if the power goes out, I usually have to go into Kasa to check that both HS110’s are connecting OK (they almost always are) and THEN restart HA. It appears that if HA comes up before the switches, HA will never go back and re-check. They stay “unavailable” until I do the above steps.
I was battling this for some time even before getting HA and had the same behaviour in Alexa tplink skill where alexa would claim devices unavailable and kasa app worked fine.Finally gave up, got different plugs (meross) and they’ve been rock solid since. Even the KL110 bulb I have does this at times and I plan to get rid of it eventually.
Perhaps it’s because I redirect timeserver requests to my router where I run my own NTP server as tp-link devices (my deco mesh does the same) abuse public time servers for internet connectivity check; you don’t have to synchronise time multiple time a minute; we’re talking tens of thousands of outgoing connections to public ntp servers a day per single plug, but even when I allowed them this they regularly “fell off the grid” until re-plugging them.
I know “just get different ones” is not really a solution, but I’ve tried everything else up to this point.
Hi, I am curious about which integration you using with the Meross switches, or how they are configured.
Thanks!
Hi, it’s in the HACS just search for meross, if you don’t use HACS the repo for the meross integration with manual instructions is here: https://github.com/albertogeniola/meross-homeassistant After installing just add it as any other integration via the yellow + in bottom right corner in HA, enter your meross cloud credentials and you’re set.
Excellent! Thank you very much for your reply. Cheers.
I too am having this issue. TP link HS110 was stable for years and the last 2-3 weeks it keeps going unavailable. Static IP (router reservation), latest HA (112.4). I’m currently using the integration but think I’ll be going back to hard coding if this continues. Not aware of any workaround, and I don’t use SmartThings. HS110 (UK) Firmware 1.2.5, hardware 1.0
I keep running into this same issue and I just switched to connecting them to the SmartThings app and using that to connect to Home Assistant. It’s not local but at least it works!
To clarify, it works running SmartThings app WITHOUT a SmartThings hub?
Yep! If you don’t want to use SmartThings and have an iOS device, I’m pretty sure you could use HomeKit as well
I’ve been running with “static” (DHCP Reserve) IPs on my devices for the last several months without issue. My only issues have been related to my router and wireless devices (Unifi DreamMachine).
My TP Devices are a in a IoT VLAN, resulting in more of a “need” for static assignment. I hadn’t validated (since my wireless “fixes”-per-say) if cross-VLAN discovery.
i can confirm that the smartthings workaround works. it seems to be more stable even than the kasa app, since it happened to see the plug as unavailable in kasa, but it worked normally in smartthings. the only downside is that i couldn’t find a way to access the measured values (v, a, kw, kwh) via this route.
Agreed. Zero problems and you don’t need a SmartThings hub. I updated my NodeRed automations with the SmartThings integration and it just works.
It is actually worth doing anyway. It actually adds a slim line to the notification bar to control a few entities. It also let me pull my Nexx garage doors in to home assistant (as of yet, there is no official integration for them).
Recently, I installed bluetooth and bluetooth_le for device tracking. My problems started there. I’ve just removed them and the issue has instantly gone away. Not sure why. Bluetooth tracking isn’t of huge interest, so happy to revert.
I always had random connection drops with my Kasa switches. However the amount and frequency of those drops were acceptable.
Just recently, I set up bluetooth presence detection via room assistant with the HA add on plus two Raspberry Pi Zero’s.
From that moment on, the Kasa switches went crazy. Switching room assistant off, think went back to normal.
So I can confirm, that bluetooth is a huge issue for the reliability of the Kasa switches. Of course, that’s not surprising since both use the 2.4GHz frequency. But I wasn’t expecting this much of an impact.
To double check this assumption see screenshot attached. Additionally to home assistant I track power consumption of all Kasa switches via Prometheus and Grafana. At 10:10 I switched off all room assistant instances. Immediately the drop outs stopped.
1 Like
Word from a noob. Same issue as everyone seems to have with these. Luckily I only have one plug -HS100 with 1.0.3 fimware - that disappears at random. It wont reappear in HA unless I restart HA, even though its in the Kasa App. Config wise HA is running on proxmox box with Gb ethernet to TP-Link C9 Wireless Router configured a a Repeater but only for 2.4GHz.(TP-Link acts as repeater (via gigabit) for BT Smart hub which does DHCP (all leases are reserved so effectively fixed IP), internet connection and provides 5GHz mesh. wont be buying anymore of these things.
I too am an HA noob.
HA Version: 0.114.3
I managed to get my 8 Kasa devices (Switches, Plugs(aka switches for HA purposes) and a KP400(strip) working with discovery: false and static IP addresses in the configuration.yaml file.
I moved my on/off times to automations.yaml (turned-off the schedules in the Kasa App).
Everything was fine. I took snapshots throughout the process. I was pleased with my progress…
…and then… I decided to change the address of my Raspberry Pi for Home Assistant to a static IP address. (No change for my TP-Link Kasa devices, they were already using fixed IP addresses. I made that change when I added them to the configuration.yaml file). “all” I did was assign the fixed IP address in my router (no changes to the HA configuration). Reboot HA … new fixed address assigned… badges, weather card, camera card, etc all work as before…
BUT all of my Kasa entities are GONE: (as shown on the lovelace dashboard)
The TP-Link Integration does not show any devices or entities.
I’ve deleted/reinstalled the TP-Link Integration (several times) reboots/shutowns/power-off/on etc.
No joy.
My next step is to re-install from scratch (having saved key config files for piecemeal restoration). Before taking the plunge, I thought I’d check to see if anyone else has had a similar problem.
(I believe this is a different kind of “Unavailable” problem. This “unavailable” problem is not intermittent, it’s “all or nothing”. It was working, now it’s not.).
Thanks!
Unfortunately I can’t help you with this, since I have never tried to change the host ip address.
Generally speaking I was struggling with Kasa Plugs for at least a year and then decided to replace 4 of my 15 plugs by Homematic HMIP-PSM switches. And so far absolutely no issues with these switches, even in monitoring them in Grafana. I will keep on replacing the rest soon. However you need an HMIP Stick but it doesn’t cost a fortune.
I hope that helps anyone who is looking for an alternative for Kasa and who is feed up like me with Kasa issues.
Best
1 Like