Good evening,
Same « error ping after »: I just migrated my zigbee2mqtt to Gladys but zigbee2mqtt was not working. By comparing the 2 instances, I noticed that I had an additional volume « /run/udev » → « /run/udev ». By adding it manually in docker, the problem was solved.
OS: Debian 9
An additional volume?
Can you elaborate on what you did and in which directory?
Hello,
Here is an extract from the docker inspect of my zigbee2mqtt:
See zigbee2mqtt documentation:
(Docker | Zigbee2MQTT)
Ps: I have a CONBEE2
ok I understand better.
« For automatic detection of the port and certain adapters like ConBee » according to the documentation.
We don’t have a key detection problem but a connection issue with the ZIgbee2mqtt container that restarts every 30 seconds.
Yes in my case, the ZIgbee2mqtt container also restarted in a loop every 30 seconds.
Hello!
Until now everything was fine with the z2m integration and since tonight, without knowing why, I also have the error…
Has a solution been found?
What kind of key do you have?
That one
From what I’ve read, it is less powerful than the CC2652R ZZH.
But the problem doesn’t come from that.
I still have 2 tests to do with this key but I haven’t had time to do them yet.
I ordered a Sonoff that solved part of the problem because no more reboots of the zigbee2mqtt container, but I can’t pair the devices even after resetting them.
And so 0 solutions? ^^’
I think we need a bit more logs to validate the source of the problem.
Can you give us the logs of the container gladys-z2m-zigbee2mqtt?
Sure thing, same here:
Zigbee2MQTT:info 2022-04-21 21:36:36: MQTT publish: topic 'zigbee2mqtt/Prise 2', payload '{"child_lock":"UNLOCK","current":0,"energy":11.1,"indicator_mode":"off/on","linkquality":131,"power":0,"power_outage_memory":"on","state":"ON","voltage":237}'
Zigbee2MQTT:error 2022-04-21 21:36:37: Adapter disconnected, stopping
Zigbee2MQTT:debug 2022-04-21 21:36:37: Saving state to file /app/data/state.json
Zigbee2MQTT:info 2022-04-21 21:36:37: MQTT publish: topic 'zigbee2mqtt/bridge/state', payload 'offline'
Zigbee2MQTT:info 2022-04-21 21:36:37: Disconnecting from MQTT server
Zigbee2MQTT:info 2022-04-21 21:36:37: Stopping zigbee-herdsman...
Zigbee2MQTT:error 2022-04-21 21:36:37: Failed to stop Zigbee2MQTT
Then I try to start the container again and then I get the error (not every time, sometimes it restarts without issues)
Zigbee2MQTT:error 2022-04-22 05:57:51: Error while starting zigbee-herdsman
Zigbee2MQTT:error 2022-04-22 05:57:51: Failed to start zigbee
Zigbee2MQTT:error 2022-04-22 05:57:51: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start.html for possible solutions
Zigbee2MQTT:error 2022-04-22 05:57:51: Exiting...
Zigbee2MQTT:error 2022-04-22 05:57:51: Error: Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms)
at ZStackAdapter.start (/app/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:102:27)
at Controller.start (/app/node_modules/zigbee-herdsman/src/controller/controller.ts:123:29)
at Zigbee.start (/app/lib/zigbee.ts:58:27)
at Controller.start (/app/lib/controller.ts:100:27)
at start (/app/index.js:101:5)
So when I get the disconnection error I pull the key then restart and voila it’s a mess 
When I look at the doc I have this:
If you are using a CC2530 or CC2531; it is a common issue for this adapter to crash (due to its outdated hardware). Reflashing the firmware should fix the problem. If it happens often consider flashing the source routing firmware or upgrade to a more powerful adapter.
Except that I can’t reflash my key.. I bought it specifically to avoid having to do it…
If I try to follow the logic of the log
Fail to stop, so serial port still in use/occupied
This results in a fail to start.
So I would direct the research on the first error. The rest is a consequence.
In this case, you need to use the warranty. There’s not much we can do about it.
Oh yes, is that the key that is dead for you?
For me, the firmware crashes, so zigbee2mqtt is in a weird state. The key no longer accepts connections, and the only way is to unplug and replug (unless your key has a reset button).
And it has been working since the beginning and from one day to the next without reason boom 
.
I am a bit surprised if it’s the firmware :-/
This means that any brand can implement planned obsolescence on Zigbee dongles ^^’
Hello I just got a Sonoff dongle!
How can I restart the container after this key change?
Because the container is still not working
Zigbee2MQTT:info 2022-04-23 15:14:18: Starting Zigbee2MQTT version 1.25.0 (commit #6f1460e)
Zigbee2MQTT:info 2022-04-23 15:14:18: Starting zigbee-herdsman (0.14.20)
Zigbee2MQTT:debug 2022-04-23 15:14:18: Using zigbee-herdsman with settings: '{"adapter":{"concurrent":null,"delay":null,"disableLED":false},"backupPath":"/app/data/coordinator_backup.json","databaseBackupPath":"/app/data/database.db.backup","databasePath":"/app/data/database.db","network":{"channelList":[11],"extendedPanID":[221,221,221,221,221,221,221,221],"networkKey":"HIDDEN","panID":6754},"serialPort":{"path":"/dev/ttyACM0"}}'
Zigbee2MQTT:error 2022-04-23 15:14:40: Error while starting zigbee-herdsman
Zigbee2MQTT:error 2022-04-23 15:14:40: Failed to start zigbee
Zigbee2MQTT:error 2022-04-23 15:14:40: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start.html for possible solutions
Zigbee2MQTT:error 2022-04-23 15:14:40: Exiting...
Zigbee2MQTT:error 2022-04-23 15:14:41: Error: Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms)
at ZStackAdapter.start (/app/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:102:27)
at Controller.start (/app/node_modules/zigbee-herdsman/src/controller/controller.ts:123:29)
at Zigbee.start (/app/lib/zigbee.ts:58:27)
at Controller.start (/app/lib/controller.ts:100:27)
at start (/app/index.js:101:5)
Have you tried disabling the service directly in Gladys with the button in the integration?
I didn’t need to do it on my side. The connection was made right away. But I still can’t pair my devices because nothing is coming up either in the Zigbee interface.
It’s good what you did but I don’t know why, it didn’t want to know anything I had to delete my z2m container and restart the service on the gladys side now it’s ok 
Have you turned your devices back on?
