I am on 2023.12.04 and ZHA. While I have had my share of ZB issues over the past few months, this build seems to be fine at the moment. I have often considered switching from ZHA to Z2M, but I have a lot of devices and resetting them all to work with Z2M just isn’t going to happen unless things really get disastrous. It would take a few days to do even if everything goes smoothly, which I am certain it won’t. Besides, I just spent about a week moving all my temp/humidity sensors from MQTT to ESPHome. Ugh! I am not a fan of MQTT. While it’s useful, it can be a royal PITA sometimes, just like ZHA.
With that said, Z2M does seem to have better support and faster fixes/updates than ZHA.
My system can’t start Zigbee ZHA either. I downgraded, but it seemed to re-auto-apply, so broke again. I’ve now disabled the Update function on the Zigbee controller.
Seems my update disablement didn’t work. An update installed yesterday, and again it’s failing. Found this error in the log:
Logger: homeassistant.helpers.dispatcher
Source: helpers/dispatcher.py:59
First occurred: January 14, 2024 at 9:12:50 AM (184 occurrences)
Last logged: January 15, 2024 at 1:16:32 PM
Unable to remove unknown dispatcher <bound method GroupProbe._reprobe_group of <homeassistant.components.zha.core.discovery.GroupProbe object at 0xffff6513bd10>>
I’ve been reverting to this as a fix: addon_core_silabs_multiprotocol_2.3.2
Sorry, just another update. To be clear, it seems that my failure for ZHA is due to the silicon labs multiprotocol add-on. There is a known bug, which I found chatter about over here, just FYI. I’ve now gone in and skipped the current update. fingers crossed!
Faced the same issue as the OP and kept getting a ton of errors in the logs after the update in mid December 2023. ZHA would initialize but there was a tremendous lag between action and response. e,g, if i turn on a switch its would respond after like 2 mins. Even reinstalled the entire OS to eliminate issue with any add-ons but the issue started again. Reverted back to the last backup I had - 2023.12.1 and it is not flooding the logs with errors and everything functions correctly.
Hope there is a fix soon.
Also, wonder how to test any new updates as it just is a cumbersome process going back to the working version (incase the new update does not have the issues resolved) as I have to re-add all the switches.
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.
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.
