I’m finally getting back into Gladys following the acquisition of a Beelink and a new Zigbee2MQTT dongle so I can use my Pi and the old dongle as a Gladys test instance (and finally run the tests requested in old threads ).
So I restored my Gladys backup and everything works correctly except Zigbee2MQTT.
Starting Zigbee2MQTT without watchdog.
[2024-12-30 10:36:59] info: z2m: Logging to console, file (filename: log.log)
[2024-12-30 10:36:59] info: z2m: Starting Zigbee2MQTT version 1.42.0 (commit #861cba6)
[2024-12-30 10:36:59] info: z2m: Starting zigbee-herdsman (2.1.9)
[2024-12-30 10:36:59] warning: zh:ezsp: ‹ ezsp › driver is deprecated and will only remain to provide support for older firmware (pre 7.4.x). Migration to ‹ ember › is recommended. If using Zigbee2MQTT see Improved Ember (EZSP) driver (experimental) · Koenkk/zigbee2mqtt · Discussion #21462 · GitHub
[2024-12-30 10:37:02] error: zh:ezsp:ezsp: Failure to init network
[2024-12-30 10:37:02] error: z2m: Error while starting zigbee-herdsman
[2024-12-30 10:37:02] error: z2m: Failed to start zigbee
[2024-12-30 10:37:02] error: z2m: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start.html for possible solutions
[2024-12-30 10:37:02] error: z2m: Exiting…
[2024-12-30 10:37:02] error: z2m: Error: This open coordinator backup format not for EZSP adapter
at EZSPAdapterBackup.getStoredBackup (/app/node_modules/zigbee-herdsman/src/adapter/ezsp/adapter/backup.ts:97:23)
at Driver.needsToBeRestore (/app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/driver.ts:943:45)
at Driver.startup (/app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/driver.ts:244:40)
at EZSPAdapter.start (/app/node_modules/zigbee-herdsman/src/adapter/ezsp/adapter/ezspAdapter.ts:152:16)
at Controller.start (/app/node_modules/zigbee-herdsman/src/controller/controller.ts:137:29)
at Zigbee.start (/app/lib/zigbee.ts:69:27)
at Controller.start (/app/lib/controller.ts:161:27)
at start (/app/index.js:154:5)
I followed the explanations in this thread because my problem seems similar but that did not solve the issue.
Normally, we shouldn’t have the dongle change problem anymore since August.
So… let’s search!
Over SSH
Let’s see if your dongle is recognized lsusb
Your dongle should appear
If it does
You need to check the existing containers docker ps -a
Then disable Z2M in Gladys
And again docker ps -a
To verify that the container has been removed
gladys@gladys:~$ sudo lsusb
[sudo] password for gladys:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 8087:0026 Intel Corp. AX201 Bluetooth
Bus 001 Device 005: ID 10c4:ea60 Silicon Labs CP210x UART Bridge
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
gladys@gladys:~$ sudo docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
322e416b6fe9 koenkk/zigbee2mqtt:1.42.0 "docker-entrypoint.s…" 21 hours ago Restarting (1) 19 seconds ago gladys-z2m-zigbee2mqtt
b1850fd9370c eclipse-mosquitto:2.0.15 "/docker-entrypoint.…" 21 hours ago Up 21 hours gladys-z2m-mqtt
8621521aba14 nodered/node-red:3.1 "./entrypoint.sh" 21 hours ago Up 21 hours (healthy) 0.0.0.0:1881-\u003e1880/tcp, [::]:1881-\u003e1880/tcp gladys-node-red
e0849fe0dd47 eclipse-mosquitto:2.0.15 "/docker-entrypoint.…" 36 hours ago Up 36 hours eclipse-mosquitto
b251392ecb69 containrrr/watchtower "/watchtower --clean…" 41 hours ago Up 36 hours (healthy) 8080/tcp watchtower
acc31a054b9d gladysassistant/gladys:v4 "docker-entrypoint.s…" 41 hours ago Up 21 hours gladys
gladys@gladys:~$ sudo docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
8621521aba14 nodered/node-red:3.1 "./entrypoint.sh" 21 hours ago Up 21 hours (healthy) 0.0.0.0:1881-\u003e1880/tcp, [::]:1881-\u003e1880/tcp gladys-node-red
e0849fe0dd47 eclipse-mosquitto:2.0.15 "/docker-entrypoint.…" 36 hours ago Up 36 hours eclipse-mosquitto
b251392ecb69 containrrr/watchtower "/watchtower --clean…" 41 hours ago Up 36 hours (healthy) 8080/tcp watchtower
acc31a054b9d gladysassistant/gladys:v4 "docker-entrypoint.s…" 41 hours ago Up 21 hours gladys
I also just realized that my Pi had stayed on 4.46.2 and when I installed the Beelink I went straight to 4.50.2. But I doubt that this has any impact since I’m supposed to have picked up all the intermediate changes…
So, the container is indeed destroyed, the dongle is properly recognized.
The latest version is supposed to correctly propagate the dongle change in the configuration
I wonder if the selected dongle is the right one…
Can you try this command ls -l /dev/serial/by-id to see if the correct port is selected?
And possibly choose another model from the list?
Or plug it into another USB port?
I seem to recall we had a similar case before, but?
No, it is always set to /dev/ttyACM0 and it’s the Docker mapping that links it to the real physical device.
First, there is a warning regarding the use of the ezsp driver. This one is deprecated in favor of the ember driver. This isn’t caused by you and I’ll create a GitHub issue so we can fix that. And it shouldn’t prevent it from working. EmberZNet adapters (Silicon Labs) | Zigbee2MQTT
Your error comes from the fact that the backup you’re restoring was made with a different dongle
Error: This open coordinator backup format not for EZSP adapter
When you change dongles, that requires re-pairing all devices FAQ | Zigbee2MQTT and therefore the backup doesn’t work.
To fix the issue ( you’ll have to re-pair all the devices but there’s no choice), you need to delete the file /var/lib/gladysassistant/zigbee2mqtt/z2m/coordinator_backup.json then restart the Z2M integration (by disabling/enabling it for example)
).
you’ll have to re-pair all the devices but there’s no choice), you need to delete the file