Z2m Stops On Coordinator Disconnect

Configuration Zigbee
1

Just got a UZG-01 network coordinator and started playing with the z2m addon connecting to the UZG over WiFi. Something unexpected is that the addon stops if it loses connection to the coordinator and will refuse to start manually unless it can talk to the coordinator again. Is this by design? That’d be a rather unreliable way to handle disconnects.

info  2024-04-26 00:02:27: MQTT publish: topic 'zigbee2mqtt/bridge/state', payload '{"state":"online"}'
info  2024-04-26 00:02:27: Zigbee2MQTT started!
error 2024-04-26 14:54:46: Adapter disconnected, stopping
info  2024-04-26 14:54:46: MQTT publish: topic 'zigbee2mqtt/bridge/state', payload '{"state":"offline"}'
info  2024-04-26 14:54:46: Disconnecting from MQTT server
info  2024-04-26 14:54:46: Stopping zigbee-herdsman...
2

What do you want Zigbee2MQTT to do without coordinator ?

1 Like
3

But instead of completely stopping it should simply check at intervals whether the connection was reestablished. Completely stopping is a denial of service on the user because you then have to start it manually.

4

If you did a linux bare metal install,

the service is written to restart Zigbee2MQTT.

Maybe the add-on relies on the Supervisor watchdog to restart ? (I don’t use the add-on myself)

5

That could be a workaround, but I’m using HAOS.

The watchdog tries to restart it a few times and quits. Found this issue on this, but it has had no traction: