Philips Hue bricked by OTA

wbsantos commented 1 year ago

What happened?

I have bought 5 Philips Hue bulbs A21 high lumen (model 9290024717).

They all paired with zigbee2mqtt through a sonOff dongle. And I got it paired with Hue app through Bluetooth.

As they were all new, I was prompted with OTA update in zigbee2mqtt, and I was not careful enough to update them one by one. I just started all of the updates at the same time.

It took just about 6 hours to finish, but three out of the 5 bulbs are completely dead now.

The two that updated correctly are shown in zigbee2mqtt with the new firmware version. The ones that are bricked are offline in zigbee2mqtt, and they are shown with the old firmware version.

The Hue app can't connect with those three through bluetooth either.

I have tried a couple of things to reset the three bulbs:

Turn on the lights for 8 seconds and then off for 2 seconds (repeated 5 times in a row)
Pressing the buttons "on" and "off/hue" of a hue dimmer very close to the bulbs
Getting the bulbs close to the coordinator and ran a touchlink scan in zigbee2mqtt
Reset the bulbs using an Alexa with zigbee, informing the serial number of the bulbs

What I haven't tried yet:

Reset the bulbs with a Hue bridge. I don't have one and they are kind of expensive just for a test
Running Hue Thief script (I will try this one, but I waiting a new zigbee coordinator I ordered that is compatible with this solution). But I have little hope that it will work

I can't blame zigbee2mqtt because I have no idea of what happened. And even if it is some bug here, this still a free and amazing software. I just want to report this problem so other people may be more careful than I when updating with OTA. And if anyone has any tip of how I can get my faulty bulbs to work again, it will be much appreciated (these things are really expensive).

What did you expect to happen?

I expected the bulbs to be updated successfully.

How to reproduce it (minimal and precise)

Update up to 5 devices firmware at the same time.

To be honest I have no idea of what caused the problem. It might have been zigbee2mqtt, my sonoff coordinator, the firmware, the bulbs themselves...

Zigbee2MQTT version

1.32.2

Adapter firmware version

20230507

Adapter

Sonoff Zigbee-Zigbee 3.0 USB Dongle Plus

Debug log

The debug log wasn't on during the update.

uli-rpi commented 1 year ago

Use an echo speaker with an integrated ZigBee hub. These are currently, for example, the large Echo Show or the Echo Plus of the second generation.

If you meet these requirements, open the Alexa app and start the search for a new Philips Hue lamp in the device menu, which of course cannot be found. In the following menu you then tap on "Get help with connecting" and there you will find the action "Reset Philips Hue lamp".

In the following display you have to enter the six-digit serial number, which can be found directly on the bulb, in the Alexa app and can then reset the lamp. It should then be found immediately via the search, whether via the Philips Hue Bridge or another ZigBee hub.

wbsantos commented 1 year ago

Use an echo speaker with an integrated ZigBee hub. These are currently, for example, the large Echo Show or the Echo Plus of the second generation.

If you meet these requirements, open the Alexa app and start the search for a new Philips Hue lamp in the device menu, which of course cannot be found. In the following menu you then tap on "Get help with connecting" and there you will find the action "Reset Philips Hue lamp".

In the following display you have to enter the six-digit serial number, which can be found directly on the bulb, in the Alexa app and can then reset the lamp. It should then be found immediately via the search, whether via the Philips Hue Bridge or another ZigBee hub.

I have tried it already, I have an Echo 4th generation (https://www.amazon.com/Echo-4th-Gen/dp/B07XKF5RM3). Nothing happens, not even a blink of the bulb.

By the way, the bulb doesn't turn on when plugged, and I haven't changed its "power on" settings from the "turn on" by default.

uli-rpi commented 1 year ago

Another idea would be with A…. ordering a Hue dimmer switch, resetting the lights with it and then sending the switch back...

WFLM commented 1 year ago

I've just faced exactly the same situation with Hue white and color ambiance E26/E27 1600lm and want to find a solution. I'd bought 2 lamps and decided to update them. One of them got 1.104.2 without any issues, the second one was bricked after the update and it doesn't give signs of life.

The adapter, Adapter's FW, and Z2M versions are the same.

I've already tried Touchlink, a Direct Bluetooth connection from the smartphone.

maartenhbe commented 1 year ago

Had the same issue with one of my bulbs. I bought a dimmer and was able to reset the bulb using the dimmer so there seems to be a way out (at least it was for me).

The strange thing is that whenever I added the once-bricked bulb to my network, others bulbs would randomly go offline after a couple of hours while it was a stable network for months before that. Currently not using that bulb anymore and all stable but unable to force re-apply the OTA update (which might help and maybe is a concrete feature to add?).

deviantintegral commented 11 months ago

I also ran into this with a Philips 9290024683 Hue white ambiance A19 1100lm with Bluetooth. One bulb updated fine, the other has stopped working completely. The dimmer switch didn't work to reset. Hue support suggested this reset procedure (which didn't work):

