Addon keeps on crashing and restarting

[mbrucher]

Description of the issue

The addon keeps on crashing and restarting. I think it's related to the latest upgrade, or a recent one, as the addon was stable for a long time before this.
For instance:

Starting Zigbee2MQTT without watchdog.
[2024-11-03 16:14:20] error: 	zh:ember:uart:ash: Received ERROR from adapter while connecting, with code=RESET_WATCHDOG.
[2024-11-03 16:15:28] error: 	z2m: Publish 'set' 'state' to '0xa4c138de5c48acae' failed: 'Error: ZCL command 0xa4c138de5c48acae/1 genOnOff.off({}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"reservedBits":0,"writeUndiv":false}) failed (Delivery failed for '37278'.)'
[2024-11-03 16:17:27] error: 	z2m: Failed to configure '0x282c02bfffebb207', attempt 1 (Error: Bind 0x282c02bfffebb207/1 msTemperatureMeasurement from '0xbc026efffe24c587/1' failed (Delivery failed for '35997'.)
    at EmberOneWaitress.deliveryFailedFor (/app/node_modules/zigbee-herdsman/src/adapter/ember/adapter/oneWaitress.ts:100:31)
    at EmberAdapter.onMessageSent (/app/node_modules/zigbee-herdsman/src/adapter/ember/adapter/emberAdapter.ts:469:42)
    at Ezsp.emit (node:events:519:28)
    at Ezsp.ezspMessageSentHandler (/app/node_modules/zigbee-herdsman/src/adapter/ember/ezsp/ezsp.ts:5032:14)
    at Ezsp.callbackDispatch (/app/node_modules/zigbee-herdsman/src/adapter/ember/ezsp/ezsp.ts:735:26)
    at Ezsp.onAshFrame (/app/node_modules/zigbee-herdsman/src/adapter/ember/ezsp/ezsp.ts:395:22)
    at UartAsh.emit (node:events:519:28)
    at Immediate.<anonymous> (/app/node_modules/zigbee-herdsman/src/adapter/ember/uart/ash.ts:1169:45)
    at processImmediate (node:internal/timers:478:21))
[2024-11-03 16:19:40] error: 	z2m: Failed to configure '0x282c02bfffebb3c1', attempt 1 (Error: Bind 0x282c02bfffebb3c1/1 msTemperatureMeasurement from '0xbc026efffe24c587/1' failed (Delivery failed for '7735'.)
    at EmberOneWaitress.deliveryFailedFor (/app/node_modules/zigbee-herdsman/src/adapter/ember/adapter/oneWaitress.ts:100:31)
    at EmberAdapter.onMessageSent (/app/node_modules/zigbee-herdsman/src/adapter/ember/adapter/emberAdapter.ts:469:42)
    at Ezsp.emit (node:events:519:28)
    at Ezsp.ezspMessageSentHandler (/app/node_modules/zigbee-herdsman/src/adapter/ember/ezsp/ezsp.ts:5032:14)
    at Ezsp.callbackDispatch (/app/node_modules/zigbee-herdsman/src/adapter/ember/ezsp/ezsp.ts:735:26)
    at Ezsp.onAshFrame (/app/node_modules/zigbee-herdsman/src/adapter/ember/ezsp/ezsp.ts:395:22)
    at UartAsh.emit (node:events:519:28)
    at Immediate.<anonymous> (/app/node_modules/zigbee-herdsman/src/adapter/ember/uart/ash.ts:1169:45)
    at processImmediate (node:internal/timers:478:21))
