Coordinator lost conection to zigbee network

[Olli2k]

Hey there, I could use some hints, because I'm literally sitting in the dark, while my wife is shouting at me.

My System:
Proxmox 8.2.8 > HA OS > Home Assistant 2024-11.3 > zigbee2mqtt as HA Addon (v1.41.0-1).

zigbee2mqtt is using a Conbee III as coordinator.
port: /dev/serial/by-id/usb-dresden_elektronik_ConBee_III_DE03216093-if00-port0
adapter: deconz
baudrate: 115200

I have about 40 zigbee devices registered and running without problems until today.

Today I did the HA core update to 2024.11.3 and after that I lost all my energy consumption in HA. So I decided to restore an backup, which was created before the update. Well.. it did not help with energy data and starting from this point (maybe I tried a couple of backups) my zigbee network was blown. z2m is starting without any problems and the adapter seems to work:

`[2024-11-22 20:36:19] info: z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/bridge/config', payload '{"commit":"unknown","coordinator":{"meta":{"maintrel":0,"majorrel":38,"minorrel":83,"product":0,"revision":"0x26530900","transportrev":0},"type":"ConBee3"},"log_level":"debug","network":{"channel":11,"extendedPanID":"0x3545e5584a8867fe","panID":43050},"permit_join":false,"version":"1.41.0"}'
[2024-11-22 20:36:19] debug: z2m: Discovering entities to Home Assistant in 5s
[2024-11-22 20:36:19] info: z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/bridge/state', payload 'online'
[2024-11-22 20:36:19] info: z2m: Zigbee2MQTT started!

[2024-11-22 20:37:16] debug: zh:deconz:frameparser: DATA_INDICATION RESPONSE - seqNr. 39 srcAddr: 0x0cae5ffffeda3e7b destAddr: 0xffff profile id: 0x0 cluster id: 0x0 lqi: 196
[2024-11-22 20:37:16] debug: zh:deconz:frameparser: response payload: 8b67470effff2e21000000
[2024-11-22 20:37:16] debug: zh:deconz:driver: networkstate: 2 apsDataConfirm: 0 apsDataIndication: 0 configChanged: 0 apsRequestFreeSlots: 1
[2024-11-22 20:37:16] debug: zh:deconz:frameparser: DATA_INDICATION RESPONSE - Error: Unsupported response reading for cluster ID '0'.
[2024-11-22 20:37:18] debug: zh:deconz:driver: send read device state from queue. seqNr: 40
`

But communication with network is not possible anymore. All devices go offline and my log is full of timeouts for every device. I did a reset for a power socket and tired to add it again, but this does not work as well. (I was testing this at its regular position and 20cm away from the conbee III) no communication is possible. I renamed my z2m config folder, to start with a new config, but even here is it not possible to pair my power socket.

So now I'm out of ideas, how to fix this and my wife will kill me soon. Has anyone a idea how to fix this mess?
Thx in advance!

Log for timeout at old config:

