I have 2 fibaro FGT001, that show up as fibaro_system_fgt001_heat_controller and sensor.fibaro_system_fgt001_heat_controller_2
In the configuration->zwave I’ve renamed them to diningroom and veranda, and in the overview, on the zwave card they appear under these names
BUT
on the overview, on the climate card, there are still the fibaro* names
going to configuration->zwave, even though the node names are fine, the entity names are still using the fibaro* name scheme
same applies to the history where also the fibaro* names are being used (consistently with the entity names ?)
My expectation would be that if I change the name of a node, then consistently all configuration locations for the whole homeassistant stuff is adapted. Rebooting didn’t solve the issue BTW, and in my /home/homeassistant/.homeassistant/config all files belong to homeassitant.homeassistant with mode 644, thus I’m excluding file permission issues.
Or am I really supposed to go through all the entities and define a custom name for each of those ? This can’t be the user-friendly solution !
what’s strange to me is that the renamed node has no meaningful entries. Is the “node-4” sufficient to relate it to the previous entry (which is the definition of the original node after discovery through z-wave) ? Or did something go wrong during renaming ?
Unfortunately, it didn’t just “stop working”. It was intentionally changed by the devs to make it work the way it does right now. Everything worked perfectly fine when we had the OZW configuration integrated into HA directly. And then it was removed.
I’ve been a pretty vocal critic of the whole new entity registry especially as it’s been applied to z wave. But no one of any import has ever responded to address my (And others!) criticism/concerns.
OTOH, I think I might have come up with a way to circumvent this issue but it’s kind of hacky and cumbersome. And I haven’t had a need to actually try it since I haven’t needed to add any z wave stuff since the HA update when this silly change was implemented (v78 I think…) so it may not even work.
But I intend to try to add my devices to z wave then stop HA, open a docker container that will run OZWCP, rename the node there, close OZWCP and then restart HA and see if the node information updates with the new config.
what about the entity_registry file ? is the format correct, i.e. the renaming creates a parallel hierarchy ? Or should just the “name” field of the existing entry be changed ?
I’ve never modified that file and according to a moderator here modifying that file manually “is not officially supported”. That said, I don’t think that modifying the “name” section will break anything. But TBH you can do the same thing thru the GUI so manually changing that file isn’t necessary. But I’m honestly not sure how that file overrides or is in addition to any entries you have in the “customize:” section.
The problem comes when you have a device that creates 13 different entities and you need to add 15 devices to you system (~ true story of another member on here) and you want to change the friendly name and entity_id of all entities you now have almost 400 things to manually change.
And be aware that changing the entity_id field doesn’t cross reference anywhere in the code that the original entity_id is currently being used and also update those to the new entity_id so you have to manually change all of those too to use the new entity_id.
and None of the changes you make to the HA system affects the information that gets stored on the z stick controller. That means that if you have 10 motion sensors that have 5 entities associated with each of them if you ever need to look in your controller (or move your existing controller to another system) you will see, for example, “Manufacturer_motion_sensor” as the first one, and the same thing with a number (_1, _2, _3, etc) appended for all the subsequent devices. Depending on how many devices you have it could be a pretty daunting task to figure out which device is serving which location.
OK, understood. So I’ll go on and rename the stuff using the GUI
The drawback I see here is that in case I setup the whole thing from scratch in far future, I’ll probably have to restart with renaming from scratch - unless I can simply copy the file to seed the new setup !?!
