TP-Link devices sporadically unavailable after some time about core

[home-assistant]

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)}}

[OldManOfTheSea69]

I have also started to experience a similar problem. It appears to be associated with the device receiving a different ip address via DHCP. Example below which shows the error containing the old ip address and Tapo showing the new ip address. I’ve tried all of the normal restarts but I don’t really want to delete and re-add all of my Tapo devices and recreate all of the automations etc.

[sdb9696]

@dinan5 what model of plugs are these? Regarding the logs can you enable debug logging for the integration and upload them.

[githubrdonefun]

This is also happening to me. It asks me to authenticate to the cloud service again if I restart. Logging in fixes it temporarily.

[s55ma]

same ...

[Ali229]

Not sure if I have the same issue but I have LB110 bulb that stops being available both on home assistant and Kasa app. I also have two Smart Plugs - no problem with them.

[issue-triage-workflows]

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.

[rytilahti]

@OldManOfTheSea69

I have also started to experience a similar problem. It appears to be associated with the device receiving a different ip address via DHCP. Example below which shows the error containing the old ip address and Tapo showing the new ip address. I’ve tried all of the normal restarts but I don’t really want to delete and re-add all of my Tapo devices and recreate all of the automations etc.

That might be a completely separate issue, but is your homeassistant configured to use both of the networks? If so, the discovery should automatically update the IP address to the config entry. You can manually trigger the discovery by going to the add integration page, start adding a new tplink device, and leaving the host field empty. It will automatically run discovery on all configured network interfaces.

[ronyoung]

I am experiencing my TP-Link devices going up and down like an old man socks every 20-30 seconds. This has been going on for a couple of days for unknown reasons. All I get in the logs are each one of the TP link devices is "unavailable" .
Is there anything that I need to do like uninstall the TP link integration or something else that would stop this sporadic behavior?

[Happyrobot33]

I will concur that I have been having the same issue, sockets will just randomly kick themselves as unavailable. However the interesting part is that they also become unavailable in the kasa app, so it maybe be a TP link issue? unless something with the integration is making it drop that connection to tplink too

[ronyoung]

This afternoon I did a factory reset of my Home Assistant Green and restored from a backup 5 days ago which I perceived was before I tried something that essentially bricked HA.

While HA now runs faster, the TP-Link devices are still randomly becoming unavailable. Unlike Happyrobot33 above, the devices that are currently not working in HA still work with the Kasa app on my phone.

Help!

[andreabafile]

To me this issue is happening almost every time I reboot HA.
The only solution found is to unplug the Tapo devices and replug them. Then they're immediately available again.
It's driving me crazy.
To be clear, on the Tapo app everything is working fine.

[NuGundam]

I have been getting the same issue too, it's been driving me nuts because I have motion sensors tied to a lot of the switches and randomly they fail to turn on or off. Wifi signal is good, factory reset them all at least twice, and moved them to a different AP.