My devices are unavailable and reconnecting every few minutes

Configuration
1

Hi all!

I have an issue where my devices are always reconnecting and I don’t know what to do :frowning: I’m not a pro so I don’t know what’s going on or what should I do…

Current config:
Home Assistant Green
Version 2025.2.0

Issue:
I started using HA since last december and I have used different versions since then. Since I know, no matter the version of HA, my sensors and devices are always reconnecting after a few, it could be seconds or minutes. This means that:

  • I can’t handle them because they are not available on those periods.
  • Select inputs I have set are not working because their config is lost at some point (not options are available) and I need to update them all the time.
  • Automations are not working properly as they are affected too.

My devices all of them are displaying the same pattern of reconnecting or being unavailable after a few minutes and due to the different brands and protocols I think should be another thing:

  • Wifi: Shelly plugs, Shelly smoke detectores, Tapo cameras
  • Ethernet: Airzone for HVAC
  • Zigbee: Tuya temperature and Aqara vibration sensors.

This is how the Airzone temperature and the Shelly plug, for instance, look like :

HA
HA1688×579 99.1 KB

I have tried to debug it and this is what I saw:

2025-02-10 11:56:04.256 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-02-10 11:56:04.260 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration alexa_media which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
...
2025-02-10 11:59:56.533 ERROR (MainThread) [homeassistant] Error doing job: Exception in callback _SelectorSocketTransport._call_connection_lost() (None)
Traceback (most recent call last):
  File "/usr/local/lib/python3.13/asyncio/events.py", line 89, in _run
    self._context.run(self._callback, *self._args)
    ~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.13/asyncio/selector_events.py", line 1184, in _call_connection_lost
    super()._call_connection_lost(exc)
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^
  File "/usr/local/lib/python3.13/asyncio/selector_events.py", line 903, in _call_connection_lost
    self._protocol.connection_lost(exc)
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^
  File "/usr/local/lib/python3.13/site-packages/aioairzone/http.py", line 238, in connection_lost
    raise InvalidState("Connection lost")
aioairzone.exceptions.InvalidState: Connection lost
2025-02-10 12:00:02.511 ERROR (MainThread) [homeassistant.components.shelly] Error fetching shellyplug-EBA1D6 data: DeviceConnectionTimeoutError(TimeoutError())

I couldn’t publish the full log but I see no more errors, just those 2 errors of the Airzone and that Shelly plug are in a loop from time to time.

I really appreciate if some of you could help! Thank you for your time in advance!

2

Those devices rely on your local network for communication.

If your network is unstable then the device, or Home Assistant, or both can lose their connection to the network.

The error message clearly indicates that Home Assistant lost connection (via your network) to the device.

aioairzone.exceptions.InvalidState: Connection lost 2025-02-10 12:00:02.511 ERROR (MainThread) [homeassistant.components.shelly] Error fetching shellyplug-EBA1D6 data: DeviceConnectionTimeoutError(TimeoutError())

Tell us about the equipment you are using to create your local network.

1 Like
3

How many wifi clients do you have and what sort of access point(s) are you using?

Most all-in-one router/wifi/internet boxes can only reliably handle about 25 client devices.

4

Forget protocols for now. I think your problem is in your network. Start with the router. Is it a consumer router provided by your ISP?

1 Like
5

Yes, the router is the one provided by my ISP and it’s a Sagecom Fast 5657.

I have around 15 devices connected to my wifi network at the same time. A few more via ethernet.

When I work in my laptop via wifi I never had an issue with the network. However, the Airzone is connected via ethernet as I mentioned and it’s also losing connection… why?

Apart from that, I have 2 sensors connected via zigbee to a SMLight SLZB-06 too. The coordinator is also connected via ethernet.

By the way, I saw tons of errors during the night. The ones mentioned above plus these new too:

2025-02-11 03:50:37.836 WARNING (MainThread) [kasa.protocols.smartcamprotocol] Device 192.168.1.137 received unknown error code: -40102
2025-02-11 03:50:37.919 WARNING (MainThread) [homeassistant.components.tplink.entity] Unable to read data for <DeviceType.Camera at 192.168.1.137 - Tapo_C210_C26E (C210)> sensor.cam_terraza_nivel_de_senal: Error accessing module data getConnectionType in devicemodule (error_code=INTERNAL_UNKNOWN_ERROR)
2025-02-11 03:54:15.501 ERROR (MainThread) [homeassistant.components.shelly] Error fetching shellyplug-EBA1D6 data: DeviceConnectionTimeoutError(TimeoutError())
2025-02-11 03:55:32.579 ERROR (MainThread) [homeassistant.components.shelly] Error fetching shellyplug-EBFF9D data: DeviceConnectionTimeoutError(TimeoutError())
2025-02-11 07:30:02.821 ERROR (MainThread) [homeassistant.components.alexa.state_report] Error when sending ChangeReport for climate.dormitorio to Alexa: THROTTLING_EXCEPTION: Request is throttled.
2025-02-11 07:44:21.486 ERROR (MainThread) [homeassistant.components.airzone.coordinator] Timeout fetching airzone data
6

When I see timeout errors, it usually means a weak WiFi signal.
Look for the client’s RSSI value. You might find it in developers tools → states (filter on rssi), or in your router’s dashboard. Lower is better. -50 is very good, -60 good, -70 not so good, -80 or worse, you’re lucky to get a connection. If your failing devices are worse than -75, I would recommend installing an Access Point closer to the devices.