zigbee2mqtt icon indicating copy to clipboard operation
zigbee2mqtt copied to clipboard

Ikea OTA is just not working

Open balihb opened this issue 2 years ago • 2 comments

What happened?

trying to update Ikea stuff via a Xiaomi GW is just now working. Or am I doing something wrong? (sorry if I do) image image

What did you expect to happen?

No response

How to reproduce it (minimal and precise)

No response

Zigbee2MQTT version

1.25.0

Adapter firmware version

6.7.10.0 build 423

Adapter

https://github.com/zvldz/mgl03_fw/tree/main/firmware/custom/mgl03_1.5.0_0102_mod20210816

Debug log

debug Received MQTT message on 'zigbee2mqtt/bridge/request/device/ota_update/update' with data '{"id":"0x14b457fffe4dcf80","transaction":"hmwma-1"}' info Updating '0x14b457fffe4dcf80' to latest firmware info MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":"Updating '0x14b457fffe4dcf80' to latest firmware","meta":{"device":"0x14b457fffe4dcf80","status":"update_in_progress"},"type":"ota_update"}' debug Updating to latest '0x14b457fffe4dcf80' (TRADFRI remote control) debug Using endpoint '1' debug Update of '0x14b457fffe4dcf80' failed (Error: Device didn't respond to OTA request) info MQTT publish: topic 'zigbee2mqtt/0x14b457fffe4dcf80', payload '{"battery":74,"linkquality":255,"update":{"state":"available"},"update_available":true}' info MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":"Update of '0x14b457fffe4dcf80' failed (Device didn't respond to OTA request)","meta":{"device":"0x14b457fffe4dcf80","status":"update_failed"},"type":"ota_update"}' info MQTT publish: topic 'zigbee2mqtt/bridge/response/device/ota_update/update', payload '{"data":{"id":"0x14b457fffe4dcf80"},"error":"Update of '0x14b457fffe4dcf80' failed (Device didn't respond to OTA request)","status":"error","transaction":"hmwma-1"}' error Update of '0x14b457fffe4dcf80' failed (Device didn't respond to OTA request) debug Error: Device didn't respond to OTA request at requestOTA (/app/node_modules/zigbee-herdsman-converters/lib/ota/common.js:196:15) at Object.updateToLatest (/app/node_modules/zigbee-herdsman-converters/lib/ota/common.js:283:21) at OTAUpdate.onMQTTMessage (/app/lib/extension/otaUpdate.ts:256:21) debug Received Zigbee message from '0x14b457fffe4dcf80', type 'attributeReport', cluster 'genPowerCfg', data '{"batteryPercentageRemaining":60}' from endpoint 1 with groupID 0 info MQTT publish: topic 'zigbee2mqtt/0x14b457fffe4dcf80', payload '{"battery":60,"linkquality":252,"update":{"state":"available"},"update_available":true}' debug Received Zigbee message from '0x14b457fffe4dcf80', type 'commandToggle', cluster 'genOnOff', data '{}' from endpoint 1 with groupID 58508 info MQTT publish: topic 'zigbee2mqtt/0x14b457fffe4dcf80', payload '{"action":"toggle","battery":60,"linkquality":255,"update":{"state":"available"},"update_available":true}' debug Received Zigbee message from '0x14b457fffe4dcf80', type 'commandToggle', cluster 'genOnOff', data '{}' from endpoint 1 with groupID 58508 info MQTT publish: topic 'zigbee2mqtt/0x14b457fffe4dcf80', payload '{"action":"toggle","battery":60,"linkquality":184,"update":{"state":"available"},"update_available":true}' debug Received Zigbee message from '0x14b457fffe4dcf80', type 'commandToggle', cluster 'genOnOff', data '{}' from endpoint 1 with groupID 58508 info MQTT publish: topic 'zigbee2mqtt/0x14b457fffe4dcf80', payload '{"action":"toggle","battery":60,"linkquality":228,"update":{"state":"available"},"update_available":true}' debug Received Zigbee message from '0x14b457fffe4dcf80', type 'commandToggle', cluster 'genOnOff', data '{}' from endpoint 1 with groupID 58508 info MQTT publish: topic 'zigbee2mqtt/0x14b457fffe4dcf80', payload '{"action":"toggle","battery":60,"linkquality":248,"update":{"state":"available"},"update_available":true}' debug Received MQTT message on 'zigbee2mqtt/bridge/request/device/ota_update/update' with data '{"id":"0x14b457fffe4dcf80","transaction":"hmwma-2"}' info Updating '0x14b457fffe4dcf80' to latest firmware info MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":"Updating '0x14b457fffe4dcf80' to latest firmware","meta":{"device":"0x14b457fffe4dcf80","status":"update_in_progress"},"type":"ota_update"}' debug Updating to latest '0x14b457fffe4dcf80' (TRADFRI remote control) debug Using endpoint '1' debug Update of '0x14b457fffe4dcf80' failed (Error: Device didn't respond to OTA request) info MQTT publish: topic 'zigbee2mqtt/0x14b457fffe4dcf80', payload '{"battery":60,"linkquality":248,"update":{"state":"available"},"update_available":true}' info MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":"Update of '0x14b457fffe4dcf80' failed (Device didn't respond to OTA request)","meta":{"device":"0x14b457fffe4dcf80","status":"update_failed"},"type":"ota_update"}' info MQTT publish: topic 'zigbee2mqtt/bridge/response/device/ota_update/update', payload '{"data":{"id":"0x14b457fffe4dcf80"},"error":"Update of '0x14b457fffe4dcf80' failed (Device didn't respond to OTA request)","status":"error","transaction":"hmwma-2"}' error Update of '0x14b457fffe4dcf80' failed (Device didn't respond to OTA request) debug Error: Device didn't respond to OTA request at requestOTA (/app/node_modules/zigbee-herdsman-converters/lib/ota/common.js:196:15) at Object.updateToLatest (/app/node_modules/zigbee-herdsman-converters/lib/ota/common.js:283:21) at OTAUpdate.onMQTTMessage (/app/lib/extension/otaUpdate.ts:256:21) debug Saving state to file /app/data/state.json debug Saving state to file /app/data/state.json

balihb avatar Nov 29 '22 05:11 balihb

Are you waking the device before trying to apply the update? The above error only usually occurs when the device is in a sleep state...

yes I do. I had access to another gw and ikea switch pairing with the same error and I have this same error for more then a year (never worked). the update works with the ikea gw with the same version of switch.

On Tue, Nov 29, 2022, 09:48 danieledwardgeorgehitchcock < @.***> wrote:

Are you waking the device before trying to apply the update? The above error only usually occurs when the device is in a sleep state...

— Reply to this email directly, view it on GitHub https://github.com/Koenkk/zigbee2mqtt/issues/15235#issuecomment-1330284814, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAV4ZGFEXYYUOBYJAZZOHPLWKW7MFANCNFSM6AAAAAASOCTRZA . You are receiving this because you authored the thread.Message ID: @.***>

balihb avatar Nov 29 '22 09:11 balihb

https://gist.github.com/balihb/57cdf1cfc4e038ed874a70b8454da473

balihb avatar Nov 30 '22 18:11 balihb

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

github-actions[bot] avatar Dec 31 '22 00:12 github-actions[bot]

the problem is still present? can I somehow give any more information that would help?

balihb avatar Jan 04 '23 21:01 balihb

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

github-actions[bot] avatar Feb 04 '23 00:02 github-actions[bot]

I have the same Error. Any solutions how to update via Z2M?

Suschibomber avatar Feb 01 '24 12:02 Suschibomber

I have the same Error. Any solutions how to update via Z2M?

Yes - make sure you are using Zigbee2MQTT 1.36 (or higher if available). Power cycle the mains adapter and then immediately try the update. It works for me.

PlasticRhino avatar Mar 08 '24 13:03 PlasticRhino

I've finally done it. The secret, which is nowhere on the Internet, is that the remote control has to be very close to the coordinator when you initiate the update and shortly beforehand Press a couple of buttons so that the remote control is not in sleep mode. Then the update works straight away! Hope this helps someone who has the same problem.

Suschibomber avatar Mar 08 '24 13:03 Suschibomber

Mine was about as far away as it can be in my house but maybe I have better coverage with my coordinator. I suspect that the significant action was bringing it out of standby.

PlasticRhino avatar Mar 08 '24 13:03 PlasticRhino