What needs to be tested here?
I have an alarm… but I don’t know how to test this PR to give feedback… 
For information, there is a double discussion regarding this PR, I am adding the link to the other discussion:
Good evening
My turn to post a Zigbee problem.
I had installed the Sonoff key and the Zigbee mqtt2 integration worked fine the first time. I installed a Sonoff click button without any problem. Today I changed my box (now RedSfR) and when I reinstalled Gadys, I noticed this, no link between zigbee and Mqtt:
I no longer have access to the association switch (it is frozen) and I no longer have access to the « IPGladys:8080 » address (maybe that’s normal 
). I checked the Sonoff key and I have the following message:
.
I checked that all services were launched on Putty:
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
eclipse-mosquitto:2 "/docker-entrypoint.…" 5 days ago Up 6 hours eclipse-mosquitto
eclipse-mosquitto:2 "/docker-entrypoint.…" 5 days ago Up 3 minutes gladys-z2m-mqtt
gladysassistant/gladys:v4 "docker-entrypoint.s…" 6 days ago Up 6 hours gladys
koenkk/zigbee2mqtt:latest "docker-entrypoint.s…" 12 days ago Up 24 seconds gladys-z2m-zigbee2mqtt
nodered/node-red:latest "npm --no-update-not…" 3 weeks ago Up 6 hours (healthy) node_red
containrrr/watchtower:latest "/watchtower --clean…" 7 weeks ago Up 6 hours 8080/tcp watchtower
Does anyone have any ideas to help me out?
Thanks to you
It seems that the container reboots every 20 seconds or so
koenkk/zigbee2mqtt:latest "docker-entrypoint.s…" 12 days ago Up 18 seconds gladys-z2m-zigbee2mqtt
koenkk/zigbee2mqtt:latest "docker-entrypoint.s…" 12 days ago Up 18 seconds gladys-z2m-zigbee2mqtt
koenkk/zigbee2mqtt:latest "docker-entrypoint.s…" 12 days ago Up 1 second gladys-z2m-zigbee2mqtt````@Psoy: z2m-zigbee2mqtt runs on port 8080, can you change gladys to 8090 and let me know if it’s okay?
Hello ProtZ,
how can I do that?
thanks
For me there’s no connection with the Gladys port or Zigbee2MQTT
Gladys is on port 80 and the Zigbee2MQTT management interface on port 8080.
What could help is the logs of the Zigbee2MQTT container, at least we’ll see why it restarts.
Bonjour VonOx
voici les logs
Using ‘/app/data’ as data directory
Zigbee2MQTT:info 2022-03-15 09:17:19: Logging to console and directory: ‘/app/data/log/2022-03-15.09-17-15’ filename: log.txt
Zigbee2MQTT:info 2022-03-15 09:17:19: Starting Zigbee2MQTT version 1.24.0 (commit #7a2ddf2)
Zigbee2MQTT:info 2022-03-15 09:17:19: Starting zigbee-herdsman (0.14.20)
Zigbee2MQTT:error 2022-03-15 09:17:40: Error while starting zigbee-herdsman
Zigbee2MQTT:error 2022-03-15 09:17:40: Failed to start zigbee
Zigbee2MQTT:error 2022-03-15 09:17:40: Check Zigbee2MQTT fails to start | Zigbee2MQTT for possible solutions
Zigbee2MQTT:error 2022-03-15 09:17:40: Exiting…
Zigbee2MQTT:error 2022-03-15 09:17:40: 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)
Using ‘/app/data’ as data directory
Maybe you changed the USB port to which you connected your dongle?
Hello Guim31,
No, I didn’t change it, and when I refresh the port list, the Sonoff dongle does appear. I will double-check that.
You have exactly the same issue as @Tlse-vins who also recently reinstalled:
Regression on the Zigbee2MQTT side?
While discussing with @jparbel, he noticed that the Sonoff dongle did not work as well as another one (brand unknown at the moment, still being researched).
Everything might be connected!!!
I see similar errors on the Github Zigbee2mqtt side:
After several tweaks, I finally restarted the Zigbee. The one that worked.
- I slid the « Zigbee2mqtt service activation » switch to Off.
Then in Putty - I stopped all services:
docker stop $(docker ps -a -q) - I deleted the two containers concerned:
docker rm gladys-z2m-zigbee2mqttand
docker rm gladys-z2m-mqtt. - I restarted all the containers:
docker start $(docker ps -a -q)
and I reinstalled Zigbee2mqtt, just like the first time, and everything started again
Sonoff click connection attempt
I was too happy, but I have a problem with the Sonoff click button, I installed it correctly, it appears in the logs, in the dashboard as well, but it does not transmit any values
For as long as I’ve struggled, I must have been one of the first to report this bug.
I thought I had broken everything again!!
This is the feeling I sometimes have, after tinkering without really understanding what I’m doing.
This is the case for my Sonoff sensor, everything was working before, and now no sound, no image 
I don’t know if Gladys is being capricious 
or if zigbee2mqtt is acting up, but today my Sonoff sensor started acting up 
and I also paired two Xiaomi click buttons. Today was a day with 
By the way, I think we’ve already talked about this, but I confirm that the same Xiaomi click button is not handled the same way when paired with zigbee2mqtt or with the Xiaomi or Node Red integration in the first case:
1 click = 1
2 clicks = 2
long press = 5
release = release
In the following cases:
1 click = 1
2 clicks = 2
long press = 3
release = 4
Good evening to everyone
Hummm.
Indeed, for the buttons, we’re still in a blur…
Otherwise, do we have other feedback regarding the integration of alarms or others?
Good evening,
I can confirm this to you, I have switched my 4 Xiaomi switches from the Xiaomi integration (and I also used it with Node RED) to the zigbee2mqtt integration