Closed iMicknl closed 6 years ago
(I solved it for myself by renaming the name in the entity_registry.yaml, however this isn't a recommended approach and in that case the Z-Wave documentation should be updated)
I've had this problem on 2 different setups with zwave components.
@iMicknl entity registry for zwave is covered here: https://www.home-assistant.io/docs/z-wave/control-panel/#z-wave-node-management
And this is a duplicate of #12430
Great, thanks for the clarification @fanaticDavid & @dshokouhi. I couldn't find any issue while searching on my keywords. :-)
However I think this should also be added to the documentation page I linked to, since the information there isn't accurate anymore.
@iMicknl anyone can click on the "edit this page in github" link and submit a PR to update it. :)
Closing because it's a duplicate.
Home Assistant release with the issue: 0.66
Last working Home Assistant release (if known): 0.62? Not sure, looks like an issue since the entity_registry has been introduced
Operating environment (Hass.io/Docker/Windows/etc.): Raspbian
Component/platform: Z-Wave
Description of problem: When adding a new Z-Wave device and renaming it through the Z-Wave control panel, it won't be reflected on the entity_registry name. This makes a huge mess, since your Z-Wave devices will have multiple different names and you can't easily keep them apart. It only happens to devices that have been added recently.
For example, if your Z-Wave device is named multisensor2 through the control panel:
binary_sensor.sensor
(current) instead ofbinary_sensor.multisensor2_sensor
(previous)sensor.neo_coolcam_unknown_type0003_id108d_burglar
(current) instead ofsensor.multisensor2_burglar
If I have a look at the same multisensor that has been added before:
binary_sensor.multisensor_sensor
sensor.multisensor_burglar
If I look at the values for
binary_sensor.sensor
, the friendly_name is updated with the Z-Wave name (multisensor2). But the entity itself isn't updated with the new name, which is still described in the Zwave Docs.