zigbee2mqtt
zigbee2mqtt copied to clipboard
Koenkk
Philips Hue dimmer switch (RWL021) OTA not working
What happened?
The switch reports a OTA Update available (Verion: 6.1.1.28573). I start the OTA but after some time it fails. I also get the switch active by pressing some buttons.
What did you expect to happen?
No response
How to reproduce it (minimal and precise)
click on the Update device firmware for the switch
Zigbee2MQTT version
2.1.1
Adapter firmware version
7.4.4
Adapter
HA Yellow with ember driver
Setup
HA Yellow
Debug log
info 2025-02-07 10:33:23z2m: Updating 'Esszimmer Schalter' to latest firmware
info 2025-02-07 10:33:26zhc:ota: [0x00178801105f9808 | RWL021] Getting latest image, meta: {"fileName":"Switch-ATmega_0012.sbl-ota","fileVersion":1124102917,"fileSize":240760,"url":"https://github.com/Koenkk/zigbee-OTA/raw/master/images/Hue/Switch-ATmega_0012.sbl-ota","imageType":265,"manufacturerCode":4107,"sha512":"6bec6b6dce7ef9bb47c4467643222871788256d5c3f0aa88ded80be24fc002dbdda525ca2cafa78b996ff7fe0c18d7c9194288e4f6b40f0f37d147bc1724dd4e","otaHeaderString":"\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000","originalUrl":"https://otau.meethue.com/storage/ZGB_100B_0109/3a1c8cf8-3f4c-4464-93f0-24cc7f67f0d7/Switch-ATmega_0012.sbl-ota"}
error 2025-02-07 10:35:56z2m: Update of 'Esszimmer Schalter' failed ([0x00178801105f9808 | RWL021] Timeout. Device did not start/finish firmware download after being notified. ({"target":18185,"apsFrame":{"clusterId":25,"profileId":260,"sequence":0,"sourceEndpoint":1,"destinationEndpoint":2,"groupId":0,"options":0},"commandIdentifier":3} timed out after 150000ms))
came there to report the same
[2025-02-07 10:28:19] info: z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/Hue Dimmer Switch (Bedroom)/action', payload 'on_press'
[2025-02-07 10:28:19] info: z2m: Updating 'Hue Dimmer Switch (Bedroom)' to latest firmware
[2025-02-07 10:28:19] info: z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/Hue Dimmer Switch (Bedroom)', payload '{"action_duration":null,"battery":93.5,"linkquality":128,"update":{"installed_version":1107324829,"latest_version":1124102917,"state":"available"}}'
[2025-02-07 10:28:19] info: z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/bridge/response/device/ota_update/update', payload '{"data":{},"error":"Update of 'Hue Dimmer Switch (Bedroom)' failed ([0x0017880102d4ae38 | RWL021] Failed to find an endpoint which supports the OTA cluster)","status":"error"}'
[2025-02-07 10:28:19] error: z2m: Update of 'Hue Dimmer Switch (Bedroom)' failed ([0x0017880102d4ae38 | RWL021] Failed to find an endpoint which supports the OTA cluster)
Hello folks,
can confirm. The old version of the dimmer switch:
https://www.zigbee2mqtt.io/devices/324131092621.html
and new version (v2) fail.
https://www.zigbee2mqtt.io/devices/929002398602.html
All of my Philips dimmer switches (1x old) and (10 x new v2) refuse to OTA update.
[2025-02-07 20:45:21] info: z2m: Updating 'HG OG1 Wohnzimmer Lichtschalter Nord' to latest firmware
[2025-02-07 20:46:44] info: z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/HG OG1 Wohnzimmer Lichtschalter Nord', payload '{"action":null,"battery":100,"device":{"applicationVersion":2,"dateCode":"20210729","friendlyName":"HG OG1 Wohnzimmer Lichtschalter Nord","hardwareVersion":1,"ieeeAddr":"0x001788010e8ce559","manufacturerID":4107,"manufacturerName":"Signify Netherlands B.V.","model":"929002398602","networkAddress":23744,"powerSource":"Battery","softwareBuildID":"2.45.2_hF4400CA","stackVersion":1,"type":"EndDevice","zclVersion":2},"last_seen":"2025-02-07T19:44:33.621Z","linkquality":40,"update":{"installed_version":33565954,"latest_version":33574183,"state":"available"}}'
[2025-02-07 20:46:44] info: z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/bridge/response/device/ota_update/update', payload '{"data":{},"error":"Update of 'HG OG1 Wohnzimmer Lichtschalter Nord' failed (Device didn't respond to OTA request)","status":"error","transaction":"haczz-1"}'
[2025-02-07 20:46:44] error: z2m: Update of 'HG OG1 Wohnzimmer Lichtschalter Nord' failed (Device didn't respond to OTA request)
{
"battery": 100,
"last_seen": "2025-02-07T19:28:13.413Z",
"linkquality": 94,
"update": {
"installed_version": 33565954,
"latest_version": 33574183,
"state": "available"
},
"action": null,
"device": {
"applicationVersion": 2,
"dateCode": "20210729",
"friendlyName": "HG OG1 Wohnzimmer Lichtschalter Nord",
"hardwareVersion": 1,
"ieeeAddr": "0x001788010e8ce559",
"manufacturerID": 4107,
"manufacturerName": "Signify Netherlands B.V.",
"model": "929002398602",
"networkAddress": 23744,
"powerSource": "Battery",
"softwareBuildID": "2.45.2_hF4400CA",
"stackVersion": 1,
"type": "EndDevice",
"zclVersion": 2
}
}
Regards
@rmi1974 Did you wake up your v2 dimmers by pressing a button? With that, mine all updated. The v1 dimmers did not. I got one to update by making it perma-awake via reporting settings (1/5/0), but hat to re-interview afterwards to get the new FW recognized by Z2M.
I also had problems in updating my old v1 dimmers, but finally 2 of them are updated now and one ist still in the process of updating. You need a lot of patience, always restart, do not more than 1 device update in parallel. Keep device alive. Press a button immediately before clicking the Ok button to start the update. It took me the entire day to get 2 out of 3 updated.
Newer dimmers and also the old indoor motions sensors as well as the newer outdoor motions sensors updated without problems.
I beliebe the difference is that the v1 accessories are not ZigBee 3.0 conformant, whereas the newer ones are.
I have 4 v1 and 1 v2 of the switches.
The v2 updated fine. 3 of the v1's appear to update but the following morning say they need update again, they will go thru the process of updating and appear to update but again will claim they need updated the following morning
1 of the v1's point blank refuses to update giving the log errors I posted earlier.
I never had issues updating these the last time there was updates for them.
@mundschenk-at thanks for the hint. I forgot about the sleep mode on those devices.
After running around, pressing one of the buttons once/twice, the v2 devices were able to update from:
20210729 2.45.2_hF4400CA
to:
20241001 2.77.39
Related to this "deep sleep" mode, but off-topic:
This (deep) sleep mode on those philips dimmer switch devices is really annoying. I have various other multi-button zigbee remotes (tuya), that never show this behaviour, reacting instantly on button presses. Especially when people need to press buttons at least twice because the device needs a "wakeup" to have some action done because the first button press is "lost" (required to wakeup?) Annoying for guests who expect the switches to operate like normal physical switches. Can someone tell me if it's possible to disable the sleep mode on those dimmer switches. I'd rather have them draining the batteries faster than the "this switch doesn't work properly" experience.
Regards
I just found a solution for my last HUE dimmer v1. I updated the firmware of my Zigbee Coordinator (SLZB-06p10) to version 2.7.1.
Changelog of that version is:
Fixed Zigbee OTA updates for SLZB-06/p7/p10.
After that update I only had to try 2 times until the update of my old HUE dimmer was successfull. Even in the first try it got close to completion (>95%). Second time it finished successfully.
So in case you are using ths SLZB-06p## Coordinator with an older firmware you could give it a chance.
Me three. Every HUE Accessory will result in fail in OTA. Either wont't start the OTA (timeout). Or the update will start, but after some period of a time will fail by Restarting the adapter. I have a solid 150 devices network, good connection, no interference, everything is rock solid - except the OTA of HUE Dimmer Switches (both Gen 1 and 2) and Motion sensors. I've tried it on EZSP 6.x.x as well as on Amber 7.4.4 versions of the SONOFF E coordinator. I've tried setting lower package size in OTA, pressing the buttons to wake accessories up, setting ping mode to accessories every 5 secs, nothing has worked for me.
I was able to update one of my Hue v1 dimmer switches, even at the first try, funnily the firmware version stayed the same after the update.
Still trying to update the other two, one of them got until 52%, but failed then, the third one didn't even start to update until now.
It didn't update, it failed. Tomorrow morning it'll be back in the list to showing update available
It didn't update, it failed. Tomorrow morning it'll be back in the list to showing update available
The update was already three days ago and it definitely went to 100%.
If the firmware version didn't change then it didn't update
I've been thru this for 3 days running. Each switch claims to have update but the next morning they all appear again saying update available
If the firmware version didn't change then it didn't update
I cannot tell you if you are right or wrong...
When I checked the dev console after your comment I saw that all clusters were gone, so I thought the switch could be broken.
I then connected it to the Hue Bridge, but surprisingly the Hue Bridge was showing that the software version of the switch is 67.115.5, which is the most recent one. I then switched back to Zigbee2MQTT again and there the SW version and date shown is still the old one ( 6.1.1.28573).
Clusters etc. are back now and the switch is fully working.
No idea what is happening, but as long as it is working and the update notice is gone it's ok for me.
New update, it now fully stopped working in Zigbee2MQTT although I can connect it. But when connected there is simply no light flashing when I press any of the buttons.
So I really do not know what happened.
I will connect it to the Hue Bridge again now and will not try to update the other switches.
To confirm my status, I only have issues with v1 hue switches.
My v2 switches, hue bulbs and hue motion sensor all updated fine.
It's just my 4 v1 switches that won't update - 3 appear to update and complete but the following morning they appear for update again and 1 refuses to even start to try and update
If the firmware version didn't change then it didn't update
I've been thru this for 3 days running. Each switch claims to have update but the next morning they all appear again saying update available
I made the same experience and I tried it 3 times.
3 times the dimmer v1 was updated up to 100%, but the version did not change.
Finally I found out, if you trigger an new interview after "successfull" (100%) update , the new firmware version is recognized and the dimmer shows the updated FW version in the z2m portal.
If the firmware version didn't change then it didn't update I've been thru this for 3 days running. Each switch claims to have update but the next morning they all appear again saying update available
I made the same experience and I tried it 3 times.
3 times the dimmer v1 was updated up to 100%, but the version did not change.
Finally I found out, if you trigger an new interview after "successfull" (100%) update , the new firmware version is recognized and the dimmer shows the updated FW version in the z2m portal.
what do you mean by that? you mean you have to sit and watch the live log until you see successfull" (100%) update, and then interview it again? that is going to be quite time consuming if you have to multiple switches.
clearly doing that can't be considered "normal".
what do you mean by that?
simply do an re-interview after the update has finished without errors. If the update breaks with errors, this obviously does not help.
what do you mean by that?
simply do an re-interview after the update has finished without errors. If the update breaks with errors, this obviously does not help.
all 4 of my v1 switches aren't showing an update fail, but a re-interview does nothing.
all 4 of my v1 switches aren't showing an update fail, but a re-interview does nothing.
okay, then it's not a general solution. For my last v1 dimmer at least it worked out.
I seem to experience the same issue
info 2025-02-10 23:32:53z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/bridge/response/device/ota_update/update', payload '{"data":{},"error":"Update of 'Switch Slaapkamer Ouders' failed ([0x0017880102c1b40b | RWL021] Timeout. Device did not start/finish firmware download after being notified. (Timeout - 57453 - 2 - undefined - 25 - 3 after 150000ms))","status":"error","transaction":"nhuqw-2"}'
error 2025-02-10 23:32:53z2m: Update of 'Switch Slaapkamer Ouders' failed ([0x0017880102c1b40b | RWL021] Timeout. Device did not start/finish firmware download after being notified. (Timeout - 57453 - 2 - undefined - 25 - 3 after 150000ms))
Adding my voice to the cacophony:
I have 5 V1 switches, I wake one of them up by pressing buttons before and after I tell Z2M to update and the firmware upgrade seems to work, but then the next day updates are available again. Obviously one device at a time is safest...
I've tried using the "Interview" button in the Z2M web UI to re-interview the devices, alongside the same method of "waking up the device" by pressing buttons for a few seconds before and after... This doesn't seem to be doing anything. Is there a different way we should be waking up/preparing these V1 dimmers for re-interview? Perhaps the old paperclip in the back, or holding On/Off for 10 seconds?
Otherwise I'm stuck in the same boat as a few others here, firmware update appears to work but either the firmware doesn't actually apply or I'm not getting the correct firmware version from the switches. It's hard to tell, either way Z2M doesn't seem to believe anything is amiss.
Sonoff E, running zStack3x0 (revision 20230507), Z2M 2.1.1
what do you mean by that?
simply do an re-interview after the update has finished without errors. If the update breaks with errors, this obviously does not help.
i tried your suggestion, it didn't work. i triggered an update on the switch, watched the log to see it complete to 100%. re-interviewed the switch by pressing the blue "i" button within zigbee2mqtt devices screen. it said it completed. waited 24 hours and the device re-appeared in the list of devices requiring an update.
[2025-02-11 09:28:46] info: z2m: Update of 'Hue Dimmer Switch (Hall)' at 98.92%, ≈ 0 minutes remaining
[2025-02-11 09:28:46] info: z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/Hue Dimmer Switch (Hall)', payload '{"action_duration":null,"battery":52,"linkquality":196,"update":{"installed_version":1107324829,"latest_version":1124102917,"progress":98.92,"remaining":29,"state":"updating"}}'
[2025-02-11 09:29:15] info: z2m: Update of 'Hue Dimmer Switch (Hall)' at 100.00%
[2025-02-11 09:29:15] info: z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/Hue Dimmer Switch (Hall)', payload '{"action_duration":null,"battery":52,"linkquality":255,"update":{"installed_version":1107324829,"latest_version":1124102917,"progress":100,"remaining":29,"state":"updating"}}'
[2025-02-11 09:29:17] info: z2m: Finished update of 'Hue Dimmer Switch (Hall)'
[2025-02-11 09:29:17] info: z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/Hue Dimmer Switch (Hall)', payload '{"action_duration":null,"battery":52,"linkquality":255,"update":{"installed_version":1124102917,"latest_version":1124102917,"state":"idle"}}'
[2025-02-11 09:29:17] info: z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"friendly_name":"Hue Dimmer Switch (Hall)","ieee_address":"0x0017880104f34798"},"type":"device_announce"}'
[2025-02-11 09:29:17] info: z2m: Device 'Hue Dimmer Switch (Hall)' was updated from 'undefined' to '{"dateCode":"20190410","softwareBuildID":"6.1.1.28573"}'
[2025-02-11 09:29:17] info: z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/bridge/response/device/ota_update/update', payload '{"data":{"id":"0x0017880104f34798","to":{"date_code":"20190410","software_build_id":"6.1.1.28573"}},"status":"ok"}'
[2025-02-11 09:29:27] info: z2m: Configuring 'Hue Dimmer Switch (Hall)'
[2025-02-11 09:29:27] info: z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/Hue Dimmer Switch (Hall)', payload '{"action_duration":null,"battery":54.5,"linkquality":148,"update":{"installed_version":1124102917,"latest_version":1124102917,"state":"idle"}}'
[2025-02-11 09:29:30] info: z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/Hue Dimmer Switch (Hall)', payload '{"action_duration":null,"battery":54.5,"linkquality":148,"update":{"installed_version":1124102917,"latest_version":1124102917,"state":"idle"}}'
[2025-02-11 09:29:30] info: z2m: Successfully configured 'Hue Dimmer Switch (Hall)'
[2025-02-11 09:30:19] info: z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/Hue Dimmer Switch (Hall)', payload '{"action":"off_press","action_duration":null,"battery":54.5,"linkquality":148,"update":{"installed_version":1124102917,"latest_version":1124102917,"state":"idle"}}'
[2025-02-11 09:30:19] info: z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/Hue Dimmer Switch (Hall)/action', payload 'off_press'
[2025-02-11 09:30:20] info: z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/Hue Dimmer Switch (Hall)', payload '{"action":"off_press_release","action_duration":null,"battery":54.5,"linkquality":148,"update":{"installed_version":1124102917,"latest_version":1124102917,"state":"idle"}}'
[2025-02-11 09:30:20] info: z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/Hue Dimmer Switch (Hall)/action', payload 'off_press_release'
[2025-02-11 09:30:21] info: z2m: Interviewing 'Hue Dimmer Switch (Hall)'
[2025-02-11 09:30:25] info: zh:controller:device: Device '0x0017880104f34798' is only compliant to revision 'pre-21' of the ZigBee specification (current revision: 23).
[2025-02-11 09:30:30] info: z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/Hue Dimmer Switch (Hall)', payload '{"action_duration":null,"battery":54.5,"linkquality":148,"update":{"installed_version":1107324829,"latest_version":1124102917,"state":"available"}}'
[2025-02-11 09:30:30] info: z2m: Update available for 'Hue Dimmer Switch (Hall)'
[2025-02-11 09:30:36] info: z2m: Successfully interviewed 'Hue Dimmer Switch (Hall)'
[2025-02-11 09:30:36] info: z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/bridge/response/device/interview', payload '{"data":{"id":"Hue Dimmer Switch (Hall)"},"status":"ok","transaction":"7jip1-1"}'
I had the same issue with the Philips Hue dimmer switch V2. For me it helped to trigger the update in Z2M and then click twice the off button on the dimmer. Then after few seconds the update progress started - first with time N/A and then later with ~ 30 minutes. It worked for my 4 dimmer switches the same way. I did not have to re-add them.
I had the same issue with the Philips Hue dimmer switch V2. For me it helped to trigger the update in Z2M and then click twice the off button on the dimmer. Then after few seconds the update progress started - first with time N/A and then later with ~ 30 minutes. It worked for my 4 dimmer switches the same way. I did not have to re-add them.
this issue is related to v1 switches, not v2. v2 switches have no issues updating.
I've been trying to update my V1 switches for week or so. When I try to reconfigure to check whenever firmware update been successful, I get this:
2025-02-11 13:31:33z2m:
Failed to configure 'Staircase 2nd floor switch 2',
attempt 2 (Error: Bind 0x0017880108f50b19/1 genOnOff from '0x00124b0029e7e16a/1' failed (AREQ - ZDO - bindRsp after 10000ms)
at Object.start (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/utils/waitress.ts:67:23)
at func (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:423:47)
at processTicksAndRejections (node:internal/process/task_queues:105:5)
at Queue.execute (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/utils/queue.ts:36:20)
at ZStackAdapter.sendZdoInternal (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:428:43)
at ZStackAdapter.sendZdo (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:305:16)
at Endpoint.bind (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/controller/model/endpoint.ts:562:30)
at Object.bind (/app/node_modules/.pnpm/[email protected]/node_modules/src/lib/reporting.ts:42:9)
at configure (/app/node_modules/.pnpm/[email protected]/node_modules/src/devices/philips.ts:2379:13)
at Object.configure (/app/node_modules/.pnpm/[email protected]/node_modules/src/index.ts:272:21))
And yes - the update keeps going to 100% and failing without any warning / error / issue.
So my final status is the following now:
Hue Dimmer Switch v1 No. 1: Successfully updated with Z2M after 2 tries Z2M is still showing the old firmware version and date, but when I connect it to the Hue bridge the Hue app shows the new firmware version Re-connection to Z2m does not change it, BUT when I search for new firmware via OTA, it says there is no update available
Hue Dimmer Switch v1 No. 2: I had no chance updating it with Z2M, failed 4 or 5 times After connecting it to the Hue bridge two days ago the old firmware version was shown in the Hue App, I had to wait until tonight, but in the end the switch was updated to the new firmware version via the Hue bridge. BUT now comes the big surprise - I re-connected it to Z2M, but here it still showing the old firmware date and version although it was updated. Searching for updates also brings the result that no new firmware is available
So the conclusion is the update for v1 is possible with Z2M, but it can be a pain in the a** The frontend does wrongly show the old firmware version and firmware date, but when searching for an update it is recodnized that the switches are updated to the newest version.
@nephrotranz: Yeah, if Z2M says there are no updates available, you can just reinterview to show the correct version.