Core: Renaming device does not rename all connected entities

[chbndrhnns]

The problem

This is maybe related to https://github.com/home-assistant/core/issues/32544.

I added an Aqara presence sensor via deconz. After clicking the property icon on the device page and renaming the device to motion-kitchen, HA asks if I want to rename the entity id's. After acknowleding this, not all related entities have been renamed:

Only the presence sensor entity was renamed to binary_sensor.motionkitchen, the others kept their old entity id's:

battery level: sensor.lightlevel_43_battery_level
light level sensor: sensor.lightlevel_43

Could we unify this and rename all connected entitys? Or am I getting the confirmation dialog wrongly?

Environment

• Home Assistant release with the issue: 0.106.5
• Last working Home Assistant release (if known): n/a
• Operating environment (Hass.io/Docker/Windows/etc.): hass.io
• Integration causing this issue: deconz maybe?
• Link to integration documentation on our website: https://www.home-assistant.io/integrations/deconz/

Problem-relevant configuration.yaml

n/a

Traceback/Error logs

n/a

Additional information

[probot-home-assistant[bot]]

Hey there @kane610, mind taking a look at this issue as its been labeled with a integration (deconz) you are listed as a codeowner for? Thanks!

[Kane610]

@springstan isn't a deconz issue but a device / entity registry request

@chbndrhnns there is no simplification that I know of that would rename more than one entity because a device could have more than one entity of the same platform and that would complicate naming them in an understandable way. I recommend closing this

[chbndrhnns]

@springstanarris isn't a deconz issue but a device / entity registry request

Thanks for the quick reply. I assume your mention has gone wrong. Did you want to mention @springstan ?

[springstan]

Sorry my bad, just quickly scanned the issue 😅

[gilperme]

Just wanted to add here, that this is also happening for non-deconz Zwave integrations as well. I have mine configured with an Aeotec Z-Stick using the Zwave integration and running version 106.6. Here's a screenshot of an example when I renamed a channel on Power Strip. Please let me know if there's anything I can provide to help resolve the issue. Thank you.

[remknul]

Experience the same on a fresh installed system: Hass 3.12, Aeotec z-stick.
Happened to a fibaro smoke sensor, and wall plugs.

[Kane610]

Unassigning myself for the moment since this is nothing I have time to look at

[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.

[chbndrhnns]

The issue still persists

[frodesoy]

Yes, I can confirm that the issue still exists. Updating the device does not affect the entities, only the friendly names

[MartinHjelmare]

The logic for this is in the frontend.

@bramkragten Was this fixed already?

[MartinHjelmare]

Looks like this was fixed in https://github.com/home-assistant/frontend/pull/6505.

Closing here for now. Please open an issue in our frontend repo if you're still experiencing problems after testing with release 0.114.0.

[nextxpert]

I still see this happening in release 0.116.4

[fysmd]

Same happens in 0.117.6

Navifate to device, rename, answer positively when asked if entities should al be be renamed and not all are: (final one will not rename, have tried repeatedly)

arch | x86_64
-- | --
chassis | vm
dev | false
docker | true
docker_version | 19.03.12
hassio | true
host_os | HassOS 4.16
installation_type | Home Assistant OS
os_name | Linux
os_version | 5.4.75
python_version | 3.8.6
supervisor | 2020.11.0
timezone | Europe/London
version | 0.117.6
virtualenv | false

[Kane610]

@nextxpert it was stated to "open an issue in our frontend repo if you're still experiencing problems after testing with release 0.114.0"