[2024-11-03 16:21:08] error: 	z2m: Failed to read state of '0xa4c13867d1e82b5b' after reconnect (ZCL command 0xa4c13867d1e82b5b/1 genOnOff.read(["onOff"], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"reservedBits":0,"writeUndiv":false}) failed (Delivery failed for '35681'.))
[2024-11-03 16:21:57] error: 	z2m: Failed to read state of '0xa4c13867d1e82b5b' after reconnect (ZCL command 0xa4c13867d1e82b5b/1 genOnOff.read(["onOff"], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"reservedBits":0,"writeUndiv":false}) failed (Delivery failed for '35681'.))
[2024-11-03 16:25:13] error: 	z2m: Failed to configure '0x282c02bfffeaaed6', attempt 1 (Error: Bind 0x282c02bfffeaaed6/1 msTemperatureMeasurement from '0xbc026efffe24c587/1' failed (Delivery failed for '49381'.)
    at EmberOneWaitress.deliveryFailedFor (/app/node_modules/zigbee-herdsman/src/adapter/ember/adapter/oneWaitress.ts:100:31)
    at EmberAdapter.onMessageSent (/app/node_modules/zigbee-herdsman/src/adapter/ember/adapter/emberAdapter.ts:469:42)
    at Ezsp.emit (node:events:519:28)
    at Ezsp.ezspMessageSentHandler (/app/node_modules/zigbee-herdsman/src/adapter/ember/ezsp/ezsp.ts:5032:14)
    at Ezsp.callbackDispatch (/app/node_modules/zigbee-herdsman/src/adapter/ember/ezsp/ezsp.ts:735:26)
    at Ezsp.onAshFrame (/app/node_modules/zigbee-herdsman/src/adapter/ember/ezsp/ezsp.ts:395:22)
    at UartAsh.emit (node:events:519:28)
    at Immediate.<anonymous> (/app/node_modules/zigbee-herdsman/src/adapter/ember/uart/ash.ts:1169:45)
    at processImmediate (node:internal/timers:478:21))
[2024-11-03 16:25:40] error: 	z2m: Failed to configure '0x282c02bfffebb3c1', attempt 2 (Error: Bind 0x282c02bfffebb3c1/1 msTemperatureMeasurement from '0xbc026efffe24c587/1' failed (Delivery failed for '7735'.)
    at EmberOneWaitress.deliveryFailedFor (/app/node_modules/zigbee-herdsman/src/adapter/ember/adapter/oneWaitress.ts:100:31)
    at EmberAdapter.onMessageSent (/app/node_modules/zigbee-herdsman/src/adapter/ember/adapter/emberAdapter.ts:469:42)
    at Ezsp.emit (node:events:519:28)
    at Ezsp.ezspMessageSentHandler (/app/node_modules/zigbee-herdsman/src/adapter/ember/ezsp/ezsp.ts:5032:14)
    at Ezsp.callbackDispatch (/app/node_modules/zigbee-herdsman/src/adapter/ember/ezsp/ezsp.ts:735:26)
    at Ezsp.onAshFrame (/app/node_modules/zigbee-herdsman/src/adapter/ember/ezsp/ezsp.ts:395:22)
    at UartAsh.emit (node:events:519:28)
    at Immediate.<anonymous> (/app/node_modules/zigbee-herdsman/src/adapter/ember/uart/ash.ts:1169:45)
    at processImmediate (node:internal/timers:478:21))
[2024-11-03 16:25:46] error: 	z2m: Failed to read state of '0xa4c13867d1e82b5b' after reconnect (ZCL command 0xa4c13867d1e82b5b/1 genOnOff.read(["onOff"], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"reservedBits":0,"writeUndiv":false}) failed (Delivery failed for '35681'.))
[2024-11-03 16:26:18] error: 	zh:ember: Delivery of BROADCAST failed for '65533'.

This seems to be related to ThirdReality thermostats, but they were working properly before, so no reason for them to start failing to be configured?

Addon version

v1.41.0-1

Platform

ore 2024.10.4
Supervisor 2024.10.3
Operating System 13.2
Frontend 20241002.4

Logs of the issue (if applicable)

No response

[qbushome]

i'm not sure it this is related but eventually also in my case Zigbee2MQTT stops and restarts, all within 10 seconds.

