HA crashes/restarts when/after adding new zigbee device (ZHA)

Configuration Zigbee
,
1

Hello everyone,

my HA recently started to crash when I try to add a new zigbee device using ZHA.

Sometimes it happens in the “configuring” stage (after starting interview) and sometimes it happens when it says that the device is ready tu use, I try to rename the device and notice that HA is not responding.

HA usually restarts automatically (after few minutes thanks to a watchdog) but sometimes i need to restart HA manually.

I’m using HA OS on Intel x86 and ZHA with Sonoff Zigbee 3.0 USB Dongle Plus and everything was working great untlill recently. I have no idea wether this can be caused by some of the zigbee devices that I have added or by some of the recent HA updates or something else.

Has anyone experienced this behavior? Could anyone help? Perhaps point me, where to look?

Thanks in advance.

Here is what I found in supervisor log:

2025-03-23 11:35:09.888 ERROR (MainThread) [supervisor.homeassistant.api] Timeout on call http://172.30.32.1:8123/api/core/state.

2025-03-23 11:35:25.878 ERROR (MainThread) [supervisor.homeassistant.api] Timeout on call http://172.30.32.1:8123/api/core/state.

2025-03-23 11:35:25.878 WARNING (MainThread) [supervisor.misc.tasks] Watchdog missed an Home Assistant Core API response.

2025-03-23 11:36:09.903 ERROR (MainThread) [supervisor.homeassistant.api] Timeout on call http://172.30.32.1:8123/api/core/state.

2025-03-23 11:37:09.873 ERROR (MainThread) [supervisor.homeassistant.api] Timeout on call http://172.30.32.1:8123/api/core/state.

2025-03-23 11:37:56.876 ERROR (MainThread) [supervisor.homeassistant.api] Timeout on call http://172.30.32.1:8123/api/core/state.

2025-03-23 11:37:56.877 ERROR (MainThread) [supervisor.misc.tasks] Watchdog missed 2 Home Assistant Core API responses in a row. Restarting Home Assistant Core!

2025-03-23 11:37:56.886 INFO (SyncWorker_4) [supervisor.docker.manager] Restarting homeassistant

2025-03-23 11:38:09.880 ERROR (MainThread) [supervisor.homeassistant.api] Timeout on call http://172.30.32.1:8123/api/core/state.

2025-03-23 11:39:09.904 ERROR (MainThread) [supervisor.homeassistant.api] Timeout on call http://172.30.32.1:8123/api/core/state.

2025-03-23 11:40:09.904 ERROR (MainThread) [supervisor.homeassistant.api] Timeout on call http://172.30.32.1:8123/api/core/state.

2025-03-23 11:41:09.904 ERROR (MainThread) [supervisor.homeassistant.api] Timeout on call http://172.30.32.1:8123/api/core/state.

2025-03-23 11:42:00.129 WARNING (MainThread) [supervisor.homeassistant.websocket] Connection is closed

2025-03-23 11:42:00.131 ERROR (MainThread) [supervisor.homeassistant.api] Error on call http://172.30.32.1:8123/api/core/state: Cannot connect to host 172.30.32.1:8123 ssl:False [Connect call failed ('172.30.32.1', 8123)]

2025-03-23 11:42:00.371 INFO (MainThread) [supervisor.homeassistant.core] Wait until Home Assistant is ready
1 Like
2

I have experienced this twice in the last few days, I had to pull the power to get it running again. Not good :-/

zha and conbee 3

image
image738×368 13.2 KB

3

Same here. After a long power outage here, I have to pair several of my devices again. After every pairing session HA restarts; really annoying.

I’m running Core 2025.3.4 as a ProxMox VM and I’m using a SLZB-06M zigbee coordinator.

4

I prefer to use a separate instance of z2m to avoid crashes when I update to a new HA version.

5

This is ZHA, not Z2M.

6

I think z2m works better than zha

7

sadly I’m facing this issue as well.
VM running on Incus (qemu) on a Dell R730XD running Ubuntu server 24.04.
I spotted nothing of relevance in the logs, but happens when I put ZHA in pairing mode and I refresh the page or back out of it or something similar. It’s like the pair in the original page is still happening and it doesn’t like the fact a second one is launched.

EDIT: I recently moved to this server and changed the radio from SkyConnect to SMLight SLZB-06, in case someone can spot a pattern.
When home assistant restarts ot takes a good 15 minutes for it to come back on its own and a fair few ZigBee devices don’t turn unavailable until I re-pair them. Very inconvenient problem to have.

8

I recently had a zigbee device/entities with _2 appended on everything for reasons I’m not sure of. I couldn’t get rid of it with a normal renaming of the device, so I instead tried to remove it so I could re-add it and name it correctly.

I’m now facing this exact issue. I’ve factory reset my switch a bunch of times, it’s going into pairing mode. It never pairs and eventually HA has often crashed while attempting to pair.

Incredibly frustrating and I’m not seeing much in logs or anywhere why this is happening.

9

Same here…thought it was a coincidence but my virtualbox based instance crashes during config stage of new Zigbee devices.