[2024-11-22 21:18:02] warning: 	z2m: Failed to ping 'Hue color lamp 1 Flur EG' (attempt 1/1, ZCL command 0x001788010c007a06/11 genBasic.read(["zclVersion"], {"timeout":10000,"disableResponse":false,"disableRecovery":true,"disableDefaultResponse":true,"direction":0,"reservedBits":0,"writeUndiv":false}) failed (no response received (8) Error: waiting for response TIMEOUT))
[2024-11-22 21:18:02] debug: 	z2m: Active device 'Hue color lamp 1 Flur EG' was last seen '367.20' minutes ago.
[2024-11-22 21:18:04] debug: 	zh:controller:endpoint: ZCL command 0x001788010c0a4c2d/11 genBasic.read(["zclVersion"], {"timeout":10000,"disableResponse":false,"disableRecovery":true,"disableDefaultResponse":true,"direction":0,"reservedBits":0,"writeUndiv":false})
[2024-11-22 21:18:04] debug: 	zh:deconz:driver: DATA_REQUEST - destAddr: 0x5642 EP:11 SeqNr. 45 request id: 9
[2024-11-22 21:18:04] debug: 	zh:deconz:frameparser: DATA_REQUEST RESPONSE - request id: 9 status: 0
[2024-11-22 21:18:04] debug: 	zh:deconz:driver: networkstate: 2 apsDataConfirm: 0 apsDataIndication: 0 configChanged: 0 apsRequestFreeSlots: 1
[2024-11-22 21:18:05] debug: 	zh:deconz:frameparser: DEVICE_STATE changed: 100110
[2024-11-22 21:18:05] debug: 	zh:deconz:driver: networkstate: 2 apsDataConfirm: 1 apsDataIndication: 0 configChanged: 0 apsRequestFreeSlots: 1
[2024-11-22 21:18:05] debug: 	zh:deconz:driver: query aps data confirm
[2024-11-22 21:18:05] debug: 	zh:deconz:driver: DATA_CONFIRM - sending data state request - SeqNr. 46
[2024-11-22 21:18:05] debug: 	zh:deconz:frameparser: DATA_CONFIRM RESPONSE - destAddr: 0x5642 request id: 9 confirm status: 0
[2024-11-22 21:18:05] debug: 	zh:deconz:driver: networkstate: 2 apsDataConfirm: 0 apsDataIndication: 0 configChanged: 0 apsRequestFreeSlots: 1
[2024-11-22 21:18:05] debug: 	zh:deconz: sendZclFrameToEndpoint - message send with transSeq Nr.: 9
[2024-11-22 21:18:05] debug: 	zh:deconz: true, true, false, 10000
[2024-11-22 21:18:05] debug: 	zh:deconz: resolve request (9)
[2024-11-22 21:18:09] debug: 	zh:deconz:driver: send read device state from queue. seqNr: 47
[2024-11-22 21:18:09] debug: 	zh:deconz:frameparser: device state: 100010
[2024-11-22 21:18:09] debug: 	zh:deconz:driver: networkstate: 2 apsDataConfirm: 0 apsDataIndication: 0 configChanged: 0 apsRequestFreeSlots: 1
[2024-11-22 21:18:14] debug: 	zh:controller:endpoint: Error: ZCL command 0x001788010c0a4c2d/11 genBasic.read(["zclVersion"], {"timeout":10000,"disableResponse":false,"disableRecovery":true,"disableDefaultResponse":true,"direction":0,"reservedBits":0,"writeUndiv":false}) failed (no response received (9) Error: waiting for response TIMEOUT)
    at DeconzAdapter.sendZclFrameToEndpoint (/app/node_modules/zigbee-herdsman/src/adapter/deconz/adapter/deconzAdapter.ts:485:19)
    at runNextTicks (node:internal/process/task_queues:60:5)
    at processTimers (node:internal/timers:511:9)
    at Request.send (/app/node_modules/zigbee-herdsman/src/controller/helpers/request.ts:82:20)
    at Endpoint.sendRequest (/app/node_modules/zigbee-herdsman/src/controller/model/endpoint.ts:325:20)
    at Endpoint.zclCommand (/app/node_modules/zigbee-herdsman/src/controller/model/endpoint.ts:951:28)
    at Endpoint.read (/app/node_modules/zigbee-herdsman/src/controller/model/endpoint.ts:446:29)
    at Device.ping (/app/node_modules/zigbee-herdsman/src/controller/model/device.ts:1259:9)
    at Availability.pingQueueExecuteNext (/app/lib/extension/availability.ts:94:17)
    at Availability.pingQueueExecuteNext (/app/lib/extension/availability.ts:124:9)

[TheDescender]

Seem to be experiencing the same problem with my UZG-01 coordinator. Honestly, I've been having issues with Z2M alot lately though.

