Issue with ZHA constantly initializing and failing

Yes, the Multiprotocol update in Jan broke something. My zigbee Devices randomly dropout. A restart is required to fix.

2024-02-24 14:37:46.534 ERROR (MainThread) [bellows.uart] Lost serial connection: ConnectionResetError(‘Remote server closed connection’)

2024-02-24 14:37:46.536 ERROR (MainThread) [bellows.ezsp] NCP entered failed state. Requesting APP controller restart

2024-02-24 14:37:46.550 WARNING (MainThread) [homeassistant.helpers.dispatcher] Unable to remove unknown dispatcher <bound method GroupProbe._reprobe_group of <homeassistant.components.zha.core.discovery.GroupProbe object at 0x7f72dd9250>>

I am having this issue too. I just expected it to resolve itself, but a few months on I’m less sure. Have you found a fix?

I’m having the same issue with Sonoff Bridge running Tasmota FW. restarting HA make it work for ~24H but it ultimately fails.

How did you solve the problem? I have a similar issue.

Same issues here :frowning:
Any new informations?

I’m having this exact issue too now. What kind of corner cases are we?

Same issues for the pass months. Seems to crash very 3 or 4 days. Was more often, but I increase the memory on my vm (proxmox). No memory errors going on when the problem is happen (now), so I doubt this is the issue. I never really had a good looks logs, as I usually have to get things working ASAP (whats the expression the wife factor). I’ve been avoiding MQTT (why use it if you don’t need to?) but I might have to use this path.

It seems now, I need to reboot my vm to get zha work, it usually was just enough to restart within HA.

For me the problem went away once I disconnected (physically) 2 devices for which I could so increasing number of open sockets in netstat -an output. May want to start with checking with netstat first.

Aplogies, I don’t understant, what to look for int rhe outut of netstat

Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 0 0 127.0.0.11:33445 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:8099 0.0.0.0:* LISTEN
tcp 0 0 172.30.33.5:8099 172.30.32.2:56766 ESTABLISHED
udp 0 0 127.0.0.11:43476 0.0.0.0:*
Active UNIX domain sockets (servers and established)
Proto RefCnt Flags Type State I-Node Path
unix 2 [ ACC ] STREAM LISTENING 11897 s
unix 3 STREAM CONNECTED 1727971 /tmp/tmux-0/default
unix 3 STREAM CONNECTED 1727418
unix 2 [ ACC ] STREAM LISTENING 1666277 /tmp/tmux-0/default

What does this tell me?

In my last failure, I notice an error message when I hovered over the ! (could not find any messages in the log) that said “No usable address”. Searching on this I found

This seems to my problem, I tried this solution, and is working so far, a few hours, so does mean much yet. I still might switch to Z2M, I just picked up an POE zigbee SLZB-06 to start the change over.

apologies, for me the problem was actually another integration (wiz) that had affected ZHA. it looks like you’re facing a different issue.