How to use variables instead of inputs?

[Craos]

I need to perform an operation ( split ) on input value before I use it in my template. So, I think, variables should work. I tried many syntaxes, but none of them work for me. Please, coukld anybody advice, what is correct approach?

My definition is:

input:
    ctrl:
      name: CTRL
      description: Select ctrl
      selector:
        select:
          mode: dropdown
          options:
            - "10:1"
            - "10:2"
 
variables:
  ctrl_val: !input ctrl
  hub_nbr: "{{ ctrl_val.split(':')[0] }}"
  switch_nbr: "{{ ctrl_val.split(':')[1] }}"

triggers:
  - trigger: event
    event_type: esphome.button_pressed
    event_data:
      hub: >-
        {{ hub_nbr }}
      switch: >-
        {{ switch_nbr }}

[Sir_Goodenough ((SG) WhatAreWeFixing.Today)]

Trigger_Variables - variables that are available when attaching a trigger

First, this is not meant to be a replacement for the section in the HA Docs about this. Please read and refer to that as the official word on this subject. Automation Trigger - Home Assistant. When I mention Triggers here I am referring to the main key trigger: used to activate an automation, and not necessarily the triggers found in key action: statements. What the Docs don’t say is the reason that there are 2 kinds of variables. Regular variables used in Automations and the ‘trigger’ varia…

[Craos]

Thanks, but there is something else. I changed it according your tip and I made it very very simple:

trigger_variables:
  hub_nbr: "10"

triggers:
  - trigger: event
    event_type: esphome.button_pressed
    event_data:
      hub: >-
        {{ hub_nbr }}
      switch: "2"

It still doesn’t work, but this works:

triggers:
  - trigger: event
    event_type: esphome.button_pressed
    event_data:
      hub: "10"
      switch: "2"

[Sir_Goodenough ((SG) WhatAreWeFixing.Today)]

The event trigger may not accept templates then. I don’t know.
If that’s the case trigger on the event_type only,
Then check in the conditions (or actions if you have more than one trigger) that the hub and switch numbers are what you are looking for.

[Didgeridrew]

IIRC, you need to template the whole event_data object:

triggers:
- trigger: event
event_type: esphome.button_pressed
event_data: |
{{ {“hub”: hub_nbr, “switch”: switch_nbr} }}

EDIT: Just tested that and it doesn’t work either…

Using a more general Event trigger with a condition does work:

triggers:
  - trigger: event
    event_type: esphome.button_pressed
variables:
  hub_nbr: "10"
  switch_nbr: "3"
conditions:
  - condition: template
    value_template: >-
      {{ (trigger.event.data.hub, trigger.event.data.switch) ==
      (hub_nbr, switch_nbr) }}

[Sir_Goodenough ((SG) WhatAreWeFixing.Today)]

That makes sense.

[petro]

it’s because templates are changing the values from a string to a number.

Only way to get around it would be to template the entire event_data section, which I’m not 100% if that’s possible.

Other way would be to make the esphome event returns ints not strs.

[Didgeridrew]

@petro

it’s because templates are changing the values from a string to a number.

Shouldn’t using an int as the value for the trigger variable work then… it doesn’t.

@petro

Only way to get around it would be to template the entire event_data section, which I’m not 100% if that’s possible.

Tried that but the automation wouldn’t save because a dictionary is expected.

@petro

Other way would be to make the esphome event returns ints not strs

That doesn’t seem to be an option:

[petro]

Then there’s no way to do this. Maybe making it a single field and concatenating the strings on esphome side? Then using the input as-is