HA logs flooded with connection drops for TPLink Kasa HS300

[mikesalz]

The problem

I'm not sure if this is an HA issue or something with the Kasa HS300. I have had it for years and only started experiencing this error in the last few days. But my log is FLOODED with connection issues for this device. It sits only about 10 feet away from my wireless router, so signal should not be an issue. And it does seem to work fine when I try to control it through HA. I'm just getting lots and lots and lots of errors.

What version of Home Assistant Core has the issue?

core-2024.8.3

What was the last working version of Home Assistant Core?

core-2024.8.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

home-assistant_tplink_2024-08-27T16-09-09.303Z.log

Example YAML snippet

No response

Anything in the logs that might be useful for us?

Error fetching 192.168.1.88 data: Unable to connect to the device: 192.168.1.88:9999:
Error fetching 192.168.1.88 data: Unable to connect to the device: 192.168.1.88:9999: [Errno 113] Connect call failed ('192.168.1.88', 9999)
Error fetching 192.168.1.88 data: Unable to query the device 192.168.1.88:9999:

Additional information

No response

[home-assistant[bot]]

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 close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign tplink` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove 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)}}

[bdraco]

@mikesalz thats a phishing attempt. Don’t download that

[DevSecNinja]

EDIT: Never mind, this fixed my issue: https://community.ui.com/questions/Anybody-seeing-weird-network-behaviors-from-TP-Link-Kasa-smart-plugs/106abe9e-25e3-4925-a4c2-200320d8d66e#answer/fe388934-c647-4563-b187-a2c3844be632

I have the same issue and the entities in the integration often go offline. I wonder if it's a Home Assistant problem or Kasa problem.

2024-09-28 13:06:43.179 ERROR (MainThread) [homeassistant.components.tplink.coordinator] Error fetching 192.168.**.** data: Unable to query the device 192.168.**.**:9999: 
2024-09-28 13:07:33.073 ERROR (MainThread) [homeassistant.components.tplink.coordinator] Error fetching 192.168.**.** data: Unable to connect to the device: 192.168.**.**:9999: 

Was seen in #93312 as well and didn't get fixed as mentioned in the issue. The sensors show "unavailable" every 10 seconds or so and take quite some time to recover again so the history data isn't reliable. I have unplugged the device and removed it from the integration. Took me a few times to get it re-added to Home Assistant but it didn't fix the issue unfortunately.

HS110(EU)
by TP-Link
Firmware: 1.5.6 Build 191125 Rel.083657
Hardware: 2.0

[sdb9696]

@mikesalz are you still having this issue with the latest version of HA?

[DevSecNinja]

I thought my issue was fixed but it still disconnects a lot.

[mikesalz]

@mikesalz are you still having this issue with the latest version of HA?

My issue ended up having nothing to do with HA. I did a factory reset on my HS300 and it has been fine ever since.

But having said that, I do have random connection drops throughout the day across all of my Kasa devices. That's been happening for years.

[DevSecNinja]

@mikesalz are you still having this issue with the latest version of HA?

My issue ended up having nothing to do with HA. I did a factory reset on my HS300 and it has been fine ever since.

But having said that, I do have random connection drops throughout the day across all of my Kasa devices. That's been happening for years.

Similar for me. Have had these connection drops for years and have adopted retry logic in my automations to cope with it. Thought it was just the device being unstable. Now that I have a few Shelly devices too I can see that one being much more stable.

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.