Core: Disabled entities should not "reserve" the entity name

[SeLLeRoNe]

Home Assistant Android version:
1.7.2-139
Android version:
9
Phone model:
OnePlus 5 (A500)
Home Assistant version:
0.105.3
Last working Home Assistant release (if known):

Description of problem:
When I de-activate an Entity (Battery Level and Wifi) and I start to use template sensor, the sensor name get a "_2" attached to his name because the name it's in use from the App Integration.
The entity that is disabled should not "reserve" the name that was stored, that name should be freed in my opinion.
The same way, if I edit the sensor it results in an error if I try to put an existing name, that's okay if the entity is activated (or if you're trying to activate it) but as long as the entity is disabled, it shouldn't really care/check for it.
Traceback (if applicable):

Screenshot of problem:

Additional information:

[SeLLeRoNe]

Additional note, even if the entity doesn't show on the states page (because disabled), the name still seems to be used

[dshokouhi]

@SeLLeRoNe this is as designed. Disabled entities are still registered to HA so that it knows that it is disabled.

https://developers.home-assistant.io/docs/entity_registry_disabled_by/#users-editing-the-entity-registry

[balloob]

This is not an issue with Android.

[SeLLeRoNe]

Ok, sorry then, I tought it might have been a bug and it was related to the mobile_app part therefore I did open it here.

I guess that if it's by design and it's not even part of the Android integration, the ticket can be closed :)

[balloob]

It's by design but you're actually right, that it's silly that disabled entities keep a claim to their entity ID. Going to re-open this.

[stale[bot]]

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 now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[stale[bot]]

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 now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[balloob]

Should still be picked up.