Newer template sensor config type with split config

Configuration
1

I’m attempting to adhere to standards and leverage the newer standard for template sensors.

I leverage a split config where I have a sensors.yaml file.

Typically I would add a template sensor like this which works.

- platform: template
    sensors:
      speedtest_download_rounded:
        friendly_name: Speed Test Download Rounded
        unique_id: sensor.speedtest_download_rounded
        value_template: '{{ states("sensor.speedtest_download") | round(0) }}'

Attempting to leverage the new standard I have this:

- template:
      - sensor:
          - name: "Runtime Remaining"
            state: "{{ states('input_text.sprinkler_qr_timer_zone1') }}"

But this format fails with error:
Invalid config for [sensor]: required key not provided @ data[‘platform’]. Got None.

I’m sure this is simple but I have yet to figure it out with the new formatting.

2

The top level for the new format is template, but by putting it in your sensors.yaml you are using setting sensor as the top level. You need to either create a new file template.yaml with an include in your main configuration file, or place your new sensors in your packages folder if you prefer to do it that way.

3

I was thinking of creating a template.yaml. Thanks for clarifying I was headed in the right direction.