Please extend use of jinja to all parameters in yaml files

[non7top]

Usage example:
I’m trying to template my setup and want to use jinja templating for
that. I have 4 sensors which are exactly the same, except for the name
which changes for each sensor. The definitinion is in separate file
sensor1.yaml, sensor2.yaml, etc. I’m trying to use something like
following, but it fails
name: “{{ self._TemplateReference__context.name }}”

(and similar for state_topic:, availability_topic:)

[123 (Taras)]

@non7top

I have 4 sensors which are exactly the same, except for the name
which changes for each sensor.

Would YAML Anchor and Aliases help you?

Reducing tasmota (or any) entity config yaml

After setting up several devices running tasmota I found I had the same config repeated many times. A way to minimise this is to use yamls Anchor and Alias pattern. In my switches.yaml I had entries like this: - platform: mqtt name: "pond_pumps" state_topic: "stat/pond_pumps/POWER" command_topic: "cmnd/pond_pumps/POWER" availability_topic: "tele/pond_pumps/LWT" qos: 1 payload_on: "ON" payload_off: "OFF" payload_available: "Online" payload_not_available: "Of…

Howto create battery alert without creating a template for every device

Node Anchors is used to simplify your configurations and avoid repetitions of settings. So instead of repeting all settings for each entity you just add an anchor to the setting. Example: Without anchors: ################################################ ## Without Node Anchors and Merge Key Tags ################################################ homeassistant: customize: light.back_porch: friendly_name: "Back Porch" package: 'philips_hue' light.chandelier: friendly_…

[non7top]

Thanks, seems to be the closest thing that can be done with homeassitant.

I’m just so used to saltstack and erb where the whole file is jinja and it’s so natural to make whatever sophisticated yet simple configuration you need with fors and ifs.