Could you add a clear Notifications button for web ui please
Got it. I feel the same need.
Hi, when using
port: tcp://ZigbeeAP-COOR-CHOD.local:6638,
Z2M has a problem connecting due to an IPv6 link-local address.
zh:ember:uart:ash: Failed to init port with error Error: connect ETIMEDOUT fe80::1e69:20ff:fe7f:9c57:6638
After changing it to
port: tcp://192.168.15.105:6638,
everything seems to work.
Dongle Max version: Beta V1.0.8
IP address: Smart IP
Z2M: 2.9.2-1
Version Beta V1.0.8 finally seems stable 
[2026-04-02 10:33:03] debug: zh:ember:ezsp: ===> [FRAME: ID=276:"EXPORT_KEY" Seq=64 Len=23]
[2026-04-02 10:33:03] debug: zh:ember:uart:ash: ---> [FRAME type=DATA frmTx=0 frmRx=1](ackRx=0)
[2026-04-02 10:33:03] debug: zh:ember:uart:ash: <--- [FRAME type=DATA]
[2026-04-02 10:33:03] debug: zh:ember:uart:ash: <--- [FRAME type=DATA ackNum=1](ackRx=0 frmTx=1)
[2026-04-02 10:33:03] debug: zh:ember:uart:ash: <--- [FRAME type=DATA ackNum=1 frmNum=1](frmRx=1) Added to rxQueue
[2026-04-02 10:33:03] debug: zh:ember:uart:ash: ---> [FRAME type=ACK frmRx=2](ackRx=1)
[2026-04-02 10:33:03] debug: zh:ember:ezsp: <=== [FRAME: ID=276:"EXPORT_KEY" Seq=64 Len=43]
[2026-04-02 10:33:03] info: zh:controller: Wrote coordinator backup to '/config/zigbee2mqtt/coordinator_backup.json'
[2026-04-02 10:33:03] info: zh:ember:uart:ash: ASH COUNTERS since last clear:
[2026-04-02 10:33:03] info: zh:ember:uart:ash: Total frames: RX=164, TX=230
[2026-04-02 10:33:03] info: zh:ember:uart:ash: Cancelled : RX=0, TX=0
[2026-04-02 10:33:03] info: zh:ember:uart:ash: DATA frames : RX=162, TX=65
[2026-04-02 10:33:03] info: zh:ember:uart:ash: DATA bytes : RX=4177, TX=1205
[2026-04-02 10:33:03] info: zh:ember:uart:ash: Retry frames: RX=1, TX=0
[2026-04-02 10:33:03] info: zh:ember:uart:ash: ACK frames : RX=0, TX=164
[2026-04-02 10:33:03] info: zh:ember:uart:ash: NAK frames : RX=0, TX=0
[2026-04-02 10:33:03] info: zh:ember:uart:ash: nRdy frames : RX=0, TX=0
[2026-04-02 10:33:03] info: zh:ember:uart:ash: CRC errors : RX=0
[2026-04-02 10:33:03] info: zh:ember:uart:ash: Comm errors : RX=0
[2026-04-02 10:33:03] info: zh:ember:uart:ash: Length < minimum: RX=0
[2026-04-02 10:33:03] info: zh:ember:uart:ash: Length > maximum: RX=0
[2026-04-02 10:33:03] info: zh:ember:uart:ash: Bad controls : RX=0
[2026-04-02 10:33:03] info: zh:ember:uart:ash: Bad lengths : RX=0
[2026-04-02 10:33:03] info: zh:ember:uart:ash: Bad ACK numbers : RX=0
[2026-04-02 10:33:03] info: zh:ember:uart:ash: Out of buffers : RX=0
[2026-04-02 10:33:03] info: zh:ember:uart:ash: Retry dupes : RX=1
[2026-04-02 10:33:03] info: zh:ember:uart:ash: Out of sequence : RX=0
[2026-04-02 10:33:03] info: zh:ember:uart:ash: ACK timeouts : RX=0
[2026-04-02 10:33:04] info: zh:ember:uart:ash: Port closed, error=null
[2026-04-02 10:33:04] info: zh:ember:uart:ash: ======== ASH stopped ========
[2026-04-02 10:33:04] info: zh:ember:ezsp: ======== EZSP stopped ========
[2026-04-02 10:33:04] info: zh:ember: ======== Ember Adapter Stopped ========
[2026-04-02 10:33:04] info: z2m: Stopped zigbee-herdsman
[2026-04-02 10:33:04] info: z2m: Stopped Zigbee2MQTT
[10:34:13] INFO: Preparing to start...
[10:34:13] INFO: Socat not enabled
[10:34:14] INFO: Starting Zigbee2MQTT...
Starting Zigbee2MQTT without watchdog.
[2026-04-02 10:34:22] debug: z2m: Removing old log directory '/config/zigbee2mqtt/log/2026-03-21.15-47-07'
[2026-04-02 10:34:22] info: z2m: Logging to console, file (filename: log.log)
[2026-04-02 10:34:22] debug: z2m: Loaded state from file /config/zigbee2mqtt/state.json
[2026-04-02 10:34:22] info: z2m: Starting Zigbee2MQTT version 2.9.2 (commit #unknown)
[2026-04-02 10:34:22] info: z2m: Starting zigbee-herdsman (10.0.5)
[2026-04-02 10:34:22] debug: z2m: Using zigbee-herdsman with settings: '"{\"network\":{\"panID\":35490,\"extendedPanID\":[242,200,243,222,105,133,23,11],\"channelList\":[11],\"networkKey\":\"HIDDEN\"},\"databasePath\":\"/config/zigbee2mqtt/database.db\",\"databaseBackupPath\":\"/config/zigbee2mqtt/database.db.backup\",\"backupPath\":\"/config/zigbee2mqtt/coordinator_backup.json\",\"serialPort\":{\"baudRate\":115200,\"rtscts\":false,\"path\":\"tcp://ZigbeeAP-COOR-CHOD.local:6638\",\"adapter\":\"ember\"},\"adapter\":{\"disableLED\":false}}"'
[2026-04-02 10:34:23] info: zh:ember: Using default stack config.
[2026-04-02 10:34:23] debug: zh:controller: Starting with options '{"network":{"networkKeyDistribute":false,"networkKey":"HIDDEN","extendedPanID":[242,200,243,222,105,133,23,11],"panID":35490,"channelList":[11]},"serialPort":{"baudRate":115200,"rtscts":false,"path":"tcp://ZigbeeAP-COOR-CHOD.local:6638","adapter":"ember"},"adapter":{"disableLED":false},"databasePath":"/config/zigbee2mqtt/database.db","databaseBackupPath":"/config/zigbee2mqtt/database.db.backup","backupPath":"/config/zigbee2mqtt/coordinator_backup.json"}'
[2026-04-02 10:34:23] info: zh:ember: ======== Ember Adapter Starting ========
[2026-04-02 10:34:23] info: zh:ember:ezsp: ======== EZSP starting ========
[2026-04-02 10:34:23] info: zh:ember:uart:ash: ======== ASH Adapter reset ========
[2026-04-02 10:34:23] debug: zh:ember:uart:ash: Opening TCP socket with ZigbeeAP-COOR-CHOD.local:6638
[2026-04-02 10:36:37] info: zh:ember:uart:ash: ASH COUNTERS since last clear:
[2026-04-02 10:36:37] info: zh:ember:uart:ash: Total frames: RX=0, TX=0
[2026-04-02 10:36:37] info: zh:ember:uart:ash: Cancelled : RX=0, TX=0
[2026-04-02 10:36:37] info: zh:ember:uart:ash: DATA frames : RX=0, TX=0
[2026-04-02 10:36:37] info: zh:ember:uart:ash: DATA bytes : RX=0, TX=0
[2026-04-02 10:36:37] info: zh:ember:uart:ash: Retry frames: RX=0, TX=0
[2026-04-02 10:36:37] info: zh:ember:uart:ash: ACK frames : RX=0, TX=0
[2026-04-02 10:36:37] info: zh:ember:uart:ash: NAK frames : RX=0, TX=0
[2026-04-02 10:36:37] info: zh:ember:uart:ash: nRdy frames : RX=0, TX=0
[2026-04-02 10:36:37] info: zh:ember:uart:ash: CRC errors : RX=0
[2026-04-02 10:36:37] info: zh:ember:uart:ash: Comm errors : RX=0
[2026-04-02 10:36:37] info: zh:ember:uart:ash: Length < minimum: RX=0
[2026-04-02 10:36:37] info: zh:ember:uart:ash: Length > maximum: RX=0
[2026-04-02 10:36:37] info: zh:ember:uart:ash: Bad controls : RX=0
[2026-04-02 10:36:37] info: zh:ember:uart:ash: Bad lengths : RX=0
[2026-04-02 10:36:37] info: zh:ember:uart:ash: Bad ACK numbers : RX=0
[2026-04-02 10:36:37] info: zh:ember:uart:ash: Out of buffers : RX=0
[2026-04-02 10:36:37] info: zh:ember:uart:ash: Retry dupes : RX=0
[2026-04-02 10:36:37] info: zh:ember:uart:ash: Out of sequence : RX=0
[2026-04-02 10:36:37] info: zh:ember:uart:ash: ACK timeouts : RX=0
[2026-04-02 10:36:37] info: zh:ember:uart:ash: ======== ASH stopped ========
[2026-04-02 10:36:37] error: zh:ember:uart:ash: Failed to init port with error Error: connect ETIMEDOUT fe80::1e69:20ff:fe7f:9c57:6638
[2026-04-02 10:36:37] error: z2m: Error while starting zigbee-herdsman
[2026-04-02 10:36:37] error: z2m: Failed to start zigbee-herdsman
[2026-04-02 10:36:37] error: z2m: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start_crashes-runtime.html for possible solutions
[2026-04-02 10:36:37] error: z2m: Exiting...
[2026-04-02 10:36:37] error: z2m: Error: Failed to start EZSP layer with status=HOST_FATAL_ERROR.
at EmberAdapter.initEzsp (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/adapter/ember/adapter/emberAdapter.ts:666:19)
at processTicksAndRejections (node:internal/process/task_queues:103:5)
at EmberAdapter.start (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/adapter/ember/adapter/emberAdapter.ts:1538:24)
at Controller.start (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/controller/controller.ts:146:29)
at Zigbee.start (/app/lib/zigbee.ts:70:27)
at Controller.start (/app/lib/controller.ts:111:29)
at start (/app/index.js:156:5)
[10:36:41] INFO: Preparing to start...
[10:36:42] INFO: Socat not enabled
[10:36:42] INFO: Starting Zigbee2MQTT...
Starting Zigbee2MQTT without watchdog.
[2026-04-02 10:36:49] debug: z2m: Removing old log directory '/config/zigbee2mqtt/log/2026-03-21.15-48-04'
[2026-04-02 10:36:49] info: z2m: Logging to console, file (filename: log.log)
[2026-04-02 10:36:49] debug: z2m: Loaded state from file /config/zigbee2mqtt/state.json
[2026-04-02 10:36:49] info: z2m: Starting Zigbee2MQTT version 2.9.2 (commit #unknown)
[2026-04-02 10:36:49] info: z2m: Starting zigbee-herdsman (10.0.5)
[2026-04-02 10:36:49] debug: z2m: Using zigbee-herdsman with settings: '"{\"network\":{\"panID\":35490,\"extendedPanID\":[242,200,243,222,105,133,23,11],\"channelList\":[11],\"networkKey\":\"HIDDEN\"},\"databasePath\":\"/config/zigbee2mqtt/database.db\",\"databaseBackupPath\":\"/config/zigbee2mqtt/database.db.backup\",\"backupPath\":\"/config/zigbee2mqtt/coordinator_backup.json\",\"serialPort\":{\"baudRate\":115200,\"rtscts\":false,\"path\":\"tcp://ZigbeeAP-COOR-CHOD.local:6638\",\"adapter\":\"ember\"},\"adapter\":{\"disableLED\":false}}"'
[2026-04-02 10:36:49] info: zh:ember: Using default stack config.
[2026-04-02 10:36:50] debug: zh:controller: Starting with options '{"network":{"networkKeyDistribute":false,"networkKey":"HIDDEN","extendedPanID":[242,200,243,222,105,133,23,11],"panID":35490,"channelList":[11]},"serialPort":{"baudRate":115200,"rtscts":false,"path":"tcp://ZigbeeAP-COOR-CHOD.local:6638","adapter":"ember"},"adapter":{"disableLED":false},"databasePath":"/config/zigbee2mqtt/database.db","databaseBackupPath":"/config/zigbee2mqtt/database.db.backup","backupPath":"/config/zigbee2mqtt/coordinator_backup.json"}'
[2026-04-02 10:36:50] info: zh:ember: ======== Ember Adapter Starting ========
[2026-04-02 10:36:50] info: zh:ember:ezsp: ======== EZSP starting ========
[2026-04-02 10:36:50] info: zh:ember:uart:ash: ======== ASH Adapter reset ========
[2026-04-02 10:36:50] debug: zh:ember:uart:ash: Opening TCP socket with ZigbeeAP-COOR-CHOD.local:6638
Unfortunately, it started acting up again 
After switching to a Sonoff Zigbee USB 3.0 Dongle Plus-E, everything works without any issues.
serial:
port: tcp://192.168.15.105:6638
baudrate: 115200
adapter: ember
rtscts: false
Current ESP32-D0WDR2-V3 firmware version: Beta V1.0.8
Z2M: 2.9.2-1
dongle log
I (420282781) webserver_logger: webserver_logger_debug_task: Running
I (420284007) firmware_manage: OTA_INFO_TIMING_CHECK: 20:22:15
I (420286007) firmware_manage: OTA_INFO_TIMING_CHECK: 20:22:17
I (420287672) network_main: [RAM Check]: Total Free : 1906876 bytes, Internal Free : 64451 bytes , Largest Internal Block : 57344 bytes
I (420288007) firmware_manage: OTA_INFO_TIMING_CHECK: 20:22:19
I (420290007) firmware_manage: OTA_INFO_TIMING_CHECK: 20:22:21
I (420292007) firmware_manage: OTA_INFO_TIMING_CHECK: 20:22:23
I (420293672) network_main: [RAM Check]: Total Free : 1904832 bytes, Internal Free : 64355 bytes , Largest Internal Block : 57344 bytes
I (420294007) firmware_manage: OTA_INFO_TIMING_CHECK: 20:22:25
I (420296007) firmware_manage: OTA_INFO_TIMING_CHECK: 20:22:27
I (420298007) firmware_manage: OTA_INFO_TIMING_CHECK: 20:22:29
W (420298680) tcp_server: Incoming connection from 192.168.15.111
I (420298684) webserver_api: send_ws_message_to_client success with sock_fd=56 message:[{"method":"Device.Mg24InfoNotify","ts":1775154150000,"data":{"z2mOrZhaConnected":true,"tcpSocket":{"connected":true,"connectionDuration":0}}}]
I (420298687) notification_manage_file: write txt:/Littlefs/notification.txt payload:zhaOrZ2mConnected,2026-04-02T20:22:30.472+02:00
I (420299515) webserver_api: send_ws_message_to_client success with sock_fd=56 message:[{"method":"Device.NotificationNotify","ts":1775154151000,"data":{"type":"zhaOrZ2mConnected","time":"2026-04-02T20:22:30.472+02:00"}}]
I (420299516) mqtt_device_ha: pub string:{"tcp":"Connected"}
W (420299517) mqtt_config: mqtt client don't connect to broker
I (420299672) network_main: [RAM Check]: Total Free : 1902624 bytes, Internal Free : 60639 bytes , Largest Internal Block : 53248 bytes
I (420300007) firmware_manage: OTA_INFO_TIMING_CHECK: 20:22:31
I (420308007) firmware_manage: OTA_INFO_TIMING_CHECK: 20:22:39
W (420308349) MG24_TYPEC: (90)=> 2d 66 b1 a9 7d 31 2a 15 b6 58 95 48 24 ab 55 93 49 9c 5d 93 62 b7 52 98 74 f5 de 6f 83 fc 7d 5e 16 a7 eb e1 4c 7e 3d 66 b1 a9 90 2a 7d 38 b2 59 7c f1 7e 4d 66 b1 a9 90 2a 7d 38 b2 59 d7 2a 7e 5d 66 b1 a9 90 2a 7d 38 b2 59 84 d4 7e 6d 66 b1 a9 90 2a 7d 38 b2 59 70 d6 7e
I (420310007) firmware_manage: OTA_INFO_TIMING_CHECK: 20:22:41
E (420310235) tcp_server: TCP connection closed by peer
I (420310240) webserver_api: send_ws_message_to_client success with sock_fd=56 message:[{"method":"Device.Mg24InfoNotify","ts":1775154162000,"data":{"z2mOrZhaConnected":false,"tcpSocket":{"connected":false}}}]
I (420310241) webhooks_manage: WEBHOOK_EVENT_TIGGER
I (420310242) webhooks_manage: webhook item[0] id was NULL skip
I (420310243) webhooks_manage: webhook item[1] id was NULL skip
I (420310243) webhooks_manage: webhook item[2] id was NULL skip
I (420310243) webhooks_manage: webhook item[3] id was NULL skip
I (420310243) webhooks_manage: webhook item[4] id was NULL skip
I (420310243) webhooks_manage: webhook item[5] id was NULL skip
I (420310243) notification_manage_file: write txt:/Littlefs/notification.txt payload:zhaOrZ2mDisconnected,2026-04-02T20:22:42.029+02:00
I (420310244) webhooks_manage: webhook item[6] id was NULL skip
I (420310244) webhooks_manage: webhook item[7] id was NULL skip
I (420310244) webhooks_manage: webhook item[8] id was NULL skip
I (420310244) webhooks_manage: webhook item[9] id was NULL skip
I (420311101) webserver_api: send_ws_message_to_client success with sock_fd=56 message:[{"method":"Device.NotificationNotify","ts":1775154162000,"data":{"type":"zhaOrZ2mDisconnected","time":"2026-04-02T20:22:42.029+02:00"}}]
I (420311101) mqtt_device_ha: pub string:{"tcp":"Disconnected"}
W (420311102) mqtt_config: mqtt client don't connect to broker
W (420311102) tcp_server: Ready for next connection
I (420311672) network_main: [RAM Check]: Total Free : 1906876 bytes, Internal Free : 64451 bytes , Largest Internal Block : 57344 bytes
Zigbee2MQTT
[2026-04-02 20:27:36] info: z2m: Started frontend on port 8099
[2026-04-02 20:27:36] warning: zh:ember:uart:ash: Frame(s) in progress cancelled in [1ac2020682af7e]
[2026-04-02 20:27:36] debug: zh:ember:uart:ash: <--- [FRAME type=ERROR]
[2026-04-02 20:27:36] error: zh:ember:uart:ash: Received ERROR from adapter, with code=RESET_ASSERT.
[2026-04-02 20:27:36] error: zh:ember:uart:ash: ASH disconnected | Adapter status: ASH_NCP_FATAL_ERROR
[2026-04-02 20:27:36] error: zh:ember:ezsp: Fatal error, status=ASH_NCP_FATAL_ERROR. Last Frame: [FRAME: ID=38:"GET_EUI64" Seq=34 Len=13]
[2026-04-02 20:27:36] debug: zh:controller: Adapter disconnected
[2026-04-02 20:27:36] info: zh:ember:uart:ash: ASH COUNTERS since last clear:
[2026-04-02 20:27:36] info: zh:ember:uart:ash: Total frames: RX=250, TX=285
[2026-04-02 20:27:36] info: zh:ember:uart:ash: Cancelled : RX=1, TX=0
[2026-04-02 20:27:36] info: zh:ember:uart:ash: DATA frames : RX=238, TX=35
[2026-04-02 20:27:36] info: zh:ember:uart:ash: DATA bytes : RX=1920, TX=349
[2026-04-02 20:27:36] info: zh:ember:uart:ash: Retry frames: RX=10, TX=0
[2026-04-02 20:27:36] info: zh:ember:uart:ash: ACK frames : RX=0, TX=249
[2026-04-02 20:27:36] info: zh:ember:uart:ash: NAK frames : RX=0, TX=0
[2026-04-02 20:27:36] info: zh:ember:uart:ash: nRdy frames : RX=0, TX=0
[2026-04-02 20:27:36] info: zh:ember:uart:ash: CRC errors : RX=0
[2026-04-02 20:27:36] info: zh:ember:uart:ash: Comm errors : RX=0
[2026-04-02 20:27:36] info: zh:ember:uart:ash: Length < minimum: RX=0
[2026-04-02 20:27:36] info: zh:ember:uart:ash: Length > maximum: RX=0
[2026-04-02 20:27:36] info: zh:ember:uart:ash: Bad controls : RX=0
[2026-04-02 20:27:36] info: zh:ember:uart:ash: Bad lengths : RX=0
[2026-04-02 20:27:36] info: zh:ember:uart:ash: Bad ACK numbers : RX=0
[2026-04-02 20:27:36] info: zh:ember:uart:ash: Out of buffers : RX=0
[2026-04-02 20:27:36] info: zh:ember:uart:ash: Retry dupes : RX=10
[2026-04-02 20:27:36] info: zh:ember:uart:ash: Out of sequence : RX=0
[2026-04-02 20:27:36] info: zh:ember:uart:ash: ACK timeouts : RX=0
[2026-04-02 20:27:36] info: zh:ember:uart:ash: ======== ASH stopped ========
[2026-04-02 20:27:36] info: zh:ember:ezsp: ======== EZSP stopped ========
[2026-04-02 20:27:36] info: zh:ember: ======== Ember Adapter Stopped ========
[2026-04-02 20:27:36] error: z2m: Adapter disconnected, stopping
[2026-04-02 20:27:36] info: z2m: Stopping Zigbee2MQTT (restart=false, code=2, signal=undefined)
[2026-04-02 20:27:36] debug: z2m: Saving state to file /config/zigbee2mqtt/state.json
[2026-04-02 20:27:36] info: z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/bridge/state', payload '{"state":"offline"}'
[2026-04-02 20:27:36] info: z2m: Disconnecting from MQTT server
[2026-04-02 20:27:37] debug: z2m: Discovering entities to Home Assistant in 5s
[2026-04-02 20:27:37] error: z2m: Failed to start 'HomeAssistant' (Error: client disconnecting
at MqttClient._checkDisconnecting (/app/node_modules/.pnpm/[email protected]/node_modules/mqtt/src/lib/client.ts:1758:14)
at MqttClient.subscribe (/app/node_modules/.pnpm/[email protected]/node_modules/mqtt/src/lib/client.ts:1146:12)
at /app/node_modules/.pnpm/[email protected]/node_modules/mqtt/src/lib/client.ts:1345:9
at new Promise (<anonymous>)
at MqttClient.subscribeAsync (/app/node_modules/.pnpm/[email protected]/node_modules/mqtt/src/lib/client.ts:1344:10)
at Mqtt.subscribe (/app/lib/mqtt.ts:166:27)
at HomeAssistant.start (/app/lib/extension/homeassistant.ts:469:25)
at processTicksAndRejections (node:internal/process/task_queues:103:5)
at Controller.startExtension (/app/lib/controller.ts:321:13)
at Controller.start (/app/lib/controller.ts:177:13))
[2026-04-02 20:27:37] info: z2m: Zigbee2MQTT start aborted, reason=STOPABORT
[2026-04-02 20:27:37] debug: z2m:mqtt: Received MQTT message on 'zigbee2mqtt/KuchyÅ/set/external_temperature_input' with data '18.4'
[2026-04-02 20:27:37] info: z2m: Stopping zigbee-herdsman...
[2026-04-02 20:27:37] debug: zh:controller:database: Writing database to '/config/zigbee2mqtt/database.db'
[2026-04-02 20:27:40] info: z2m: Stopped zigbee-herdsman
[2026-04-02 20:27:40] info: z2m: Stopped Zigbee2MQTT
Hello, we are the Dongle-M development team.
Based on the logs you provided, we are unable to pinpoint the exact cause of the issue.
Could you please enable debug logging, reproduce the problem, and then send us the complete debug logs along with the Zigbee2MQTT logs?
We will investigate the issue and work to identify the cause as quickly as possible.
- My ESP32-D0WDR2-V3 already on STABLE V1.0.7, why does it still prompt
New firmware version is available? - Is Sonoff suggesting that everybody should be on BETA V1.0.8?
- If everybody should be on BETA, why is there a need for STABLE?
Pleaseā¦ let us prioritize proper fixes.
The āNew firmware version is availableā shown here does not refer exclusively to the ESP32-D0WDR2-V3 firmware version; it also includes the version of the EFR32MG24. The version prompt appears in your case because the EFR32MG24 on your device is not yet running the most up-to-date firmware.
Hi,
Iām running on BETA 1.0.8 and the network collapsed tonigh (about a month of operation, then freeze) Iām powering up the unit form POE and Zigbee2MQTT is connected via TCP.
I bet the problem is in the TCP to Serial software component. The old Dongle-E serial never had an issue in years.
I Installed custom Zigbee firmware version 8.2.2 that works fine in the Dongle-E
I like the capacity to connect to the dongle via TCP/IP so I can configure Zigbee2MQTT VM in High Availability in Proxmox and migrate it to a new server when needed. So Iāll continue using it despite it is far worst than the old one.
My Zigbee network contains 111 devices. But this is not an issue. Low LQI exists also on some devices but that is a complete separate issue
So how you got it back working?
Yes, when the dongle-D is freeze it has to be power cycle and it goes back to work
It just happened again tonight. The Coordinator freezes and Iād to manually power cycle. I canāt use a not reliable Zigbee Coordinator so This is starting to be critical for me.
What solutions are there? What coordinator can I use? Iām thinking on plugging in the old model-e to a RPI and use socat to offer it via tcp/ip port
We have confirmed that the incorrect version prompt is indeed a bug. We will arrange to fix it in an upcoming beta release and merge the fix into a stable version when appropriate. We sincerely apologize for the inconvenience and the poor experience this has caused.
When the device freezes, could you please press the button on the dongle and observe how the indicator light behaves?
Also, please provide the Zigbee2MQTT logs captured at the time of the freeze. We will use the logs to help identify the cause of the issue.
Hi SuiKa,
I am sending the full log from dongle and Z2M
https://drive.google.com/drive/folders/1N9e2aGqxwGjlHCsR3cXIhrWR9IK9youO?usp=share_link
It has not happened tonight.
When the problem occurs last night, the light was blinking blue. Then I power cycle and, after some time, it went solid blue and everything was ok after that. The next time Iāll use the button at the unit as suggested. Let me share couple of additional comments in the event they are useful for you.
When I enable the the log facilities, the log file is sent back to the host after it reaches 10Mb. This takes a bit longer than 1 hour. Iām afraid it wont be possible to use that facility to capture the freeze issue as it does not have a specific source. It is random.
I also notice there are 38 pages with notifications. The notifications log canāt be downloaded (AFAIK).
This is the first page that I see in the notifications log:
[2026-04-07 19:54:36]
HA/Zigbee2MQTT connected
[2026-04-07 19:54:25]
HA/Zigbee2MQTT disconnected. Please check your network and HA/Zigbee2MQTT configuration.
[2026-04-07 19:52:58]
The device has been assigned a new IP: 192.168.1.47.
[2026-04-07 19:52:57]
HA/Zigbee2MQTT connected
[2026-04-07 19:52:53]
The device has been assigned a new IP: 169.254.88.154.
[2026-04-07 19:52:44]
HA/Zigbee2MQTT disconnected. Please check your network and HA/Zigbee2MQTT configuration.
[2026-04-07 08:02:15]
HA/Zigbee2MQTT connected
[2026-04-07 08:02:04]
HA/Zigbee2MQTT disconnected. Please check your network and HA/Zigbee2MQTT configuration.
[2026-04-07 08:00:36]
HA/Zigbee2MQTT connected
[2026-04-07 08:00:34]
HA/Zigbee2MQTT disconnected. Please check your network and HA/Zigbee2MQTT configuration.
As you can see, there are also random network disconnections. Maybe the freeze is due to a disconnection not properly recovered!
The Dongle is powered via POE. And Iām not using WIFI not using the USB connection. Just the Ethernet cable.
The switch the Dongle is connected to is a Cisco C1300-48MGP-4X (not a bad unitā¦) it provides POE to 3 devices in total, one of them is the Dongle-M and total watts capacity is 740 W. The power consumption is less than 10 W.
Analysing the last disconnection issue, the switch log matches the dongle-m when it disconnects and reconnects.
2147483321 2026-Apr-07 19:52:50 Warning %STP-W-PORTSTATUS: gi1/0/6: STP status Forwarding
2147483322 2026-Apr-07 19:52:46 Informational %LINK-I-Up: gi1/0/6
2147483323 2026-Apr-07 19:52:42 Warning %LINK-W-Down: gi1/0/6
But I doubt the problem is at the Switch side as it is powering other 2 devices that are not suffering random disconnections.
I hope this information is useful for you. Let me know if there are possibilities to upload a firmware with additional log capabilities.
Regards
Ignacio
After reviewing the logs, we suspect that there are duplicate Zigbee network addresses in your Zigbee network. The conflict between the two devices using the same address is causing Zigbee2MQTT to restart.
At the moment, the conflicting address we can see is 0 (0 is the coordinatorās address), which means that there appear to be two devices in your Zigbee network using Zigbee network address 0.
Could you please check whether this is the case in your Zigbee network? You may refer to the image below for the location of the network address.
I think i got the same issue yesterday morning
Just restarted it by unplugging/replugging poe cable and back online.
logs looked like yours.
1 Like
At the moment, we suspect that the issue may be related to PoE power supply, but we are still investigating and testing. Since we are unable to fully replicate your usage environment, it may take some time before we can reach a definitive conclusion.
Could you please try switching to a different network port, or use USB power instead and run it for a period of time?
- If it runs stably, we can confirm that the issue is related to PoE power.
- If the issue still occurs, please also download and provide the corresponding debug logs and Zigbee2MQTT logs to us. We will proceed with further investigation as soon as possible.
Similarly, we suspect that the issue may be related to PoE power supply. Please follow the instructions in my previous post and try switching the power supply method to help us further investigate the cause of the issue.
We sincerely apologize for the inconvenience this has caused, and we truly appreciate your cooperation.
1 Like