with the new template: integration we can no longer configure friendly_names for sensors and binary sensors. The new name: variable is used to create identical object_id and friendly_name. see: Template - Home Assistant However, many object id’s will be not suitable for usage in the frontend, (way…

FYI default_entity_id was added to 2025.9 which essentially solves this feature request. This sensor: - platform: template sensors: backdoor_buiten_sensor_calibrated_temperature: friendly_name: Backdoor buiten value_template: > {{(states('sensor.backdoor_buite…

If I’m understanding correctly, the first time this entity is created, you manually go in via the ui and edit the entity_id. Once you do that, the entity_id will remain unchanged, but the “Friendly Name” can continue to be changed as needed? Thanks

Yepp, that’s exactly the way (as described from @Mariusthvdb ). :+1:

[image] ccpk1: I got stuck because there are still too many of the integrations and cards that only don’t allow efficient use of custom attributes They work perfectly in anything that supports templates. Recorder doesn’t support templating and only provides a simplistic wild-card text-matchi…

I’m just starting to get familiar with the new template format and find myself struggling with similar problems as described above. To me, the legacy format has a few strengths which makes me hesitant to migrate over to the new format before the issue of being able to separately define the name, uni…

REALY? I have to create something in the configuration.yaml and then switch to the UI and adjust it there afterwards (again)?? As Per mentoined, I will stay at the legacy format where I can setup those figures on one place.

So if I want to convert existing legacy template sensors to the new format and retain: the original sensor name (without the added template_ ) the equivalent of friendly_name Is there something easier than: Convert to the new format template: - sensor: - unique_id: legacy_sensor_name …

make sure legacy doesn’t exist when doing this template: - sensor: - unique_id: legacy_sensor_name name: Legacy Sensor Name state: > {{ states('sensor.example')}} attributes: friendly_name: Legacy Sensor Friendly Name

FWIW, all I did was add this template: - sensor: - unique_id: legacy_sensor_name name: Legacy Sensor Name state: > {{ states('sensor.example')}} and delete the legacy system and restart and everything was back up and running. However all my names are controlled i…

[image] petro: make sure legacy doesn’t exist when doing this Thanks for the fast reply. So are you saying that if sensor.legacy_sensor_name doesn’t exist, the new template sensor defined with unique_id won’t have template_ prefixed? Can making the old entity_id go away be done without a r…

[image] rct: So are you using if sensor.legacy_sensor_name doesn’t exist, it won’t be called but it does exist in legacy format. You do it all in 1 sweep. Keep HA running: Delete old, add new, restart HA. Not: delete old, restart, add new, restart.

Home Assistant Community

Add (bring back) friendly_name to template sensors

Feature Requests

show post in topic

Home
Categories
Guidelines
Terms of Service
Privacy Policy

Powered by Discourse, best viewed with JavaScript enabled