It seem to mess up as soon as any update that requires a soft restart occurs (even just a restart for a YAML update).
It boots back up and the Zigbee2 MQTT is always failed.
Cycle power on the dongle, no better. Cycle power on the rPi, let it fully boot (Zigbee2MQTT won’t start and fails), cycle power on the dongle - now it works.
Just seems more like a problem between HA and the add-on rather than a hardware issue
I just rechecked the process of getting this to work again:
The troubleshooting guide didn’t help and I’ve gone through that a few times now. I feel that is more for situations when this add-on just doesn’t work at all.
No changes to anything.
Developer tools > Restart
Let it fully boot
Zigbee2MQTT not running (set to Start on Boot)
Manually Start Zigbee2MQTT, give it a few minutes
Fails to start
Power cycle the Sonoff dongle
Manually Start Zigbee2MQTT, give it a few minutes
Fails to start
Power cycle the rPi
Zigbee2MQTT started on boot (or tried at least)
Zigbee2MQTT fails
Manually Start Zigbee2MQTT, give it a few minutes
Fails to start
Power cycle the Sonoff dongle
Manually Start Zigbee2MQTT, give it a few minutes
All is well and the UI loads with the devices all present
Not sure if this is helpful, but this pattern is repeatable.
Just not sure where to go from here as I do feel the issue is out of my control
I did try this and I had no success. Since it functioned as-is, I gave up on that venture.
I will give this another shot though and perhaps that’s all it is
I got this too. It is super unstable. Did some update to HA core at 10pm, it had some thing about needing a restart due to config changes in z2m.
After that, it ran until 3am, when it died. Noticed all my stuff not working at 5am. Restart everything multiple times, until w/o any config changes it worked again.
That is not helpful. Upgraded from what version to which version?
FWIW I keep my HA and Z2M religiously up to date (via the Addon for Z2M). I presently have HA 2023.6.1 and Z2M Addon v 1.31.2-1. It is working fine, and highly reliable.
Had the same problem, using a Texas Instruments CC2531 dongle on a Odroid-m1.
The TI CC2531 has a tendency of being stuck (happened to me twice in a year). There’s no magic fix, other than replacing it with a better Zigbee dongle.
Solution: disconnect/reconnect the dongle AND then reboot the whole system (not just HA).
You my friend just solved my problems. I had issues with HA not starting properly after updates and zigbee2mqtt failing for a couple of weeks now and couldn’t figure it out. Turns out for some reason HA decided to add ZHA to my integrations. I’ve been using zigbee2mqtt for years now so I didn’t even consider this to be the issue.
Hi guy’s,
I have had the same issue, but explain me from beginning:
I’m using the adapter from “deCONZ (Dresden Elektronik)” and the integration ZHA.
Now I want to switch to ZigBee2MQTT.
Well, I saved my config, disabled ZHA and installed ZigBee2MQTT and MQTT broker. So far so good.
In the ZigBee2MQTT- configuration I edit in YAML and add:
serial:
port: /dev/ttyACM0
I start the add-on and got the same error as descripte: “Error: SRSP - SYS - getExtAddr after 6000ms”
After reading on Supported Adapters | Zigbee2MQTT
under “deCONZ based (Dresden Elektronik)” I got a very usefull hint for the configuration.
So I put the following code in the yaml- config:
serial:
port: /dev/ttyACM0
adapter: deconz
That’s all. For me it was helpfull to read the specific configuration for the device and try again I guess the configuration can be changed or you must reconfig after an update.
Where possible you should use the /dev/serial/by-id/ path of the stick, instead of /dev/tty* . This is because the /dev/tty* path can change - for example /dev/ttyACM0 may become /dev/ttyACM1 and then later back to /dev/ttyACM0 . The /dev/serial/by-id/ path won’t change.
I guess the configuration can be changed or you must reconfig after an update.