Light.turn_on/_off with service_template

Configuration
1

Hi!
I am new to HA and still struggling with the configuration. The following does not want to work. It also shows a “Unsupported action:” error in the GUI.

- id: '1570730536258'
  alias: Schuhzimmer an aus
  trigger:
    - platform: state
      entity_id: binary_sensor.tradfri_motion_sensor
      to: 'on'
    - platform: state
      entity_id: binary_sensor.tradfri_motion_sensor
      to: 'off'
      for:
        minutes: 10
  action:
    entity_id: switch.fibaro_system_fgs213_switch_switch_2
    service_template: >
      {% if trigger.to_state.state == 'on' %}
        light.turn_off
      {% elif trigger.to_state.state == 'off' %}
        light.turn_on
      {% else %}
      {% endif %}

Anybody has a clue what I am doing wrong?

Thanks!
M

2

first of all, you have no service in your else clause.
What do you want to do if the if, nor the else are evaluated to true?

your probably be better of using

    service_template: >
      light.turn_{{trigger.to_state.state}}
    entity_id: switch.fibaro_system_fgs213_switch_switch_2

must say I havent used the same trigger entity_id for 2 different states in 1 automation, so you’d have to see what happens

1 Like
3

Thanks for the quick response, but unfortunately that one does not work either.

4

of course, it should be switch.turn_off/on…

5

Change this:

      light.turn_{{trigger.to_state.state}}

to this:

      switch.turn_{{trigger.to_state.state}}

… ninja’d by Marius

6

hahaha yes we were heavily occupied with the exact same thought! cool. should have seen it in my earlier post, sorry for that.

7

Ha, what’s a domain between friends ? :rofl:

8

I have data_template instead of entity_id in my service_template.
Hope that works for you.

  - service_template: >
      light.turn_{{trigger.to_state.state}}
    data_template:
      entity_id: "light.basement_{{'corridor' if trigger.to_state.object_id[-1:] == 'stair' else 'stair'}}"
9

Your example needs to include data_template because the data supplied to the service includes templates (your example’s entity_id uses a template). In MatthiasR’s example, none of the data supplied to the service uses a template, so it doesn’t need data_template.

10

You are correct, thanks for pointing that out. So OP is missing the data:

  - service_template: >
      {% if is_state('light.dinner_table_light','on') %}
        automation.turn_off
      {% else %}
        automation.turn_on
      {% endif %}
    data:
      entity_id: automation.smart_kitchen_lights_off
11

Not sure what you are trying to do here.
Why do you want to turn on/off an automation ?

12

Mutt, that’s part of my automation with motion sensor, when the dinner_table_light is on, i.e. eating dinner, I don’t want the motion sensor to control kitchen lights at all.

13

No, in the OP’s example, data: is not required because the only data presented is entity_id (which is understood to be data for the service without explicitly supplying the option word data:).

14

That is poor coding, just put a condition in the other automation.
The danger being that you ‘may’ leave the automation in an unknown state should something unexpected happen (say a reboot)

1 Like
15

I know this is getting off topic, but thanks to 123 and Mutt, all true, always things to improve and correct.