Stopped working suddenly

[tcheronneau]

What happened?

I'm using zigbee2mqtt for a while now and most of the time it works super well. But today all of the sudden it stopped working properly with a lot of : Zigbee2MQTT:error 2023-11-01 17:09:51: Publish 'set' 'state' to '0x001788010c6556c3' failed: 'Error: Command 0x001788010c6556c3/11 genOnOff.on({}, {"sendWhen":"immediate","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: 'undefined' (25))' Zigbee2MQTT:info 2023-11-01 17:09:51: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":"Publish 'set' 'state' to '0x001788010c6556c3' failed: 'Error: Command 0x001788010c6556c3/11 genOnOff.on({}, {\"sendWhen\":\"immediate\",\"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: 'undefined' (25))'","meta":{"friendly_name":"0x001788010c6556c3"},"type":"zigbee_publish_error"}'

From time to time it's still working but it's not viable. I've changed nothing in my setup recently.

This kind of problem already happened from time to time but normally I reset the adapter by flashing the firmware again but here it's not working. I got a big network (60 devices) but even those close to the adapters are not working. I was using the 20230507 firmware but I saw an issue saying to try the 20230923 so I did with no luck.

What did you expect to happen?

My lights to turn on directly.

How to reproduce it (minimal and precise)

Trying to stop / start lights.

Zigbee2MQTT version

1.33.1

Adapter firmware version

20230923

Adapter

SONOFF Zigbee 3.0 USB Dongle Plus ZBDongle-P

Debug log

info 2023-11-01 17:09:47: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":"Publish 'set' 'state' to '0x001788010c6556c3' failed: 'Error: Command 0x001788010c6556c3/11 genOnOff.off({}, {\"sendWhen\":\"immediate\",\"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: 'undefined' (25))'","meta":{"friendly_name":"0x001788010c6556c3"},"type":"zigbee_publish_error"}' error 2023-11-01 17:09:47: Publish 'set' 'state' to '0x001788010c6556c3' failed: 'Error: Command 0x001788010c6556c3/11 genOnOff.off({}, {"sendWhen":"immediate","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: 'undefined' (25))' info 2023-11-01 17:09:47: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":"Publish 'set' 'state' to '0x001788010c6556c3' failed: 'Error: Command 0x001788010c6556c3/11 genOnOff.off({}, {\"sendWhen\":\"immediate\",\"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: 'undefined' (25))'","meta":{"friendly_name":"0x001788010c6556c3"},"type":"zigbee_publish_error"}'

[mshamash]

I noticed the same today on my Home Assistant Yellow, using the built-in zigbee system. Suddenly stopped working for all devices, and can't reach them or do LQI queries to make a map. Restarting the Yellow didn't seem to fix anything, and everything is up to date – haven't made any changes for a few weeks...

[diegoweb]

Same here. Same adapter as yours. It stopped working today. Nothing is working in there. I can't turn on lights, light sockets, led controller, etc. Not even the link quality updates, so I pretty much have a static dashboard in z2m

[awudarowicz]

same here, almost everything stopped working 😱

[diegoweb]

I set z2m to debug mode and this is what I get when I try to refresh the state of any switch.

----EDIT OK! I disconnected my Adapter from the USB and did a power cycle. After HA started I reinserted the adapter into the USB and manually ran z2m. It's now working great.

Now I'm not sure if it's something in z2m code or if the USB got misconnected for some reason.

[merlinpimpim]

Hi, It's strange, I now have the same problem (with the Skyconnect coordinator) and more particularly certain devices (Nodon module, Ledvance socket...). And the strangest thing is that the problems are minimized when I run Z2M in debug mode (but in that case, watch out for the disk space consumed!). In the logs themselves, nothing extraordinary though (cf error message already posted above). I don't understand what exactly is going on!

Z2M=1.34.0

(I haven't yet tried the suggestion of booting HA without the USB key, then plugging it in and starting Z2M manually. Even if it worked, it wouldn't be very normal !).

[Koenkk]

@tcheronneau try the 20221226 firmware, both 20230507 and 20230923 might be unstable.

[tcheronneau]

Hey @Koenkk I also tried this one I think without success. In the end it came back after a day (without any action) so maybe it was linked to something in the environment (some interference or something).

[merlinpimpim]

Hot plugging the Skyconnect and then manually turning on ZM afterwards doesn't change the problem. 😒

For the record, here's what I see regularly:

Zigbee2MQTT:error 2023-13-12 20:59:09: Failed to configure 'ALLÉE - Portail - Module Nodon', attempt 1 (Error: Read 0x9035eafffed8d440/1 genOnOff(["nodonTransitionTime"], {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Status 'UNSUPPORTED_ATTRIBUTE') at Endpoint.checkStatus (/app/node_modules/zigbee-herdsman/src/controller/model/endpoint.ts:421:28) at Endpoint.read (/app/node_modules/zigbee-herdsman/src/controller/model/endpoint.ts:563:22) at processTicksAndRejections (node:internal/process/task_queues:96:5) at Object.configure (/app/node_modules/zigbee-herdsman-converters/src/devices/nodon.ts:55:13) at Configure.configure (/app/lib/extension/configure.ts:117:13) at Immediate.<anonymous> (/app/lib/extension/configure.ts:69:17))

It's this reference for information: https://www.zigbee2mqtt.io/devices/SIN-4-1-20.html

(And I think there's a specific problem with this model because Z2M constantly offers a higher OTA fw but it never applies and the official Android Nodon app that works via Bluetooth says I already have the latest firmware)

Warning 2024-01-09 15:16:26OTA: Firmware on '0x9035eafffed8d440' is newer than latest firmware online.

[lieblinger]

I found the solution for me... I've done a migration from Sonoff ZBDongle-E to ZBDongle-P afterwards I got exactly the same network issue... Then I checked the docs and found something very useful on the following page:

https://www.zigbee2mqtt.io/guide/usage/mqtt_topics_and_messages.html#zigbee2mqtt-bridge-request

With the coordinator_check mqtt request I got all routers which were not connected properly:

zigbee2mqtt/bridge/request/coordinator_check

After I was repairing them everything seems to be normal again.

[merlinpimpim]

According to the documentation, this command only works with Texas Instrument-based adapters (CC2652/CC1352).

[github-actions[bot]]

This issue is stale because it has been open 180 days with no activity. Remove stale label or comment or this will be closed in 30 days