Zigbee OTA - Osram Lightify Bulbs stuck at 80%

Hi guys,
I'm trying to update the firmware of my Osram Lightify Bulbs but looks like the process enters in an infinite loop trying to upload the firmware to the bulb stopping at 80% progress.

Firmware update for [name:luz_corredor_fundos_casa, manufacturer:OSRAM, imageFileName:110C-0008-01020509, fileVersion:01020509] is 80% complete.

After this message, it starts all over again:

Starting firmware update for luz_corredor_fundos_casa, OSRAM from 01020205 to 01020509.

If I don't restart the hub, it stays like this forever... Not sure how to proceed to update bulb's firmware.

you might try starting the process at night when there's less zigbee traffic.

1 Like

Besides @mike.maxwell's suggestion, also try this:

Reset the bulb and re-pair it adjacent to the Hubitat, so it appears as a direct child device (or neighbor) of the Hubitat.

Iā€™m convinced that there are some zigbee repeaters/routers that do not play nice during firmware updates of devices that they route packets to.

3 Likes

I re-paired another bulb very close to the hub and the issue still persists as we can see with the timestamps. It reaches 80% then goes back to start...

2021-05-12 18:15:27.638 Firmware update for [name:luz_banheiro_ed, manufacturer:OSRAM, imageFileName:110C-0008-01020509, fileVersion:01020509] is 80% complete.
2021-05-12 18:19:00.578 Starting firmware update for luz_banheiro_ed, OSRAM from 01020205 to 01020509.
2021-05-12 18:20:51.667 Firmware update for [name:luz_banheiro_ed, manufacturer:OSRAM, imageFileName:110C-0008-01020509, fileVersion:01020509] is 40% complete.

Here is my route table:
Parent child parameters
EzspGetParentChildParametersResponse [childCount=1, parentEui64=0000000000000000, parentNodeId=65535]

Child Data
child:[botaosala, 7263, type:EMBER_SLEEPY_END_DEVICE]

Neighbor Table Entry
[luz_corredor_escada, 75A8], LQI:170, age:7, inCost:7, outCost:0
[luz_banheiro_ed, 8C0E], LQI:254, age:4, inCost:1, outCost:3
[luz_corredor_fundos_casa, E57B], LQI:215, age:4, inCost:5, outCost:7

Iā€™m having the exact same problem with the Garden Spots upgrading. They make it to 80% then restart. Any thoughts?

+1 here, stuck at 80%, same device, same firmware.

+1 Here - Same issue - Stuck at 80% and restarts. It is close to the HUB and is a new device for this location.

Firmware

search

sys:12021-07-22 12:37:23.403 Firmware update for [name:Porch Light, manufacturer:OSRAM, imageFileName:110C-0008-01020509, fileVersion:01020509] is 20% complete.

sys:12021-07-22 12:34:47.048 Starting firmware update for Porch Light, OSRAM from 01020492 to 01020509.

+1 - Stuck at 80%. I have 8 bulbs all purchased at the exact same time (came in 2 packs of 4 ea) - this is the only bulb doing it.
I have an OSRAM lightify gateway. I reset the bulb, and put it into a desk lamp 5 ft from the HE. After reset I connected it to the OSRam Gateway. According to it, there is no firmware update for this model bulb (at least none is offered and the bulb shows as 'up to date' (as of today, 7-28-21). I connected 1 other of the set (that was in also in place on hubitat and working), and it also showed no updates.
Last night I did update the HE to the 8.143 (?) version fwiw. I had never had this problem before.
I'm hoping that by removing this from my zigbee network and re-putting it back in the firmware update failure will stop. Here's my log:

and here's the device data values:
image

a simple reboot of the hub will clear out any in process firmware updates.

ooh. that's a new tidbit - I'll give it a try - though I thought that the reboot started it. thx.

Did anyone find a solution for this? I'm trying to update my Sylvania/Osram Gardenspots. It'll hit 80% and then restart after a few minutes and then loop.

"Starting firmware update for Gardenspot, OSRAM from 01020492 to 01020510"

It looks like others are having issues upgrading from the 492 firmware. Could it be that the new firmware isn't compatible and perhaps it's incorrectly flagged with this model?

I have other Lightify Flex Strips (Indoor and Outdoor) and Hubitat states the 492 firmware is the latest for them.

+1, OSRAM tunable white bulbs stuck in firmware update loop, never makes it further than 80% in the logs.

In my case, it's trying to go from version 01020492 to 01020509.

  • 1 - Thought I'd give this a shot - I have 2 bulbs of this model and tried an update on a test bulb. It looped. took forever. I looked as hard as I could for the firmware bin file to put it local and push it to the device but couldn't find the file anywhere. Needed (as previously noted) to reboot my hub to stop this loop.

these files are copied to the hub prior to being sent to the device, so they are local.
the zigbee process works differently than the zwave one...

It's entirely possible the device itself is puking and isn't capable of updating to the latest firmware version, at this point given the repeatability of this issue that's where I would place my money...

2 Likes