zigbee2mqtt
zigbee2mqtt copied to clipboard
Koenkk
Wrong firmware flashed on IKEA LED2201G8, bulbs do only flash now, offline
What happened?
Today new a firmware upgrade for IKEA bulbs was offered, so I started to upgrade the corresponding bulbs. Sometime later I noticed my LED2201G8 in the basement do flash every few seconds. They are offline, factory reset does not work. After looking for the cause, I noticed the new 3.0.21 is not for the LED2201G8, but only for my other LED2107C4, which do work fine after the upgrade. Since the firmware versions of both bulbs types where the same before, I think, there has to be some sort of error by IKEA? Or is it z2m?
What did you expect to happen?
No response
How to reproduce it (minimal and precise)
n/a
Zigbee2MQTT version
1.38.0 commit: fe048e6
Adapter firmware version
20221226
Adapter
Sonoff USB P
Setup
docker in lxc container
Debug log
Logs for LED2201G8: [2024-07-11 13:33:44] info: z2m: Update available for 'Keller Lampe 2' [2024-07-11 13:33:44] info: z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/Keller Lampe 2', payload '{"brightness":254,"color_mode":"xy","color_options":{"execute_if_off":true},"last_seen":"2024-07-11T13:33:44+02:00","linkquality":200,"power_on_behavior":"on","state":"OFF","update":{"installed_version":50331664,"latest_version":50331681,"state":"available"},"update_available":null}' [2024-07-11 13:33:44] info: z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/bridge/response/device/ota_update/check', payload '{"data":{"id":"Keller Lampe 2","updateAvailable":true},"status":"ok","transaction":"izs9s-2"}' [2024-07-11 13:33:44] info: z2m: Update available for 'Keller Lampe 1' [2024-07-11 13:33:44] info: z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/Keller Lampe 1', payload '{"brightness":254,"color_mode":"xy","color_options":{"execute_if_off":true},"last_seen":"2024-07-11T13:33:43+02:00","linkquality":196,"power_on_behavior":"on","state":"OFF","update":{"installed_version":50331664,"latest_version":50331681,"state":"available"},"update_available":null}' [2024-07-11 13:33:44] info: z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/bridge/response/device/ota_update/check', payload '{"data":{"id":"Keller Lampe 1","updateAvailable":true},"status":"ok","transaction":"izs9s-1"}'
Logs for LED2107C4: [2024-07-11 13:52:20] info: z2m:mqtt: MQTT publish: topic 'fkg/Schlafzimmer Nachtkästchenlampe rechts', payload '{"action":"off","brightness":1,"color_mode":"color_temp","color_options":null,"color_temp":370,"last_seen":"2024-07-11T13:52:20+02:00","linkquality":144,"power_on_behavior":"on","state":"OFF","update":{"installed_version":50331664,"latest_version":50331681,"state":"available"},"update_available":null}'
Corresponding entries in http://fw.ota.homesmart.ikea.net/feed/version_info.json Maybe the wrong entry is already removed?
{"fw_binary_url":"http://fw.ota.homesmart.ikea.net/global/GW1.0/01.21.031/bin/zingo_ws-0x2200-3.0.21-prod.ota.ota.signed","fw_file_version_LSB":33,"fw_file_version_MSB":768,"fw_filesize":307758,"fw_image_type":8704,"fw_manufacturer_id":4476,"fw_type":2}, {"fw_binary_url":"http://fw.ota.homesmart.ikea.net/global/GW1.0/01.21.031/bin/zingo_ws_soc-0x2206-3.0.21-prod.ota.ota.signed","fw_file_version_LSB":33,"fw_file_version_MSB":768,"fw_filesize":306714,"fw_image_type":8710,"fw_manufacturer_id":4476,"fw_type":2}
Came here to comment the same. Seems that 3.0.10 broke the bulb. @Koenkk can you prevent others from flashing this firmware to their bulbs asap?
I also flashed two of my LED2201G8 to 3.0.21 and it seems to work fine for me. I am currently on Z2M 1.36.1.
The only thing i needed to do was to re add the device because it had some strange behaviour (everytime i increased/decrease the brightness the color temp was reseted to some default value)
I also flashed two of my LED2201G8 to 3.0.21 and it seems to work fine for me. I am currently on Z2M 1.36.1.
The only thing i needed to do was to re add the device because it had some strange behaviour (everytime i increased/decrease the brightness the color temp was reseted to some default value)
Maybe you have a different hardware revision of the bulb? I bought mine not even a month ago. I will take a close look at the bulb itself.
Errr.. sh... upgrade is in progress right now (z2m: 1.36.1) - i guess i'll find out what's in store for me as somehow stopping the upgrade is probably a worse idea than potentially bricking one bulb?
Errr.. sh... upgrade is in progress right now (z2m: 1.36.1) - i guess i'll find out what's in store for me as somehow stopping the upgrade is probably a worse idea than potentially bricking one bulb?
I'd turn it off now, before it is at 100%. It happens all the time an update can't be finished, because someone turns the switch off or because of other problems.
Lets see what happens - switched the bulb off, Z2M still pretends the update is in progress...
Edit: red popup came up, saying that the device didn't request any further data and called the update off...
Edit2: everything still seems to work correctly - update was only at 3.5%ish or something tho...
The problem seems to exist when using the tradfri gateway as well, there's a reddit post, with my comments: https://www.reddit.com/r/tradfri/comments/1e0ohmc/why_are_my_lamps_in_disco_mode/
Lets see what happens - switched the bulb off, Z2M still pretends the update is in progress...
Edit: red popup came up, saying that the device didn't request any further data and called the update off...
Edit2: everything still seems to work correctly - update was only at 3.5%ish or something tho...
You're a lucky man!
Indeed! I need to level up to a "wise man" tho - read sh*t about updates before clicking any damn buttons :D
Indeed! I need to level up to a "wise man" tho - read sh*t about updates before clicking any damn buttons :D
Well, this seems to be part of our education to "wise man".
I also flashed two of my LED2201G8 to 3.0.21 and it seems to work fine for me. I am currently on Z2M 1.36.1. The only thing i needed to do was to re add the device because it had some strange behaviour (everytime i increased/decrease the brightness the color temp was reseted to some default value)
Maybe you have a different hardware revision of the bulb? I bought mine not even a month ago. I will take a close look at the bulb itself.
I bought mine like 3-4 month ago. Here is a screenshot of my bulb which is updated and working.
But I will also not update the rests of my LED2201G8 in case one of them bricks.
After looking for the cause, I noticed the new 3.0.21 is not for the LED2201G8, but only for my other LED2107C4, which do work fine after the upgrade.
Just for the record: the LED2201G8 is the only lightbulb i've got on my Zigbee network... So, z2m (or Ikea, rather) addresses this bulb with that firmware update...
I had the update offered for LED2201G8, however after re-triggering the update check a few minutes ago the update disappeared, so I guess the issue is resolved now?
Same here. Bought today. Old firmware was 3.0.8 (still shown in zigbee2mqtt)
Same here. Bought today. Old firmware was 3.0.8 (still shown in zigbee2mqtt)
Latest valid firmware for LED2201 is 3.0.10, so if you have 3.0.8 then you should see the update. See the release notes page: https://ww8.ikea.com/ikeahomesmart/releasenotes/releasenotes.html
This issue is about 3.0.21 being wrongly offered to said bulbs,
Same here today. Slow flashing cold white light after updating my 2 LED2201G8 bulbs. Home Assistant/zigbee2mqtt has no control anymore after the update.
If they are bricked by the firmware IKEA has pushed out, how can we swap them for new bulbs at IKEA ?
Well, just upgraded mine today and they're bricked. Sadly found out too late about this github issue.
Is there any way to reflash it or do I have to try convince IKEA to exchange the bulbs?
Ouch. Same experinece here. Interestingly enough, I updated two LED2201G8 from 3.0.10 to 3.0.21 and one them is working fine, while the other is blinking continuously. They were bought together but are probably from different batches, since they came with different firmware revisions originally.
Well, just upgraded mine today and they're bricked. Sadly found out too late about this github issue.
Is there any way to reflash it or do I have to try convince IKEA to exchange the bulbs?
My devices were bricked yesterday by the upgrade. I went to IKEA today and exchanged them. They accepted them without any issues. However, it didn't seem like the saleswoman was aware of the error.
I had 4 bulbs to exchange because I wasn’t home during the update so I did all 4 updates at the same time.
Just wonder if you get the same issue when installing the new bulbs. If we get new LED2201G8 and (auto) update them, do we repeat the issue?
Just wonder if you get the same issue when installing the new bulbs. If we get new LED2201G8 and (auto) update them, do we repeat the issue?
I now have firmware 3.0.8 on the new bulbs. Currently, no new update is being offered through zigbee2mqtt.
IKEA has confirmed to sent me 2 new LED2201G8 bulbs. I have just called customer service and explained them on internet there are bulb owners complaining about their bulbs has been bricked after the (auto) firmware update and leave them with out-of-control flashing bulbs.
Hope the "wrong" firmware is removed.
I only updated one LED2201G8 I had. I just returned the bricked bulb to IKEA and bought a new one. This one has firmware 2.4.5. Zigbee2mqtt still wants to update it to 3.0.21 (I think?, HomeAssistant lists it as 50331681) and also for the other LED2201G8 the update that bricks them is still available. Protip: Force remove the old lamp from Zigbee2mqtt and give the new lamp exactly the same friendly name after pairing. All the HA integrations keep working with the new lamp.
Found this thread after one of my bulbs starting blinking after a firmware update, my newest LED2201G8 IKEA bulb survived this update while an older one did not?
Maybe we should document, which bulbs survive the firmware update, and which do not? On my two bulbs, there are numbers printed, that differ somewhat, so maybe this relates to a hardware revision? Numbers are following the text "TRADRFI WS". Those do not work with firmware 3.0.21, and had firmware 3.0.10 before the attempted upgrade: 2346 50050 2337 50050
I already contaced IKEA support for Austria, and they said, I should return the bulbs in the shop.
failing: 2347 50050 working: 2322 50050
ieee addresses might be an interesting variable as well? My two LED2201G8 bulbs use different address series/OUIs failing: 0x881a14fffexxxxxx working: 0x980c33fffexxxxxx
EDIT: I replaced the failing one now. The 4 digits before 50050 are printed on the box. I took a quick look at several of bulbs and they all seemed to have different numbers. Was so fascinated by this that I didn't notice that the one I finally ended up with was a misplaced 806 lm LED2103G5. Stupid. Should probably have noticed that it was much cheaper and didn't match the amount on the return gift card I got... Oh, well. FWIW, the LED2103G5 is labelled 2349 50050 so I'm not sure what to read into those numbers.
Can't check my working LED2201G8 right now, but the failing one is
2347 50050
ieee addresses might be an interesting variable as well? My two LED2201G8 bulbs use different address series/OUIs
failing: 0x881a14fffexxxxxx
working: 0x980c33fffexxxxxx
The failed ones were all 0x881, but I also have a 0xb43522fffexxxxxx which updated fine.
I bought two lamps at the same time, returned the other one that broke during the update already. Remaining one indeed starts with 0x881a1.....
New one I got in return is 0x60ef...
Didnt dare to update either yet.