Constantly have to reload devices manually for them to work after a restart of HA #648
Comments
|
I'm having this issue with all my Tapo devices for a while now, certainly not just with the last version of the integration - multiple duplicate entries listed under all devices, and often going "unavailable". I've had to set up an automation that detects when the device has changed to unavailable and reloads. Also, devices seem to merge within each other. For example, I have a P110 used for my son's heated blanket, and a P100 for his guitar amp. Clicking on "2 devices" then shows the following - note that the devices appear to have become nested, and the integration is listed twice alongside one device. P110, P100, L530 bulbs - all are affected. Integration version 2.12.1 |
|
I have both of these issues too, I love HA, and this Tapo plugin is fantastic, but a couple of usability issues around how the devices look on my system, especially post-reboot means I'm spending a lot of time "managing" this when it should "just work". I don't add devices very often, it's a fairly static system now. Here's how my devices look after a reboot this morning: From the Second post on the multiple devices, I have 5 devices total, but showing as multiple devices against the headers, 2 of them are not working at all and will require further reconfiguration to work properly, this is my Tapo Hub H100 which also controls "Office Sensor" the T315 - IP addresses are fine, so I have turned on Debug Logging to review later. But my reason for posting is to say, that I have both issues raised above, so I'm joining the thread to make sure I get the updates because I've been impressed with all the updates and fixes so far on this, you've solved many issues I've experienced in the last few releases, so looking forward to this stabilising a little more! |
|
@Bodfrey I didn't even think about that workaround. Care to share the automation you did ? |
|
Sure. I also added a notification so I could see how often it had to reload. |
|
@jaward916 I'm the same - it's the only aspect of HA that's needed attention and everything's pretty static in terms of devices. I'm having to delete and add devices back in all the time to resolve problems. All devices have static IPs and the MAC address tracking switched on. I've even made sure that the devices are locked to the closest mesh node on my wifi network to rule out connectivity issues. |
|
+1 |
@Bodfrey Does it happen other than when rebooting HA? |
Yes, it does. It'll be fine for a while, but then will happen a few times an hour. Of course, it could just be a device issue - not ruling that out. |
|
Not sure if same underlying cause but a few of my Tapo bulbs need reinstalling on a regular basis (since 2023.12 I think). Log messages: |
I gave it a go, and I think reloading one plug sometimes screws up another one. |
I did not specify it, but I've been having these issues since at least 2023.10 |
|
I'm having the same two types of issues, but my IP's are not static. Where does the integration store its config? I have added all the devices through the UI, not configuration.xml. |
|
The documentation says "manually change ip address. Now you can change the ip address of a tapo device wihtout removing and re-adding it." is a feature. |
Not the issue I guess, because I have static IPs. I did however enabled the feature to automatically change the device ip based on its mac adress. I should disable it to see if it changes anything. EDIT: After disabling MAC following and a restard, all plugs seem to work fine. @Bodfrey @jaward916 @BettySwallocks do you have dynamic ips and mac following enabled ? |
I have that enabled, too. I've removed the devices and added them back manually, so they don't get grouped again. There was an update of the integration, introducing KLAP protocol from Tapo. Maybe migrating to that messed things up... |
I have removed and readded at the weekend, and it seems more stable, I do have dynamic IPs and Mac Following, but IPs only change if router reboots, if device is powered off and on it gets the same IP 9/10 times. |
|
Same here, for now. |
|
Just ran into this issue as well, not figuring out why a device/bulb would stop responding and I'm seeing most my devices multi-linked many times like others in this thread (I do have EERO router with dynamic IPs and I have also enabled the MAC tracking in HA's Tapo intergration). I am thinking I'll assign each bulb an fixed IP adress via my EERO app then re-add them all to get this fixed I guess or is static addresses not required for a fix as well as turning off MAC tracking? Not sure I fully understand if this has been fixed already and is just a one off removal and re-add to resolve or something else? |
|
Most of the time, if your router is not that busy, even you use DHCP, it will try to assign the same IP address if that is still available for use. For me, I would use DHCP but once the IP is assigned, I will set that as permanent to avoid this kind of issues. How you configure would depend on what router you use. |
|
Please upgrade to 2.13.0 its more stable |
|
I have this regularly with the latest version, the tapo module unfortunately seems very unstable. I have to reload at least once a day. Is there anything I can provide log wise etc. that might help to narrow down what's happening? Thank you for your help! |
|
Like many of you I've had a similar issue and tried a number of fixes (ensuring DNS was mapped to 8.8.8.8 which I read on another post) - none of these worked until I disabled the 'Try to track device dynamic ip using MAC address' as soon as I disabled this all devices came back online. I have a Ubiquiti Dream Machine and all these are on their own IOT VLAN (and were accessible on the app and via pinging) and will now assign them all static IP addresses to see if that helps... |
Version of the integration
2.12.0
Configuration
P115 (x10)
Describe the bug
Sometimes (almost all the time when restarting Home Assistant), my Tapo plugs entities become unavailable. To make them work, I have to "reload" each device on the Tapo integration page manually:
Might be related, almost all plugs have the "TP-Link Tapo" integration listed multiple times:
Debug log
This is the log after a restart. I think my issue has to do with the unique ids errors
The text was updated successfully, but these errors were encountered: