Splitting config for template:

Configuration
63

This route will cause you issues. Instead use this:

  1. create folder in integrations folder named templates

  2. add this to configuration.yaml

    template: !include_dir_merge_list integrations/templates

  3. Use this format in your files, you can even combine or separate your sensors/binary_sensors/trigger based. Name the file whatever you want, the name won’t matter. You can organize your files based on what it’s doing.

    - binary_sensor:
  - name: "Group Family Manual"
    unique_id: "3e43a954-abc1-447a-af7c-8f789ba73f2f"
    state: "{{ is_state('input_boolean.helpers_kay_home_homekit', 'on') or is_state('input_boolean.helpers_peter_home_homekit', 'on') }}"
    device_class: presence
    delay_off: "00:15:00"

  ... etc

- sensor:
  - name: ...

If you continue with your current method, you’ll need to make a separate include for every template entity type. You’ll have to maintain a correct name, and there will be no organization to your filenames. They will be rigid.

This is what my folder looks like, it tells me exactly what each file does.

image

2 Likes