I understood : I though the override name was the friendly name…
Yes it is… I’ve said that bout 400000000000 times now. What are you not understanding?
| item | description | example |
|---|---|---|
domain |
type of the device, i.e. light, switch, etc. | light |
object_id |
unique name inside the <domain> |
living_room |
entity_id |
<domain>.<object_id>: A unique identifier that is unlike all other entity_id’s. |
light.living_room |
friendly_name |
attribute that holds the name inside a state object. This is what you see in the UI | Living Room Light |
Override Name |
This is where you set the friendly_name in the UI. | Living Room Light |
name |
This is only inside the configuration of the device in lovelace or in the integration itself | Living Room Light |
friendly_name attribute, override name in UI, name in configurations are all the same and have nothing to do with the domain, object_id, or entity_id. These “names” are what you see in the UI.
Thank you for the very clear explanation !
Hi, is it possible to automatically change the friendly name of a card based on a sensor?
Thank you
based on a sensor value?
yes.
for example add a sensor value to friendly name
You’d have to use the (custom)100% template card, (custom) jinja template card, or make a template sensor.
will check, thank you
That’s how it always worked for me.
Now that I switched to a ui-lovelace file instead of managing it directly in the browser, something seems to have broken this logic.
Sensors shown on these cards show the entity_id.
At first I thought that I messed up the customizations. But when I click a card, it does show a configured friendly name for the sensor. 
Another option was that the custom mini graph card I’m using doesn’t handle friendly names, but even adding the default Sensor card shows the same entity_id instead of friendly name.
That doesn’t more info look correct. The attribute should appear on the left and the attributes value will be on the right.
You’ll have to show your configuration for these
In my configuration.yaml:
homeassistant:
packages: !include_dir_named integrations
customize: !include_dir_named customizations/entities
In the entities directory I have a .yaml for each entity I wanted a customized name. So for the living room sensor the file name is sensor.aqara_thp_living_room.yaml with the following contents:
sensor.aqara_thp_living_room:
friendly_name: Temperatuur
UPDATE
Issue resolved. I needed to use include_dir_merge_named instead of include_dir_named.
@pedro ironic I am speaking to you on two forums.
Question related to this, on the default entities card, when a card’s name is specified by the area, it takes away the area’s name from any entities that share that (like Living Room Light becomes just “Light” in the Living Room card). I am trying to replicate this on my light dashboard. Do you know how I can accomplish this? I’ve not done too much digging so feel free to just link me in the right direction.
Edit: real-world I want to remove "Dining Room: from each of these:
1 Like
Bump, does anyone know how the default lovelace setup removes the area name from the cards when named with the area in the device name (see prior post).
Hey DeltaNu thanks for the tip, however this isn’t what I am looking for. In the default Lovelace dashboard, if you have a “Dining Room” area and “Dining Room Dimmer” entity within that area, when the card is built it removes “Dining Room” from the entity Name and instead changes it to “Dimmer”. I’m wondering how I can replicate that on my own Entities cards.
You have to manually add the name field for each entity in the entities card
I was hoping this wasn’t the answer (name override) but alas here we are.
Perhaps a feature request around this would be good. This ties into when adding devices from integrations automatically populating an area of the area name (exact) is in the device name.
Is github the best place for feature requests?
Feature requests on the forums is the best place for those
1 Like
Threw it out there, hope others think its a good idea!:
2 Likes
Don’t forget to vote for it yourself