Home Assistant custom component event control

[m3730r]

How can I control different scenes with the event options?

    event:
      "up":
        - service: scene.turn_on
          target:
            entity_id: >-
              {% if val == 0 %}
                scene.light_night
              {%-elif val == 1 %}
                scene.light_day
              {% endif %}

throws configuration error

Invalid config for [openhasp]: not a valid value for dictionary value @ data['openhasp']['plate_sz']['objects'][0]['event']['up'][0]['target']['entity_id']. Got '{% if val == 0 %}\n scene.light_night\n{%-elif val == 1 %}\n scene.light_day\n{% endif %}'. (See /home/h0bi/.homeassistant/configuration.yaml, line 186).

Are there other options, e.g. on off events?

[dgomes]

From the error message I take it the problem is on the service configuration. I suggest you first experiment the syntax on the developer tools page of Home Assistant

[m3730r]

I‘ve tried different versions syntax, but no success:

      "up":
        - service: scene.turn_on
          entity_id: >
           {% if val == 0 %}
             scene.light_night
           {% else %}
             scene.light_day
           {% endif %}

This works in the template editor in HA, but not in the configuration.yaml.
It is the same syntax like the examples in the documentation. But no success.

this weird writing seems to work, because there is no configuration error, but it turns both scenes on

        "up":
           - service: scene.turn_on
             entity_id: 
#               {% if val == 0 %}
                - scene.light_night
#               {% else %}
                - scene.light_day
#               {% endif %}

Any suggestions?

[dgomes]

check your spaces... everything need to be properly indented
on the initial comment: scene has 2 spaces more then necessary and it's > not >-

[m3730r]

          "up":
            - service: scene.turn_on
              entity_id: >
                {% if val == 0 %}
                scene.kai_sz_aus
                {% else %}
                scene.kai_sz_normallicht
                {% endif %}

The spaces are the same, like the sample code here. I didn’t write it clean in the post

I can’t find the error, could you please mark it

[dgomes]

"up":
  - service: scene.turn_on
    target:
      entity_id: >
        {% if val == 0 %}
        scene.kai_sz_aus
        {% else %}
        scene.kai_sz_normallicht
        {% endif %}

[m3730r]

Thank you, but now there is another error

Error loading /home/xxx/.homeassistant/configuration.yaml: while scanning for the next token found character '%' that cannot start any token

It points to the line with the first {%

[dgomes]

can't figure that now :/

[m3730r]

It‘s crazy. I’ve tried different versions to write it in a single line, but none works

entity_id: '{{% if val == 0 %} scene.kai_sz_aus {% else %} scene.kai_sz_normallicht {% endif %}}'

or

entity_id: '{{ scene.kai_sz_aus if val == 0 else scene.kai_sz_normallicht }}'

I‘ll give up.

Does anyone have another solution suggestion to trigger 2 different scenes from a toggle button event, if the value is 1 or 0 ?

[nagyrobi]

See the "Cover with button matrix" example in the link above.

Use the jinja routines at target section.

[dgomes]

It seams that scenes are not temptable

https://community.home-assistant.io/t/scene-with-dynamic-templated-entities-parameter/133283

[dgomes]

in another post I found this:

https://community.home-assistant.io/t/motion-sensor-template-action-to-turn-on-different-scenes/105057/3

[m3730r]

Thank you very much at all for your incredibly support. The last post gives me the solution:

[m3730r]

This now works

       event:
          "up":
            - service: scene.turn_on
              data_template:
                entity_id: >
                  {% if val == 0 %}
                  scene.kai_sz_aus
                  {% else %}
                  scene.kai_sz_normallicht
                  {% endif %}

[rlust]

Thanks!