Koenkk
OTA update fails with error: "Update failed (Device didn't respond to OTA request)"
What happened?
I'm trying to push a firmware update to a Salus SR600 model. “Checking for new updates” was successful and new firmware was detected. When you click the OTA "Update device firmware" button, the error message "Update failed (device did not respond to OTA request)" appears. The Salus SR600 is powered via mains power, restarting the device by disconnecting the power for a few seconds does not have the desired result.
What did you expect to happen?
I expected the OTA firmware update process to begin.
How to reproduce it (minimal and precise)
Click OTA "Update device firmware" button, wait 60 seconds for error
Zigbee2MQTT version
1.33.2
Adapter firmware version
20230507
Adapter
Slaesh's CC2652RB stick
Debug log
info 2023-11-29 14:58:09 Updating 'CV-ketel' to latest firmware info 2023-11-29 14:58:09 MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":"Updating 'CV-ketel' to latest firmware","meta":{"device":"CV-ketel","status":"update_in_progress"},"type":"ota_update"}' info 2023-11-29 14:58:09 MQTT publish: topic 'zigbee2mqtt/CV-ketel', payload '{"last_seen":"2023-11-29T14:58:36+01:00","linkquality":174,"power_on_behavior":null,"state":"ON","update":{"installed_version":538380576,"latest_version":538510357,"state":"available"},"update_available":true}' info 2023-11-29 14:59:09 MQTT publish: topic 'zigbee2mqtt/CV-ketel', payload '{"last_seen":"2023-11-29T14:58:36+01:00","linkquality":174,"power_on_behavior":null,"state":"ON","update":{"installed_version":538380576,"latest_version":538510357,"state":"available"},"update_available":true}' info 2023-11-29 14:59:09 MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":"Update of 'CV-ketel' failed (Device didn't respond to OTA request)","meta":{"device":"CV-ketel","status":"update_failed"},"type":"ota_update"}' info 2023-11-29 14:59:09 MQTT publish: topic 'zigbee2mqtt/bridge/response/device/ota_update/update', payload '{"data":{"id":"CV-ketel"},"error":"Update of 'CV-ketel' failed (Device didn't respond to OTA request)","status":"error","transaction":"vdw7p-1"}' error 2023-11-29 14:59:09 Update of 'CV-ketel' failed (Device didn't respond to OTA request)
same problem
same problem with bticino K4003C. Z2m version: 1.34 CORE version 2023.11.03 SUPERVISOR version 2023.11.6 even after turning off the power for a few seconds it still gives an error: device did not respond to OTA request
same problem with legrand 067773 and 067774 Z2M: 1.35.1-dev commit: ef84ff8 EZSP v7 coordinator (hacked tuya gateway) HA 2023.12.0
Hi Z2M 1.36.1 Legrand device 067774 (wireless double hangs) with 24 firmware A firmware is ready in Z2M but update don't working. The update don't start...
https://github.com/home-assistant/core/issues/110103#issuecomment-2041526310
Hi all, hi @Nerivec
Since upgrade Z2M to 1.39.0 (using Ember driver on Sonoff Dongle E), I no longer have the "device dodn't respond to OTA").
But I have now the following message :
zh:ember: ~x~> [ZCL to=2225] Failed to send request with status=MESSAGE_TOO_LONG.
Note I had upgraded sucessfully 412171, 067771 Legrand device this morning.
I already have a problem for :
- 067773 wireless simple switch (object of this post and fews line upstairs)
- 067774 double gangs wireless => update go to 100% but the device isn't upgraded
- 064873 home away wireless
Are these devices with "message too long" farther away from the coordinator? It could happen if the devices are nested too deeply (as in "device > router > router > ... > coordinator"). Since ZigBee needs some overhead to get messages to the destination, that can eat away at the possible payload size (which OTA tends to push close to the limit).
067773 with 3c firmware are still getting Update failed (device did not respond to OTA request) z2m 1.39.0-dev commit: [addc238]