Hue Bulbs direct to Hubitat. Power on options?


Having had some issues with my Hue Bridge and/or interface recently, I'm re-thinking the wisdom of having a large number of my devices connected to a separate hub so have just moved a few of them over to be connected direct to Hubitat. It went really smoothly if anyone wants to do the same - just delete them from the Hue Bridge in the Hue app and that leaves the bulb in pairing mode which Hubitat then found instantly as a Generic Zigbee Bulb and they work great. I have been careful not to move over any that are likely to be picked up as repeaters for other Zigbee devices as I know they can cause problems with that.

But the question is, when connected directly to Hubitat, can you chose the behaviour of the bulbs when they start up (eg after a power cut) as you could when they were connected to the Hue bridge? My bulbs have all had the firmware update to allow that feature in Hue and were set up to retain last settings there. But having just turned one off at the switch and back on again to test it, it came on even though it was previously off.

The bulbs I have moved are in bedrooms, so it would be a bit annoying to have them all come on if we had a power cut in the middle of the night which isn't unknown here. There is nothing in the Generic driver to set start up behaviour, and I couldn't see a specific Hue bulb driver other than the huebridge ones.


This very likely is configured in the firmware of the hue hub and therfore the firmware version of the bulb probably won't be helpful unless you are using the hue hub. Hopefully I'm wrong here but I think what youi want would need to be handled by an app and that app would need to know when there is power outage.

Before Hue made the power on changes, I had the exact problem in my bedrooms and the fix took 2 steps to resolve. I had to setup a way to know when there was a power outage and then set the Hue bulbs to what they were before the power was cut. My solution did/could not prevent the bulbs from turning on, but at least they would turn of a couple of seconds later on their own.

I no longer use the app I created but it is located here:

For power outage detection, there are a few option depending on your skillset


@Geoff_T, I just thought of something else. I never connected my hue bulb directly so I don't know what the logging looks like but...if you turn on debug logging and cut the power to the bulb and then turn it back on, you can see whether the bulbs send a zigbee report back to the hub. If they do send a "power returned" message of some kind, then @mike.maxwell may be able to use this zigbee report to set a power on behavior like you requested...or at least to set an attribute that you can tie into an app like RM.


Interesting thoughts. I have just tried the power off and on again with logging on and get this line when the power is switched back on:

dev:25022019-06-18 05:39:38.884 pm debugParse: catchall: 0000 0013 00 00 0040 00 0279 00 00 0000 00 00 007902297A6604018817008E

Even when connected to the Hue bridge though, wouldn't the start up behaviour have to be coded into the bulb itself somehow? If not by the time the bridge was back up and running to be able to send anything to the bulb, it would have already turned on the instant the power was back wouldn't it?


If I had to guess, the Hue app via the Hue Bridge sent a custom setting that is likely stored on the bulb itself, so unless it's following some ZLL/ZHA convention for how this is done, the traffic would likely have to be sniffed and, if reverse-engineered, added to a special driver Hubitat driver for Hue bulbs. Mike will probably know. But I agree it's likely not the Bridge "listening in" and fixing things after the fact since the behavior is instant (you could test this by powering the Bridge off and seeing what happens when you flip a switch on the lights, I guess).

On Hubitat as-is, you'll have to use some solution like the above. I never got quite that fancy--I just had a rule that watched for a bunch of lights I wouldn't normally turn on at the same time all coming on and staying on for a certain amount of time, and then notified me to check on things. :laughing:

PS - Did the Hue Bridge integration get worse for some people? I recently experimented with moving some bulbs from the Bridge directly to Hubitat (a separate hub I set up for this--I wouldn't recommend doing it this way if you have other Zigbee devices on the same hub, as you know). Turns out that's not perfect, either, partly due to the lack of true "scenes" causing everything to be a bit slower than Hue was. Right now I'm half and half and might stay that way to see which ends up working better.

PPS - I'm not sure if it's 100% necessary, but you might also want to keep your Hubitat hub on a ZLL-compatible Zigbee channel so it's easier to move bulbs back to Hue if you can't properly remove them from Hubitat first for some reason (I think you'll have to find another way to reset them like a Hue Dimmer or Lutron Connected Bulb Remote if you can't, otherwise I'm not sure if they'll be able to "listen" even with the serial number to get "stolen" back to Hue...but I could be wrong).


If I had to guess, and I am, the power on options set while the bulbs were connected to the Hue bridge, would likely have been wiped from the bulb when you removed it from the bridge.


Yes, a few of us have had issues with bulbs randomly getting set to 1% instead of the correct value.

I think that's most likely too. I was hoping there was a way for Hubitat to resend the necessary code back to the bulb as part of it's configuration.


I can confirm that this is true. :slight_smile: (I suspect there's something, like the motion sensitivity on the Hue Outdoor Motion Sensor, whose traffic could be sniffed to discover the setting that configures this on the bulb itself to allow configuring this when paired to Hubitat. But I'm definitely guessing on this part.)


I'm getting that with directly-paired bulbs, too, though I'm not sure I've seen it on Hue bulbs. I have seen weird values on Sengled, but I think it was something like turning on to 44% instead of 100% like they were told. That being said, I don't think Sengleds show a big difference between 1% and 44%, so unlike Hue I can't tell by looking and am only going with what Hubitat tells me. :laughing:

I'll do some more playing with mine to see if I can narrow this down at some point.