OTA update fails with error: "Update failed (Device didn't respond to OTA request)"

[c0mplex1]

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)

[aspfirst]

same problem

[essegi65]

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

[muzzy124]

same problem with legrand 067773 and 067774
Z2M: 1.35.1-dev commit: ef84ff8
EZSP v7 coordinator (hacked tuya gateway)
HA 2023.12.0

[532910]

same issue with ikea E1745 motion sensor

[Loic691]

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...

[532910]

home-assistant/core#110103 (comment)

[kdkavanagh]

Same issue with all my inovelli blue switches

[Loic691]

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

[Nerivec]

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).

[muzzy124]

067773 with 3c firmware are still getting Update failed (device did not respond to OTA request)
z2m 1.39.0-dev commit: [addc238]

[github-actions]

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

[Mincka]

Not stale

[Nihvel]

Got the same error "Update failed (Device didn't respond to OTA request)" and fixed as follows:

1. Force remove the device from z2m and remove the batteries
2. Stop z2m
3. Add the 'ext_converter.js', because my device is a Ikea Styrbar and I followed the instructions here
4. Start z2m
5. Add the batteries and let it join the network (I like to rename the devices at this point and have them on Home Assistant with a friendly name)
6. Stop z2m and remove the batteries again

At this point your device is in HA (with the friendly name of your choice) and you can use the button.mysensor_identify button.

7. Start z2m; Add back the batteries and Press the identify button from HA - Do all of this quickly!!!
8. In z2m go to the OTA page and click on "Check for new updates". The update will be found and asked if it should be installed.

The OTA update definitely works, but requires some tinkering. Start the update with fully charged batteries. It can take hours to complete.

I understand this issue was open for a wired device. I believe the procedure is the same.

Reason for Edit: Had to replicate the steps for a second device and updated accordingly.

EDIT2: Tried with a 3rd device. It is enough to do step 6 and 7:

1. Remove the batteries
2. Insert the batteries
3. Press the identify button
4. Click the "Check for new updates"

This however only worked properly after I restarted z2m. When I did not restart it it hung at the download info for the newer fw.

[lluisd]

same problem here from time ago

[c0mplex1]

It's been 200 days since I reported the issue, but the Salus SR600 firmware upgrade issue "Update failed (device did not respond to OTA request)" is still not resolved.
Please fix it.
Thank you.

[DominikFilipiak]

I had a lot of problems updating my Sonoff TRVZB through z2m. I tried with different channels and setting some z2m options, but no luck.

Turns out, my z2m network was kind of overloaded by HA-side hysteresis automations adjusting radiator valve degrees. Every 30 seconds there were messages flying around from every radiator.

When I turned automations generating the traffic off, the update worked like a charm (well, it still took about an hours, but it eventually worked).

In z2m, just open logs and see how many messages are you getting. If there's a lot, try to disable their sources (such as mine automations) during the update. Good luck!

[fabian19vs]

This worked for me… not a solution but a workaround…
#6729 (comment)

[defanator]

@fabian19vs thanks for sharing this - I was able to update IKEA's Rodret E2201 using that advice - #6729 (comment)