Can't recognise entities only by its names in the UI automation editor

notabene00 commented 2 years ago

Checklist

[X] I have updated to the latest available Home Assistant version.
[X] I have cleared the cache of my browser.
[X] I have tried a different browser to see if it is related to my browser.

Describe the issue you are experiencing

If I define e.g. state trigger, in the entity field I can see only its name - "Door", "Window", or "Presence sensor". But if I have more than one area, I can't realise where this door, window or sensor is located.

Describe the behavior you expected

Maybe, there should be area name at least, or the entity_id itself, as a subtitle

Steps to reproduce the issue

open UI automation editor
define state trigger
choose entity ... Look at its name and try to figure out where's this "Door" located

What version of Home Assistant Core has the issue?

2022.3.0b4

What was the last working version of Home Assistant Core?

No response

In which browser are you experiencing the issue with?

No response

Which operating system are you using to run this browser?

No response

State of relevant entities

No response

Problem-relevant frontend configuration

No response

Javascript errors shown in your browser console/inspector

No response

Additional information

No response

bramkragten commented 2 years ago

This is because of your specific naming strategy, not really a bug 🤷‍♂️

notabene00 commented 2 years ago

I agree that this actually is not a bug, but don't know what label should be here then And I understand that I can include area name into entity name, but who really want it to be so? You've already placed this entity into an area and want to know where is it without additional renaming Don't want to see Motion sensor (Kitchen) in cards on a tab named Kitchen or to have a need to rename it in every card I use entity names e.g. in templates to send notifications of what have triggered an automation and don't want to see duplicating area names (I have area_name(trigger.entity_id) in the title) or to have a need to cut off all after parenthesis every time

I think, this is not only my opinion, subtitle with area name will be very convenient This information for entities is already exists, only needed to be displayed

ildar170975 commented 2 years ago

Same useless changes: https://github.com/home-assistant/frontend/issues/11938

This is because of your specific naming strategy

No. I have several entities with the same "friendly_name". It is NORMAL to have same friendly_names for different entities. The "entity_id" is UNIQUE name which is supposed to be selected and DISPLAYED in Automation. Displaying friendly_names CONFUSING.

github-actions[bot] commented 2 years ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

ildar170975 commented 2 years ago

Still same in HA 2022.6.1. How am I supposed to guess which entity it is?

github-actions[bot] commented 2 years ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

notabene00 commented 2 years ago

2022.9.0b2 Still the same

github-actions[bot] commented 1 year ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

notabene00 commented 1 year ago

2022.11.4, still relevant

eigan commented 1 year ago

After adding all my sensors, grouping them into areas, am I now supposed to go over all of these and copy the area into the name? Seems not so user friendly (I have 300+ entities). And what if i choose to move the device, I have to update not only the area, but the name too.

Regarding my naming strategy: I number my entities and write the number on the entity.

Changing the dropdown would probably not be enough as the labels should be updated too. There is probably not an easy solution for my problem. Allowing variables in the friendly_name would be helpful perhaps, at least for my case.

ildar170975 commented 1 year ago

Still in 2023.6.0

github-actions[bot] commented 1 year ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

ildar170975 commented 1 year ago

Still same - cannot recognize which entity_id was selected:

And even worse - cannot see it even after selecting the control, none entity is selected (https://github.com/home-assistant/frontend/issues/17395):

github-actions[bot] commented 9 months ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

ildar170975 commented 9 months ago

Still there. Guess which entity is selected.

github-actions[bot] commented 6 months ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

ildar170975 commented 6 months ago

Seems that Devs do not care about all similar issues. The only place where it was fixed within last 2-3 years is "Dev tools -> Set state".

github-actions[bot] commented 3 months ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

ildar170975 commented 3 months ago

Up

github-actions[bot] commented 1 week ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

ildar170975 commented 1 week ago

up

home-assistant / frontend