Can't update Ikea Styrbar 1.0.024 to latest version #18515
Comments
|
I've found someone having the same issues as me. I've entered |
|
I've also tried (and failed) to force update Styrbar by downloading the file locally and using local index.json. It seems that zigbee2mqtt ignores local index.json for those devices which are found in online feed, like IKEA. @Koenkk can you confirm this? |
|
It's only used when
external_converters:
- ext_converter.js
|
|
Thanks! I was able to update to 2.4.5 with the external converter. I opened a pull request to get this information to the official docs. |
|
Great, assuming this can be closed now. |
|
I've tried it in several ways and couldn't get it to work. I've created the .js-file, I've changed the config, I've restarted Z2M from within Home Assistant numerous times and I can't get the button to update. I've added my my_index.json to the config and then I got the message that 1.0.024 is newer than 2.4.5. |
|
@crispy78 this is the index.json I used for successful OTA (I downloaded the file from IKEA feed to the /app/data directory): |
|
I'm about to quit this struggle. I can't find the app/data directory, so I've placed the file in the Zigbee2MQTT config-directory. I've changed the my_index.json-file, changed the config-file and still no luck. I'm thinking of changing to ZHA temporarily, the device seems to be updating on that platform with less hassle. I might be wrong. |
I've just managed to start the update, maybe I can help... My problem was that I didn't know that GUI settings override the settings I've put in config files by hand. I've used simple-web-server from GitHub on my PC, and put 10078031-zingo_kt_styrbar_remote-2.4.5.ota.ota.signed and my_index.json files in the root directory. Then in Z2M\Settings\OTA Updates I've unchecked "IKEA TRADFRI OTA use test url" and put url to my_index.json file on web server - in my case it was http://192.168.1.100/my_index.json Contents of my my_index.json: and last thing was ext_converter.js which I've uploaded with File Editor to the zigbee2mqtt directory. Contents were taken from the link that koenkk provided above. Then i just entered converter filename in Z2M\Settings\External Converters |
|
@tishcufksips thanks for your instructions, it finally got to the point that it found an update and it's currently updating. |
|
There is no need to run a server or anything like that. zigbee2mqtt is perfectly capable of serving the file. The firmware file and my_index.json can both go in the data directory, which is the same directory that zigbee2mqtt configuration.yaml is located.
[ { "manufacturerCode": 4476,
"imageType": 4555,
"fileVersion": 581,
"url": "10078031-zingo_kt_styrbar_remote-2.4.5.ota.ota.signed",
"force": true } ]
external_converters:
- ext_converter.js
ota:
zigbee_ota_override_index_location: my_index.json
|
|
Hi y'all: I'm pretty sure I've done all the steps here correctly, and have tried both using a web server and putting the necessary files on the HA instance directly, but I'm getting errors (see below) that seem to point to another problem. The buttons are working correctly, so I'm not sure these errors really mean what they say. Any help or pointers is appreciated! Info 2023-10-04 18:30:39MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":"Failed to check if update available for 'IKEAButton2' (Device didn't respond to OTA request)","meta":{"device":"IKEAButton2","status":"check_failed"},"type":"ota_update"}' with DEBUG on, these errors appear: Error 2023-10-04 19:13:07Failed to check if update available for 'IKEAButton2' (Device didn't respond to OTA request) |
|
Did you press button on the remote to wake it up immediately after clicking Check for updates? |
I did. I've reverted all the changes to force an OTA update and reset the devices and configs. And even then I get the same error :( EDIT: Finally got it to work. I, like [tishcufksips], found that I had to add the converter and index entries into the GUI for it to work. Also, pulling the batteries from the buttons seems to help the process along, as it checks for an update immediately after power-on. |
|
After flashing the firmware, the buttons stopped working, action commands are no longer sent, 3 buttons were flashed and they all stopped working. What have I done wrong? |
|
You have to remove the external converter and restart zigbee2mqtt to get all functionality back. |
Thank you, everything returned after completely stopping the container and starting it, restarting did not help. |
|
Hi, i did the update from #18515 (comment) and now only got device_announce messages when i insert battery. |
I alas seem to experience the same problem, even after restarting z2m/the whole system: both of my buttons stopped working after flashing the new firmware. No action commands are sent from them and I also can't seem to remove them. They do however seem to pair perfectly again when factory resetting them, but the result is the same: no functionality whatsoever. |
|
I think something worked here. |
I was about to do this, when I suddenly realized one of the two buttons worked. The only thing I had been doing (repeatedly) was removing the device, pairing it again and rebooting my entire system, to no avail. After leaving the button many hours, it suddenly worked. The second button I had still didn't work, but worked immediately after re-pairing it. I can't really pinpoint what suddenly changed... |
I've seen this behavior before. Mostly with IKEA shortcut button. It paired well, but sent no actions. Sometimes it started to work after multiple factory reset, sometimes I left it on the table and started to work after some hours by itself. |
|
same here - after the FW update it did not work anymore. Pairing was fine, just didn't trigger any action. I took out the batteries and replaced the remote with an old FW-level. After two days I wanted to do further tests and after inserting the batteries, the Styrbar worked just normal. So maybe it helps to take out the batteries over night... thanks @jkl1337 for the above manual!! |
|
same issue , tried to pair, it pairs ok ( long process of interview but finally pairs) but no actions triggered , also You can force a update for the firmware by pairing with hub and letting it update and then unpairing , but still when i connect to HA there is no trigger or binds working |
|
Since it is fixed (in container installation) by completely removing the container, it must be that the external converter gets somehow included in some other directory than data. Is it somehow cached or compiled in under files in dist? |
|
Few days ago something strange happened. Styrbar started to light up the bulbs on 1% of brightness no matter the previous state (not by automation but through binding). I had no such problem before. During my experiments I've excluded the fault of bulbs (they remembered brightness on power outage) and automations. It was Styrbar that was a culprit. And so I found this topic and decided to upgrade it. Thx @jkl1337 for great instruction! Upgrade didn't help. The bulbs are still turned on with 1% brightness no matter what (I can move brightness up, but after I turn off the lights they forget previous value). No gain here. Update breaks single arrow press. To recover from it I had to delete the device from z2m and re-pair anew. After that the new binding to Coordinator appeared - Scenes which fixes lack of single press as explained in this topic #15725 I still have to find the fix for this 1% brightness.. |
Same here 😞 |
|
Hi @Redominus As for the Styrbar remote it is not worth it to update. With firmware 1.0.024 the remote could be bound with Lidl bulbs ( https://www.zigbee2mqtt.io/devices/HG06492B.html#lidl-hg06492b ). After update the remote works only with original IKEA ones. |
Have you tried to upgrade to 2.4.5 then to 2.4.11 though ? I was in the same boat, then I went thru the update process described above (for 2.4.5) then updated thru regular OTA. Since then, only the 2 arrows were not working same as you, for which I described the fix above (right and left arrow are color temperature controls):
|
I updated directly to 2.4.11, so I can't try via 2.4.5 |
I have exactly the same issue with version 2.4.11 as well as 2.4.5.. updated zigbee2mqtt recently, might be an issue with zigbee2mqtt. All other buttons work as expected! |
|
I can confirm that after updating firmware to 2.4.11 both left/right long press don't work anymore. Any fixes for this (since I use both long presses for different lights toggling)? |
For me, waiting a couple of days made them working again. |
|
https://community.home-assistant.io/t/ikea-styrbar-e2001-2002-ultimate-zigbee2mqtt-z2m/625090 |
|
In my case, the problem was resolved after upgrade zigbee2mqtt to the 1.37.1 version AND Home assistant to the 2024.5.2 version |
|
for me helped to reconfigure device (the orange icon with arrows) |
|
I had the same problem, removing the noise once and retraining solved the problem. |
Any way of achieving this with ZHA? |
Same problem, left and right buttons stopped working after firmware update. When you remove the battery and add it back, they start working again until it happens again. So the only way for now is reset via battery. |
|
I have a working fix that worked for me. I have 5 IKEA buttons. After the update 1 worked, the other 4 didn't report button presses anymore. I noticed the one that worked had different bind settings Steps:
you should now get a bunch of popups for each bind that was successful. To get the battery to work again, it is possible it fixes itself, but you can also force the reporting by doing a similar process Steps:
The endpoint should create and save. Now you should be 100% working |
|
So I followed all suggestions and managed to update to 2.4.5 then even update to 2.4.11. I followed @devWaves instructions above also no luck, I did notice one difference though. Destination endpoint for me is 0 rather than 1.
|
@yarafie you can create a new binding. Use source endpoint = 1 , destination endpoint = 1, and destination = coordinator. Try creating a new one, then do the same bind process (take batteries out, fill out bind settings, put batteries back, press bind) if that works then do an unbind on the original messed up one. or try unbind first |
|
I had 2 spare STYRBAR not updated yet so used those for the time being will get back to the other ones, one at 2.4.5 and the other at 2.4.11 and will post my trials here later when I get the chance. I'm using a SLZB-06 as a coordinator and am at z2m 1.37.1 |
|
I updated to 2.4.11, and then discovered the device is not working properly anymore (no left / right click). So, I ended up here in hope of how I can restore 1.0.024. But, can not find the answer here, and ticket is already closed. Am I missing something? |
|
I got 6 [E2001/E2002] when pressing up on the 3 that are not working, then sends brightness_move_up command with no stop command |
This worked like a charm for me! (I am so happy right now) This Ikea Remote drove me crazy for at least 30 hours, fiddling around and nothing worked. What was my problem regarding this remote: So i tried to trigger a forced firmware update, by lecturing the guides above regarding updating by editing my_index.json etc. As last resort i tried this binding to clusters thing and it worked like a charm. But my batterie percentage is at 200% now.... - i can live with that hick-up :D |
|
Hi guys, I've got the same issue and have opened a new issue but no one seems to have chimed in until now. |
|
I started out with HA Green and ZBT-1 and ZHA around a week ago, after adding my first Styrbar and IKEA bulb I saw limitations with ZHA and changed over to Z2M. Added my Styrbar and bulb and everything worked great. Thought it would be wise to update the firmware (from 1.0.024), and of course it did not work, found this thread and got it to work after following this advice. I wasn't used to Zigbee updates so it took a surprisingly long time, but afterwards everything worked fine again (on 2.4.16). So today I thought I would add another Styrbar/lamp pair. Got them working fine in Z2M. Again I got update notice for the old 1.0.024 firmware and thought it would be wise to do so. Followed the same procedure as the first time but I got stuck on a missing module (zigbee-herdsman-converters/lib/extend) for the external converter. Solved that following this advice. Update to 2.4.16 ran and finished. Then Spook notified me that my automations using the Styrbars were referencing unknown entities. Well I will have to edit and set them up again I thought. Oh no, there are no matching entities, and there is no "action" for any(!) of the two Styrbars now. I tried restarting HA and Z2M without any improvement. I tried removing (forcibly) and re-pairing, no better. I tried removing batteries and re-inserting after a minute, nothing. I tried following this advice with no improvement, no change except that one of the Styrbars now refuse to show the battery level (and also some error about TABLE_FULL when trying to bind. If I can help trying out something else, or provide logs of interest, I would be happy to. Edit for clarity: Zigbee2MQTT version |
i got excatly the same issue, except it stopped working for me with Z2M 2.0.0-1 there seem to be no entities for my Styrbar remotes. |
|
Just for info. Z2M 2.0.0 has some breaking changes about triggers. Seems like all old Styrbar blueprints are now obsolete (without some z2m configuration.yaml legacy tweaking) #24198 I adopt the changes early after 1.4.2 and made some basic functionality for Styrbar with automation (automation trigger > device > select styrbar > select action > three dots > Edit ID (my automation has 11 triggers :) ) And the action are like (using building blocks > if-then and condition trigger with id generated in trigger) |
|
Neither 2.0.0 nor 2.1.0 accept this workaround to force the OTA update. |
|
After several repair, and Z2M reboot, I cannot get the action updated in Z2M Everything seems to be well configured. How did you manage to get the action reported in Z2M?
|
In newer versions there's functionality for be able to downgrade the firmware. Z2m thinks the newer version is an older version. So "downgrading" could be a way do to this. Though there doesn't seem to be any UI to initiate the downgrade. There's some docs on sending an MQTT message, though wonder the MQTT downgrade perhaps needs a version argument. Docs are at: https://www.zigbee2mqtt.io/guide/usage/ota_updates.html#downgrade |
It's easy to miss this advice in this long thread but this worked for me with Z2M 2.1.1. |
and others
What happened?
When using the OTA functionality Zigbee2MQTT concludes that the version 1.0.024 is newer than the firmware available online 2.4.5, so it won't update the device.
I've tried forcing the update, but that didn't work. To accomplish that I've renamed the index.json from pull request Koenkk/zigbee-OTA#340 to my_index.json and put it in \config\zigbee2mqtt in Home Assistant and entered /config/zigbee2mqtt/my_index.json in Zigbee2MQTT as the OTA index override file name.
What did you expect to happen?
I would have liked the device to update to the latests firmware.
How to reproduce it (minimal and precise)
Press "Check for new updates" on a Ikea Styrbar in the OTA-menu.
Zigbee2MQTT version
1.32.2-dev commit: 68ec507
Adapter firmware version
20220928
Adapter
CC2652RB
Debug log
info 2023-08-03 22:04:53: Checking if update available for 'Drukknop voordeur'
info 2023-08-03 22:04:53: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":"Checking if update available for 'Drukknop voordeur'","meta":{"device":"Drukknop voordeur","status":"checking_if_available"},"type":"ota_update"}'
debug 2023-08-03 22:04:53: Check if update available for '0x540f57fffe8f81f0' (Remote Control N2)
debug 2023-08-03 22:04:53: Using endpoint '1'
debug 2023-08-03 22:04:54: Received Zigbee message from 'Drukknop voordeur', type 'commandOff', cluster 'genOnOff', data '{}' from endpoint 1 with groupID 0
info 2023-08-03 22:04:54: MQTT publish: topic 'zigbee2mqtt/Drukknop voordeur', payload '{"action":"off","battery":100,"last_seen":"2023-08-03T22:04:54+02:00","linkquality":36,"update":{"installed_version":65572,"latest_version":581,"state":"idle"},"update_available":false}'
info 2023-08-03 22:04:54: MQTT publish: topic 'zigbee2mqtt/Drukknop voordeur', payload '{"action":"","battery":100,"last_seen":"2023-08-03T22:04:54+02:00","linkquality":36,"update":{"installed_version":65572,"latest_version":581,"state":"idle"},"update_available":false}'
info 2023-08-03 22:04:54: MQTT publish: topic 'zigbee2mqtt/Drukknop voordeur/action', payload 'off'
debug 2023-08-03 22:04:54: Received Zigbee message from 'Drukknop voordeur', type 'commandOff', cluster 'genOnOff', data '{}' from endpoint 1 with groupID 0
info 2023-08-03 22:04:54: MQTT publish: topic 'zigbee2mqtt/Drukknop voordeur', payload '{"action":null,"battery":100,"last_seen":"2023-08-03T22:04:54+02:00","linkquality":36,"update":{"installed_version":65572,"latest_version":581,"state":"idle"},"update_available":false}'
debug 2023-08-03 22:04:56: Received Zigbee message from 'Drukknop voordeur', type 'commandTradfriArrowSingle', cluster 'genScenes', data '{"value":256,"value2":13}' from endpoint 1 with groupID 0
info 2023-08-03 22:04:56: MQTT publish: topic 'zigbee2mqtt/Drukknop voordeur', payload '{"action":"arrow_right_click","battery":100,"last_seen":"2023-08-03T22:04:56+02:00","linkquality":36,"update":{"installed_version":65572,"latest_version":581,"state":"idle"},"update_available":false}'
info 2023-08-03 22:04:56: MQTT publish: topic 'zigbee2mqtt/Drukknop voordeur', payload '{"action":"","battery":100,"last_seen":"2023-08-03T22:04:56+02:00","linkquality":36,"update":{"installed_version":65572,"latest_version":581,"state":"idle"},"update_available":false}'
info 2023-08-03 22:04:56: MQTT publish: topic 'zigbee2mqtt/Drukknop voordeur/action', payload 'arrow_right_click'
debug 2023-08-03 22:04:56: Received Zigbee message from 'Drukknop voordeur', type 'commandTradfriArrowSingle', cluster 'genScenes', data '{"value":256,"value2":13}' from endpoint 1 with groupID 0
info 2023-08-03 22:04:56: MQTT publish: topic 'zigbee2mqtt/Drukknop voordeur', payload '{"action":null,"battery":100,"last_seen":"2023-08-03T22:04:56+02:00","linkquality":36,"update":{"installed_version":65572,"latest_version":581,"state":"idle"},"update_available":false}'
debug 2023-08-03 22:04:57: Received Zigbee message from 'Drukknop voordeur', type 'commandTradfriArrowSingle', cluster 'genScenes', data '{"value":257,"value2":13}' from endpoint 1 with groupID 0
info 2023-08-03 22:04:57: MQTT publish: topic 'zigbee2mqtt/Drukknop voordeur', payload '{"action":"arrow_left_click","battery":100,"last_seen":"2023-08-03T22:04:57+02:00","linkquality":36,"update":{"installed_version":65572,"latest_version":581,"state":"idle"},"update_available":false}'
info 2023-08-03 22:04:57: MQTT publish: topic 'zigbee2mqtt/Drukknop voordeur', payload '{"action":"","battery":100,"last_seen":"2023-08-03T22:04:57+02:00","linkquality":36,"update":{"installed_version":65572,"latest_version":581,"state":"idle"},"update_available":false}'
info 2023-08-03 22:04:57: MQTT publish: topic 'zigbee2mqtt/Drukknop voordeur/action', payload 'arrow_left_click'
debug 2023-08-03 22:04:57: Received Zigbee message from 'Drukknop voordeur', type 'commandTradfriArrowSingle', cluster 'genScenes', data '{"value":257,"value2":13}' from endpoint 1 with groupID 0
info 2023-08-03 22:04:57: MQTT publish: topic 'zigbee2mqtt/Drukknop voordeur', payload '{"action":null,"battery":100,"last_seen":"2023-08-03T22:04:57+02:00","linkquality":36,"update":{"installed_version":65572,"latest_version":581,"state":"idle"},"update_available":false}'
debug 2023-08-03 22:04:57: Received Zigbee message from 'Drukknop voordeur', type 'commandQueryNextImageRequest', cluster 'genOta', data '{"fieldControl":1,"fileVersion":65572,"imageType":4555,"manufacturerCode":4476}' from endpoint 1 with groupID 0
info 2023-08-03 22:04:57: MQTT publish: topic 'zigbee2mqtt/Drukknop voordeur', payload '{"action":null,"battery":100,"last_seen":"2023-08-03T22:04:57+02:00","linkquality":36,"update":{"installed_version":65572,"latest_version":581,"state":"idle"},"update_available":false}'
debug 2023-08-03 22:04:57: Got OTA request '{"fieldControl":1,"manufacturerCode":4476,"imageType":4555,"fileVersion":65572}'
debug 2023-08-03 22:04:58: Received Zigbee message from 'Drukknop voordeur', type 'commandOn', cluster 'genOnOff', data '{}' from endpoint 1 with groupID 0
info 2023-08-03 22:04:58: MQTT publish: topic 'zigbee2mqtt/Drukknop voordeur', payload '{"action":"on","battery":100,"last_seen":"2023-08-03T22:04:58+02:00","linkquality":32,"update":{"installed_version":65572,"latest_version":581,"state":"idle"},"update_available":false}'
info 2023-08-03 22:04:58: MQTT publish: topic 'zigbee2mqtt/Drukknop voordeur', payload '{"action":"","battery":100,"last_seen":"2023-08-03T22:04:58+02:00","linkquality":32,"update":{"installed_version":65572,"latest_version":581,"state":"idle"},"update_available":false}'
info 2023-08-03 22:04:58: MQTT publish: topic 'zigbee2mqtt/Drukknop voordeur/action', payload 'on'
debug 2023-08-03 22:04:58: Received Zigbee message from 'Drukknop voordeur', type 'commandOn', cluster 'genOnOff', data '{}' from endpoint 1 with groupID 0
info 2023-08-03 22:04:58: MQTT publish: topic 'zigbee2mqtt/Drukknop voordeur', payload '{"action":null,"battery":100,"last_seen":"2023-08-03T22:04:58+02:00","linkquality":36,"update":{"installed_version":65572,"latest_version":581,"state":"idle"},"update_available":false}'
debug 2023-08-03 22:04:58: Is new image available for '0x540f57fffe8f81f0', current '{"fieldControl":1,"manufacturerCode":4476,"imageType":4555,"fileVersion":65572}', latest meta '{"fileVersion":581,"url":"http://fw.ota.homesmart.ikea.net/global/GW1.0/01.20.065/bin/10078031-zingo_kt_styrbar_remote-2.4.5.ota.ota.signed"}'
debug 2023-08-03 22:04:58: Update available for '0x540f57fffe8f81f0': NO
warn 2023-08-03 22:04:58: Firmware on '0x540f57fffe8f81f0' is newer than latest firmware online.
info 2023-08-03 22:04:58: No update available for 'Drukknop voordeur'
The text was updated successfully, but these errors were encountered: