{"id":11977,"date":"2026-11-13T22:22:20","date_gmt":"2026-11-13T20:22:20","guid":{"rendered":"https:\/\/www.sigalou-domotique.fr\/?p=11977"},"modified":"2026-11-13T22:34:25","modified_gmt":"2026-11-13T20:34:25","slug":"je-corrige-les-noms-a-rallonge-dans-mes-cartes-depuis-home-assistant-2026-11","status":"publish","type":"post","link":"https:\/\/www.sigalou-domotique.fr\/en\/je-corrige-les-noms-a-rallonge-dans-mes-cartes-depuis-home-assistant-2026-11","title":{"rendered":"I correct names to extend in my cards (since Home Assistant 2026.11)"},"content":{"rendered":"<p>After an update of Home Assistant, I notice a change on my dashboard: some titles have become much longer, sometimes with a feeling of repetition.<\/p>\n<p>In my map of the lights on the ground floor, I find, for example, \u2018Lights of the Sofa Sofa\u2019, \u2018Lights of the Kitchen Kitchen Lounge\u2019 or \u2018Light of the Entry Entrance\u2019.<\/p>\n<p>The lights still work, but the display is less readable. Some names are even truncated for lack of space.<\/p>\n<p>However, I have not changed this map. So I look for the origin of the change before I start renaming my equipment.<\/p>\n<p>In this feedback, I show you what I found, the update note explaining this new behaviour and the correction I apply to find shorter headings.<\/p>\n<h2>\ud83d\udc40 I see repetitions in my map on the ground floor<\/h2>\n<p>I use a card <code>self-entities<\/code> to automatically display the lights of my group <code>light.lumieres_rdc<\/code>.<\/p>\n<p>This is convenient: I do not need to declare each light individually in the dashboard. The list is built from the members of the group.<\/p>\n<p>But after the update, I note that several headings seem to repeat the same information:<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-11978\" src=\"https:\/\/www.sigalou-domotique.fr\/wp-content\/uploads\/2026\/11\/Capture-decran-2026-11-13-211301.png\" alt=\"\" width=\"426\" height=\"363\" srcset=\"https:\/\/www.sigalou-domotique.fr\/wp-content\/uploads\/2026\/11\/Capture-decran-2026-11-13-211301.png 426w, https:\/\/www.sigalou-domotique.fr\/wp-content\/uploads\/2026\/11\/Capture-decran-2026-11-13-211301-300x256.png 300w, https:\/\/www.sigalou-domotique.fr\/wp-content\/uploads\/2026\/11\/Capture-decran-2026-11-13-211301-14x12.png 14w\" sizes=\"auto, (max-width: 426px) 100vw, 426px\" \/><\/p>\n<p>Here is the configuration of my card before modification (it is included in a standard card: picture-elements):<\/p>\n<pre><code class=\"language-yaml\">  - type: custom:auto-entities card: type: entities title: Ground floor filter: include: - group: light.lumieres_rdc sort: method: friendly_name style: top: 63% left: 68% width: 18%<\/code><\/pre>\n<p>My first reflex is to look on the side of<code>self-entities<\/code>. However, this extension here only selects the entities and transmits them to the native map <code>entities<\/code>, which is responsible for displaying them.<\/p>\n<h2>\ud83d\udd0e I am looking for the source of the concern and I find the update note<\/h2>\n<p>By consulting the official notes, I find the explanation in the version <strong>Home Assistant 2026.11<\/strong>, published on 4 November 2026.<\/p>\n<p>The relevant section is entitled \u2018Name it once, Home Assistant adds the context\u2019.<\/p>\n<p>I find her in the <a href=\"https:\/\/www.home-assistant.io\/blog\/2026\/11\/04\/release-202611\/\" target=\"_blank\" rel=\"noopener\">Official Home Assistant 2026.11 update note<\/a>.<\/p>\n<p>Home Assistant announced in particular:<\/p>\n<blockquote><p>Cards, badges, and rows without a name now show the device name followed by the entity name, instead of the friendly name.<\/p><\/blockquote>\n<p>In other words, cards, badges and lines without an explicitly configured name now display the name of the device followed by the name of the entity, instead of the old one. <code>friendly_name<\/code>.<\/p>\n<p>I then understand why my titles have changed without changing my YAML: my card lets Home Assistant automatically choose names, and this presentation rule has evolved.<\/p>\n<p>[Image from the section \"Name it once, Home Assistant adds the context\" in the Home Assistant 2026.11 update note]<\/p>\n<p>The team also explains this change in the announcement <a href=\"https:\/\/www.home-assistant.io\/blog\/2026\/11\/03\/naming-things-in-home-assistant\/\" target=\"_blank\" rel=\"noopener\">Naming things in Home Assistant, shaped by your feedback<\/a>.<\/p>\n<h2>\ud83e\udde9 I understand why names repeat themselves<\/h2>\n<p>To understand what is happening, I distinguish three pieces of information:<\/p>\n<ul>\n<li>The name of the device: the equipment to which the entity is attached.<\/li>\n<li>The name of the entity: the function or measure represented.<\/li>\n<li>The entity identifier: the technical reference used in the configurations, such as <code>light.lumieres_rdc<\/code>.<\/li>\n<\/ul>\n<p>The new system adds the device context on behalf of the entity. When both names already contain similar words, their association can produce a repetitive result.<\/p>\n<p>This is exactly what I see on my map: \"Sofa\", \"Cooking\" or \"Entry\" appear at the end of labels that already contain this information.<\/p>\n<p>I'm not trying to change the way my lights work. I just want to choose the information displayed on this map.<\/p>\n<h2>\ud83d\uddc2\u2718 I check the other cards concerned<\/h2>\n<p>Even though I spotted this change in a map <code>self-entities<\/code>, the subject is not limited to this extension.<\/p>\n<p>The new behavior concerns more broadly the cards, badges and lines that use the automatic names of Home Assistant.<\/p>\n<p>I therefore check that:<\/p>\n<ul>\n<li>The lines of the native cards <code>entities<\/code>.<\/li>\n<li>Names displayed in native maps <code>tile<\/code> or <code>button<\/code>.<\/li>\n<li>Badges that display an entity name.<\/li>\n<li>Automatically generated lists, especially with <code>self-entities<\/code>.<\/li>\n<\/ul>\n<p>On the other hand, if I have defined explicit text in a map, for example <code>name: Terrace<\/code>, this text remains unchanged.<\/p>\n<p>I also keep a reserve for custom maps: their behavior depends on their implementation. Some still use the old attribute <code>friendly_name<\/code>, which may explain differences in display between several cards.<\/p>\n<h2>\ud83d\udee0\u2718 I choose to display only the name of the entity<\/h2>\n<p>The <a href=\"https:\/\/www.home-assistant.io\/dashboards\/naming\/\" target=\"_blank\" rel=\"noopener\">documentation of card naming<\/a> provides an option to choose which elements of the name to display.<\/p>\n<p>To request only the entity\u2019s own name, I use:<\/p>\n<pre><code class=\"language-yaml\">name: type: entity<\/code><\/pre>\n<p>I can also write it on one line:<\/p>\n<pre><code class=\"language-yaml\">name: {type: entity}<\/code><\/pre>\n<p>This configuration requires the name of the entity, without adding the name of the device or part.<\/p>\n<p>The point is that I keep a dynamic name. If I rename the entity in its settings, the card automatically follows this new name.<\/p>\n<p>Therefore, I do not need to manually enter a fixed heading for each light.<\/p>\n<h2>\u2699\u2718 I pass this option to the lines of my auto-entities card<\/h2>\n<p>In my map, the lines are generated automatically from the group. I don't want to replace this dynamic list with a manual declaration of all my lights.<\/p>\n<p>So I rely on the block <code>options<\/code> d<code>self-entities<\/code>.<\/p>\n<p>As explained in <a href=\"https:\/\/github.com\/thomasloven\/lovelace-auto-entities\" target=\"_blank\" rel=\"noopener\">documentation of the auto-entities project<\/a>, this block allows adding options to entities found by a filter rule.<\/p>\n<p>I would add the following:<\/p>\n<pre><code class=\"language-yaml\">options: name: type: entity<\/code><\/pre>\n<p>in the rule that selects the members of my group:<\/p>\n<pre><code class=\"language-yaml\">filter: include: - group: light.lumieres_rdc options: name: type: entity<\/code><\/pre>\n<p>I pay attention to indentation: <code>options<\/code> is at the same level as <code>group<\/code>, in the same rule <code>include<\/code>.<\/p>\n<p>I don't place it under <code>card:<\/code>, because I want to configure the generated rows, not the map title.<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-11982\" src=\"https:\/\/www.sigalou-domotique.fr\/wp-content\/uploads\/2026\/11\/Capture-decran-2026-11-13-212356-1.png\" alt=\"\" width=\"465\" height=\"273\" srcset=\"https:\/\/www.sigalou-domotique.fr\/wp-content\/uploads\/2026\/11\/Capture-decran-2026-11-13-212356-1.png 465w, https:\/\/www.sigalou-domotique.fr\/wp-content\/uploads\/2026\/11\/Capture-decran-2026-11-13-212356-1-300x176.png 300w, https:\/\/www.sigalou-domotique.fr\/wp-content\/uploads\/2026\/11\/Capture-decran-2026-11-13-212356-1-18x12.png 18w\" sizes=\"auto, (max-width: 465px) 100vw, 465px\" \/><\/p>\n<h2>\ud83d\udccb I replace my card with this full version<\/h2>\n<p>Here is the updated code of my map on the ground floor:<\/p>\n<pre><code class=\"language-yaml\">  - type: custom:auto-entities card: type: entities title: Ground floor filter: include: - group: light.lumieres_rdc options: name: type: entity sort: method: name style: top: 63% left: 68% width: 18%<\/code><\/pre>\n<p>I keep my position and width settings. The addition that corrects the headings is in the block <code>options<\/code>.<\/p>\n<p>I also take the opportunity to replace <code>method: friendly_name<\/code> by <code>method: name<\/code>, which is the method of sorting by name documented by <code>self-entities<\/code>.<\/p>\n<p>I make a clear distinction between the two settings:<\/p>\n<ul>\n<li><code>options.name<\/code> choose the name displayed on each line.<\/li>\n<li><code>sort.method<\/code> chooses the method for classifying rows.<\/li>\n<\/ul>\n<p>The change in sorting is therefore not what removes the prefix: it is <code>name: {type: entity}<\/code> which regulates the presentation of the name.<\/p>\n<h2>\ud83d\udc41\u2718 I control the headings after modification<\/h2>\n<p>Once the card is saved, I control the displayed names and their readability.<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-11984\" src=\"https:\/\/www.sigalou-domotique.fr\/wp-content\/uploads\/2026\/11\/Capture-decran-2026-11-13-212629.png\" alt=\"\" width=\"436\" height=\"352\" srcset=\"https:\/\/www.sigalou-domotique.fr\/wp-content\/uploads\/2026\/11\/Capture-decran-2026-11-13-212629.png 436w, https:\/\/www.sigalou-domotique.fr\/wp-content\/uploads\/2026\/11\/Capture-decran-2026-11-13-212629-300x242.png 300w, https:\/\/www.sigalou-domotique.fr\/wp-content\/uploads\/2026\/11\/Capture-decran-2026-11-13-212629-15x12.png 15w\" sizes=\"auto, (max-width: 436px) 100vw, 436px\" \/><\/p>\n<p>I keep an important point in mind: this option does not automatically delete duplicate words in a text.<\/p>\n<p>It asks Home Assistant to use only the \u2018entity\u2019 component of the name.<\/p>\n<p>The result therefore depends on the registered proper name for each entity. If it already contains a long formulation, it will remain displayed.<\/p>\n<p>I also check that the names remain understandable: several lines called simply \"Light\" would be shorter, but not necessarily more practical.<\/p>\n<h2>\ud83e\uddf1 I can apply the same principle to classic cards<\/h2>\n<p>In a native card <code>entities<\/code>, I place this option directly on each line concerned:<\/p>\n<pre><code class=\"language-yaml\">type: entities title: Ground floor entities: - entity: light.lumieres_rdc name: type: entity<\/code><\/pre>\n<p>In a native card <code>tile<\/code>, I place the setting at the level of the card:<\/p>\n<pre><code class=\"language-yaml\">type: tile entity: light.lumieres_rdc name: type: entity<\/code><\/pre>\n<p>In both cases, I keep a dynamic name rather than manually copied text in the dashboard.<\/p>\n<h3>\u2795 I repeat the setting if my card uses multiple filters<\/h3>\n<p>In <code>self-entities<\/code>, the options are associated with the rule that contains them.<\/p>\n<p>If I use more than one rule in <code>include<\/code>, I therefore add this block to each of the rules concerned:<\/p>\n<pre><code class=\"language-yaml\">options: name: {type: entity}<\/code><\/pre>\n<p>A block added to a filter does not automatically become the setting of the entire board.<\/p>\n<h2>\ud83d\udd12 I keep my credentials and automations<\/h2>\n<p>To correct this display, I do not need to change the credentials of my entities or rewrite my automations.<\/p>\n<p>Home Assistant specifies that this naming migration retains existing credentials.<\/p>\n<p>The correction I apply here remains local to the dashboard: I choose what the map displays, without touching the entities used.<\/p>\n<p>This is what I prefer in this approach. I can keep short headings in a map already organised by area, while keeping more context in other displays.<\/p>\n<h2>\ud83c\udfaf I mostly retain an option, not a new obligation<\/h2>\n<p>At first, I thought I had a problem in my card. The names seemed to repeat themselves and some became too long for the space available.<\/p>\n<p>Looking for the source of the change, I understand that this is Home Assistant\u2019s new behaviour, not an error in my group of lights.<\/p>\n<p>I'm not going to add this option everywhere without looking at the result. The name of the device may be useful to distinguish similar entities.<\/p>\n<p>On the other hand, on my maps already grouped under an explicit title like \"Ground floor\", I prefer to be able to choose a more compact display.<\/p>\n<h2>\ud83c\udfc1 I keep a simple correction for my next cards<\/h2>\n<p>The setting <code>name: {type: entity}<\/code> did not become mandatory with Home Assistant 2026.11. It is a possibility to display only the name of the entity when the automatically added context is not useful to me.<\/p>\n<p>For a classic card, I remember:<\/p>\n<pre><code class=\"language-yaml\">name: {type: entity}<\/code><\/pre>\n<p>For lines generated by a filter <code>self-entities<\/code>, I note:<\/p>\n<pre><code class=\"language-yaml\">options: name: {type: entity}<\/code><\/pre>\n<p>I keep my dynamic lists and names that follow those of my entities, without having to copy all the titles by hand.<\/p>","protected":false},"excerpt":{"rendered":"<p>Apr\u00e8s une mise \u00e0 jour de Home Assistant, je remarque un changement sur mon tableau de bord : certains intitul\u00e9s sont devenus beaucoup plus longs, avec parfois une impression de r\u00e9p\u00e9tition. Dans ma carte des lumi\u00e8res du rez-de-chauss\u00e9e, je retrouve par exemple \u00ab\u00a0Lumi\u00e8res du Canap\u00e9 Canap\u00e9\u00a0\u00bb, \u00ab\u00a0Lumi\u00e8res Salon Cuisine Cuisine\u00a0\u00bb ou encore \u00ab\u00a0Lumi\u00e8re de l\u2019Entr\u00e9e [&hellip;]<\/p>","protected":false},"author":1,"featured_media":11978,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[14,53,166],"tags":[],"class_list":["post-11977","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-domotique","category-home-assistant","category-retex"],"acf":[],"_links":{"self":[{"href":"https:\/\/www.sigalou-domotique.fr\/en\/wp-json\/wp\/v2\/posts\/11977","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.sigalou-domotique.fr\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.sigalou-domotique.fr\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.sigalou-domotique.fr\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.sigalou-domotique.fr\/en\/wp-json\/wp\/v2\/comments?post=11977"}],"version-history":[{"count":5,"href":"https:\/\/www.sigalou-domotique.fr\/en\/wp-json\/wp\/v2\/posts\/11977\/revisions"}],"predecessor-version":[{"id":11986,"href":"https:\/\/www.sigalou-domotique.fr\/en\/wp-json\/wp\/v2\/posts\/11977\/revisions\/11986"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.sigalou-domotique.fr\/en\/wp-json\/wp\/v2\/media\/11978"}],"wp:attachment":[{"href":"https:\/\/www.sigalou-domotique.fr\/en\/wp-json\/wp\/v2\/media?parent=11977"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.sigalou-domotique.fr\/en\/wp-json\/wp\/v2\/categories?post=11977"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.sigalou-domotique.fr\/en\/wp-json\/wp\/v2\/tags?post=11977"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}