I’m liking the new hs300 integration, but on my strip the first two switches often will switch from switch.plug_1 and switch.plug_2 to switch.unnamed_device and switch.unnamed_device2. This only seems to happen to the first two switches and it only happens when I restart home-assistant. It doesn’t always happen as it sometimes randomly switches back to the normal names. I’ve been working around this by just not using those switches for anything I want to be able to turn off or on, but this is really obnoxious and renders those switches unreliable for any automation. Anybody else notice this in using the hs300?
1 Like
Any update? I am thinking about buying one of these but your feedback has me holding off. Thanks!
No, I haven’t gotten any nibbles and the behavior hasn’t changed. Part of me wonders if there is something defective with my unit as it seems to be only the first two switches that have the issue, but it also seems similar to the issue with other tplink switches randomly not showing up on auto-Discovery. I might try to exchange my unit and see if there’s any change.
When I recently installed a TP-Link smart outlet, it took three restarts of Hass.IO before the device names were correctly represented. I suspect it’s bad lag on the part of TP-Link’s Kasa servers, honestly.
Oh, I have restarted MANY times since I first installed everything and the issue is usually there, sometimes not. It has always come back if it gets restarted once or twice. Most tplink switches are only reliable (in my experience) if you turn off auto-discovery and just reserve the ip addresses for them and keep a list in the config, but that’s not the way the switches on the hs300 work as there is only one ip address for the whole strip.
At this point I’ve ordered a replacement strip and I’ll see if I have the issue with the new one…
No dice, new strip still having the same issue. sigh…
Thanks for your updates, Nick. I bought the HS300 because it fit my application perfectly but this instability of the entities is making it very difficult to work with. Hopefully someone on the forum knows what is going on and how to fix it.
Just as an update, seems like the integration has been updated at some point. The switches still become unavailable sometimes, but now seem to refresh themselves after a brief time rather than just staying offline until a restart. I’ve worked around this as best I can by using wait commands in automation to wait until switches come back online to proceed with the automation instead of just stopping cold. It’s a good-enough solution for me currently.
Thanks for the information and the idea about using Wait in your automation but are we really considering this issue solved? This is an OK workaround but not a solution, in my opinion.
I don’t disagree, but I suspect a more perfect solution is well beyond what I am capable of fixing myself at this point and it’s doing what I want it to do reliably. So it goes with a platform like this.
I have three of the KP400 two-outlet outdoor plugs. They actually are pretty reliable, even though each pair of outlets shares an IP. BUT… I just bought the HS300 and it does not play well with HA. I should have read this thread first!!
I have the same problem I have 2 of the steps and one is a little better than the other but each has their issues. I have discovery turned off but it doesn’t help.