Seems that this is not possible?
- event: >- {{ EVENT }} event_data: ...
i.e. I need to use
- event: some_hardcoded_event event_data: ...
?
OK, made it with just
- event: !input .... event_data: ...
The idea behind an event is that you make your event static and you add different data to key off of in your event_data.
e.g.
event: my_custom_event data: event_type: "{{ EVENT }}"
I see, I just wanted to make it templatable in a blueprint. And it turned be easier by just using “!input”. I wanted to compose “event_type” in a blueprint; now I just pass it as a composed string.
Yes, from a blueprint, use a text selector with !input pointing to the selector