`[2024-11-25 08:06:48] error: zh:ember:uart:ash: Port Error: read ECONNRESET

[2024-11-25 08:06:48] error: zh:ember: Adapter fatal error: ERROR_SERIAL_INIT

[2024-11-25 08:06:48] info: zh:ember:uart:ash: ASH COUNTERS since last clear:

[2024-11-25 08:06:48] info: zh:ember:uart:ash: Total frames: RX=163, TX=217

[2024-11-25 08:06:48] info: zh:ember:uart:ash: Cancelled : RX=0, TX=0

[2024-11-25 08:06:48] info: zh:ember:uart:ash: DATA frames : RX=162, TX=53
[2024-11-25 08:06:48] info: zh:ember:uart:ash: DATA bytes : RX=3579, TX=788
[2024-11-25 08:06:48] info: zh:ember:uart:ash: Retry frames: RX=0, TX=0
[2024-11-25 08:06:48] info: zh:ember:uart:ash: ACK frames : RX=0, TX=163
[2024-11-25 08:06:48] info: zh:ember:uart:ash: NAK frames : RX=0, TX=0
[2024-11-25 08:06:48] info: zh:ember:uart:ash: nRdy frames : RX=0, TX=0
[2024-11-25 08:06:48] info: zh:ember:uart:ash: CRC errors : RX=0
[2024-11-25 08:06:48] info: zh:ember:uart:ash: Comm errors : RX=0
[2024-11-25 08:06:48] info: zh:ember:uart:ash: Length < minimum: RX=0
[2024-11-25 08:06:48] info: zh:ember:uart:ash: Length > maximum: RX=0
[2024-11-25 08:06:48] info: zh:ember:uart:ash: Bad controls : RX=0
[2024-11-25 08:06:48] info: zh:ember:uart:ash: Bad lengths : RX=0
[2024-11-25 08:06:48] info: zh:ember:uart:ash: Bad ACK numbers : RX=0
[2024-11-25 08:06:48] info: zh:ember:uart:ash: Out of buffers : RX=0
[2024-11-25 08:06:48] info: zh:ember:uart:ash: Retry dupes : RX=0
[2024-11-25 08:06:48] info: zh:ember:uart:ash: Out of sequence : RX=0
[2024-11-25 08:06:48] info: zh:ember:uart:ash: ACK timeouts : RX=0
[2024-11-25 08:06:48] info: zh:ember:uart:ash: ======== ASH stopped ========
[2024-11-25 08:06:48] info: zh:ember:ezsp: ======== EZSP stopped ========
[2024-11-25 08:06:48] info: zh:ember: ======== Ember Adapter Stopped ========
[2024-11-25 08:06:48] error: z2m: Adapter disconnected, stopping
[2024-11-25 08:06:48] info: z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/bridge/state', payload '{"state":"offline"}'
[2024-11-25 08:06:48] info: z2m: Disconnecting from MQTT server
[2024-11-25 08:06:48] info: z2m: Stopping zigbee-herdsman...
[2024-11-25 08:06:48] info: z2m: Stopped zigbee-herdsman
[2024-11-25 08:06:48] info: z2m: Stopped Zigbee2MQTT
/app/node_modules/winston/node_modules/readable-stream/lib/_stream_writable.js:264
var er = new ERR_STREAM_WRITE_AFTER_END();
^
Error: write after end
at writeAfterEnd (/app/node_modules/winston/node_modules/readable-stream/lib/_stream_writable.js:264:12)
at DerivedLogger.Writable.write (/app/node_modules/winston/node_modules/readable-stream/lib/_stream_writable.js:300:21)
at DerivedLogger.log (/app/node_modules/winston/lib/winston/logger.js:231:12)
at Logger.log (/app/lib/util/logger.ts:198:25)
at Logger.info (/app/lib/util/logger.ts:211:14)
at UartAsh.onPortClose (/app/node_modules/zigbee-herdsman/src/adapter/ember/uart/ash.ts:547:16)
at Object.onceWrapper (node:events:634:26)
at Socket.emit (node:events:519:28)
at TCP. (node:net:338:12)
[08:06:55] INFO: Preparing to start...
[08:06:55] INFO: Socat not enabled
[08:06:55] INFO: Starting Zigbee2MQTT...
Starting Zigbee2MQTT without watchdog.
[2024-11-25 08:06:57] info: z2m: Logging to console, file (filename: log.log)
[2024-11-25 08:06:57] info: z2m: Starting Zigbee2MQTT version 1.41.0 (commit #unknown)
[2024-11-25 08:06:57] info: z2m: Starting zigbee-herdsman (2.1.7)
`

Frequency can be seen in screenshot below:
I have multiple temperature sensors. 2 for each room. I calculate the average and create a new sensor. The graph below is this average sensor.
Every time Zigbee2MQTT crashes, the Zigbee sensor reports '0', resulting in an average temperature of approx. half real temperature.

For my Zigbee buttons:
I have triggers in automations based on state change, the automation sees this crash as a button press, and 10 seconds later again.

Using an smlight slzb-06m, PoE powered

[Koenkk]

These looks like connection issues with the dongle, likely cannot be fixed from the Z2M side. Make sure that you don't have any other addons that use USB devices running (I would advise to stop all other addons and see if the issue is still there)