# \[Z2M\] Tests en zigbee2mqtt 1.42.0 \> 2.1.3 \>..\> 2.4.0 \>..\> 2.6.1\>...\>2.7.2

**URL:** <https://community.gladysassistant.com/t/z2m-tests-en-zigbee2mqtt-1-42-0-2-1-3-2-4-0-2-6-1-2-7-2/9421>\
**Category:** Développement\
**Tags:** zigbee2mqtt\
**Created:** [Mars 10, 2025, 5:47 UTC](https://community.gladysassistant.com/t/z2m-tests-en-zigbee2mqtt-1-42-0-2-1-3-2-4-0-2-6-1-2-7-2/9421 "2025-03-10T17:47:33Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![prohand](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/prohand/32/15713_2.png) [@prohand](https://community.gladysassistant.com/u/prohand)\
**Post date:** [Juin 5, 2025, 2:53 UTC](https://community.gladysassistant.com/t/z2m-tests-en-zigbee2mqtt-1-42-0-2-1-3-2-4-0-2-6-1-2-7-2/9421/5 "2025-06-05T14:53:09Z")

</div>

Je viens également de passer en 2.3.0 directement sans problème pour le moment.

Je ne suis pas passé en 2.4.0 au vu des différents bugs remontés :

> <https://github.com/Koenkk/zigbee2mqtt/issues/27580>
>
> \### What happened?
> 
> I am noticing frequent restarts of zigbee2mqtt since updatin…g to 2.4.0:
> 
> \[2025-06-02 00:39:26\] info: z2m: Disconnecting from MQTT server
> \[2025-06-02 00:41:07\] info: z2m: Disconnecting from MQTT server
> \[2025-06-02 00:42:48\] info: z2m: Disconnecting from MQTT server
> \[2025-06-02 00:44:29\] info: z2m: Disconnecting from MQTT server
> \[2025-06-02 00:46:10\] info: z2m: Disconnecting from MQTT server
> \[2025-06-02 00:47:51\] info: z2m: Disconnecting from MQTT server
> \[2025-06-02 00:49:32\] info: z2m: Disconnecting from MQTT server
> 
> This is what I see in the logs:
> 
> \[2025-06-02 00:49:33\] info: zh:controller: Wrote coordinator backup to '/opt/zigbee2mqtt/data/coordinator\_backup.json'
> \[2025-06-02 00:49:33\] info: zh:ember:uart:ash: ASH COUNTERS since last clear:
> \[2025-06-02 00:49:33\] info: zh:ember:uart:ash: Total frames: RX=3787, TX=4886
> \[2025-06-02 00:49:33\] info: zh:ember:uart:ash: Cancelled : RX=0, TX=0
> \[2025-06-02 00:49:33\] info: zh:ember:uart:ash: DATA frames : RX=3678, TX=1148
> \[2025-06-02 00:49:33\] info: zh:ember:uart:ash: DATA bytes : RX=110150, TX=30288
> \[2025-06-02 00:49:33\] info: zh:ember:uart:ash: Retry frames: RX=9, TX=51
> \[2025-06-02 00:49:33\] info: zh:ember:uart:ash: ACK frames : RX=49, TX=3686
> \[2025-06-02 00:49:33\] info: zh:ember:uart:ash: NAK frames : RX=50, TX=0
> \[2025-06-02 00:49:33\] info: zh:ember:uart:ash: nRdy frames : RX=0, TX=0
> \[2025-06-02 00:49:33\] info: zh:ember:uart:ash: CRC errors : RX=0
> \[2025-06-02 00:49:33\] info: zh:ember:uart:ash: Comm errors : RX=0
> \[2025-06-02 00:49:33\] info: zh:ember:uart:ash: Length \< minimum: RX=0
> \[2025-06-02 00:49:33\] info: zh:ember:uart:ash: Length \> maximum: RX=0
> \[2025-06-02 00:49:33\] info: zh:ember:uart:ash: Bad controls : RX=0
> \[2025-06-02 00:49:33\] info: zh:ember:uart:ash: Bad lengths : RX=0
> \[2025-06-02 00:49:33\] info: zh:ember:uart:ash: Bad ACK numbers : RX=0
> \[2025-06-02 00:49:33\] info: zh:ember:uart:ash: Out of buffers : RX=0
> \[2025-06-02 00:49:33\] info: zh:ember:uart:ash: Retry dupes : RX=9
> \[2025-06-02 00:49:33\] info: zh:ember:uart:ash: Out of sequence : RX=0
> \[2025-06-02 00:49:33\] info: zh:ember:uart:ash: ACK timeouts : RX=2
> \[2025-06-02 00:49:33\] info: zh:ember:uart:ash: Port closed.
> \[2025-06-02 00:49:33\] info: zh:ember:uart:ash: ======== ASH stopped ========
> \[2025-06-02 00:49:33\] info: zh:ember:ezsp: ======== EZSP stopped ========
> \[2025-06-02 00:49:33\] info: zh:ember: ======== Ember Adapter Stopped ========
> \[2025-06-02 00:49:33\] info: z2m: Stopped zigbee-herdsman
> \[2025-06-02 00:49:33\] info: z2m: Stopped Zigbee2MQTT
> 
> It was working quite stable with 2.3.0 and earlier versions.
> 
> \### What did you expect to happen?
> 
> \_No response\_
> 
> \### How to reproduce it (minimal and precise)
> 
> It just happens continuously.
> 
> \### Zigbee2MQTT version
> 
> 2.40.0
> 
> \### Adapter firmware version
> 
> 8.0.2
> 
> \### Adapter
> 
> Sonoff ZBDongle
> 
> \### Setup
> 
> Z2M plain running on RPI 4+ with Homebridge.
> 
> \### Debug log
> 
> \[debug.log.zip\](https://github.com/user-attachments/files/20542949/debug.log.zip)

> <https://github.com/Koenkk/zigbee2mqtt/issues/27605>
>
> \### What happened?
> 
> Zigbee2MQTT 2.4.0, OTA. Incorrect detection of firmware vers…ion of all devices.
> 
> !\[Image\](https://github.com/user-attachments/assets/df9d26c8-7165-4628-9ef6-7575afefe4a0)
> 
> \### What did you expect to happen?
> 
> \_No response\_
> 
> \### How to reproduce it (minimal and precise)
> 
> Update Zigbee2MQTT from 2.3. to 2.4.0
> 
> \### Zigbee2MQTT version
> 
> 2.4.0
> 
> \### Adapter firmware version
> 
> 7.4.5 \[GA\]
> 
> \### Adapter
> 
> Sonoff Zigbee 3.0 USB Dongle Plus V2” (model "ZBDongle-E"). Ember protocol.
> 
> \### Setup
> 
> Zigbee2MQTT in docker.
> Linux MyHomeAssistant 6.8.0-60-generic #63-Ubuntu SMP PREEMPT\_DYNAMIC Tue Apr 15 19:04:15 UTC 2025 x86\_64 x86\_64 x86\_64 GNU/Linux
> Ubuntu 24.04.2 LTS
> 
> \### Debug log
> 
> \_No response\_

Je vous tiens au courant si j’ai des problèmes particulier

---

_[View the full topic](https://community.gladysassistant.com/t/z2m-tests-en-zigbee2mqtt-1-42-0-2-1-3-2-4-0-2-6-1-2-7-2/9421)._