[2025-01-27 18:35:21] debug: 	z2m:mqtt: Received MQTT message on 'zigbee2mqtt/Dinner Light/set' with data '{"state":"ON"}'
[2025-01-27 18:35:21] debug: 	z2m: Publishing 'set' 'state' to 'Dinner Light'
[2025-01-27 18:35:21] debug: 	zh:controller:endpoint: ZCL command 0x00178801030302a0/11 genOnOff.on({}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"reservedBits":0,"writeUndiv":false})
[2025-01-27 18:35:21] debug: 	zh:zstack: sendZclFrameToEndpointInternal 0x00178801030302a0:31431/11 (0,0,1)
[2025-01-27 18:35:21] debug: 	zh:zstack:znp: --> SREQ: AF - dataRequest - {"dstaddr":31431,"destendpoint":11,"srcendpoint":1,"clusterid":6,"transid":107,"options":0,"radius":30,"len":3,"data":{"type":"Buffer","data":[1,116,1]}}
[2025-01-27 18:35:21] debug: 	zh:zstack:unpi:writer: --> frame [254,13,36,1,199,122,11,1,6,0,107,0,30,3,1,116,1,155]
[2025-01-27 18:35:21] debug: 	zh:zstack:unpi:parser: <-- [254,1,100,1,2,102]
[2025-01-27 18:35:21] debug: 	zh:zstack:unpi:parser: --- parseNext [254,1,100,1,2,102]
[2025-01-27 18:35:21] debug: 	zh:zstack:unpi:parser: --> parsed 1 - 3 - 4 - 1 - [2] - 102
[2025-01-27 18:35:21] debug: 	zh:zstack:znp: <-- SRSP: AF - dataRequest - {"status":2}
[2025-01-27 18:35:21] debug: 	zh:zstack:unpi:parser: --- parseNext []
[2025-01-27 18:35:21] debug: 	zh:controller:endpoint: Error: ZCL command 0x00178801030302a0/11 genOnOff.on({}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"reservedBits":0,"writeUndiv":false}) failed (--> 'SREQ: AF - dataRequest - {"dstaddr":31431,"destendpoint":11,"srcendpoint":1,"clusterid":6,"transid":107,"options":0,"radius":30,"len":3,"data":{"type":"Buffer","data":[1,116,1]}}' failed with status '(0x02: INVALID_PARAM)' (expected '(0x00: SUCCESS)'))
    at /app/node_modules/.pnpm/zigbee-herdsman@3.2.1/node_modules/zigbee-herdsman/src/adapter/z-stack/znp/znp.ts:258:27
    at processTicksAndRejections (node:internal/process/task_queues:105:5)
    at Queue.execute (/app/node_modules/.pnpm/zigbee-herdsman@3.2.1/node_modules/zigbee-herdsman/src/utils/queue.ts:36:20)
    at ZStackAdapter.dataRequest (/app/node_modules/.pnpm/zigbee-herdsman@3.2.1/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:1046:9)
    at ZStackAdapter.sendZclFrameToEndpointInternal (/app/node_modules/.pnpm/zigbee-herdsman@3.2.1/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:509:35)
    at /app/node_modules/.pnpm/zigbee-herdsman@3.2.1/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:443:20
    at Queue.execute (/app/node_modules/.pnpm/zigbee-herdsman@3.2.1/node_modules/zigbee-herdsman/src/utils/queue.ts:36:20)
    at ZStackAdapter.sendZclFrameToEndpoint (/app/node_modules/.pnpm/zigbee-herdsman@3.2.1/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:441:16)
    at Request.send (/app/node_modules/.pnpm/zigbee-herdsman@3.2.1/node_modules/zigbee-herdsman/src/controller/helpers/request.ts:82:20)
    at Endpoint.sendRequest (/app/node_modules/.pnpm/zigbee-herdsman@3.2.1/node_modules/zigbee-herdsman/src/controller/model/endpoint.ts:324:20)

[Olli2k]

If i remember correctly, my problem was solved by waiting. Something destroyed my network, but it was self repairing. But until today I'm absolutely not satisfied with stability of my Zigbee network.

[TheDescender]

Wish I were that lucky.