Simply adding support for multiple entities would cause errors in the while condition:
while:
- condition: state
entity_id: !input 'light'
state: 'on'
…as it expects exactly one entity. If anyone knows more about state conditions supporting multiple entities, please chime in.
In the meantime you can use the Blueprint as-is on multiple lights by adding a group as the light entity…
groups.yaml:
my_custom_group:
name: My Custom Group
entities:
- light.my_light_1
- light.my_light_2
- light.my_light_3
Then add group.my_custom_group as the light.
The group won’t show up in the auto-complete of the lights field unless the blueprint is changed from:
light:
name: Light
selector:
entity:
domain: light
multiple: false
to:
light:
name: Light
selector:
entity:
domain:
- light
- group
multiple: false
But manually adding group.my_custom_group seems to work without modifying the blueprint.
EDIT:
Also the notion of being able to disable the color loop by turning the light off doesn’t quite work well with a light group. If you have 3 lights running on the color loop and you turn one off, it will get turned right back on with the next iteration. You would need to be able to turn all 3 off within the loop transition time in order to have the script disabled which is like whack-a-mole if you have the transition set to one second. If you already have a button to turn on/off the group as a whole, or a button to turn on/off the script it should be fine though.