Platform template does not generate unique IDs

[bcutter]

The problem

During reload of template sensors, this Platform template does not generate unique IDs is logged (see below).

This is a problem not only but especially for binary_sensor.deckel_redacted (notice it's not binary_sensor.deckel_redacted_2 but the original/first/master/whatever entity), which stops working completely.

Only a HA restart works around this.
Template sensor unique_ids are 100 % unique: created by VS code, every affected sensor has been searched for in all .yaml files - only one occurence.

What version of Home Assistant Core has the issue?

core-2025.10.4

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

template

Link to integration documentation on our website

https://www.home-assistant.io/integrations/template/

Diagnostics information

No response

Example YAML snippet

template:
  - trigger:
      - platform: state
        entity_id: binary_sensor.vibration_redacted
        id: "sensor"
      # Backup
      - platform: state
        entity_id: binary_sensor.deckel_redacted
        to: "on"
        for: "00:30:00"
        id: "stuck"
      - platform: homeassistant
        event: start
      - platform: event
        event_type: event_template_reloaded
    binary_sensor:
      - name: "Deckel Redacted XYZ"
        # entity_id: binary_sensor.deckel_redacted
        unique_id: 9b66d7b5-608b-43f1-b838-edcce4e11130
        device_class: opening
        icon: mdi:door
        delay_off:
          seconds: 1
        state: >
          {{ trigger.id == "sensor" and state_attr('binary_sensor.vibration_redacted', 'orientation')[2] > -70 }}
        availability: "{{ 'binary_sensor.vibration_redacted' | has_value }}"
        auto_off:
          minutes: 30

Anything in the logs that might be useful for us?

Logger: homeassistant.components.binary_sensor
Quelle: helpers/entity_platform.py:843
Integration: Binärsensor (Dokumentation, Probleme)
Erstmals aufgetreten: 16:42:45 (24 Vorkommnisse)
Zuletzt protokolliert: 23:48:13

Platform template does not generate unique IDs. ID 99c55cc8-bee1-412b-b117-2427080dde68 is already used by binary_sensor.updater_rpi3_host - ignoring binary_sensor.updater_rpi3_host_2
Platform template does not generate unique IDs. ID 9b66d7b5-608b-43f1-b838-edcce4e11130 already exists - ignoring binary_sensor.deckel_redacted



Logger: homeassistant.components.sensor
Quelle: helpers/entity_platform.py:843
Integration: Sensor (Dokumentation, Probleme)
Erstmals aufgetreten: 16:42:46 (12 Vorkommnisse)
Zuletzt protokolliert: 23:48:11

Platform template does not generate unique IDs. ID e558114c-3273-4016-9e15-33038a274a2b is already used by sensor.updater_any - ignoring sensor.updater_any_2

Additional information

• We have had a similar thing in the past with command_line sensors in Platform command_line does not generate unique IDs #80188. This was magically fixed when I updated to HA Core 2023.6 at that time. I could not track down following the issue which change for command_line sensors might have got implemented at that time.
• https://community.home-assistant.io/t/how-to-manually-set-state-value-of-sensor/43975/277

[home-assistant]

Hey there @Petro31, @home-assistant/core, mind taking a look at this issue as it has been labeled with an integration (template) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of template can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign template Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

template documentation
template source
_{^{(message by IssueLinks)}}

[Petro31]

Sorry, I can't replicate the issue. You'll need to provide more information with steps to reproduce the error.

[bcutter]

Oh, okay. Basically it's as simple as that for me:

1. Create template sensors exactly as in the example snippet. Two more for reference:

binary_sensor:
  - platform: template
    sensors:
      # True if there's updates available for the host
      updater_rpi3_host:
        friendly_name: "Updater - RPi3 Host"
        unique_id: 99c55cc8-bee1-412b-b117-2427080dde68
        #device_class: problem
        icon_template: "mdi:package-up"
        value_template: "{{ states('sensor.updates_rpi3_host') | int(0) > 0 }}"
        availability_template: "{{ (states('sensor.updates_rpi3_host') | int(-1)) > -1 }}"

sensor:
  - platform: template
    scan_interval: 3600
    sensors:
      updater_any:
        friendly_name: "Updater - Anything"
        unique_id: e558114c-3273-4016-9e15-33038a274a2b
        icon_template: "mdi:package-up"
        value_template: >-
          {% if ...redacted... %}
            True
          {% else %}
            False
          {% endif %}

2. Reload template sensors from dev tools section
3. Check HA log

[Petro31]

Yep, I have multiple template entities like that in my configuration and the error does not occur.

[bcutter]

I have no clue what's special about them. How can we find out?
I only realized they are "old-school" types, not the "new template sensor definition" right?

[Petro31]

I have no clue what's special about them. How can we find out?

There's someplace you aren't looking in your configuration that is using that unique_id inside another template. That's the only way the error appears.

As for legacy vs modern style, they both use the same system, so the issue would be present in both if it exists.

[bcutter]

As mentioned:

Template sensor unique_ids are 100 % unique: created by VS code, every affected sensor has been searched for in all .yaml files - only one occurence.

Want me to double-check this? I did:

One example, system-wide search:

[Petro31]

All you can do is search for the string. The code is pretty straight forward, HA tells me if it's unique or not. It's not even controlled by the template integration, the message comes from core.

Post your configuration.yaml, and if you use packages, post those as well.

I'd be willing to bet you are including a file more than once, which HA see's as separate entities.

[bcutter]

I'd be willing to bet you are including a file more than once, which HA see's as separate entities.

I don't think so, but it is a valid guess so I also checked this:

configuration.yaml (without webserver and logging stuff etc.)

# Configure a default setup of Home Assistant (frontend, api, etc)
default_config:

frontend:
  themes: !include_dir_merge_named themes
  extra_module_url:
    - /local/community/custom-brand-icons/custom-brand-icons.js
    - /hacsfiles/lovelace-card-mod/card-mod.js

group: !include groups.yaml
automation: !include automations.yaml
script: !include scripts.yaml
scene: !include scenes.yaml

homeassistant:
  customize: !include customize.yaml
  customize_domain: !include customize_domain.yaml
  customize_glob: !include customize_glob.yaml
  allowlist_external_dirs:
    - /config
  packages: !include_dir_named integrations

integrations directory (included as package) with the .yaml files where the 3 affected sensors are located:

integrations directory with files:

• custom_sensors.yaml --> home of binary_sensor.deckel_redacted
• server_management.yaml --> home of sensor.updater_rpi3_host
• system_updates.yaml --> home of sensor.updater_any

All those are included only once via packages: !include_dir_named integrations.

[Petro31]

Some of my own setup is similar, here's a link to my files inside packages and I do not get this error when reloading.

https://github.com/Petro31/home-assistant-config/tree/master/packages

In order to fix any bugs, I need to be able to replicate the issue.

[bcutter]

So you did create the same sensors and reloaded template sensors and did not get this? I have no idea what else to check ☹️

[Petro31]

I do not get the error, at all. I can't replicate it either. And you aren't providing your full config, there's always something that's redacted or removed. So my hands are tied.