# Non communication Zigbee2mqtt

**URL:** <https://community.gladysassistant.com/t/non-communication-zigbee2mqtt/9027>\
**Category:** Configuration\
**Created:** [Août 2, 2024, 2:01 UTC](https://community.gladysassistant.com/t/non-communication-zigbee2mqtt/9027 "2024-08-02T14:01:32Z")\
**Posts on this page:** 18\
**Page:** 1

<div class="post-metadata">

**Author:** ![Xenicle](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/xenicle/32/4893_2.png) [@Xenicle](https://community.gladysassistant.com/u/Xenicle)\
**Post date:** [Août 2, 2024, 2:01 UTC](https://community.gladysassistant.com/t/non-communication-zigbee2mqtt/9027/1 "2024-08-02T14:01:32Z")

</div>

J’ai essayé d’installer un dongle Sonoff Zigbee et d’utiliser le service Zigbee2mqtt mais ce dernier n’a pas l’air de fonctionner :

 ![image](https://gladys-assistant-community.b-cdn.net/uploads/default/original/3X/4/b/4be9581507e3d32524b89c16a598feaed814486c.png)  
La page de configuration [http://192.168.3.2:12000/](http://192.168.3.2:12000/) est indisponible également…

Que puis-je faire ?

---

<div class="post-metadata">

**Author:** ![Xenicle](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/xenicle/32/4893_2.png) [@Xenicle](https://community.gladysassistant.com/u/Xenicle)\
**Post date:** [Août 2, 2024, 2:10 UTC](https://community.gladysassistant.com/t/non-communication-zigbee2mqtt/9027/2 "2024-08-02T14:10:29Z")

</div>

docker logs gladys-z2m-zigbee2mqtt

```auto
[2024-08-02 14:09:01] info: z2m: Logging to console, file (filename: log.log)
[2024-08-02 14:09:01] info: z2m: Starting Zigbee2MQTT version 1.39.1 (commit #e132316)
[2024-08-02 14:09:01] info: z2m: Starting zigbee-herdsman (0.55.3)
[2024-08-02 14:09:03] warning: zh:ezsp: Deprecated driver 'ezsp' currently in use, 'ember' will become the officially supported EmberZNet driver in next release. If using Zigbee2MQTT see https://github.com/Koenkk/zigbee2mqtt/discussions/21462
[2024-08-02 14:09:03] error: zh:ezsp:uart: Error: \u003c-- CRC error: bf7e|bf|ffff
[2024-08-02 14:09:03] error: zh:ezsp:uart: Error while parsing to NpiFrame 'Error: \u003c-- CRC error: bf7e|bf|ffff
    at Frame.checkCRC (/app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/frame.ts:87:19)
    at SerialDriver.onParsed (/app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/uart.ts:167:19)
    at Parser.emit (node:events:517:28)
    at Parser._transform (/app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/parser.ts:50:26)
    at Parser.Transform._write (node:internal/streams/transform:175:8)
    at writeOrBuffer (node:internal/streams/writable:392:12)
    at _write (node:internal/streams/writable:333:10)
    at Parser.Writable.write (node:internal/streams/writable:337:10)
    at SerialPort.ondata (node:internal/streams/readable:809:22)
    at SerialPort.emit (node:events:517:28)'
[2024-08-02 14:09:07] info: z2m: zigbee-herdsman started (resumed)
[2024-08-02 14:09:07] info: z2m: Coordinator firmware version: '{\"meta\":{\"maintrel\":\"3 \",\"majorrel\":\"6\",\"minorrel\":\"10\",\"product\":8,\"revision\":\"6.10.3.0 build 297\"},\"type\":\"EZSP v8\"}'
[2024-08-02 14:09:07] info: z2m: Currently 0 devices are joined:
[2024-08-02 14:09:07] info: z2m: Zigbee: disabling joining new devices.
[2024-08-02 14:09:08] info: z2m: Connecting to MQTT server at mqtt://localhost:1884
[2024-08-02 14:09:08] error: z2m: MQTT error: Connection refused: Not authorized
[2024-08-02 14:09:08] error: z2m: MQTT failed to connect, exiting...
[2024-08-02 14:09:08] info: z2m: Stopping zigbee-herdsman...
[2024-08-02 14:09:09] info: zh:controller: Wrote coordinator backup to '/app/data/coordinator_backup.json'
[2024-08-02 14:09:09] info: z2m: Stopped zigbee-herdsman
Using '/app/data' as data directory
Starting Zigbee2MQTT without watchdog.

```

---

<div class="post-metadata">

**Author:** ![Xenicle](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/xenicle/32/4893_2.png) [@Xenicle](https://community.gladysassistant.com/u/Xenicle)\
**Post date:** [Août 2, 2024, 2:12 UTC](https://community.gladysassistant.com/t/non-communication-zigbee2mqtt/9027/3 "2024-08-02T14:12:44Z")

</div>

docker logs gladys-z2m-mqtt

```auto

1722607922: New connection from ::1:59344 on port 1884.
1722607922: Client gladys-main-instance-816862 disconnected, not authorised.
1722607924: New connection from ::1:59346 on port 1884.
1722607924: Client mqttjs_e19f996c disconnected, not authorised.

```

---

<div class="post-metadata">

**Author:** ![pierre-gilles](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/pierre-gilles/32/5886_2.png) [@pierre-gilles](https://community.gladysassistant.com/u/pierre-gilles)\
**Post date:** [Août 2, 2024, 3:04 UTC](https://community.gladysassistant.com/t/non-communication-zigbee2mqtt/9027/4 "2024-08-02T15:04:06Z")

</div>

@Xenicle Hello !

L’erreur est là :

> [@Xenicle](#):
>
> ` zh:ezsp:uart: Error while parsing to NpiFrame 'Error: <-- CRC error: bf7e|bf|ffff`

En cherchant côté Zigbee2mqtt, je trouve des gens qui ont le même souci :

> <https://github.com/Koenkk/zigbee2mqtt/issues/22267>
>
> \### What happened?
> 
> It starts successfully, but after a while the devices stop… regressing. It was disabled with an error on the regular version:
> "Adapter disconnected, stopping"
> 
> The latest error on the Edge version:
> \[2024-04-19 16:15:15\] debug: zh:ezsp:ezsp: ==\> nop: null
> \[2024-04-19 16:15:25\] debug: zh:ezsp:ezsp: Time to watchdog ... 0
> \[2024-04-19 16:15:25\] debug: zh:ezsp:ezsp: ==\> nop: null
> \[2024-04-19 16:15:35\] debug: zh:ezsp:ezsp: Time to watchdog ... 0
> \[2024-04-19 16:15:35\] debug: zh:ezsp:ezsp: ==\> nop: null
> \[2024-04-19 16:15:46\] debug: zh:ezsp:ezsp: Time to watchdog ... 0
> \[2024-04-19 16:15:47\] debug: zh:ezsp:ezsp: ==\> nop: null
> \[2024-04-19 16:15:56\] debug: zh:ezsp:ezsp: Time to watchdog ... 0
> \[2024-04-19 16:15:56\] debug: zh:ezsp:ezsp: ==\> nop: null
> 
> Config:
> data\_path: /config/zigbee2mqtt
> socat:
> enabled: false
> master: pty,raw,echo=0,link=/tmp/ttyZ2M,mode=777
> slave: tcp-listen:8485,keepalive,nodelay,reuseaddr,keepidle=1,keepintvl=1,keepcnt=5
> options: "-d -d"
> log: false
> mqtt:
> server: mqtt://core-mosquitto:1883
> serial:
> port: \>-
> /dev/serial/by-id/usb-ITEAD\_SONOFF\_Zigbee\_3.0\_USB\_Dongle\_Plus\_V2\_20231215111023-if00
> adapter: ezsp
> 
> \### What did you expect to happen?
> 
> \_No response\_
> 
> \### How to reproduce it (minimal and precise)
> 
> \_No response\_
> 
> \### Zigbee2MQTT version
> 
> 1.36.1-dev commit:
> 
> \### Adapter firmware version
> 
> 6.10.3.0 build 297
> 
> \### Adapter
> 
> SONOFF Zigbee 3.0 USB Dongle Plus V2 (Dongle E)
> 
> \### Setup
> 
> Home Assistant OS 11.4, Home Assistant Core: 2023.12.3, Raspberry Pi 3-64
> 
> \### Debug log
> 
> \_No response\_

> <https://github.com/Koenkk/zigbee2mqtt/issues/22563>
>
> \### What happened?
> 
> The docker crashes and, even after rebooting, it remains i…n error
> 
> \### What did you expect to happen?
> 
> \_No response\_
> 
> \### How to reproduce it (minimal and precise)
> 
> \_No response\_
> 
> \### Zigbee2MQTT version
> 
> 1.37.0
> 
> \### Adapter firmware version
> 
> 6.10.3.0 build 297
> 
> \### Adapter
> 
> ITEAD\_SONOFF\_Zigbee\_3.0\_USB\_Dongle\_Plus\_V2
> 
> \### Setup
> 
> Docker in a Unraid system
> 
> \### Debug log
> 
> Error: zdoRequest\>request error
> at Driver.zdoRequest (/app/node\_modules/zigbee-herdsman/src/adapter/ezsp/driver/driver.ts:724:23)
> at EZSPAdapter.nodeDescriptorInternal (/app/node\_modules/zigbee-herdsman/src/adapter/ezsp/adapter/ezspAdapter.ts:390:28)
> at /app/node\_modules/zigbee-herdsman/src/adapter/ezsp/adapter/ezspAdapter.ts:380:32
> at Queue.execute (/app/node\_modules/zigbee-herdsman/src/utils/queue.ts:35:20)
> at EZSPAdapter.handleDeviceJoin (/app/node\_modules/zigbee-herdsman/src/adapter/ezsp/adapter/ezspAdapter.ts:147:13)
> \[2024-05-09 13:19:38\] error: zh:ezsp:uart: -!- break waiting (4)
> \[2024-05-09 13:19:38\] error: zh:ezsp:uart: Can't send DATA frame (3,6,0): 3b00010500
> \[2024-05-09 13:19:47\] error: zh:ezsp:uart: --\> Error: Error: {"sequence":4} after 4000ms
> \[2024-05-09 13:19:47\] error: zh:ezsp:uart: -!- break rewaiting (4)
> \[2024-05-09 13:19:47\] error: zh:ezsp:uart: Can't resend DATA frame (3,6,1): 3b00010500
> \[2024-05-09 13:19:47\] error: zh:ezsp:ezsp: Watchdog heartbeat timeout Error: Failure send nop:{"type":"Buffer","data":\[59,0,1,5,0\]}
> at /app/node\_modules/zigbee-herdsman/src/adapter/ezsp/driver/ezsp.ts:686:23
> at Queue.execute (/app/node\_modules/zigbee-herdsman/src/utils/queue.ts:35:20)
> at Ezsp.watchdogHandler (/app/node\_modules/zigbee-herdsman/src/adapter/ezsp/driver/ezsp.ts:795:13)
> \[2024-05-09 13:19:55\] error: zh:ezsp:uart: --\> Error: Error: {"sequence":1} after 4000ms
> \[2024-05-09 13:19:55\] error: zh:ezsp:uart: -!- break waiting (1)
> \[2024-05-09 13:19:55\] error: zh:ezsp:uart: Can't send DATA frame (0,1,0): 00000004
> \[2024-05-09 13:19:59\] error: zh:ezsp:uart: --\> Error: Error: {"sequence":1} after 4000ms
> \[2024-05-09 13:19:59\] error: zh:ezsp:uart: -!- break rewaiting (1)
> \[2024-05-09 13:19:59\] error: zh:ezsp:uart: Can't resend DATA frame (0,1,1): 00000004
> \[2024-05-09 13:20:16\] error: zh:ezsp:uart: --\> Error: Error: {"sequence":6} after 4000ms
> \[2024-05-09 13:20:16\] error: zh:ezsp:uart: -!- break waiting (6)
> \[2024-05-09 13:20:16\] error: zh:ezsp:uart: Can't send DATA frame (5,5,0): 250001630003
> \[2024-05-09 13:21:20\] error: zh:ezsp:uart: --\> Error: Error: {"sequence":1} after 4000ms
> \[2024-05-09 13:21:20\] error: zh:ezsp:uart: -!- break waiting (1)
> \[2024-05-09 13:21:20\] error: zh:ezsp:uart: Can't send DATA frame (0,5,0): 3000010500
> \[2024-05-09 13:21:28\] error: zh:ezsp:uart: --\> Error: Error: {"sequence":1} after 4000ms
> \[2024-05-09 13:21:28\] error: zh:ezsp:uart: -!- break rewaiting (1)
> \[2024-05-09 13:21:28\] error: zh:ezsp:uart: Can't resend DATA frame (0,5,1): 3000010500
> \[2024-05-09 13:21:28\] error: zh:ezsp:ezsp: Watchdog heartbeat timeout Error: Failure send nop:{"type":"Buffer","data":\[48,0,1,5,0\]}
> at /app/node\_modules/zigbee-herdsman/src/adapter/ezsp/driver/ezsp.ts:686:23
> at Queue.execute (/app/node\_modules/zigbee-herdsman/src/utils/queue.ts:35:20)
> at Ezsp.watchdogHandler (/app/node\_modules/zigbee-herdsman/src/adapter/ezsp/driver/ezsp.ts:795:13)
> \[2024-05-09 13:21:29\] error: zh:ezsp:uart: \<-- CRC error: 9c148f6d633f9874f0cf638bfc5836a5ebc9de6f8fffc5ed577e|ed57|f562
> \[2024-05-09 13:21:29\] error: zh:ezsp:uart: Error while parsing to NpiFrame 'Error: \<-- CRC error: 9c148f6d633f9874f0cf638bfc5836a5ebc9de6f8fffc5ed577e|ed57|f562
> at Frame.checkCRC (/app/node\_modules/zigbee-herdsman/src/adapter/ezsp/driver/frame.ts:87:19)
> at SerialDriver.onParsed (/app/node\_modules/zigbee-herdsman/src/adapter/ezsp/driver/uart.ts:169:19)
> at Parser.emit (node:events:517:28)
> at Parser.\_transform (/app/node\_modules/zigbee-herdsman/src/adapter/ezsp/driver/parser.ts:49:26)
> at Parser.Transform.\_write (node:internal/streams/transform:175:8)
> at writeOrBuffer (node:internal/streams/writable:392:12)
> at \_write (node:internal/streams/writable:333:10)
> at Parser.Writable.write (node:internal/streams/writable:337:10)
> at SerialPort.ondata (node:internal/streams/readable:809:22)
> at SerialPort.emit (node:events:517:28)'
> \[2024-05-09 13:21:29\] error: zh:ezsp:uart: \<-- CRC error: f0cf638bfc5836a5ebc9de6f8fffc55e577e|5e57|489f
> \[2024-05-09 13:21:29\] error: zh:ezsp:uart: Error while parsing to NpiFrame 'Error: \<-- CRC error: f0cf638bfc5836a5ebc9de6f8fffc55e577e|5e57|489f
> at Frame.checkCRC (/app/node\_modules/zigbee-herdsman/src/adapter/ezsp/driver/frame.ts:87:19)
> at SerialDriver.onParsed (/app/node\_modules/zigbee-herdsman/src/adapter/ezsp/driver/uart.ts:169:19)
> at Parser.emit (node:events:517:28)
> at Parser.\_transform (/app/node\_modules/zigbee-herdsman/src/adapter/ezsp/driver/parser.ts:49:26)
> at Parser.Transform.\_write (node:internal/streams/transform:175:8)
> at writeOrBuffer (node:internal/streams/writable:392:12)
> at \_write (node:internal/streams/writable:333:10)
> at Parser.Writable.write (node:internal/streams/writable:337:10)
> at SerialPort.ondata (node:internal/streams/readable:809:22)
> at SerialPort.emit (node:events:517:28)'
> \[2024-05-09 13:21:36\] error: zh:ezsp:uart: --\> Error: Error: {"sequence":1} after 4000ms
> \[2024-05-09 13:21:36\] error: zh:ezsp:uart: -!- break waiting (1)
> \[2024-05-09 13:21:36\] error: zh:ezsp:uart: Can't send DATA frame (0,3,0): 00000004
> \[2024-05-09 13:21:40\] error: zh:ezsp:uart: --\> Error: Error: {"sequence":1} after 4000ms
> \[2024-05-09 13:21:40\] error: zh:ezsp:uart: -!- break rewaiting (1)
> \[2024-05-09 13:21:40\] error: zh:ezsp:uart: Can't resend DATA frame (0,3,1): 00000004
> \[2024-05-09 13:22:11\] error: zh:ezsp:uart: --\> Error: Error: {"sequence":2} after 4000ms
> \[2024-05-09 13:22:11\] error: zh:ezsp:uart: -!- break waiting (2)
> \[2024-05-09 13:22:11\] error: zh:ezsp:uart: Can't send DATA frame (1,1,0): 290001630005
> \[2024-05-09 13:22:18\] error: zh:ezsp:uart: --\> Error: Error: {"sequence":3} after 4000ms
> \[2024-05-09 13:22:18\] error: zh:ezsp:uart: -!- break waiting (3)
> \[2024-05-09 13:22:18\] error: zh:ezsp:uart: Can't send DATA frame (2,3,0): 2a00010500
> \[2024-05-09 13:22:31\] error: zh:ezsp:uart: --\> Error: Error: {"sequence":4} after 4000ms
> \[2024-05-09 13:22:31\] error: zh:ezsp:uart: -!- break waiting (4)
> \[2024-05-09 13:22:31\] error: zh:ezsp:uart: Can't send DATA frame (3,0,0): 2b0001630006
> \[2024-05-09 13:22:44\] error: zh:ezsp:driv: Request send status 24. Attempt to repeat the request
> \[2024-05-09 13:22:48\] error: zh:ezsp:uart: --\> Error: Error: {"sequence":7} after 4000ms
> \[2024-05-09 13:22:48\] error: zh:ezsp:uart: -!- break waiting (7)
> \[2024-05-09 13:22:48\] error: zh:ezsp:uart: Can't send DATA frame (6,6,0): 2e00010500
> \[2024-05-09 13:22:56\] error: zh:ezsp:uart: --\> Error: Error: {"sequence":7} after 4000ms
> \[2024-05-09 13:22:56\] error: zh:ezsp:uart: -!- break rewaiting (7)
> \[2024-05-09 13:22:56\] error: zh:ezsp:uart: Can't resend DATA frame (6,6,1): 2e00010500
> \[2024-05-09 13:22:56\] error: zh:ezsp:ezsp: Watchdog heartbeat timeout Error: Failure send nop:{"type":"Buffer","data":\[46,0,1,5,0\]}
> at /app/node\_modules/zigbee-herdsman/src/adapter/ezsp/driver/ezsp.ts:686:23
> at Queue.execute (/app/node\_modules/zigbee-herdsman/src/utils/queue.ts:35:20)
> at Ezsp.watchdogHandler (/app/node\_modules/zigbee-herdsman/src/adapter/ezsp/driver/ezsp.ts:795:13)
> \[2024-05-09 13:23:08\] error: zh:ezsp:uart: --\> Error: Error: {"sequence":7} after 4000ms
> \[2024-05-09 13:23:08\] error: zh:ezsp:uart: -!- break waiting (7)
> \[2024-05-09 13:23:08\] error: zh:ezsp:uart: Can't send DATA frame (6,3,0): 1e0001340000000000000200000000010000020303020000
> \[2024-05-09 13:23:16\] error: zh:ezsp:uart: --\> Error: Error: {"sequence":7} after 4000ms
> \[2024-05-09 13:23:16\] error: zh:ezsp:uart: -!- break rewaiting (7)
> \[2024-05-09 13:23:16\] error: zh:ezsp:uart: Can't resend DATA frame (6,3,1): 1e0001340000000000000200000000010000020303020000
> 
> restart docker
> 
> \[2024-05-09 13:30:43\] info: z2m: Logging to console, file (filename: log.log)
> \[2024-05-09 13:30:45\] info: z2m: Starting Zigbee2MQTT version 1.37.0 (commit #46f34c8)
> \[2024-05-09 13:30:45\] info: z2m: Starting zigbee-herdsman (0.45.0)
> \[2024-05-09 13:30:45\] warning: zh:ezsp: Deprecated driver 'ezsp' currently in use, 'ember' will become the officially supported EmberZNet driver in next release. If using Zigbee2MQTT see https://github.com/Koenkk/zigbee2mqtt/discussions/21462
> \[2024-05-09 13:30:45\] error: zh:ezsp:uart: \<-- CRC error: 112a15b65894a524ab5593499ccb8f6d633f9874f0cfc78bfcb436a5ebc9de6f8fffee5b7e|ee5b|f22e
> \[2024-05-09 13:30:45\] error: zh:ezsp:uart: Error while parsing to NpiFrame 'Error: \<-- CRC error: 112a15b65894a524ab5593499ccb8f6d633f9874f0cfc78bfcb436a5ebc9de6f8fffee5b7e|ee5b|f22e
> at Frame.checkCRC (/app/node\_modules/zigbee-herdsman/src/adapter/ezsp/driver/frame.ts:87:19)
> at SerialDriver.onParsed (/app/node\_modules/zigbee-herdsman/src/adapter/ezsp/driver/uart.ts:169:19)
> at Parser.emit (node:events:517:28)
> at Parser.\_transform (/app/node\_modules/zigbee-herdsman/src/adapter/ezsp/driver/parser.ts:49:26)
> at Parser.Transform.\_write (node:internal/streams/transform:175:8)
> at writeOrBuffer (node:internal/streams/writable:392:12)
> at \_write (node:internal/streams/writable:333:10)
> at Parser.Writable.write (node:internal/streams/writable:337:10)
> at SerialPort.ondata (node:internal/streams/readable:809:22)
> at SerialPort.emit (node:events:517:28)'
> \[2024-05-09 13:30:45\] error: zh:ezsp:uart: \<-- CRC error: 478bfc4136a5ebc9de6f8fff5cbf7e|5cbf|6ba9
> \[2024-05-09 13:30:45\] error: zh:ezsp:uart: Error while parsing to NpiFrame 'Error: \<-- CRC error: 478bfc4136a5ebc9de6f8fff5cbf7e|5cbf|6ba9
> at Frame.checkCRC (/app/node\_modules/zigbee-herdsman/src/adapter/ezsp/driver/frame.ts:87:19)
> at SerialDriver.onParsed (/app/node\_modules/zigbee-herdsman/src/adapter/ezsp/driver/uart.ts:169:19)
> at Parser.emit (node:events:517:28)
> at Parser.\_transform (/app/node\_modules/zigbee-herdsman/src/adapter/ezsp/driver/parser.ts:49:26)
> at Parser.Transform.\_write (node:internal/streams/transform:175:8)
> at writeOrBuffer (node:internal/streams/writable:392:12)
> at \_write (node:internal/streams/writable:333:10)
> at Parser.Writable.write (node:internal/streams/writable:337:10)
> at SerialPort.ondata (node:internal/streams/readable:809:22)
> at SerialPort.emit (node:events:517:28)'
> \[2024-05-09 13:30:45\] error: zh:ezsp:uart: \<-- CRC error: 7e5fb1a9629874f0cf478bfc4136a5ebc9de6f8fffc9947e|c994|8b7a
> \[2024-05-09 13:30:45\] error: zh:ezsp:uart: Error while parsing to NpiFrame 'Error: \<-- CRC error: 7e5fb1a9629874f0cf478bfc4136a5ebc9de6f8fffc9947e|c994|8b7a
> at Frame.checkCRC (/app/node\_modules/zigbee-herdsman/src/adapter/ezsp/driver/frame.ts:87:19)
> at SerialDriver.onParsed (/app/node\_modules/zigbee-herdsman/src/adapter/ezsp/driver/uart.ts:169:19)
> at Parser.emit (node:events:517:28)
> at Parser.\_transform (/app/node\_modules/zigbee-herdsman/src/adapter/ezsp/driver/parser.ts:49:26)
> at Parser.Transform.\_write (node:internal/streams/transform:175:8)
> at writeOrBuffer (node:internal/streams/writable:392:12)
> at \_write (node:internal/streams/writable:333:10)
> at Parser.Writable.write (node:internal/streams/writable:337:10)
> at SerialPort.ondata (node:internal/streams/readable:809:22)
> at SerialPort.emit (node:events:517:28)'
> \[2024-05-09 13:30:45\] error: zh:ezsp:uart: \<-- CRC error: 5e5fb1a9112a15b65894a524ab5593499cca8f6d633f9874112a15b65894a524ab5593499ccb8f6d633f9874f0cfc78bfcb436a5ebc9de6f8fffee5b7e|ee5b|f21f
> \[2024-05-09 13:30:45\] error: zh:ezsp:uart: Error while parsing to NpiFrame 'Error: \<-- CRC error: 5e5fb1a9112a15b65894a524ab5593499cca8f6d633f9874112a15b65894a524ab5593499ccb8f6d633f9874f0cfc78bfcb436a5ebc9de6f8fffee5b7e|ee5b|f21f
> at Frame.checkCRC (/app/node\_modules/zigbee-herdsman/src/adapter/ezsp/driver/frame.ts:87:19)
> at SerialDriver.onParsed (/app/node\_modules/zigbee-herdsman/src/adapter/ezsp/driver/uart.ts:169:19)
> at Parser.emit (node:events:517:28)
> at Parser.\_transform (/app/node\_modules/zigbee-herdsman/src/adapter/ezsp/driver/parser.ts:49:26)
> at Parser.Transform.\_write (node:internal/streams/transform:175:8)
> at writeOrBuffer (node:internal/streams/writable:392:12)
> at \_write (node:internal/streams/writable:333:10)
> at Parser.Writable.write (node:internal/streams/writable:337:10)
> at SerialPort.ondata (node:internal/streams/readable:809:22)
> at SerialPort.emit (node:events:517:28)'
> \[2024-05-09 13:30:48\] error: zh:ezsp:ezsp: Frame changeSourceRouteHandler parsing error: RangeError: Attempt to access memory outside buffer bounds
> at new NodeError (node:internal/errors:405:5)
> at boundsError (node:internal/buffer:86:11)
> at Buffer.readUInt16LE (node:internal/buffer:245:5)
> at Buffer.readUIntLE (node:internal/buffer:182:17)
> at Function.deserialize (/app/node\_modules/zigbee-herdsman/src/adapter/ezsp/driver/types/basic.ts:19:67)
> at new EZSPFrameData (/app/node\_modules/zigbee-herdsman/src/adapter/ezsp/driver/ezsp.ts:180:54)
> at /app/node\_modules/zigbee-herdsman/src/adapter/ezsp/driver/ezsp.ts:154:23
> at Array.every (\<anonymous\>)
> at Function.createFrame (/app/node\_modules/zigbee-herdsman/src/adapter/ezsp/driver/ezsp.ts:148:15)
> at Ezsp.onFrameReceived (/app/node\_modules/zigbee-herdsman/src/adapter/ezsp/driver/ezsp.ts:439:35)
> \[2024-05-09 13:30:48\] error: zh:ezsp:ezsp: Unparsed frame 0xc4. Skipped
> \[2024-05-09 13:30:48\] error: zh:ezsp:ezsp: Frame changeSourceRouteHandler parsing error: RangeError: Attempt to access memory outside buffer bounds
> at new NodeError (node:internal/errors:405:5)
> at boundsError (node:internal/buffer:86:11)
> at Buffer.readUInt16LE (node:internal/buffer:245:5)
> at Buffer.readUIntLE (node:internal/buffer:182:17)
> at Function.deserialize (/app/node\_modules/zigbee-herdsman/src/adapter/ezsp/driver/types/basic.ts:19:67)
> at new EZSPFrameData (/app/node\_modules/zigbee-herdsman/src/adapter/ezsp/driver/ezsp.ts:180:54)
> at /app/node\_modules/zigbee-herdsman/src/adapter/ezsp/driver/ezsp.ts:154:23
> at Array.every (\<anonymous\>)
> at Function.createFrame (/app/node\_modules/zigbee-herdsman/src/adapter/ezsp/driver/ezsp.ts:148:15)
> at Ezsp.onFrameReceived (/app/node\_modules/zigbee-herdsman/src/adapter/ezsp/driver/ezsp.ts:439:35)
> \[2024-05-09 13:30:48\] error: zh:ezsp:ezsp: Unparsed frame 0xc4. Skipped
> \[2024-05-09 13:30:49\] error: zh:ezsp:ezsp: Frame changeSourceRouteHandler parsing error: RangeError: Attempt to access memory outside buffer bounds
> at new NodeError (node:internal/errors:405:5)
> at boundsError (node:internal/buffer:86:11)
> at Buffer.readUInt16LE (node:internal/buffer:245:5)
> at Buffer.readUIntLE (node:internal/buffer:182:17)
> at Function.deserialize (/app/node\_modules/zigbee-herdsman/src/adapter/ezsp/driver/types/basic.ts:19:67)
> at new EZSPFrameData (/app/node\_modules/zigbee-herdsman/src/adapter/ezsp/driver/ezsp.ts:180:54)
> at /app/node\_modules/zigbee-herdsman/src/adapter/ezsp/driver/ezsp.ts:154:23
> at Array.every (\<anonymous\>)
> at Function.createFrame (/app/node\_modules/zigbee-herdsman/src/adapter/ezsp/driver/ezsp.ts:148:15)
> at Ezsp.onFrameReceived (/app/node\_modules/zigbee-herdsman/src/adapter/ezsp/driver/ezsp.ts:439:35)
> \[2024-05-09 13:30:49\] error: zh:ezsp:ezsp: Unparsed frame 0xc4. Skipped
> \[2024-05-09 13:30:50\] info: z2m: zigbee-herdsman started (resumed)
> \[2024-05-09 13:30:50\] info: z2m: Coordinator firmware version: '{"meta":{"maintrel":"3 ","majorrel":"6","minorrel":"10","product":8,"revision":"6.10.3.0 build 297"},"type":"EZSP v8"}'
> \[2024-05-09 13:30:50\] info: z2m: Currently 25 devices are joined:
> \[2024-05-09 13:30:50\] info: z2m: porta armadio (0xa4c1388c7195ac2b): TS0203 - TuYa Door sensor (EndDevice)
> \[2024-05-09 13:30:50\] info: z2m: stufa soppalco (0xa4c13892f8925bb9): TS011F\_plug\_1 - TuYa Smart plug (with power monitoring) (Router)
> \[2024-05-09 13:30:50\] info: z2m: luce soppalco (0xa4c138e23472888c): TS0505B\_2\_1 - TuYa Zigbee 3.0 18W led light bulb E27 RGBCW (Router)
> \[2024-05-09 13:30:50\] info: z2m: Luce bagno (0x287681fffeef52e9): LED2103G5 - IKEA TRADFRI bulb E26/E27, warm white, globe, 806 lumen (Router)
> \[2024-05-09 13:30:50\] info: z2m: luce divano (0x287681fffedbcfc3): LED2103G5 - IKEA TRADFRI bulb E26/E27, warm white, globe, 806 lumen (Router)
> \[2024-05-09 13:30:50\] info: z2m: Interruttore 1 (0x705464fffe2cf61d): E1743 - IKEA TRADFRI on/off switch (EndDevice)
> \[2024-05-09 13:30:50\] info: z2m: Interruttore 2 (0x705464fffe2cfd43): E1743 - IKEA TRADFRI on/off switch (EndDevice)
> \[2024-05-09 13:30:50\] info: z2m: luce camera 1 (0x60efabfffef11725): LED1836G9 - IKEA TRADFRI bulb E26/E27, warm white, globe, opal, 806 lm (Router)
> \[2024-05-09 13:30:50\] info: z2m: luce camera 2 (0x60efabfffeeeaf13): LED1836G9 - IKEA TRADFRI bulb E26/E27, warm white, globe, opal, 806 lm (Router)
> \[2024-05-09 13:30:50\] info: z2m: sensore presenza camera (0xa4c138c1b02ba2d3): ZY-M100-S\_2 - TuYa Mini human breathe sensor (Router)
> \[2024-05-09 13:30:50\] info: z2m: sensore presenza bagno (0xa4c138f4805f4052): ZY-M100-S\_2 - TuYa Mini human breathe sensor (Router)
> \[2024-05-09 13:30:50\] info: z2m: Stufa (0xa4c13864618cc92b): TS011F\_plug\_1 - TuYa Smart plug (with power monitoring) (Router)
> \[2024-05-09 13:30:50\] info: z2m: Deumidificatore (0xa4c138f0dc604c29): TS011F\_plug\_1 - TuYa Smart plug (with power monitoring) (Router)
> \[2024-05-09 13:30:50\] info: z2m: scaldasalviette (0xa4c138a817624e0b): TS011F\_plug\_1 - TuYa Smart plug (with power monitoring) (Router)
> \[2024-05-09 13:30:50\] info: z2m: Interruttore 3 (0xb43a31fffe6ca19b): TS0044 - TuYa Wireless switch with 4 buttons (EndDevice)
> \[2024-05-09 13:30:50\] info: z2m: Termometro camera (0xa4c1388e897386d0): LYWSD03MMC - Custom devices (DiY) Xiaomi temperature & humidity sensor with custom firmware (EndDevice)
> \[2024-05-09 13:30:50\] info: z2m: Termometro soppalco (0xa4c13813b058957a): LYWSD03MMC - Custom devices (DiY) Xiaomi temperature & humidity sensor with custom firmware (EndDevice)
> \[2024-05-09 13:30:50\] info: z2m: Termometro bagno (0xa4c13812b9cbc29f): LYWSD03MMC - Custom devices (DiY) Xiaomi temperature & humidity sensor with custom firmware (EndDevice)
> \[2024-05-09 13:30:50\] info: z2m: Termometro cucina (0xa4c138617507605c): LYWSD03MMC - Custom devices (DiY) Xiaomi temperature & humidity sensor with custom firmware (EndDevice)
> \[2024-05-09 13:30:50\] info: z2m: Termometro esterno (0xa4c13854cc2f5dc4): LYWSD03MMC - Custom devices (DiY) Xiaomi temperature & humidity sensor with custom firmware (EndDevice)
> \[2024-05-09 13:30:50\] info: z2m: Sensore movimento 1 (0xa4c13838deb326e8): 809WZT - TuYa Motion sensor (EndDevice)
> \[2024-05-09 13:30:50\] info: z2m: Sensore movimento 2 (0xa4c138844b034bc3): TS0202 - TuYa Motion sensor (EndDevice)
> \[2024-05-09 13:30:50\] info: z2m: Stufa bagno (0xa4c1388df3c5b76f): TS011F\_plug\_1 - TuYa Smart plug (with power monitoring) (Router)
> \[2024-05-09 13:30:50\] info: z2m: Finestra camera (0xa4c13828510a4df2): TS0203 - TuYa Door sensor (EndDevice)
> \[2024-05-09 13:30:50\] info: z2m: Termometro soggiorno (0xa4c138ee74d78cd7): WSD500A - TuYa Temperature & humidity sensor (EndDevice)
> \[2024-05-09 13:30:50\] info: z2m: Zigbee: disabling joining new devices.
> \[2024-05-09 13:30:50\] info: z2m: Connecting to MQTT server at mqtt://192.168.1.5:1883
> \[2024-05-09 13:30:50\] info: z2m: Connected to MQTT server
> \[2024-05-09 13:30:50\] info: z2m: Started frontend on port 9442
> \[2024-05-09 13:30:50\] info: z2m: Zigbee2MQTT started!
> \[2024-05-09 13:30:55\] error: zh:ezsp:uart: --\> Error: Error: {"sequence":5} after 4000ms
> \[2024-05-09 13:30:55\] error: zh:ezsp:uart: -!- break waiting (5)
> \[2024-05-09 13:30:55\] error: zh:ezsp:uart: Can't send DATA frame (4,6,0): 3400013400008ef1040100ef0101000100000a0b0510780b0200
> \[2024-05-09 13:30:59\] error: zh:ezsp:uart: --\> Error: Error: {"sequence":5} after 4000ms
> \[2024-05-09 13:30:59\] error: zh:ezsp:uart: -!- break rewaiting (5)
> \[2024-05-09 13:30:59\] error: zh:ezsp:uart: Can't resend DATA frame (4,6,1): 3400013400008ef1040100ef0101000100000a0b0510780b0200
> \[2024-05-09 13:30:59\] error: zh:controller:device: Default response to 0xa4c138f4805f4052 failed
> \[2024-05-09 13:30:59\] error: zh:controller:device: Default response to 0xa4c138f4805f4052 failed
> \[2024-05-09 13:30:59\] error: zh:controller:device: Default response to 0xa4c138f4805f4052 failed
> \[2024-05-09 13:30:59\] error: zh:controller:device: Default response to 0xa4c138f4805f4052 failed
> \[2024-05-09 13:30:59\] error: zh:controller:device: Default response to 0xa4c138f4805f4052 failed
> \[2024-05-09 13:30:59\] error: zh:controller:device: Default response to 0xa4c138f4805f4052 failed
> \[2024-05-09 13:30:59\] error: zh:controller:device: Default response to 0xa4c138f4805f4052 failed
> \[2024-05-09 13:30:59\] error: zh:controller:device: Default response to 0xa4c138f4805f4052 failed
> \[2024-05-09 13:30:59\] error: zh:controller:device: Default response to 0xa4c138f4805f4052 failed
> \[2024-05-09 13:30:59\] error: zh:controller:device: Default response to 0xa4c138f4805f4052 failed
> \[2024-05-09 13:30:59\] error: zh:controller:device: Default response to 0xa4c138f4805f4052 failed
> \[2024-05-09 13:30:59\] error: zh:controller:device: Default response to 0xa4c138f4805f4052 failed
> \[2024-05-09 13:30:59\] error: zh:controller:device: Default response to 0xa4c138f4805f4052 failed
> \[2024-05-09 13:31:00\] error: zh:ezsp:uart: \<-- CRC error: ebc9de6f8fffc5a7f57e|a7f5|bcdb
> \[2024-05-09 13:31:00\] error: zh:ezsp:uart: Error while parsing to NpiFrame 'Error: \<-- CRC error: ebc9de6f8fffc5a7f57e|a7f5|bcdb
> at Frame.checkCRC (/app/node\_modules/zigbee-herdsman/src/adapter/ezsp/driver/frame.ts:87:19)
> at SerialDriver.onParsed (/app/node\_modules/zigbee-herdsman/src/adapter/ezsp/driver/uart.ts:169:19)
> at Parser.emit (node:events:517:28)
> at Parser.\_transform (/app/node\_modules/zigbee-herdsman/src/adapter/ezsp/driver/parser.ts:49:26)
> at Parser.Transform.\_write (node:internal/streams/transform:175:8)
> at writeOrBuffer (node:internal/streams/writable:392:12)
> at \_write (node:internal/streams/writable:333:10)
> at Parser.Writable.write (node:internal/streams/writable:337:10)
> at SerialPort.ondata (node:internal/streams/readable:809:22)
> at SerialPort.emit (node:events:517:28)'
> \[2024-05-09 13:31:00\] error: zh:ezsp:uart: \<-- CRC error: 0c71b1a9112a15b65894a524ab5593499cf28f6d633f9874f0cfe78bfcd936a5ebc9de6f7471b1a9112a15b65894a524ab5593499cf59b6003629874f0cf368bfc1336a5ebc9de6f8fffc582847e|8284|4d82
> \[2024-05-09 13:31:00\] error: zh:ezsp:uart: Error while parsing to NpiFrame 'Error: \<-- CRC error: 0c71b1a9112a15b65894a524ab5593499cf28f6d633f9874f0cfe78bfcd936a5ebc9de6f7471b1a9112a15b65894a524ab5593499cf59b6003629874f0cf368bfc1336a5ebc9de6f8fffc582847e|8284|4d82
> at Frame.checkCRC (/app/node\_modules/zigbee-herdsman/src/adapter/ezsp/driver/frame.ts:87:19)
> at SerialDriver.onParsed (/app/node\_modules/zigbee-herdsman/src/adapter/ezsp/driver/uart.ts:169:19)
> at Parser.emit (node:events:517:28)
> at Parser.\_transform (/app/node\_modules/zigbee-herdsman/src/adapter/ezsp/driver/parser.ts:49:26)
> at Parser.Transform.\_write (node:internal/streams/transform:175:8)
> at writeOrBuffer (node:internal/streams/writable:392:12)
> at \_write (node:internal/streams/writable:333:10)
> at Parser.Writable.write (node:internal/streams/writable:337:10)
> at SerialPort.ondata (node:internal/streams/readable:809:22)
> at SerialPort.emit (node:events:517:28)'
> \[2024-05-09 13:31:08\] error: zh:ezsp:uart: --\> Error: Error: {"sequence":1} after 4000ms
> \[2024-05-09 13:31:08\] error: zh:ezsp:uart: -!- break waiting (1)
> \[2024-05-09 13:31:08\] error: zh:ezsp:uart: Can't send DATA frame (0,1,0): 00000004
> \[2024-05-09 13:31:12\] error: zh:ezsp:uart: --\> Error: Error: {"sequence":1} after 4000ms
> \[2024-05-09 13:31:12\] error: zh:ezsp:uart: -!- break rewaiting (1)
> \[2024-05-09 13:31:12\] error: zh:ezsp:uart: Can't resend DATA frame (0,1,1): 00000004
> \[2024-05-09 13:37:25\] error: zhc: Failed to apply calibration to 'illuminance\_lux': 'illuminance\_lux\_calibration' is not a number, got string ()

Tu utilise bien un dongle Sonoff E ?  
Tu as mis à jour le firmware récemment ?

---

<div class="post-metadata">

**Author:** ![Xenicle](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/xenicle/32/4893_2.png) [@Xenicle](https://community.gladysassistant.com/u/Xenicle)\
**Post date:** [Août 2, 2024, 3:25 UTC](https://community.gladysassistant.com/t/non-communication-zigbee2mqtt/9027/5 "2024-08-02T15:25:50Z")

</div>

Hello @pierre-gilles !  
Le dongle est sortie de la boite je n’ai pas toucher au firmware…

Faut t’il que je le mettent a jour ?

(sinon je m’étais trompé de choix de dongle au début j’avais choisi le P et j’ai switché sur le E qui est le bon…)

---

<div class="post-metadata">

**Author:** ![pierre-gilles](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/pierre-gilles/32/5886_2.png) [@pierre-gilles](https://community.gladysassistant.com/u/pierre-gilles)\
**Post date:** [Août 2, 2024, 3:36 UTC](https://community.gladysassistant.com/t/non-communication-zigbee2mqtt/9027/6 "2024-08-02T15:36:59Z")

</div>

ça peut-être une piste ^^

Le site de Zigbee2mqtt peut être de bon conseil : [https://www.zigbee2mqtt.io/](https://www.zigbee2mqtt.io/)

Leur forum aussi : [Koenkk/zigbee2mqtt · Discussions · GitHub](https://github.com/Koenkk/zigbee2mqtt/discussions)

Les issues Github: [Issues · Koenkk/zigbee2mqtt · GitHub](https://github.com/Koenkk/zigbee2mqtt/issues)

Tu es sur quel hardware sinon ?

Il faut que le port USB soit correctement alimenté (les ports des Pi sont parfois sous-alimenté par exemple)

---

<div class="post-metadata">

**Author:** ![Xenicle](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/xenicle/32/4893_2.png) [@Xenicle](https://community.gladysassistant.com/u/Xenicle)\
**Post date:** [Août 2, 2024, 3:39 UTC](https://community.gladysassistant.com/t/non-communication-zigbee2mqtt/9027/7 "2024-08-02T15:39:18Z")

</div>

> [@pierre-gilles](#):
>
> Tu es sur quel hardware sinon ?
> 
> Il faut que le port USB soit correctement alimenté (les ports des Pi sont parfois sous-alimenté par exemple)

Ah ! Il y a des chances que c’est cela je suis sur un raspi 3…

---

<div class="post-metadata">

**Author:** ![pierre-gilles](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/pierre-gilles/32/5886_2.png) [@pierre-gilles](https://community.gladysassistant.com/u/pierre-gilles)\
**Post date:** [Août 2, 2024, 3:40 UTC](https://community.gladysassistant.com/t/non-communication-zigbee2mqtt/9027/8 "2024-08-02T15:40:40Z")

</div>

Tu as tous les conseils de Zigbee2mqtt sur cette page :

> **[Zigbee2MQTT fails to start | Zigbee2MQTT](https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start.html)**
>
> Zigbee to MQTT bridge, get rid of your proprietary Zigbee bridges

Tu as notamment ce conseil pour Raspberry Pi :

 ![Screenshot 2024-08-02 at 17.40.15](https://gladys-assistant-community.b-cdn.net/uploads/default/original/3X/5/2/520f848068da8dea646518481d95f72bd3fec392.png)

---

<div class="post-metadata">

**Author:** ![Xenicle](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/xenicle/32/4893_2.png) [@Xenicle](https://community.gladysassistant.com/u/Xenicle)\
**Post date:** [Août 2, 2024, 3:51 UTC](https://community.gladysassistant.com/t/non-communication-zigbee2mqtt/9027/9 "2024-08-02T15:51:43Z")

</div>

`dmesg | grep volt` ne me retourne rien…

---

<div class="post-metadata">

**Author:** ![pierre-gilles](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/pierre-gilles/32/5886_2.png) [@pierre-gilles](https://community.gladysassistant.com/u/pierre-gilles)\
**Post date:** [Août 2, 2024, 4:00 UTC](https://community.gladysassistant.com/t/non-communication-zigbee2mqtt/9027/10 "2024-08-02T16:00:43Z")

</div>

Quelques pistes à tester :

- Essayer sur un autre port USB
- Utiliser un cable d’extension USB ou mieux un hub USB alimenté
- Mettre à jour le firmware du dongle

---

<div class="post-metadata">

**Author:** ![Xenicle](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/xenicle/32/4893_2.png) [@Xenicle](https://community.gladysassistant.com/u/Xenicle)\
**Post date:** [Août 2, 2024, 4:02 UTC](https://community.gladysassistant.com/t/non-communication-zigbee2mqtt/9027/11 "2024-08-02T16:02:52Z")

</div>

OK je vais regarder cela, merci !

Par contre c’est normal les «&nbsp;connexion unauthorised&nbsp;» sur les diffèrent logs ?

---

<div class="post-metadata">

**Author:** ![pierre-gilles](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/pierre-gilles/32/5886_2.png) [@pierre-gilles](https://community.gladysassistant.com/u/pierre-gilles)\
**Post date:** [Août 2, 2024, 4:06 UTC](https://community.gladysassistant.com/t/non-communication-zigbee2mqtt/9027/12 "2024-08-02T16:06:45Z")

</div>

Ah tu as raison, j’avais pas été plus loin que le premier souci !

En fait c’est peut-être ça le souci, ça ressemble beaucoup à un autre souci récent que j’avais vu ici :

> [@Zigbee2MQTT Toujours indisponible](https://community.gladysassistant.com/t/zigbee2mqtt-toujours-indisponible/9010):
>
> Désolé d’encore vous importuner avec mes problèmes de connexion Zigbee2Mqtt, mais soit, il y a des petits bonhommes verts dans mon entourage ou je ne suis vraiment pas doué (explication la plus plausible). Tout à l’air OK Service OK Configuration OK Petit bémol en orange (je ne sais si c’est important) dans le tableau «&nbsp;conteneurs&nbsp;» [image] J’ai voulu commencer l’intégration de mes modules Zigbee et impossible de se connecter à l’interface Zigbee2mqtt → (Adresse IP bonne…

Tu as peut-être mis Zigbee2mqtt dans un état bancal en sélectionnant le mauvais dongle, peut-être que tout purger pour repartir de zéro serait plus sage:

> [@Zigbee2MQTT Toujours indisponible](https://community.gladysassistant.com/t/zigbee2mqtt-toujours-indisponible/9010/11):
>
> On avance ! Le container ZigBee2MQTT fonctionne mais n’arrive pas à se connecter au container MQTT… On recommence innocent docker stop gladys Puis Mais aussi Et enfin docker restart gladys Ça va le faire !

---

<div class="post-metadata">

**Author:** ![Xenicle](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/xenicle/32/4893_2.png) [@Xenicle](https://community.gladysassistant.com/u/Xenicle)\
**Post date:** [Août 2, 2024, 4:18 UTC](https://community.gladysassistant.com/t/non-communication-zigbee2mqtt/9027/13 "2024-08-02T16:18:56Z")

</div>

Ok merci je m’y mets ^^

---

<div class="post-metadata">

**Author:** ![Xenicle](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/xenicle/32/4893_2.png) [@Xenicle](https://community.gladysassistant.com/u/Xenicle)\
**Post date:** [Août 2, 2024, 4:25 UTC](https://community.gladysassistant.com/t/non-communication-zigbee2mqtt/9027/14 "2024-08-02T16:25:53Z")

</div>

C’était bien ça ! :

 ![image](https://gladys-assistant-community.b-cdn.net/uploads/default/original/3X/e/a/ea3c9e5deef1b511e0b3536b43b4cfc934c8983e.png)  
 ![image](https://gladys-assistant-community.b-cdn.net/uploads/default/original/3X/a/c/acf35b83267713c64001d56555099105094a6c70.png)

Merci @pierre-gilles !

---

<div class="post-metadata">

**Author:** ![pierre-gilles](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/pierre-gilles/32/5886_2.png) [@pierre-gilles](https://community.gladysassistant.com/u/pierre-gilles)\
**Post date:** [Août 2, 2024, 4:38 UTC](https://community.gladysassistant.com/t/non-communication-zigbee2mqtt/9027/15 "2024-08-02T16:38:23Z")

</div>

Excellent ! Bonne installation !

---

<div class="post-metadata">

**Author:** ![GBoulvin](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/gboulvin/32/10006_2.png) [@GBoulvin](https://community.gladysassistant.com/u/GBoulvin)\
**Post date:** [Août 2, 2024, 10:11 UTC](https://community.gladysassistant.com/t/non-communication-zigbee2mqtt/9027/16 "2024-08-02T22:11:58Z")

</div>

> [@pierre-gilles](#):
>
> ça ressemble beaucoup à un autre souci récent

@pierre-gilles Ça serait peut-être à ajouter dans la doc ?  
Ou un truc à modifier dans l’intégration. On dirait que le changement de dongle n’est pas pris en compte…

---

<div class="post-metadata">

**Author:** ![pierre-gilles](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/pierre-gilles/32/5886_2.png) [@pierre-gilles](https://community.gladysassistant.com/u/pierre-gilles)\
**Post date:** [Août 3, 2024, 9:59 UTC](https://community.gladysassistant.com/t/non-communication-zigbee2mqtt/9027/17 "2024-08-03T09:59:20Z")

</div>

Je pense que c’est un bug de l’intégration effectivement, depuis la nouvelle UI le clean n’est pas parfaitement fait quand l’intégration est désactivée

J’ai créé une issue :

> <https://github.com/GladysAssistant/Gladys/issues/2108>

---

<div class="post-metadata">

**Author:** ![pierre-gilles](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/pierre-gilles/32/5886_2.png) [@pierre-gilles](https://community.gladysassistant.com/u/pierre-gilles)\
**Post date:** [Août 5, 2024, 2:09 UTC](https://community.gladysassistant.com/t/non-communication-zigbee2mqtt/9027/18 "2024-08-05T14:09:50Z")

</div>

Effectivement il y avait un bug dans l’intégration actuelle, je suis capable de reproduire le bug chez moi !

J’ai créé une PR pour corriger le souci.

> <https://github.com/GladysAssistant/Gladys/pull/2109>
>
> \### Pull Request check-list
> 
> To ensure your Pull Request can be accepted as fa…st as possible, make sure to review and check all of these items:
> 
> \- \[x\] If your changes affects code, did your write the tests?
> \- \[x\] Are tests passing? (\`npm test\` on both front/server)
> \- \[x\] Is the linter passing? (\`npm run eslint\` on both front/server)
> \- \[x\] Did you run prettier? (\`npm run prettier\` on both front/server)
> \- \[x\] If you are adding a new features/services, did you run integration comparator? (\`npm run compare-translations\` on front)
> \- \[x\] Did you test this pull request in real life? With real devices? If this development is a big feature or a new service, we recommend that you provide a Docker image to the community (\[french forum\](https://community.gladysassistant.com/)/\[english forum\](https://en-community.gladysassistant.com/)) for testing before merging.
> 
> \### Description of change
> 
> Fix #2108 - Remove containers when disabling the integration. It fixes a bug when the user disable then re-enable containers, the new credentials are not taken into account

@cicoub13 @AlexTrovato si jamais vous avez le temps de jeter un oeil 😉