#All ZHA devices become unavailable

1 messages Β· Page 1 of 1 (latest)

finite plaza
#

This happens frequently, maybe once a day. Everything works, then at some point (I usually notice it in the morning) they all stop responding.

I use an SMLIGHT SLZB-06 coordinator if that's relevant.

I'm looking for help on how to troubleshoot.

#

The only relevant logs I found are below but I suspect they are just a symptom of something else happening at the coordinator or network level.

2025-11-30 11:39:31.701 DEBUG (MainThread) [homeassistant.components.zha] Failed to set up ZHA
Traceback (most recent call last):
  File "/usr/local/lib/python3.13/site-packages/zigpy_znp/api.py", line 701, in _skip_bootloader
    result = await responses.get()
             ^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.13/asyncio/queues.py", line 186, in get
    await getter
asyncio.exceptions.CancelledError

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/zha/__init__.py", line 185, in async_setup_entry
    await zha_gateway.async_initialize()
  File "/usr/local/lib/python3.13/site-packages/zha/application/gateway.py", line 274, in async_initialize
    await self._async_initialize()
  File "/usr/local/lib/python3.13/site-packages/zha/application/gateway.py", line 257, in _async_initialize
    await self.application_controller.startup(auto_form=True)
  File "/usr/local/lib/python3.13/site-packages/zigpy/application.py", line 236, in startup
    await self.connect()
  File "/usr/local/lib/python3.13/site-packages/zigpy_znp/zigbee/application.py", line 73, in connect
    await znp.connect()
  File "/usr/local/lib/python3.13/site-packages/zigpy_znp/api.py", line 744, in connect
    self.capabilities = (await self._skip_bootloader()).Capabilities
                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.13/site-packages/zigpy_znp/api.py", line 700, in _skip_bootloader
    async with asyncio_timeout(CONNECT_PROBE_TIMEOUT):
               ~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.13/asyncio/timeouts.py", line 116, in __aexit__
    raise TimeoutError from exc_val
TimeoutError
#

If I attempt to reconfigure the network using the cog icon, it says it can't connect to the coordinator.

#

The coordinator is listening on that socket.

#

I can access the coordinator's web UI and it shows ZHA greyed out (disconnected).

thorn raven
#

sounds like a network or interference issue. How did you connect the slzb06? show network info and dashboard info pls.

#

have you done a reboot yet?

#

connected with lan, ok

#

no need to grey out local ip addresses πŸ˜‰

finite plaza
#

Yeah abundance of caution really.

#

It's connected via ethernet to the main switch.

#

It looks like it happened just past 4AM which coincides with a reboot of my router.

#

After rebooting the SLZB-06, everything comes back online.

thorn raven
#

what causes the router to reboot? anything in router logs?

deft terrace
#

I have the same issue (connection to my zigbee devices gets regularly lost), but I found no connection to the router. Unfortunately, I can't give further help, but I follow just in case we could try something on two different systems.

finite plaza
#

In any case, I always expect networked systems to recover from networking partitions. Resilience needs to be built in.

#

Another data point, this is likely not related to ZHA. I used to run Z2M and the same thing would happen - in fact, I migrated to ZHA as a blind attempt to fix it.

thorn raven
#

maybe set your slzb-06 static to same ip as given by router (check router). Use your local dns server 192.168.48.1 for dns1 and dns2

finite plaza
finite plaza
#

A couple developments since last time.

I moved the device to the same VLAN as Home Assistant (it was in the IoT VLAN) while troubleshooting - this suddenly allowed OTA firmware updates to work.

Despite the seeming improvement, the problem still happened this morning, entirely unrelated to a router reboot so that can be crossed off. I made the IP assignment static, put the same local DNS server as both resolvers which rebooted the unit. ZHA is still unresponsive. I restarted the integration, still no luck. I'll restart Home Assistant now.

#

Before that I checked logs - absolutely no logs related to Zigbee or ZHA.

thorn raven
#

instead of restarting ha, do a reboot.. πŸ˜‰

finite plaza
#

Still off after restarting, so rebooting now.

#

Still off after rebooting. I'll reboot the SLZB again.

#

Restarting the integration didn't help, reconfiguring the coordinator in ZHA didn't either. πŸ€”

#

It looks like HA is actually unable to connect to the device, which is odd as there are no firewalls in between them and they're on the same network - traffic should literally just cross ports on the switch.

I can connect to it from my workstation across VLANs though. Still investigating that.

#

SLZB shows ZHA connected now, but HA disagrees.

thorn raven
#

can you reload the slzb integration?

finite plaza
#

Reloaded it now. ZHA reloaded automatically after that but still no luck.

finite plaza
#

I put the device back on the IoT VLAN and forced a ZHA migration. That seems to have sorted it for now. I have no idea why, and it may just be a red herring but I need to get back to work. πŸ˜†

#

And now the automatic backup failed. I wonder if it's related. It has been failing intermittently.

#

Error creating backup: Backup failed: [{'type': 'HomeAssistantBackupError', 'message': "Preparing backup of Home Assistant Core failed. Failed to inform HA Core: Unsuccessful websocket message - {'id': 11, 'type': 'result', 'success': False, 'error': {'code': 'pre_backup_actions_failed', 'message': 'Error during pre-backup: '}}.", 'stage': 'home_assistant'}]

finite plaza
#

I'm back with the ZHA/Zigbee outage. Unrelated to backups. πŸ™

finite plaza
#

Restarting HA didn't help. Rebooting didn't help. Rebooting the SLZB didn't help.