Zigbee2MQTT restarting continuously

Configuration Zigbee
1

I updated to the latest version and now it doesn’t work. The error that’s continuously printed out is

Starting Zigbee2MQTT without watchdog.
[2025-02-14 19:13:05] info:     z2m: Logging to console, file (filename: log.log)
[2025-02-14 19:13:05] debug:    z2m: Loaded state from file /config/state.json
[2025-02-14 19:13:05] info:     z2m: Starting Zigbee2MQTT version 2.1.1 (commit #unknown)
[2025-02-14 19:13:05] debug:    z2m: sd-notify loaded
[2025-02-14 19:13:05] info:     z2m: Starting zigbee-herdsman (3.2.5)
[2025-02-14 19:13:05] debug:    z2m: Using zigbee-herdsman with settings: '"{\"network\":{\"panID\":6754,\"extendedPanID\":[221,221,221,221,221,221,221,221],\"channelList\":[11],\"networkKey\":\"HIDDEN\"},\"databasePath\":\"/config/database.db\",\"databaseBackupPath\":\"/config/database.db.backup\",\"backupPath\":\"/config/coordinator_backup.json\",\"serialPort\":{\"path\":\"/dev/ttyUSB0\",\"adapter\":\"zstack\"},\"adapter\":{\"disableLED\":false}}"'
[2025-02-14 19:13:05] debug:    zh:adapter:discovery: Error while trying to match USB adapter (spawn udevadm ENOENT).
[2025-02-14 19:13:05] debug:    zh:controller: Starting with options '{"network":{"networkKeyDistribute":false,"networkKey":"HIDDEN","panID":6754,"extendedPanID":[221,221,221,221,221,221,221,221],"channelList":[11]},"serialPort":{"path":"/dev/ttyUSB0","adapter":"zstack"},"adapter":{"disableLED":false},"databasePath":"/config/database.db","databaseBackupPath":"/config/database.db.backup","backupPath":"/config/coordinator_backup.json"}'
[2025-02-14 19:13:05] info:     zh:zstack:znp: Opening SerialPort with {"path":"/dev/ttyUSB0","baudRate":115200,"rtscts":false,"autoOpen":false}
Starting Zigbee2MQTT without watchdog.

I’ve tried rolling back to a previous version of Zigbee2MQTT but the same error is being produced. I’ve tried to reflash the firmware on my ZigStar v4 (ZigStar Stick v4 - ZigStar) and still no luck.

Additional information this is running on my unraid server with the docker command

docker run
  -d
  --name='zigbee2mqtt'
  --net='bridge'
  --privileged=true
  -e TZ="America/Los_Angeles"
  -e HOST_OS="Unraid"
  -e HOST_HOSTNAME="[HIDDEN]"
  -e HOST_CONTAINERNAME="zigbee2mqtt"
  -e 'PUID'='99'
  -e 'PGID'='100'
  -e 'UMASK'='022'
  -l net.unraid.docker.managed=dockerman
  -l net.unraid.docker.webui='http://[IP]:[PORT:9442]'
  -l net.unraid.docker.icon='https://raw.githubusercontent.com/imagegenius/templates/main/unraid/img/zigbee2mqtt.png'
  -p '9442:9442/tcp'
  -v '/mnt/user/appdata/zigbee2mqtt':'/config':'rw'
  --device='/dev/serial/by-id/usb-1a86_USB_Serial-if00-port0' 'ghcr.io/imagegenius/zigbee2mqtt'

Z2M Config:

version: 4
frontend:
  enabled: true
  port: 9442
homeassistant:
  enabled: true
mqtt: [HIDDEN]
serial:
  # Could be either USB port (/dev/ttyUSB0), network Zigbee adapters (tcp://192.168.1.1:6638) or mDNS adapter (mdns://my-adapter).
  port: /dev/ttyUSB0
  adapter: zstack
  disableLED: false
advanced:
  log_level: debug
device_options: {}
2

Share your z2m config. Redact the network key.

1 Like
4

Darn, it looks like no one has seen this issue before. I’m going to order a new adapter. Maybe the community will find a solution to this issue, and I’ll have a backup available next time something like this happens.

5

I haven’t looked into migrating to a new adapter, especially a POE one. Does anyone know if you can copy the config from one to another and get the devices all connected without having to re-pair everything?

6

I’ve updated to the latest Z2M

and now the log messages are:


[2025-02-17 07:27:37] debug:    zh:adapter:discovery: Error while trying to match USB adapter (spawn udevadm ENOENT).
[2025-02-17 07:27:37] debug:    zh:controller: Starting with options '{"network":{"networkKeyDistribute":false,"networkKey":"HIDDEN","panID":6754,"extendedPanID":[221,221,221,221,221,221,221,221],"channelList":[11]},"serialPort":{"path":"/dev/ttyUSB0","adapter":"zstack"},"adapter":{"disableLED":false},"databasePath":"/config/database.db","databaseBackupPath":"/config/database.db.backup","backupPath":"/config/coordinator_backup.json"}'
[2025-02-17 07:27:37] info:     zh:zstack:znp: Opening SerialPort with {"path":"/dev/ttyUSB0","baudRate":115200,"rtscts":false,"autoOpen":false}
Starting Zigbee2MQTT without watchdog.
[2025-02-17 07:27:40] debug:    z2m: Removing old log directory '/config/log/2025-02-17.07-26-57'
[2025-02-17 07:27:40] info:     z2m: Logging to console, file (filename: log.log)
[2025-02-17 07:27:40] debug:    z2m: Loaded state from file /config/state.json
[2025-02-17 07:27:40] info:     z2m: Starting Zigbee2MQTT version 2.1.1 (commit #unknown)
[2025-02-17 07:27:40] debug:    z2m: sd-notify loaded
[2025-02-17 07:27:40] info:     z2m: Starting zigbee-herdsman (3.2.5)
[2025-02-17 07:27:40] debug:    z2m: Using zigbee-herdsman with settings: '"{\"network\":{\"panID\":6754,\"extendedPanID\":[221,221,221,221,221,221,221,221],\"channelList\":[11],\"networkKey\":\"HIDDEN\"},\"databasePath\":\"/config/database.db\",\"databaseBackupPath\":\"/config/database.db.backup\",\"backupPath\":\"/config/coordinator_backup.json\",\"serialPort\":{\"path\":\"/dev/ttyUSB0\",\"adapter\":\"zstack\"},\"adapter\":{\"disableLED\":false}}"'

Thankfully, I’m getting an error now with the debug logging turned on, but I haven’t found a solution yet.