home-assistant
TP-Link Smart Home integration issue in 2024.10.2
The problem
TP-link KL125 and KL135 bulbs intermittent connection and non responsive to commands after update. Restore to 2024.10.1 resolved.
What version of Home Assistant Core has the issue?
core-2024.10.2
What was the last working version of Home Assistant Core?
core-2024.10.1
What type of installation are you running?
Home Assistant OS
Integration causing the issue
TP-Link Smart Home
Link to integration documentation on our website
https://www.home-assistant.io/integrations/tplink
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response
Hey there @rytilahti, @bdraco, @sdb9696, 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!
Code owner commands
Code owners of tplink can trigger bot actions by commenting:
@home-assistant closeCloses the issue.@home-assistant rename Awesome new titleRenames the issue.@home-assistant reopenReopen the issue.@home-assistant unassign tplinkRemoves the current integration label and assignees on the issue, add the integration domain after the command.@home-assistant add-label needs-more-informationAdd a label (needs-more-information, problem in dependency, problem in custom component) to the issue.@home-assistant remove-label needs-more-informationRemove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.
(message by CodeOwnersMention)
tplink documentation tplink source (message by IssueLinks)
![home-assistant[bot] avatar](https://avatars.githubusercontent.com/in/97978?v=4 "Published by a pub.dev verified publisher"){kind=small}
I'm seeing "connection call failed" errors on each device (I'm using Tapo P110 sockets) since upgrading to 2024.10.2 and when removing devices they aren't appearing on local network check
Does downgrading fix it? If so, then we have a regression. Otherwise, it sounds like a networking problem. You could try to see if you can manually control the devices using python-kasa and its kasa tool.
Logbook is constantly flooded with events relating to disconnected TPLink devices. [image: image.png]
Seems to be only a subset of my devices though. I have a TP-Link Omada mesh wireless network. All the devices not communicating below were associated to a single access point. Upon rebooting they migrated to another AP and were showing online. [image: image.png]
Downgrading also resolved the issue previously without bouncing clients to other AP.
On Fri, Oct 11, 2024 at 4:10 PM Teemu R. @.***> wrote:
Do you see any relevant errors in the logs?
— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/128190#issuecomment-2408060511, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKETUJPUSQ4QGKP3QHZNSNTZ3AWFHAVCNFSM6AAAAABPZR2Q7SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMBYGA3DANJRGE . You are receiving this because you authored the thread.Message ID: @.***>
@wrighpat I also use Omada Controller, bounced one of the AP's and the devices all connected again, have then rebooted other AP and devices are happily reporting in HA spread across both AP's. Interesting as no network changes or updates have occurred in 2+ weeks and devices only went offline post 2024.10.2 upgrade with you pointing out that a downgrade to 2024.10.1 also resolves the issue.
I'm seeing the same issues since 2024.10.2 - I'm running TP-Link K-125 bulbs. Turning them on and off in groups is unreliable as is updating color and brightness. For example I have a group of 4 office lights, turning them on sometimes turns on three, sometimes turns on one or two. There is often a delay of four to five seconds between the response of each bulb in the group.
Closing this issue as the OP has resolved what appears to have been network issues. If anyone else on the thread is still experiencing the same or a different issue please open a new issue and include debug logging.
