New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for the KP200 #179
Comments
Can you do a traffic capture from the discovery process (wireshark, or maybe --debug flag gives more details, too)? #175 may also be related. |
Here is the sysinfo dump of the KP200. Hope this helps.
|
The KP200 is reported as fully working in home assistant 0.101. Can you guys check whether yours are working? |
It is working with the "strip" designation |
Thanks for your input, that's how all multisocket devices work. If you don't mind doing |
There is also a KP400, which looks like an outdoor variation on the KP200. I do not have one to provide any dumps as yet. Perhaps it owuld just need a different label/ID? https://www.kasasmart.com/us/products/smart-plugs/kasa-smart-wifi-outdoor-plug-kp400 |
^^ Issue with KP400 brought me here. It's not being properly discovered in 0.101.x. |
Home Assistant release with the issue: Last working Home Assistant release (if known): Operating environment (Hass.io/Docker/Windows/etc.): Integration: Description of problem: Also will not auto discover tp-link devices, I had to manually add TP-Link and add IP of switches in the Config file. The HS200 working fine and reports as it should, the KP200 is not, only shows it is off. It shows unavailable if I disconnect the power to it, so it kind of talks to HA Problem-relevant Traceback (if applicable):
Additional information: |
My KP200 came to life with the addition of the 400 in HA 101.0 and was discovered and works perfectly. It shows as a separate entity for each socket on the outlet. |
I'm running HA 0.103.5. KP400 does not get discovered:
And auto-discovery is behaving so horribly, I can't reboot my device without losing ALL my TP Link devices. Getting them back is not a simple task: it takes multiple (a dozen) reboots to finally rediscovery. It's so bad, I dread every moment I have to reboot after they (finally) get discovered. (I suspect this exception is breaking auto-discovery) |
Same issuse, same release, same error. Seems like there was an API change we need to fix. |
it appears yours a fluke |
Actually if you search the forum there are several others who are working just like mine is even though not officially supported, yet... call it what you may it's not the only one working sorry yours isn't. With your TP-Link auto integration not working I would say you have other issues preventing it. Mine shows up like this, I edited entity names... |
I wouldn't say that. My KP200 is working just fine. My KP400, however, is not. |
I found this thread yesterday because my KP400 suddenly stopped working (the log showed the same traceback listed above). I had tried removing the integration and re-adding it, and the error prevented re-adding the integration. What didn't make sense to me was that the KP400 and other kasa devices had worked perfectly until yesterday. This morning I decided to try to re-add the integration, and for some reason everything is working again (including both outlets on the KP400). The firmware hasn't changed (it showed 1.0.10 yesterday and today). I did unplug the KP400 yesterday night because one of the two outlets stopped responding to the Kasa app too. Maybe that made a difference. I can't imagine that the local api changes without a firmware update. But the device could be in an error state. Is it possible that the api is affected by something server side? Also, I know that this is a thread for the KP200 (which I do not have and cannot test) but the mentions of the KP400 made me think I should include my information. Home-assistant: 0.103.5
|
An update on my situation: Kasa was having trouble communicating with my plug. So, I decided to give it a power cycle -- I unplugged/plugged the plug. After a reboot of HA: Connected! Looks like there was a firmware update to the KP400 that probably didn't go according to plan. Try rebooting your outlets / plugs to see if that works. |
rebooted and power down so many time I lost count currently completely wiped out my HA and raspberry pi done a clean metal install auto discovery still does not work move back to v101.1 still nothing doing another clean metal install will manually add the TP link intergration once again not counting on the KP200 to take hold but at least the HS200 works as intended |
I did mean your devices -- i.e. the plugs themselves -- not just HA. You caught that, right? I'm honestly not sure with the lack of periods. I'm sorry if that is what you tried. Everything is running together, I can't figure out what are separate statements or connected sequencing. |
yes everything full blown shut down breaker off to devices no more power to them. the problem was because I had to manually configure them and the instruction to add TPlink is vague on the KP200 and other multi plug devices. it only really showed lights and switches to add to Home assistant. further digging revealed the strip option, once I put the KP200 under that all is well with it. periods installed for your benefit |
@trentjw, feel free to improve the documentation in those parts that were unclear, thanks! @guice do you encounter the problem also when using the discovery from console? To me it looks like that the problem is mostly on homeassistant's side and not in this project? What homeassistant displays is not very helpful, testing is much easier with the |
@rytilahti I had not tested or used the console commands. These errors were from within HA. After rebooting my KP400 device, connectivity started working again. Now I've completely removed KP400 as the Christmas season is now over. ;) My KP200 is functioning, and has been functioning for a bit now. No issues there. |
Then it is a known issue with multiplug devices and homeassistant. Considering that this issue is about adding support for KP200 in pyhs100, I'm closing this issue for now. |
Kasa added a new smart outlet the kp200 - https://www.kasasmart.com/us/products/smart-plugs/kasa-smart-wifi-power-outlet-kp200
It is not being discovered automagically. I am hopeful that it uses the same api as the rest of the smart sockets.
The text was updated successfully, but these errors were encountered: