Where can I expand templates?

[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…