[BUG REPORT] Philips Hue Dimmer Level when turning on

🛎️ Get Help Devices
1

I’ve just upgraded to 2.4.0.148 and immediately a problem has surfaced.

I’m using a Hubitat C-8 (NOT a Pro), paired to two Philips Hue Bridges, and things had been fine, but once I upgraded I now notice that when turning lights on they only turn on to 50% brightness at best. Within Hubitat they are actually indicating 100% but that’s not the case.

The same applies if I tell Alexa, Siri, or Google to set the brightness of a bulb thats currently on. It will only hit 50% at best, yet it will indicate 100% (or whatever value I told the voice assistant to set).

As I said, I have two Hue Bridges and I have this problem on both of them. When bypassing Hubitat and using the Hue app, everything works just fine.

I do not use dimmer switches. My switches are all set to “always on” and the actual on/off function is achieved through the use of rules and/or virtual switches. All of those methods have been rock solid for as long as I can remember though, so I know the problem isn’t there somewhere. Unfortunately, as far as dimmers are concerned all I have are Philips Hue bulbs, so I can’t say whether or not this is limited to Hue or affects other dimmable smart bulb brands.

I tried rolling back to the previous version of Hubitat (2.3.9.201) with the Diagnostic Tool but this only made things worse. After the rollback I wasn’t able to control my Hue lighting at all. So I re-updated to 2.4.0.148.

Does anyone know of a fix for this issue, or a workaround until such time that Hubitat can fix the issue?

Thank you all for your time and attention,
Emerson

1 Like
3

Enable debug logging for one of the devices in question . Then, send a command and see what happens and what the Logs say (posting them here, filtered to just this device, would be helpful; screenshots normally provide the best formatting for these).

Also, check the "Events" page/tab for this device to see the command and event history. Commands will be particularly interesting; I suspect you have something else commanding this device, whether on the hub or elsewhere I can't say, but this will rule out the hub.

You will need to follow the process in the 2.4.0 release notes (linked to when you updated on the Check for Updates page) to do this; the easiest method is to restore a matching hub database.

1 Like
4

I ended up finding a solution to my issue. I just had to create rules to bump the brightness to 100 whenever the bulbs were commanded on. Unfortunately the wife-seal of approval was at risk, so I didn’t really have time for data collection.