[Feature Request] better usability with Entity ID and Naming

[Ltek]

Checklist

• I have filled out the template to the best of my ability.
• This only contains 1 feature request (if you have multiple feature requests, open one feature request for each feature request).
• This issue is not a duplicate feature request of previous feature requests.

Is your feature request related to a problem? Please describe.

Battery Notes names its sensors based only on the device name in the device registry, not the friendly name of the native battery sensor. It also just blindly append numbers to the Entity IDs... and this, creates inconsistencies and usability challenges for many things.

BN then creates duplicate names with no each way to know which is tied to what actual device without looking at the Area properties... the Entity ID nor the Entity Name help. So as it is with my setup, I now have 4 BN device with named "Shade Remote Battery+" and multiple entity duplicate names for all my shades (Shade 1, Shade 3, Shade 3, etc) also.
And the entity IDs are not consistent as seen below...

Describe the solution you'd like

Keep all entities tied to a single device using a consistent Entity ID nomenclature, some examples...

EntityName_RoomName_number (and keep all the related items with the same number... not like what happens where some may be 2, some 3

Describe alternatives you've considered

non exists other than manually renaming / re-IDing ... doing that for 273 Battery Notes entities is not a recommended task

Additional context

n/a

[andrew-codechimp]

Hi, Home Assistant itself is undergoing some changes with entity names/entity id's which I'm watching.

At the moment they are doing it in small steps and actually reverted some changes due out this week but once they have settled on a preferred method I am going to revisit what I do here.

[github-actions]

This issue is stale because it has been open for 30 days with no activity.