#my understanding is you would need to

1 messages · Page 1 of 1 (latest)

grizzled stirrup
#

thanks, it actually is already a variable, just need to figure out the right syntax for passing the flash configuration to the light service

versed geode
#

Well, it would be the same way you do it in an automation.

#

I have not done this but other than the entity name starts with !input, it's the same syntax.

#

These questions you have are why I suggest do your thing as an automation first, then convert it to a blueprint, See the Pins 📌 .

grizzled stirrup
#

yeah good call, my problem is i copied it from the automation and it doesnt work at all (once created, the automation doesnt show up in the ui, meaning theres an issue with the blueprint):

  - type: turn_on
    entity_id: !input main_light
    domain: light
    flash: short```

while the following does work for only turning the light on, not flashing it:
```action:
  - service: light.turn_on
    target: !input main_light```
trying to figure out what works for blueprint that turns light on and flashes it. it is an argument in the light service, but i dont know how to pass arguments to a blueprint's service action.
versed geode
#

The syntax is wrong, look here...

#

@grizzled stirrup