Device_id as variable in script?

[kylepyke]

I have the following script:

alias: Inovelli - Clear LEDs
variables:
  switch: 0e8b546b7257587a218f63ad4547d13a
sequence:
  - type: issue_all_led_effect
    domain: zha
    device_id: "{{switch}}"
    effect_type: Clear
    color: 0
    level: 100
    duration: 255
  - type: issue_individual_led_effect
    domain: zha
    device_id: "{{switch}}"
    led_number: 0
    effect_type: Clear
    color: 0
    level: 100
    duration: 255
  - type: issue_individual_led_effect
    domain: zha
    device_id: "{{switch}}"
    led_number: 1
    effect_type: Clear
    color: 0
    level: 100
    duration: 255
  - type: issue_individual_led_effect
    domain: zha
    device_id: "{{switch}}"
    led_number: 2
    effect_type: Clear
    color: 0
    level: 100
    duration: 255
  - type: issue_individual_led_effect
    domain: zha
    device_id: "{{switch}}"
    led_number: 3
    effect_type: Clear
    color: 0
    level: 100
    duration: 255
  - type: issue_individual_led_effect
    domain: zha
    device_id: "{{switch}}"
    led_number: 4
    effect_type: Clear
    color: 0
    level: 100
    duration: 255
  - type: issue_individual_led_effect
    domain: zha
    device_id: "{{switch}}"
    led_number: 5
    effect_type: Clear
    color: 0
    level: 100
    duration: 255
  - type: issue_individual_led_effect
    domain: zha
    device_id: "{{switch}}"
    led_number: 6
    effect_type: Clear
    color: 0
    level: 100
    duration: 255
mode: single
icon: mdi:led-outline

But it throws the following error:

Message malformed: Unknown device '{{switch}}'

As far as I can see based on the docs, this is the correct syntax… is device_id not able to take a variable?

[browetd (Browet Didier)]

Maybe try to put quotes for the variable like:

variables:
  switch: "0e8b546b7257587a218f63ad4547d13a"

[tom_l]

Device actions do not support templating. Use the light turn on service call if you want to use templates.

You should avoid device automations altogether.

Disappearing automations

I’m guessing you are using either device triggers, conditions or actions. This is one of the problems with using this simple method. Automations are only visible if all the devices they depend upon are available. It’s a big problem that you can avoid by not using device triggers, conditions or actions. There are always other triggers conditions and actions you can use instead. e.g. instead of a device turn on trigger use a state trigger. See: and For the actions, refer to the documentat…

[kylepyke]

Gotcha. How disappointing. Is this documented anywhere? Also- how would I use ‘light turn on’ service in this case? The individual LEDs are not entities.

[tom_l]

Which integration are you using to connect to the LEDs?

[kylepyke]

I’m using the ZHA Integration.

[tom_l]

I think you are out of luck then.

[kylepyke]

Boooooo. Thanks!

[jtbandes]

Hi @kylepyke, did you find an alternate solution for this problem? I am hoping to do the same thing. I was unable to figure out how to use a “call service” action to invoke this command. (Posted the same question in this related thread as well)

It sounds like zha-toolkit might offer some solutions to problems like this, but it seems to bring some additional complexity I would like to avoid if possible.

Would the zigbee2mqtt integration make this eaiser? I am open to switching since my system is not very large yet.