This blueprint lets you apply a (optionally dynamic) light scene to a selection of lights. It’s the ‘blueprintification’ of this script. Next to the dynamic scenes, it was updated to allow light selection by label.
Scene selection dropdown now shows scene set (Cozy, Defaults, Dreamy, Futuristic, Lush, Luxurious, Party vibes, Peaceful, Pure, Refreshing, Serenity, Sunrise). When launching the script (e.g. as an action), users can use the simple name as before, or a combination of set and scene name (e.g., Cozy: Savanna sunset).
The script now includes pre-defined brightness settings. When starting, one now has three options: a) Define a brightness value, b) use the scene-defined value, and c) leave the brightness as it is.
As part of the blueprint input settings, it is now possible to also set default values for the script. All script fields can be specified, and the script can then be run without any arguments (e.g., if you’re mostly using one scene, you can set it as default).
Fixed a bug for non-dynamic scenes
2.5.1
Fixed a bug in assigning first colors for colorloop.
2.5
Added input stop_when_lights_turn_off to allow running the script continuously.
Added scene “Colorloop”, which iterates over the entire color wheel. Colorloop uses hs color scheme, and only changes the hue value without touch the saturation.
Re-added a scene consisting of random colors. Note that random colors are selected once when the script starts and then distributed over the lights.
Added input debug to generate debug messages in the log.
2.4
It is now possible to also specify devices. If a device has multiple entities from the light domain, all will be added individually.
2.3
Selecting the lights is now done via proper lists, and no longer relies on parsing json
New scene: Malibu pink
Description of the scene field is shorter
Added a report entity field. This can be a input_text entity and whenever a scene is set, the scene name is written into the entity.
2.2
Transition time is now a blueprint field.
Repeat delay now has a default value of two minutes.
Fixed bug in duration format.
2.1
The blueprint now contains all the Hue color scenes that are listed here.
2.0
Made into a blueprint. Intended use case: Instantiate blueprint for each area (then they can run independently in parallel).
Hi there! I have been using this blueprint for a long time and really like it! Thanks for all the work!
I have added a script per room so that’s quite s few now. I saw that I was currently on blueprint version 2.1. I am not using blueprints that much; what is the easiest way to update the scripts to use the new version of the blueprint?
If you’ve installed it by clicking on the above link, it should be possible to update by going to Settings → “Automations & Scenes” → Blueprints. Then search for the blueprint, click on the three dots to the right and select “reimport blueprint”. That’s it.
Thanks a lot for the support, that did the trick! Very nice updates and love the new scenes! Some extra work for me since I need to update my input list
EDIT: I am sorry, the following does still work, there was another error causing this issue in my setup!
Another question: I have always sent a transition time into the script like in the image, since I want to vary that depending on the trigger (so the trigger.id is an integer).
It seems that this does not work anymore, and the transition is always 2 seconds.
Could you check that and help me out with that?
Hi, I have updated my blueprints but currently cannot use the developer tools because it thinks I would like to create ‘my scene…’ without any colors input.
Oh right, sorry for that. Didn’t think about this. Will be fixed asap. It should be possible to wrap the action call into a script.turn_on in the meantime.
I have been looking for something exactly like this, and I’m excited to try it. However, when I attempt to import the Blueprint, I get a timeout error. Any ideas how to get around this? Thank you!
Good question. Timeout doesn’t sound like it’s caused by the contents of the blueprint. What exactly did you do to import it? Click the button above? Does that work for other blueprints?
I imported the schematic and selected entity then I savedand then, After saving it, I ran the script and nothing happened (no changes in the color of the lights) and no error So where to look for the problem?
I chose the download trace option, but this file is so long that it won’t fit here, and I don’t see the option to add the file, so how can I add it here?
