Where can I expand templates?

[klimek (Manuel Klimek)]

Hi all,

I’m still trying to understand where I’m allowed to expand templates to save typing.
E.g., I have a blueprint where I hand in a group to save some typing and use filters to get the data.
I want to trigger on changes to the underlying entities in the (old style) group, which groups a couple of number sensors.
I’ve tried various attempts to put put a template into the entity_id: of a state trigger, but it seems like templates are not expanded there? Are there any write-ups on where exactly I can template / what I can template? I’d like to use template loops / filters in multiple places to save typing, but it seems I can’t just throw them in at arbitrary places to create the config. What am I missing?

Thanks!

[exxamalte]

@klimek

Are there any write-ups on where exactly I can template / what I can template?

Correct, you can’t use templates anywhere, but only where it’s explicitly mentioned in the documention.

For example:

[123 (Taras)]

@klimek

put a template into the entity_id: of a state trigger

Here’s the documentation for State Trigger.

It doesn’t explicitly mention that entity_id supports a template and doesn’t provide any examples where entity_id contains a template. In general, the documentation limits itself to presenting only what is possible.

[klimek (Manuel Klimek)]

Thanks for the answers, that’s helpful.

Are people using other mechanism to avoid endless repetition? I could write some python to generate the yaml, but that sounds like I’d be basically introducing another programming layer above home assistant. I know about the various python integrations, but is there something that’s more along the lines of “make writing yaml less repetitive”?

[123 (Taras)]

YAML Anchors and Aliases

YAML anchors | Bitbucket Cloud | Atlassian Support

Examples

Way to create multiple sensors per device with template?

Here’s how I use it. The following is a portion of my lights.yaml file. The configuration of the first light includes the definition of a node anchor called dimmer. All subsequent light configurations refer to the dimmer anchor. - name: "Foyer" state_topic: "premise/foyerlight/powerstate" command_topic: "premise/command/foyerlight/powerstate" brightness_state_topic: "premise/foyerlight/brightness" brightness_command_topic: "premise/command/foyerlight/brightness" <<: &dimm…

Multiple time condition in automation trigger - clean solution?

I agree that this is the simplest approach with the benefit of reporting the name of the unavailable entity. FWIW, to simplify maintenance, you can employ YAML anchors and aliases. It will allow you to define the list of entities in the first State Trigger and use it in the other two State Triggers. trigger: - platform: state for: '00:30:00' <<: &entities to: unavailable entity_id: - sensor.esp01_wifi - sensor.esp02_wifi - sensor.esp03_wifi …

Filtering and counting entities in state by area - Jinja templates in front end?

I believe I have a means for you to create multiple Template Binary Sensors, one per area, with the least amount of effort. It employs this.name, as mentioned in my previous post, plus the use of YAML anchors and aliases. The following configuration creates four Template Binary Sensors. The second through fourth sensors share the same configuration as the first except they have their own unique name option. Any change you make to the first one’s options or templates are inherited by the other t…