Using the deprecated hue_activate_scene I had an automation that checked the current time against a global list of time ranges and their correspondig scenes. Example: The “morning” range (06:30-07:59) was associated with the “Bright” scene.
This function node sent the name of the scene (“Bright”) to the Call service node in the msg object, which then used hue_activate_scene to trigger the correct scene, with this in the data field:
{"group_name": "Living room", "scene_name": msg.scene}
Very dynamic and simple.
Using the new activate_scene service, I’m struggling to keep the simplicity up and the number of nodes down.
We’re supposed to now use the scene entities created by the hue integration, but I can’t seem to figure out how this could be done programmatically, if at all possible. I don’t want to have 5 call service nodes, each using the correct manually chosen scene entity. And even if I did, would I be able to put 5 outputs on the function node and only send something on the correct one (i.e. on output 1 in the morning and output 3 in the afternoon)?
I’m open to completely rewriting these automations, but I’m hoping you guys have suggestions on how to do this with the same level of dynamism, and around the same number of nodes. Separate nodes for each scene scales poorly.