Under review

How to use Scenes with the new HUE Parameter set?

Geir Hardt 4 years ago in bOS Configurator / Devices updated by Ricardo Pinto | visiontech pt 4 years ago 12

After ugrading to the new version of bOS, my scenes containing HUEs are not getting recogniczed any more.
What do I need to configure in a sceene to make the sceene recognize that the room setting are according to the sceene?
In the previous version, The color values of the light was enough for a scene to be recongnized.
I have tried with most combinations 
of  HUE.Power with HUE.Brightness, HUE. Color Temperature and HUE.Color with little success. The scene's State does not seem to be set consistently. 
Is there an explanation of how to use Scenes with HUEs after version 4.4.4?


Please follow up on this as soon as possible.

I have a configuration with almost 50 scenes, which has stopped reporting the scene state as true when the sceene is activated. The true state for the scene is used to trigger scripts which will set status on scene swiches around the house, etc.
At the moment, my house is not working  due to the upgrade. 

Removing the hue configuration from the scenes, makes the scene work as expected...

This seems almost like my previous attempt to upgrade 8 months ago, then it was the z-wave devices which stopped working. Do I need to downgrade again?
Plase start testing releases better to avoid situations like this one. 

It is really hard to understand how to utilise functionality without proper documentation, and especially with functionality that does not work properly! 

Under review


apologies for delayed response, We will do some internal testing regarding this issue in the office and try to troubleshoot the issue and try to resolve it, if it turns out there are some issues with our HUE driver in scenes.

Best regards.

Thank you for answering. I had to get around this problem. So I ended up removing my HUEs from the all scene definition ib bOS.

To replace the functionality, I have defined a set of scenes for each Room in the HUE app and are now activating these scenes through the HUE API.

This has turned out to work quite well. (Actually much better than using HUEs as part of scenes in bOS), and it enables all functionality of the HUE app to be utilized, with respect of light configuration for scenes.

I guess the functionality of the HUE app will allways be at least one step before the functionality offered in bOS. A way to get around this and still support scenes, is to add support for Roms and Scenes in bOS. So that it would be easier to utilize the HUE API.

What do you think?


In fact the scenes in bOS are not turning to "true" state, with simple things like a "true" Power state from a HUE light.

And by the way, I've noticed a strange thing:

If the HUE lights are controlledfrom the HUE app, or an external device, such a HUE remote, bOS takes around 12s to update the status. Is that normal? I've noticed the same thing in previous bOS versions.

In fact, every HUE state (Power, brightness, etc) is actually only changed after around 12s if controlled from outside bOS.

More findings:

When using the brightness on HUE lights, if I press a certain percentage, it would make sense that the light would turn on at that percentage. But it doesn't. The brightness only works if the light is already on. Which means, that I have to turn the light on and then I can set the percentage. This doesn't happens in a regular KNX dimmer...but probably is a limitation from the API.

And even more findings:

The HUE lights at the minimum brigthness on the HUE App, show as 0% in the brightness scale of bOS...

Best regards

Hello Ricardo,

thank you for your extended post. We'll look into it more and try to see how to improve the communication and resolve these issues.

Best regards.


unfortunately, the HUE lamps are not sending change values by themselves.. bOS needs to constantly ask for the status in order to update the values. Currently there's a request function enabled on our HUE so bOS tries to be updated with the device. To prevent package overlay, there's of course a delay between each request, hence the delay when controlling the lamp via it's app.

Best regards.


Got it... I was pretty sure that it could be something like that, or an API limitation from HUE side.

As for the states, if you're querying the lamp status, then I think it should be easy to solve the states of HUE lamps on scenes, even with the delay between requests. Hope so... :-)


Hi all,

Geir, are you sure you've tested the HUE power state in the scenes correctly?

I own 2 hue lights on my office, and in the past days I've decided to recreate some of my scenes.

The fact is that I've placed the 2 hue lights on the scene (which contains dozens of KNX lights as well), just to make a general off, and the truth is that I'm getting a correct state of the scene.

The only noticeable thing is the 12s delay when using hue externally. It means that the scene is actually working.

If I use hue from the hue app or my hue remote, bOS will change the scene state after the delay between requests (approximately 12s). Otherwise the state is immediately changed.

Best regards

@ComfortClick; did you manage to decrease the lag between setting the HUE and bOS detecting? I did create some logic where a sensor triggers some lights, and on the "power:true" of the HUE other KNX based lamps are triggered as well, but there is a 3 à 5 second delay... 

Can we decrease this? 


The lag is a "must", or kind of.

This is to prevent pooling the HUE too often. So the lag, is actually implement on purpose...

Personally, for me the lag is acceptable.

Best regards

Hi Ricardo, 

Yes, I figured. The this is the only way to control my KNX lights with my HUE motion sensors; so the lag is too long for my case... Do you have any idea if I can perform PUT requests within bOS? If I can do this, my issue is one step closer to getting fixed :-) 



You can use the Phillips Hue API to do that.

The API is public, and free. You need to pool the sensor on the API, for example every second, and to create your logic.

I don't have any example with a sensor, as I don't own any, but I use the API for other things and it's perfectly possible.

We shared some thoughts on other post: