search

zinen / node-red-contrib-hue-tunable-white

Node-RED node automatic change white color temperature of lights as the day progress.
MIT License
2 stars 0 forks source link

Feature Requests / Questions #6

Open Galapagon opened 3 years ago

Galapagon commented 3 years ago

Is there any way I can opt-out specific lights from this node? I don't want my porch lights to be "tuned" as they're set to follow dusk/dawn.

I'm also curious if it would be possible to inject payloads into the data points to make them changeable. EG: Inject sun rise/set times into the node to change the data points.

Thank you!

zinen commented 3 years ago

Just to make sure.

But you do know that this node only changes the hue/'glow color' of the light and not the brightness nor turning it on and off right?

Cause it should not be necessary to exclude your porch lights even if they are switched on/off via dusk/dawn rutine.

But if your feature requests is still valid after reading this then... Yes I guess it would be possible for me to make a dynamic menu of light registered in the bridge and add possibilities to uncheck some of them.

Galapagon commented 3 years ago

Let me play with it a bit and see how the lights perform before you change that. I do know that this should change kelvin without changing state or brightness, that's what's so interesting about it! I believe you also said that I could just have something run at say 401am to set the color of the porch lights if I don't want them to change, is that right?

I'm more interested to know if I can change the data points by passing values into the node currently.

Thanks again!

Galapagon commented 3 years ago

I've played with it a bit more today, and it's only outputting 5 of my hue lights in an array out of all the lights in the home. Any ideas what I should do? Also, what should the default power on behavior of the lights be?

zinen commented 3 years ago

I believe you also said that I could just have something run at say 401am to set the color of the porch lights if I don't want them to change, is that right?

Maybe I misunderstand you here. But yes this node will only change lights with a current color temperature at either the default startup level (for Philips lights that is 366) or the last calculated color temperature based on data points1-3. Although when you first drag this node in and deploy - a reset of all lights are made and they should all be changed to the calculated color temperature. This is not explained that detailed in the README I see that now.

I've played with it a bit more today, and it's only outputting 5 of my hue lights in an array out of all the lights in the home. Any ideas what I should do? Also, what should the default power on behavior of the lights be?

You could either send a msg.reset = true into this node to retake control of any lights not at the expected color temperature or define the power on behavior of your lights to be the default setting. Like in the screenshot below.

Philips hue app screenshot