Philips Hue bugs x2 (v4.118)
-
I've noticed two bugs with the current Philips Hue integration when controlling some Hue ambience bulbs, connected via a Philips Hue Bridge 2.0.
-
When dragging the custom color slider in flux from left to right, from 1900k-6450k, the monitor and connected Philips bulbs perform as expected. Unfortunately, when dragging the slider up one extra notch, from 6450k -> 6500k, then connected Philips bulbs suddenly drastically REDUCE their color temperature to a much more orangy color (approximately the level you see when flux is set to 2700k). The color of the monitor is correct at 6500k, it's just connected bulbs that seem to respond incorrectly at the 6500k mark.
-
When flux is running but disabled, it does not relinquish control of the smart bulbs, resulting in a room's bulbs as being dim and relatively orange, despite the computer monitor being bright and relatively blue. There seems to be a disconnect here, forcing the user to exit out of flux completely if they want not only their monitor to have full brightness again but also the bulbs in their room to revert to full brightness also.
Here are the situations where flux will be running and has intentionally been disabled, where connected smart bulbs will behave as if flux has NOT been disabled:
- flux is disabled due to a full-screen app
- flux is disabled due to the user (i.e. using disable "for an hour" or "until sunrise")
Has anyone else with experience of using Philips Hue bulbs got any ideas what's going on here?
-
-
Thank you - we have the first issue on our list to fix. We did not detect it earlier because we usually use the default "Quite a bit warmer" setting which doesn't trigger it.
For the second one, this is on purpose, but really there should be an option. Mainly, if you use Hue in any room where your computer isn't, then it can be quite unexpected to have the lights in all the rooms of your house change to 6500K. We probably should add a way to specify which rooms/lamps are close to you, and which are usually not!
-
@herf said in Philips Hue bugs x2 (v4.118):
For the second one, this is on purpose, but really there should be an option. Mainly, if you use Hue in any room where your computer isn't, then it can be quite unexpected to have the lights in all the rooms of your house change to 6500K.
We probably should add a way to specify which rooms/lamps are close to you, and which are usually not!
Isn't that what this feature is for? You can already pick individual Hue bulbs for f.lux to control/ignore (essentially allowing f.lux to only control bulbs near your PC).
Am I missing something here? :)
-
@Mr-Ethernet Well, lamps in that list are outside the f.lux schedule entirely.
I thought this question was only about how we've not made "disable" show full daylight. It's really different depending on if you have roommates/family in other rooms vs. if your whole hue kit is in one room.
-
This post is deleted! -
@herf said in Philips Hue bugs x2 (v4.118):
Well, lamps in that list are outside the f.lux schedule entirely
I'm super confused now!
So the lamps in that list are actually outside the f.lux schedule? I can't quite get my head around that.
The bulbs immediately follow any custom color you set using the slider, which basically just modifies the schedule for daytime/sunset/bedtime.
I thought the point of Hue -> f.lux integration was that you would get ambient light that automatically matched your screen brightness.
If the bulbs always ignored the schedule after pairing them with f.lux, what would be the point of integrating Hue with f.lux in the first place? :)
I must still be missing something about how this is supposed to be used!
-
Yes, if you turn off a lamp within the "Hue lights to use" menu, f.lux will not change it at all - and everything else is automatically in the schedule.
-
So, the way I see it, being able to uncheck bulbs in this manner means we can already easily get f.lux to selectively control only Hue bulbs that are close to our computer screen.
@herf said in Philips Hue bugs x2 (v4.118):
We probably should add a way to specify which rooms/lamps are close to you, and which are usually not!
My point is that such functionality already exists!
If we simply uncheck all bulbs that aren't close to the computer screen where f.lux is running, then it already works as intended and there would be no problem with only those bulbs behaving differently during a f.lux disable. It's not going to interfere with any other bulbs in the house as the user can uncheck all the other ones.
-
Well the goal of this feature is mainly to keep consistent timing across as many screens and lights as possible (because people move between rooms).
Our goal with it is to change the timing of light vs dark overall, and not just for one room or one screen. So it's really people-centric and not screen-centric. It would be worse if the default behavior was narrow and only about one screen.
We will have more controls for this (including multiple users) in the future (there are a ton of internal ones that we haven't exposed yet).
-
Awesome. Thanks for the explanation.
And I'm glad to hear there are new bells and whistles coming - looking forward to trying them out!
