Error: ZCL command genOnOff.on

[rw-django-fan-2020]

What happened?

My Home Assistant System crashed. Dont know why. Had to move to another Device (ThinClient). Restored my Home Assistant Backup. But zigbee dont work anymore. Help.

What did you expect to happen?

I expected it to work.

How to reproduce it (minimal and precise)

No response

Zigbee2MQTT version

1.36.1-1

Adapter firmware version

0x26780700

Adapter

ConBee2/RaspBee2

Setup

Add-on on Home Assistant OS on Proxmox VM

Debug log

error 2024-04-12 00:24:18Publish 'set' 'state' to 'Blitzwolf Steckdose 2' failed: 'Error: ZCL command 0x3425b4fffe4984d2/1 genOnOff.on({}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (no response received (76))'
debug 2024-04-12 00:24:18Error: ZCL command 0x3425b4fffe4984d2/1 genOnOff.on({}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (no response received (76)) at DeconzAdapter.sendZclFrameToEndpoint (/app/node_modules/zigbee-herdsman/src/adapter/deconz/adapter/deconzAdapter.ts:666:23) at Request.send (/app/node_modules/zigbee-herdsman/src/controller/helpers/request.ts:79:20) at Endpoint.zclCommand (/app/node_modules/zigbee-herdsman/src/controller/model/endpoint.ts:760:28) at Endpoint.command (/app/node_modules/zigbee-herdsman/src/controller/model/endpoint.ts:591:24) at Object.convertSet (/app/node_modules/zigbee-herdsman-converters/src/converters/toZigbee.ts:46:17) at Publish.onMQTTMessage (/app/lib/extension/publish.ts:259:36) at EventEmitter.wrappedCallback (/app/lib/eventBus.ts:174:17)

[robertomontinaro80]

Similar error for me for that getonoff command after the update
I can't turn on any lamp in my home.
I add also this error stack trace if it can help

18Publish 'set' 'state' to 'osram_kitchen_lamp' failed: 'Error: ZCL command 0x7cb03eaa0a038452/3 genOnOff.on({}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Data request failed with error: 'No network route' (205))'

[gentleman1979]

Similar problems for a few days
Zigbee2MQTT:error 2024-04-12 22:25:07: Publish 'set' 'state' to 'SFZ-Wand-rechts' failed: 'Error: ZCL command 0x00178801037e0089/11 genOnOff.off({}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Data request failed with error: 'MAC channel access failure' (225))'

[albert-canfield]

Similar issue too with a SONOFF ZBMINIL2 switch.

Publish 'set' 'state' to 'Entrance lights' failed: 'Error: ZCL command 0x0ceff6fffe16f9fb/1 genOnOff.on({}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Timeout - 33295 - 1 - 36 - 6 - 11 after 10000ms)'

[majkers]

Same here. I updated to 1.36.1-1 from 1.35.2-1 because I wanted to test #21162

Publish 'set' 'state' to 'gniazdko_xiaomi' failed: 'Error: Command 0x00158d0002347282/1 genOnOff.off({}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (no response received (16))'

Publish 'set' 'state' to 'gniazdko_neo' failed: 'Error: Command 0xa4c1389a7623f41a/1 genOnOff.off({}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (no response received (17))'

They are Xiaomi ZNCZ02LM and Tuya TS011F_plug_1

[robertomontinaro80]

Same here. I updated to 1.36.1-1 from 1.35.2-1 because I wanted to test #21162

Publish 'set' 'state' to 'gniazdko_xiaomi' failed: 'Error: Command 0x00158d0002347282/1 genOnOff.off({}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (no response received (16))'

Publish 'set' 'state' to 'gniazdko_neo' failed: 'Error: Command 0xa4c1389a7623f41a/1 genOnOff.off({}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (no response received (17))'

They are Xiaomi ZNCZ02LM and Tuya TS011F_plug_1

For me ver 1.36.0 works fine. 1.36.1 does not.

[hyteplus]

Similar issue

[Pepeuch]

Similaire issue with conbee 2 hassos supervised on rpi4 8go.

[blakefrain]

I am having the same issue conbee 2 and multiple connected devices

[vencakratky]

Similar Issue with Immax bulbs

[Langhii]

Me too

[galant-ho]

Having similar issue with my Aqara E1 Roller Shade Driver starting last week. Thought it was my setting issue so repair it several times. The E1 paired successfully, able to control the blind for certain times until the next day, lost control from HA.

2024-04-17 08:03:54Publish 'set' 'state' to 'E1-blind' failed: 'Error: ZCL command 0x54ef4410009ff334/1 genAnalogOutput.write({"presentValue":0}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Timeout - 47747 - 1 - 208 - 13 - 4 after 10000ms)'

[shanec42]

I've got the same problem as others above. Here's the important failure, but I'm including the full log just in case it helps.
log.txt

Zigbee2MQTT version [1.36.1] (https://github.com/Koenkk/zigbee2mqtt/releases/tag/1.36.1) commit: ffc2ff1
Coordinator type zStack3x0
Coordinator revision 20230507
Coordinator IEEE Address 0x00124b002a2f28c2
Frontend version 0.6.161
zigbee_herdsman_converters_version 19.11.2
zigbee_herdsman_version 0.40.3

debug 2024-04-17 20:17:19: Received MQTT message on 'zigbee2mqtt/Office Ceiling Light 4/set' with data '{"state":"OFF"}'
debug 2024-04-17 20:17:19: Publishing 'set' 'state' to 'Office Ceiling Light 4'
error 2024-04-17 20:17:42: Publish 'set' 'state' to 'Office Ceiling Light 4' failed: 'Error: ZCL command 0xb0ce18140352fa2f/1 genOnOff.off({}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Timeout - 53320 - 1 - 64 - 6 - 11 after 10000ms)'
debug 2024-04-17 20:17:42: Error: ZCL command 0xb0ce18140352fa2f/1 genOnOff.off({}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Timeout - 53320 - 1 - 64 - 6 - 11 after 10000ms)
at Object.start (/app/node_modules/zigbee-herdsman/src/utils/waitress.ts:63:23)
at ZStackAdapter.sendZclFrameToEndpointInternal (/app/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:499:47)
at Queue.execute (/app/node_modules/zigbee-herdsman/src/utils/queue.ts:35:20)
at Request.send (/app/node_modules/zigbee-herdsman/src/controller/helpers/request.ts:79:20)
at Endpoint.zclCommand (/app/node_modules/zigbee-herdsman/src/controller/model/endpoint.ts:760:28)
at Endpoint.command (/app/node_modules/zigbee-herdsman/src/controller/model/endpoint.ts:591:24)
at Object.convertSet (/app/node_modules/zigbee-herdsman-converters/src/converters/toZigbee.ts:46:17)
at Object.convertSet (/app/node_modules/zigbee-herdsman-converters/src/converters/toZigbee.ts:1129:32)
at Publish.onMQTTMessage (/app/lib/extension/publish.ts:259:36)
at EventEmitter.wrappedCallback (/app/lib/eventBus.ts:174:17)

[siddharthghiya]

Hi, I was having the same issue where I restored my HA installation from a backup. Zigbee stopped working. I also had individual add-on backups, and things started working again after I downgraded zigbee2mqtt from 1.36.1-1 to 1.36.0-1.

It started working again after downgrading to 1.36.0-1 and then I upgraded back to 1.36.1-1. Hope this helps!

[Aposei]

Seems like the same problem to me.
zigbee2mqtt 1.36.1-1

I'm using the plugin in HA and I don't have a backup for version 1.36.0-1

Error 2024-04-20 14:19:20Publish 'set' 'state' to 'Plancha' failed: 'Error: ZCL command 0xa4c138e4e6ae7bd2/1 genOnOff.on({}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Timeout - 43659 - 1 - 76 - 6 - 11 after 10000ms)' Debug 2024-04-20 14:19:20Error: ZCL command 0xa4c138e4e6ae7bd2/1 genOnOff.on({}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Timeout - 43659 - 1 - 76 - 6 - 11 after 10000ms) at Object.start (/app/node_modules/zigbee-herdsman/src/utils/waitress.ts:63:23) at EZSPAdapter.sendZclFrameToEndpointInternal (/app/node_modules/zigbee-herdsman/src/adapter/ezsp/adapter/ezspAdapter.ts:492:47) at Queue.execute (/app/node_modules/zigbee-herdsman/src/utils/queue.ts:35:20) at Request.send (/app/node_modules/zigbee-herdsman/src/controller/helpers/request.ts:79:20) at Endpoint.zclCommand (/app/node_modules/zigbee-herdsman/src/controller/model/endpoint.ts:760:28) at Endpoint.command (/app/node_modules/zigbee-herdsman/src/controller/model/endpoint.ts:591:24) at Object.convertSet (/app/node_modules/zigbee-herdsman-converters/src/converters/toZigbee.ts:46:17) at Publish.onMQTTMessage (/app/lib/extension/publish.ts:259:36) at EventEmitter.wrappedCallback (/app/lib/eventBus.ts:174:17)

[bezdekf]

The same problem:

Zigbee2MQTT:error 2024-04-20 16:43:04: Publish 'set' 'state' to 'IKEA 3' failed: 'Error: ZCL command 0xcc86ecfffe8d422e/1 genOnOff.off({}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Data request failed with error: 'No network route' (205))'
Zigbee2MQTT:error 2024-04-20 16:43:06: Publish 'set' 'state' to 'WOOX 1' failed: 'Error: ZCL command 0x588e81fffede3426/1 genOnOff.off({}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Data request failed with error: 'No network route' (205))'

etc

[paboman]

same here:

Failed to configure '0xa4c1387bc939184d', attempt 2 (Error: ZCL command 0xa4c1387bc939184d/1 haElectricalMeasurement.configReport([{"attribute":"rmsCurrent","minimumReportInterval":5,"maximumReportInterval":3600,"reportableChange":50}], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Data request failed with error: 'MAC no ack' (233)) at ZStackAdapter.sendZclFrameToEndpointInternal (/app/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:415:23) at processTicksAndRejections (node:internal/process/task_queues:95:5) at Queue.execute (/app/node_modules/zigbee-herdsman/src/utils/queue.ts:35:20) at Request.send (/app/node_modules/zigbee-herdsman/src/controller/helpers/request.ts:79:20) at Endpoint.zclCommand (/app/node_modules/zigbee-herdsman/src/controller/model/endpoint.ts:760:28) at Endpoint.configureReporting (/app/node_modules/zigbee-herdsman/src/controller/model/endpoint.ts:561:9) at Object.rmsCurrent (/app/node_modules/zigbee-herdsman-converters/src/lib/reporting.ts:216:5) at configure (/app/node_modules/zigbee-herdsman-converters/src/devices/tuya.ts:3773:13) at Object.configure (/app/node_modules/zigbee-herdsman-converters/src/index.ts:162:21) at Configure.configure (/app/lib/extension/configure.ts:122:13))

[bezdekf]

The same problem:

Zigbee2MQTT:error 2024-04-20 16:43:04: Publish 'set' 'state' to 'IKEA 3' failed: 'Error: ZCL command 0xcc86ecfffe8d422e/1 genOnOff.off({}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Data request failed with error: 'No network route' (205))' Zigbee2MQTT:error 2024-04-20 16:43:06: Publish 'set' 'state' to 'WOOX 1' failed: 'Error: ZCL command 0x588e81fffede3426/1 genOnOff.off({}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Data request failed with error: 'No network route' (205))'

etc

I didn't change anything and suddenly after 2 days everything works. But just to be sure, I'm switching from the not recommended CC 2531 to the SONOFF ZB Dongle-P Zigbee 3.0

[Pepeuch]

Est il possible d’avoir une réponse à cette erreur qui est récurrente et surtout qui bloque tout fonctionnement? Par avance merci

[mhzawadi]

I now have this issue too, was working fine till a stop and start of the z2m.

2024-04-21 10:31:22Publish 'set' 'state' to '01 - switch - mbed' failed: 'Error: ZCL command 0x00124b00246cb0b6/1 genOnOff.on({}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (no response received (70))'

Conbee2 in a Pi 4

DEVLINKS: >-
  /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2436161-if00
  /dev/serial/by-path/platform-fd500000.pcie-pci-0000:01:00.0-usb-0:1.2:1.0
DEVNAME: /dev/ttyACM0
DEVPATH: >-
  /devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.2/1-1.2:1.0/tty/ttyACM0
ID_BUS: usb
ID_MODEL: ConBee_II
ID_MODEL_ENC: ConBee\x20II
ID_MODEL_ID: '0030'
ID_PATH: platform-fd500000.pcie-pci-0000:01:00.0-usb-0:1.2:1.0
ID_PATH_TAG: platform-fd500000_pcie-pci-0000_01_00_0-usb-0_1_2_1_0
ID_REVISION: '0100'
ID_SERIAL: dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2436161
ID_SERIAL_SHORT: DE2436161
ID_TYPE: generic
ID_USB_DRIVER: cdc_acm
ID_USB_INTERFACES: ':020201:0a0000:'
ID_USB_INTERFACE_NUM: '00'
ID_USB_MODEL: ConBee_II
ID_USB_MODEL_ENC: ConBee\x20II
ID_USB_MODEL_ID: '0030'
ID_USB_REVISION: '0100'
ID_USB_SERIAL: dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2436161
ID_USB_SERIAL_SHORT: DE2436161
ID_USB_TYPE: generic
ID_USB_VENDOR: dresden_elektronik_ingenieurtechnik_GmbH
ID_USB_VENDOR_ENC: dresden\x20elektronik\x20ingenieurtechnik\x20GmbH
ID_USB_VENDOR_ID: 1cf1
ID_VENDOR: dresden_elektronik_ingenieurtechnik_GmbH
ID_VENDOR_ENC: dresden\x20elektronik\x20ingenieurtechnik\x20GmbH
ID_VENDOR_ID: 1cf1
MAJOR: '166'
MINOR: '0'
SUBSYSTEM: tty
TAGS: ':systemd:'
USEC_INITIALIZED: '1797972056257'

[gregorth]

The same issuse started on 1.36.1
I've moved back to 1.36 but the issue exists:
zigbee2mqtt | Zigbee2MQTT:debug 2024-04-22 16:10:54: Error: Command 0x84fd27fffee27a55/1 genOnOff.on({}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Timeout - 55120 - 1 - 13 - 6 - 11 after 10000ms) zigbee2mqtt | at Object.start (/app/node_modules/zigbee-herdsman/src/utils/waitress.ts:63:23) zigbee2mqtt | at ZStackAdapter.sendZclFrameToEndpointInternal (/app/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:499:47) zigbee2mqtt | at processTicksAndRejections (node:internal/process/task_queues:95:5) zigbee2mqtt | at Queue.execute (/app/node_modules/zigbee-herdsman/src/utils/queue.ts:35:20) zigbee2mqtt | at Request.send (/app/node_modules/zigbee-herdsman/src/controller/helpers/request.ts:79:20) zigbee2mqtt | at Endpoint.command (/app/node_modules/zigbee-herdsman/src/controller/model/endpoint.ts:746:28) zigbee2mqtt | at Object.convertSet (/app/node_modules/zigbee-herdsman-converters/src/converters/toZigbee.ts:46:17) zigbee2mqtt | at Object.convertSet (/app/node_modules/zigbee-herdsman-converters/src/converters/toZigbee.ts:3242:28) zigbee2mqtt | at Publish.onMQTTMessage (/app/lib/extension/publish.ts:259:36) zigbee2mqtt | at EventEmitter.wrappedCallback (/app/lib/eventBus.ts:174:17)

device

Zigbee 3.0 smart light switch module 2 gang (BW-SS7_2gang)
producent: BlitzWolf

logs attached
mqtt-e9c00b799d38e6cea56d6ca67013c4a7-0x84fd27fffee27a55-cfb76b68aa064a467d78c69ab1342f1f.json

[DiegoJp]

Same behaviour with a ZB-GW04 v1.2 (latest fw: v7.4.1.0) and some Tuya lightbulbs: TS0505B_1_1 and TS0505B_2_1

[galant-ho]

Does anyone here have this error with SONOFF Zigbee dongle-P?

I am trying to understand if this is an isolated issue with ConBee2/RaspBee2. If so then it's something else I need to resolve with my SONOFF Zigbee dongle-P.

[paveltsytovich]

Have the same issue with TS0002 (model _TZ3000_fisb3ajo) 2 gang switch module

Publish 'get' 'power_on_behavior' to 'Bathroom_Switch' failed: 'Error: ZCL command 0xa4c13873a4df1d0c/1 genOnOff.read(["moesStartUpOnOff"], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Timeout - 391 - 1 - 5 - 6 - 1 after 10000ms)'

Actual version 1.36. Coordinator Sonoff dongle E

[shanec42]

Does anyone here have this error with SONOFF Zigbee dongle-P?

I am trying to understand if this is an isolated issue with ConBee2/RaspBee2. If so then it's something else I need to resolve with my SONOFF Zigbee dongle-P.

Yes. I ran into the errors while running the "Sonoff Zigbee 3.0 USB Dongle Plus" (idVendor=10c4, idProduct=ea60) which I believe is identical.

[remcotjeerdsma]

Migrated my Zigbee network on a Conbee 2 from Deconz to Zigbee2Mqtt this weekend. Now none of my lamps work anymore because of this. Seems to have started after an unintended shutdown of HassOS and with it Zigbee2Mqtt.

[majkers]

I've just migrated from Conbee II to Sonoff dongle P and after abour 18 hours just got an error:

error 2024-04-25 12:02:45: Publish 'set' 'state' to 'gniazdko_xiaomi' failed: 'Error: ZCL command 0x00158d0002347282/1 genOnOff.off({}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Timeout - 18793 - 1 - 158 - 6 - 11 after 10000ms)'

You can see in my previous post #22189 (comment) with Conbee that the error was a bit different but more or less the same. So it is not a matter of dongle I guess

[Trzinka]

The same problem:

[11:46:25] INFO: Preparing to start...
[11:46:25] INFO: Socat not enabled
[11:46:26] INFO: Starting Zigbee2MQTT...
Zigbee2MQTT:error 2024-04-26 11:47:18: Failed to read state of 'Me-HoRa' after reconnect (ZCL command 0x94deb8fffe4c0d2a/1 genOnOff.read(["onOff"], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Data request failed with error: 'MAC channel access failure' (225)))
Zigbee2MQTT:error 2024-04-26 11:47:21: Failed to read state of 'Me-Sk' after reconnect (ZCL command 0x94deb8fffe314afe/1 genOnOff.read(["onOff"], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Data request failed with error: 'MAC channel access failure' (225)))
Zigbee2MQTT:error 2024-04-26 12:20:40: Publish 'set' 'state' to 'Zs-Ho' failed: 'Error: ZCL command 0xa4c138104f2150a6/1 genOnOff.on({}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (SRSP - AF - dataRequest after 6000ms)'

After restarting, Z2M works for a while!

[vxav]

Same issue after downgrading to 1.36.0 and 1.35.3. It seems to be somewhat transient as it works again after a moment.

• I have 2 Tuya WHD02 with the problem. I can turn it on, but not off, fixed by pressing the physical switch.
• Once turned on and before pressing the switch (to "fix" it), the zbminil2 that is paired to it can no longer be controlled, other than that it works ok).
• I identified the issue with 2 WHD02 and a 3rd one works fine.
• The only diff I can tell is that the one that works has no end device connected to it. Other than that, not sure..
• Restarting z2m fixes the issue altogether for some time.

Zigbee2MQTT:error 2024-04-26 15:15:14: Publish 'set' 'state' to 'Light Ceiling Kitchen' failed: 'Error: Command 0xa4c1387e52c34552/1 genOnOff.off({}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Timeout - 17076 - 1 - 26 - 6 - 11 after 10000ms)'

Zigbee2MQTT:info  2024-04-26 15:15:14: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":"Publish 'set' 'state' to 'Light Ceiling Kitchen' failed: 'Error: Command 0xa4c1387e52c34552/1 genOnOff.off({}, {\"timeout\":10000,\"disableResponse\":false,\"disableRecovery\":false,\"disableDefaultResponse\":false,\"direction\":0,\"srcEndpoint\":null,\"reservedBits\":0,\"manufacturerCode\":null,\"transactionSequenceNumber\":null,\"writeUndiv\":false}) failed (Timeout - 17076 - 1 - 26 - 6 - 11 after 10000ms)'","meta":{"friendly_name":"Light Ceiling Kitchen"},"type":"zigbee_publish_error"}'

[rosicenko]

I use:

• Zigbee2MQTT 1.39.0
• ZBDongle-E with ncp-uart-hw-v7.4.3.0-zbdonglee-115200.gbl
• Ember driver

And this not solve my problems.

Exactly same issue here

[coolspot18]

Add me to the list. All routers will sporadically (every 10-14 days) become unavailable with that error. Only interim solution is restarting the HA host system. System runs on N100 box with HAOS and a ConBee II as coordinator.

Core 2024.7.1 Supervisor 2024.06.2 Operating System 12.4 Z2M 1.39.0 (within HA addon)

I'm running 1.39.1 and I experienced this issue for the first time - restarting the add-on seemed to also fix it, I did not need a full reboot.

[markus-fischbacher]

Same here:
Home Assistant 2024.7.4 on RPi 5
ConBee2
Z2M 1.39.1
Zigbee RGB light (TS0503B)

[codedesperate]

I just started getting this on 1.39.1. rolled back to 1.39.0 but error persists :( Tried rebooting didn't help.

[Tvojm100]

Same here: Home Assistant 2024.7.4 on RPi 5 ConBee2 Z2M 1.39.1 Zigbee RGB light (TS0503B)

My ZigBee network devices (20 odd) have been running fine for a couple of years. I actually last added a TS0503B and that works for me fine. This was a couple of days ago. But a few days before that, I added a QS-Zigbee-SEC01-U and that device gets the timeout error.

[NikoGrub]

Same issue with 1 smart plug with power monitoring.

Edit:
Just sent the plug back and ordered a DECT Plug from AVM.
It's much more expensive, but I don't want to waste my time with this sh...t.

[firstchair]

Also here, got different errors with genBasic.read and genOnOff.on

[Razor648]

i have the same issue since today.
Home Assistant 2024.7.4 on RPi 5
ZBDongle-E
Z2M 1.39.1

Devices not working :
ZBMINIL2, SNZB-04

zigbee2mqtt  | [2024-08-22 22:48:01] error:     z2m: Publish 'set' 'state' to 'Lumière Parking Garage ' failed: 'Error: ZCL command 0x0ceff6fffe1704ce/1 genOnOff.on({}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Delivery failed for {"profileId":260,"clusterId":6,"sourceEndpoint":1,"destinationEndpoint":1,"options":4160,"groupId":0,"sequence":230})'

[maxifaxi]

same issue since last week
Raspberry 4
Z2M add on 1.39.1
zStack3x0 20230507

Device E2112 IKEA, interview fails with various errors.

• Error: ZCL command
• no active endpoints
• Error: Interview failed because can not get node descriptor

Randomly I get this message:

• zh:controller: Failed to keep permit join alive: Error: SREQ '--> ZDO - mgmtPermitJoinReq

Troubleshooting
Tried channels 11, 15, 20 and 25
With / Without USB 2.0 cable
On USB 3.0 and 2.0 port
Different locations in the house

The device is recognized and I see the picture of the device in the dashboard but the interview fails.

Is there any update from developer side? Is this bug worked on?

[bartj12]

as a temporary fix I’m restarting Z2M twice a day (when no automations are running).

[xjikka]

I use SZLB-06 + HASS OS. After the update to 2.5.2, my devices started disconnecting and stopped responding - "Publish set state to ... failed". I tried flashing it to base opensource 0.9.9, it was slightly better, but it did the same thing (after a few hours the device stopped responding). So I did a flash to 2.3.6 (0.9.9 to 2.3.6 can be done over USB only). After flashing and restarting the Zigbee firmware returned to version 20221226 and since then /it was about a month ago/ everything is ok again.
If anyone has problems with disconnecting SZLB-06, it's useless to try 0.9.9., just try to return it to 2.3.6 (and thus return Zigbee to 20221226).

[nmusatov]

I confirm that downgrade zigbee to version 20221226 solved the same issue for my ZigStar Olizig coordinator regardless of z2m version.

[SayAndre]

I just lost the connection to my INNR SP120 plugs after the update.
How can I downgrade without destroying the connection to all other devices ? I tried to just restore a older backup but then, the addon never starts again, updating it back to 1.40.1 makes it work again, but the INNR SP120 Plugs are still not working anymore.

[mremedi2023]

Same here, you need to restart m2qtt permanently

[nmusatov]

Same here, you need to restart m2qtt permanently

Full HomeAssistant restart (including mqtt) didn't resolve the issue for me

[Baael]

After a year I updated zigbee2mqtt in perfectly working network of devices, and now nothing is working correctly anymore. I am spammed by this error. It seems it is random, not related to any specific device.

[bricololo44]

Similar problem for me, after upgrade to Zigbee2MQTT 1.40.1
Module TS0003 => Recognised as "TS0003_switch_module" : Working Good
Module TS0002 => Recognised as "TS0002_basic" : NOT WORKING since 1.40.1 ( Error ZCL genOnOff)
Module TS0004 => Recognised as "TS0004_basic" : NOT WORKING since 1.40.1 ( Error ZCL genOnOff)
Module are recognized but error during switching

[MairusuPawa]

Impacted as well

[leocotes]

Hello guys.

I have the same issue. I try to use ember with last firmware and zstack, and i have the same problem:

Products: ZB-TD5-RCW-GU10

[MichalKuzma21]

Same here with ZB-TD5-RCW-GU10

[infinicode]

I can confirm the issue with a Sonoff ZBDongle-P running Zigbee2MQTT v1.40.1, after upgrading the firmware to the latest version.

• With firmware CC1352P2_CC2652P_launchpad_coordinator_20240710.hex the problem is present.
• Downgrading to CC1352P2_CC2652P_launchpad_coordinator_20230507.hex solves the issue.

[jLemmings]

I have the exact same issue in my network.

Coordinator: SLZB-06, Firmware version: 20240710 v2.5.6
zigbee2mqtt: 1.40.1

[2024-10-07 17:16:34] error: 	z2m: Publish 'set' 'color_temp' to 'Office Light' failed: 'Error: ZCL command 0xa4c1382e9dd2da3e/1 lightingColorCtrl.moveToColorTemp({"colortemp":370,"transtime":0}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"reservedBits":0,"writeUndiv":false}) failed (Timeout - 12765 - 1 - 3 - 768 - 11 after 10000ms)'
[2024-10-07 17:16:57] error: 	z2m: Publish 'set' 'color_temp' to 'Office Light' failed: 'Error: ZCL command 0xa4c1382e9dd2da3e/1 lightingColorCtrl.moveToColorTemp({"colortemp":370,"transtime":0}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"reservedBits":0,"writeUndiv":false}) failed (Timeout - 12765 - 1 - 4 - 768 - 11 after 10000ms)'

[xjikka]

Here my results after about 2 months of testing.

Coordinator: SLZB-06

Zigbee2MQTT: 1.40.1 + ESP 2.3.6. + Zigbee 20221216 - after 1 month was everything OK

I've tried update Zigbee2MQTT: 1.40.2 - OK
I've tried update ESP to 2.5.6 - OK

I've tried update Zigbee to 20240710 - problem is back.
I've tried downgrade Zigbee to 20230507 - problem is gone, everything OK

After one week Zigbee2MQTT: 1.40.2 + ESP 2.5.6. + Zigbee 20230507- everything still OK

If anyone has "Publish failed" issues, I recommend trying to downgrade Zigbee to 20230507 or older. Everything other (ESP, Zigbee2MQTT) doesn't matter.

[xjikka]

Someone asked me how to downgrade Zigbee, here's how to do it on SZLB-06 via web admin

[majkers]

Downgrading to CC1352P2_CC2652P_launchpad_coordinator_20230507 doesn't solve the problem for me with my Sonoff ZBDongle-P running Zigbee2MQTT v1.40.2

[majkers]

Since this issue is closed, I think noone will help us. Can someone reopen this issue?

[paveltsytovich]

We can`t reopen this issue, have no permission. I suggest to create new issue. How could create new issue with full describe issue?

[majkers]

@rw-django-fan-2020 can You reopen this issue since it is not fixed?

[majkers]

OK I decided to open new issue #24375. Please reposrt your problems there from now on