What you posted isn’t a self-contained automation, it is associated with a blueprint. We would need to see the blueprint in order to make accurate suggestions. However, based on what I see I assume that the value of target_brightness will be applied to all devices listed under device_id.
Is it simply adding target_brightness: 50in between each entity/id?
No, you can’t put anything within the device_id option other than a valid device identifier.
blueprint:
name: Lights On At Sunset
description: Turn on the following lights at sunset
domain: automation
input:
target_light:
name: Lights
description: This is the light (or lights) that will be activated at sunset
selector:
target:
entity:
domain: light
target_brightness:
name: Brightness
description: Brightness of the light(s) when they're activated
default: 50
selector:
number:
min: 5.0
max: 100.0
mode: slider
step: 5.0
unit_of_measurement: '%'
elevation_shift:
name: Elevation Shift
description: Using an elevation offset (height of sun relative to the horizon)
to shift the sunset trigger, either earlier or later. Positive values bring
the automation start time forward, whilst negative values delay the start
time. To approximate Golden Hour - set the Elevation Offset to 1.
default: 0.0
selector:
number:
min: -3.0
max: 3.0
mode: slider
step: 1.0
source_url: https://gist.github.com/CyanAutomation/1b8bafd033f73e3c24e42e8f381ff906
mode: single
variables:
target_brightness: !input target_brightness
target_light: !input target_light
trigger:
platform: numeric_state
entity_id: sun.sun
attribute: elevation
below: !input elevation_shift
condition:
condition: sun
after: sunrise
after_offset: 01:00:00
action:
- service: light.turn_on
target: !input target_light
data_template:
brightness_pct: '{{ target_brightness | int }}'
In that case, the blueprint you are currently using cannot be used for that purpose unless you modify it extensively.
The major obstacle is that your requirements are challenging to implement. You want a blueprint that can accept one or more devices and potentially a different brightness value for each device or possibly only for some devices or even no brightness specified at all.
I don’t know of any selector that can accomodate that requirement.
OK, some time could have been saved had you mentioned that in your first post.
In that case, your automation will require a hard-coded list of devices with a corresponding brightness level specified for each one. I suggest using a dictionary to store that information and then use a repeat to iterate through the dictionary, retrieving the values needed for the light.turn_on service call.
If you look at the debug of the automation, it will show you actual yaml of the automation used(under tab automation config); you can copy that 1:1 into a new automation (so no blue print needed anymore)
From there it is quite easy to alter the automation for you own needs
Here’s an alternative based on the approach I had suggested.
The repeat - for_each steps through the list of entities and brightness values, turning on each entity and setting its brightness to the specified value.
