There does not seem to be any pattern to when it goes into the unavailable state which can last from 2 to 10 minutes. WiFi Signal is excellent as it’s only a few metres from the AP.
Ideas appreciated.
EDIT: Purchased another new P110 and also becoming unavailable at random times.
Setup a python script to ping the latest two P110’s at 30 secs intervals an both are failing pings at different and sometimes the same time of day.
2025-01-23 18:30:09.027 ERROR (MainThread) [custom_components.tapo.coordinators] Error fetching tapo data: Unexpected exception:
2025-01-23 18:32:20.893 ERROR (MainThread) [custom_components.tapo.coordinators] Error fetching tapo data: Unexpected exception:
2025-01-23 18:32:22.027 ERROR (MainThread) [custom_components.tapo.coordinators] Error fetching tapo data: Unexpected exception:
2025-01-23 18:32:28.878 ERROR (MainThread) [custom_components.tapo.coordinators] Error fetching tapo data: Unexpected exception:
2025-01-23 18:32:37.196 ERROR (MainThread) [homeassistant.components.ipp.coordinator] Error fetching ipp data: Invalid response from API: Timeout occurred while connecting to IPP server.
2025-01-23 18:32:53.278 ERROR (MainThread) [homeassistant.components.brother.coordinator] Timeout fetching brother data
2025-01-23 18:35:50.892 ERROR (MainThread) [custom_components.tapo.coordinators] Error fetching tapo data: Unexpected exception:
2025-01-23 18:35:52.027 ERROR (MainThread) [custom_components.tapo.coordinators] Error fetching tapo data: Unexpected exception:
2025-01-23 18:35:53.195 ERROR (MainThread) [homeassistant.components.ipp.coordinator] Error fetching ipp data: Invalid response from API: Timeout occurred while connecting to IPP server.
2025-01-23 18:35:58.879 ERROR (MainThread) [custom_components.tapo.coordinators] Error fetching tapo data: Unexpected exception:
I’m having a similar issue here. I’ve added some more tapo plugs to monitor energy usage. All of a sudden all of them (old an new) are not showing up in the energy dashboard anymore.
I’m having the same issue. I have 17 Tapo devices switches, lights and cameras. I get HAOS up and running on a Pi 4 and since then a switch goes unavailable at least once a week.
A light has only done this once I think.
My camera often goes into privacy mode.
Right now I can’t afford for some switches to go offline so I am moving them back to the tapo app.
I think this happens because HAOS polls the devices very frequently to reflect any changes in state made by other systems.
I wrote a node-red flow to control Tapo switches but only polled the each switch once a minute for a change in state. Any changes made within node-red were reflected immediately in the NR display. This is much like the HA system.
I would like to be able to control the polling rate which would reduce system load and possible conflicts with Tapo polling.
If anybody has solved this another way let me know.
I came to the solution that this was “normal” for the Tapo Switches. They would go unavailable and not only screw up my automations but fill up the HA Logs.
My taop plugs are working again. I did a reset on every plug and re-added them into the tapo app. While doing this, the app promts that the added plug is already present and asks, if the settings already set should be carried over - Yes.
All i did in HA is reload every plug inside the integration. After that, some plugs required a new login. After that, everything started working again. The power readings right after re-login where garbage (ver high, negative values) but today everything works as it should.
My TAPO plugs became unavailable after a recent firmware update. I found the solution for me was to open the TAPO app (on the phone), and enable Third-Party Compatibility, I wasn’t aware of this setting before, but it was off, turning on brought my devices back on in HA.