Add Area Info to Entity Selection Panel

[OlJohnny]

Why this is useful

in my case i have a Shelly Dimmer for each room.
I only name the devices according to what light they control (e.g. "ceiling light") and assign them an aera. (as haveing the area in the area tag and the name is redundant)
afaik the whole idea of the area assignment is that we don't have to put the area into the device name.

As the entity selector doesn't display areas, it makes differentiation unnecessarily tedious.
I think that adding the area (if one is assigned) into a third row for each option should work perfectly fine.

[matthiasdebaat]

Currently, the entity ID is quite important. It is the only thing that is unique to an entity and is often changed to something that is readable by humans, so you can: select the right entity from a list as in your example or to write YAML. I assume that people also change their entity IDs to have a clean system, even if these entities aren't used. Naming entity IDs adds an extra administrative task. Home Assistant tries to help in advanced mode, but isn't always what the user expects.

For the type of users who only care about the name and the area, this is not a fun exercise. Personally, I would like to hide the entity ID from them and let the entity IDs be a hidden mess. My only concern is how do we help users who have 5 "Deckenlampe" with no assigned areas? How do you know which lamp is which? Do we want to make the name unique?

[OlJohnny]

Just to clarify :D
My 5 "Deckenlampe" each have an unique assigned area, I just would like to be able to see this area when e.g. building my own Dashboard

But to your other point: I don't think that many people are changing their entity ids to be descriptive. That's what the name and area are for.
Also changing the entity's id is a huge pain, when the entity is already used anywhere, as you then have to remember where it is used and change it in every place (e.g. automatations just fail silently otherwise)
And you would have to change entity ids when naming them according to their purpose, as the purpose of a device (e.g. smart plug) can definitely change over the lifecycle of a smart device.

[ildar170975]

I don't think that many people are changing their entity ids to be descriptive.

Strongly disagree.
As it was noted, entity_id is a unique identifier which is used by users in yaml.
I guess, many beginners start using UI only & do not care about internal entity_id; but for advanced applications using yaml is necessary.
We already have examples of poor implementation like

or

where it is impossible to guess which entity is used.