Closed vinmar1 closed 1 year ago
Hey there @rytilahti, @thegardenmonkey, mind taking a look at this issue as it has been labeled with an integration (tplink
) you are listed as a code owner for? Thanks!
(message by CodeOwnersMention)
tplink documentation tplink source (message by IssueLinks)
Can confirm this is also happening for Power strip KP303. If you turn one outlet on they all turn on.
Sounds like a duplicate of #97487 which should be fixed in the upcoming patch release, see https://github.com/home-assistant/core/pull/97658 for the fix.
Same issue with the EP40. Thanks for the info.
HS107 broke also. Seems to be a generic issue with any Kasa device with multiple controlled outlets.
Please see my earlier comment, this should be fixed already in the upcoming patch release. I think this can be closed now, please reopen if the issue persists with .1 release.
Hey guys thanks for being on top of this! I did a search for kp200 guess I should have looked for tp-link didn't see it was happening to other devices as well.
The problem
Since the upgrade to core-2023.8.0 my Kasa kp-200 only has one working toggle causing both outlets to switch on/off. Both toggles show in the UI as do 1 device with 2 entities. If I toggle the bottom outlet the top outlet follows. The states in the UI also change for both. If I toggle the top outlet it pauses and falls back to the current state. I have also verified everything works properly in the Kasa application and it is not the equipment, I can independently toggle the outlets. I have also deleted the integration and reinstalled with the same outcome.
What version of Home Assistant Core has the issue?
core-2023.8.0
What was the last working version of Home Assistant Core?
all previous versions
What type of installation are you running?
Home Assistant OS
Integration causing the issue
TP-Link Kasa kp-200
Link to integration documentation on our website
https://www.home-assistant.io/integrations/tplink/
Diagnostics information
I can find no data or errors in any logs
Example YAML snippet
No response
Anything in the logs that might be useful for us?
Additional information
No response