[RELEASE] Philips Hue Zigbee Driver (not using Hue Bridge)

@jonathanb - would this driver work with plain White Ambiance (non-RGB) bulbs too?

I was planning to test this driver out tomorrow, but I just realized my couple of applicable bulbs aren't full color so I figured I'd ask before diving in...


1 Like

If they are generation 3 or newer then yes, there is no reason why it would not work too for all non-RGB functions (e.g. color temperature).

My plan was to take the driver and split out the non-RGB code to have a individual version for the white if it worked.

I'm also able to support the previous Hue generation by falling back to polling mode that @kkossev has been testing.

Lastly, I'm incorporating the healthCheck attribute that @kkossev has been putting into his Tuya zigbee drivers to indicate when the bulb is not responding.


Awesome -- I'm planning to play around with it over the weekend here, so I'll let you know how it goes. Thanks again!!

Thank you @jonathanb !
Your driver is working excellently with my $25 '“midnight/third shift” produced :slight_smile: Philips Hue Gen2 color bulb! (model: LCT007).


Updated version (0.2)

  • Fallback polling mode to support earlier generation of Hue bulbs
  • Health Check attribute added to detect offline (option to select check interval)
  • Some bug fixes

Thank you for adding the healthCheck attribute, Jonathan!

I have configured the healthCheck interval to 1 hour :

Works as expected - if the bulb is powered off from the mains switch, it changes its status to offline after one hour if there were no any commands sent in this period, or 10 seconds after sending a command to the bulb without a confirmation!


Overall, the driver works well, but the odd thing I ran into was that Color Temperature is only coming across as 2 digits... Is that expected behavior?

I have an odd-ball setup that depends on my white-ambiance bulbs always getting reset to certain default CT value, so s 2-digit value was throwing that logic off.

But I really dig the potential here -- thanks again!

Nope, must be something to do with the parsing of the private data that is different. I'm researching it :slight_smile:

1 Like

Uploaded version 0.3 with the following changes:

  • Added support for 'set Enhanced Hue' command which takes an enhanced range hue value from 0 - 360 for when you want more accurate colors than the default 0-100 hue (the hue attribute in the driver will still show 0-100 range but the bulb will get the more accurate level sent to it)
  • Added step hue change (like stepped level change but for hue) and for color temperature
  • Available effects are now set dynamically by querying the bulb for which ones are supported
  • Added mode parsing for the 'Philips Hue White' bulb (on/off and level)
  • Various code cleanups

Known issues:

  • Color Temperature for Hue White Ambience bulbs not showing correctly

I'm really enjoying the added native stepped hue change (up/down with step size) commands so I can use the Hubitat button controller to make it easy for people to control the color from my Inovelli Switches. I have it so 3 taps on the up or down button on the switch will step through the available colors :smiley:


I've pushed a few more updates with fixes for some obscure bugs that needed squashing related to transition times.

Speaking of transition times, this version now lets you set specific times for color changes (vs. level changes) and for level changes you can set the time for dimming up vs. dimming down.

1 Like

Release 1.0 pushed to the repository and should also be available from HPM soon.

Note that the driver URL has changed (new URL in the first post) for manual installation. There are versions of the driver for Philips White and Color Ambiance, White Ambiance (Color Temperature) and White (Dimmable) bulbs.

When updating the driver please run the "Configure" command or simply update the preferences and save as that will also configure the bulb.


White Ambiance driver is working great! I finally got the kinks worked out of my crazy bathroom lighting setup... It's now grown to involve a G&S Group (to get reliable ZGM for the 2 bulbs) that's leveraged by a motion-based RL setup, and then a RM rule ensures the CT always gets properly reset in any "off" scenario.

Messier than I hoped, but hey, it works! And your driver definitely helps a lot - thank you!

1 Like

Hey @jonathanb, came down stairs to let the dogs out late last night, saw your post on my request for help, installed your driver, and went back to bed. Woke up this morning and my bulbs were off... victory!

Well, almost. While these appear to be working as advertised (CCT White 1600lm Hue with BT) the Current States field on the device page does not update to reflect commands that have been sent to the bulb. The bulb is getting them, but changes don't show. I've tried it with, and without the "Enable State Reporting" toggle on and off, but no joy.

@jonathanb Nice driver! I too am waiting on a bunch of Inovelli Blue 2 in 1's. I have about 22 recessed downlights that I'm going to retrofit with Hue downlights. Most will be white ambiance but a few will be color.

New to the Hue ecosystem, so maybe this is just how things work but if I set the color temp through your driver and then cycle the power off and on (which I will have to do until the Inovelli Blue's come someday), the bulbs revert to what I assume is the factory default setting. Is this just how they work when cycling power? I have power restore mode set to "last state".

The power restore last state is just on/off state so it is doing as expected. However, they may support the "power on color temperature" setting which allows setting a fixed color temperature to power on with, I'd have to try it out to see.

I will give Hue credit for their bulbs really adhering to the Zigbee 3 specifications even the more obscure ones like remembering the color temperature option.

Just released a minor 1.02 update for the CT and RGB bulbs that configure the bulb to remember the last color temperature and revert to it upon power cycle.

Note: After upgrading the driver you will need to select "Configure" on each device to push the updated settings to the bulb.

Fantastic, works great. Thanks. I guess this is why they can get away with charging big bucks for their products.

Have a feeling I'm not going to see any of my Inovelli Blue switches anytime soon (only on backorder for 3+ months :frowning_face:) but at least I can start replacing my downlights.

Thanks again.

I've posted a couple of minor update tweaks to the driver based on my heavy usage of it.

  • I ran into a situation where if you turn the light off, then instead of turning it back on you set a dim level (e.g. 20%) it would turn on to the last level and THEN dim to 20%. While this follows the Zigbee specifications as far as I can tell, I changed the code so that if it detects the light is off when a dim command is issued, it will force it to dim UP from off and so you don't get temporarily blinded at night :laughing:

  • I made a change to the preferences to determine what happens when you turn OFF the light.

    • The default is the native 0.8s fade to off
    • I found a Zigbee parameter that also allows for instant off so I added that as an option too
    • Lastly, there is the option to change the OFF command to a DIM to zero which allows for a custom transition length to be used and saves the previous level to use for the ON command

I just received one of the new 6 inch low profile RGBW downlights and will be testing the driver with it this weekend to see if any changes are needed for it.


Update to 1.05 now pushed live

  • Includes new "setScene" command with a list of Philips Hue scene definitions that I was able to find online.
  • This will set color temperature for the ambiance lights and RGB colors for the Color and Ambience lights.

Also, I have tested the new 6 inch low profile downlight and it works with the driver without any changes :slight_smile: It is not cheap but it is well constructed and really bright!