This does seem to imply it. Why would you support OTA for bulbs you don’t support?
Why imply and not just say though? Isn’t this something that you would want to shout as a company? This just seems odd.
1 Like
Even though it is not officially supported some people choose to connect their Hue bulbs directly to the SmartThings hub. The SmartThings hub firmware update includes the latest Hue firmware that Hue bridge users received back in October.
Note that we are still finalizing the testing of the Hue firmware and haven’t enabled users to actually update the direct connected Hue devices. Sorry for the confusion.
3 Likes
.028V against the batteries would appear to be a resistance and would cause them to drain faster. It would not be like they were being charged, if that is what people are arguing over. Now what would really concern me is if 6.xx+ volts were being applied to the batteries because that would be a serious fire risk.
Has anyone got the firmware update yet?
Edited:
Just went back and fully removed the batteries and tested again and I too am only seeing .02 V+ against the batteries. But I believe that this is just the monitoring circuit because if I leave the probes connected, the reading keeps approaching zero. Without having the circuit diagram, it is impossible to know for sure, but the reading is insignificant.
Ultimately the question becomes, why does the HUB not have a low battery notification so that we could remove the batteries before they leak?
Crazy. Okay.
@tpmanley any possibility that we may see HUE lights (directly connected) supported in the future?
Showing updated today, but on 16.00013. Not sure what’s up with that…
I’m guessing that is because they already released 16.00012 to beta testers for OSRAM updates several weeks ago. That firmware did not include the battery fixes.
1 Like
They forgot to update me :’(
1 Like
Me too. I think rebooting the hub may force the update (assuming that it’s been pushed out).
I’ve only just got mine, be patient. Don;t reboot it, it might be half way through an update!
Got it on all three hubs.
Once the update is received how does one trigger an osram RGBW firmware update? I have gone into the IDE and pushed check now and waited but no changes.
Current Version: 0x01020325
Target Version: 0x01020492
Last Updated: N/A
Last Checked: 2017-01-30 2:18 PM EST - Check Now
I had to do it by physically power cycling the bulbs but I’ve heard that the check now button works as well.
There is a limit of 5 simultaneous firmware updates.
wow… three? 
1 Like
Mine is still 000.016.00009 
Just got mine in the last hour. V16.13 like everyone else.
You need to click ‘Allow OTA’ in hub utilities. See https://support.smartthings.com/hc/en-us/articles/215394303-ZigBee-OTA-firmware-updates for more info. Once you’ve done that, like @jhamstead said you can power cycle the bulbs or click Check Now.
Sorry, I don’t have any information on that. I’m just a zigbee firmware guy 
1 Like
Rebooted the hub in IDE and once it came back online it displayed 16.13 
lucky it wasn’t halfway thru when it went offline!!