Reset with wall switch (this will reset all lights controlled by that wall switch):

Turn the switch off, wait 5 seconds, turn it on, wait 5 seconds, turn it off again.

Repeat this process at least 5 times.

The light will blink if the process was done correctly.

Repeat the process for all the lights, if needed.

I suppose it's possible there's some hardware issue that breaks updates, especially given I've never had trouble on any previous bulb.

github-actions[bot] commented 10 months ago

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

deviantintegral commented 10 months ago

Not stale - and challenging to test, given that AFAIK there's no way to reset the bulbs if firmware does fail to apply.

wernerdaehn commented 8 months ago

Same here. When turning the light on via the 230V power switch, they remain dark. Unresponsive to dimmer switch reset, bluetooth, and hue bridge. Happened to two out of six.

DaleJP commented 6 months ago

The same thing happened to me. I banged it on the table a couple of times, and it started working. No lie.

Bizarre.

wernerdaehn commented 6 months ago

Bricked one more. This time I updated via bluetooth and then the lights got the signal to turn off. I wonder if it's that - getting a command during the update.

matiasnl23 commented 2 months ago

I'm reading this while my Hue LightStrip is updating. Thankfully, I started with one light instead of updating all of them at once. It's my first time updating it with zigbee2mqtt. Previously, I've always used the Hue Bridge. I'm hoping the update goes smoothly. I'm not sure if I'll proceed with updating the other lights...

wbsantos commented 2 months ago

I'm reading this while my Hue LightStrip is updating. Thankfully, I started with one light instead of updating all of them at once. It's my first time updating it with zigbee2mqtt. Previously, I've always used the Hue Bridge. I'm hoping the update goes smoothly. I'm not sure if I'll proceed with updating the other lights...

What I usually do nowadays is to pair the light to the smartphone app using Bluetooth, I then update the firmware through Bluetooth instead of through ZigBee.

matiasnl23 commented 2 months ago

What I usually do nowadays is to pair the light to the smartphone app using Bluetooth, I then update the firmware through Bluetooth instead of through ZigBee.

Thanks for the recommendation. I'll do that. I hope it takes less time than through the Zigbee network.

wbsantos commented 2 months ago

What I usually do nowadays is to pair the light to the smartphone app using Bluetooth, I then update the firmware through Bluetooth instead of through ZigBee.

Thanks for the recommendation. I'll do that. I hope it takes less time than through the Zigbee network.

It does. Through Bluetooth takes a couple of minutes (5 at maximum). Through ZigBee I found that takes about an hour. It might be a problem with the protocol or with my mesh network.

calos9999 commented 2 months ago

Hi I was upgrading my bulb to the latest firmware version. Everything seemed to go smoothly, the bulb rebooted as it usually does, but since then it can't connect to bluetooth It tries but can't Any idea?

WFLM commented 2 months ago

Hi @calos9999 Have you tried to reset the bulb via Touchlink?

WFLM commented 2 months ago

Hi @calos9999 Have you tried to reset the bulb via Touchlink?

No, touchlink is part of “Hue Essential” app? I have to unpair the bulb from my phone?

No, you can find it in Zigbee2MQTT. You need to power on the lamp and place it a few centimeters from your Zigbee adapter. Then, use Touchlink in Z2M to find and reset the lamp.

wernerdaehn commented 2 weeks ago

Bricked one more. This time I updated via bluetooth and then the lights got the signal to turn off. I wonder if it's that - getting a command during the update.

I felt brave and updated some more Hue lights. No issues. So either something changed or my suspicion that any command during an update, bricks the hue light, is correct.

Before I updated approx 5 devices and 3 got bricked. Now I updated 20 devices without a single issue. I disable all automations and make sure nobody is using the lights and then click on update in the ZigBee2MQTT --> OTA screen one after the other. Each device takes approx 30 minutes to update and if I update two simultaneously, the time estimate doubles. Most of the time the send is interrupted when updating multiple in parallel and a new update picks up where the send was interrupted, e.g. with 20%. Hence updating one after the other.

My suggestions:

Even if the user updates multiple, queue the requests and update a single one at any time. This way I can queue to update all 100 lights and don't have to watch the updates myself.
During the update do not let any commands pass to the lights.
Document this issue with hue lights!

Koenkk / zigbee2mqtt