I’ve been trying the commands that were suggested by @splnut and @fanaticDavid but am getting errors when trying to make the suggested changes. I believe I’ve identified the issue which is zwcfg_xxxx in home/hass/.homeassistant/ is owned by hass and the zwcfx_xxxx in /open-zwave-control-panel/ is owned by root. Should they both have the same ownership? If so, root or hass and how do I make that change?
Check the post just before yours.
chown hass:hass /home/hass/.homeassistant/zwcfg_xxxxxxxxxx.xml
You will need to change the zwcfg_xx to your filename or use * in place of all the x’s (as in zwcfg_*.xml)
/home/hass/.homeassistant/zwcfg_xxxxxxxxxx.xml was owned by hass:hass
/srv/hass/src/open-zwave-control-panel/zwcfg_xxxxxxx.xml was owned by root:root
Since that last post, I’ve changed all files in both directories to hass:hass. I’m hoping that resolves my issues.
I’'m working on getting rid of the node id number in the end of zwave names.
I’m new to Home Assistant and not “official” developer so it might take a while before it’s in releases.
I made a thread about this in Feature requests but no one voted it ( boo-hoo )
You can also make symbolic links between OZWCP config and hass config. I’ve symbolic links for zwcfg and options.xml. No need to cppy those files anymore.
3 Likes
I would love to use symbolic links instead of copying the files over every time. Could you elaborate on how you did that?
ln -s /usr/local/lib/python3.4/dist-packages/libopenzwave-0.3.1-py3.4-linux-armv7l.egg/options.xml /home/pi/.homeassistant/options.xml
ln -s /usr/local/lib/python3.4/dist-packages/libopenzwave-0.3.1-py3.4-linux-armv7l.egg/zwcfg_0xXXXXXXXX.xml /home/pi/.homeassistant/zwcfg_0xXXXXXXXX.xml
I’m not quite sure if hass has right to write those but I don’t use hass to add new devices but OZWCP.
I should also put config files to /etc/openzwave because config files are more important to keep up to date if you have new devices. I could just create a script that fetches the latest from openzwave which is easier than updating the whole software.
2 Likes
I already wrote the code to get rid of node id’s in the end of device name but the changes seem to be turned down.
So if you want this change to happen, go vote my feature request.
It of course needs the user to understand to name the devices uniquely.
I’ll be using my version because I need more control with the names. There will be problems also if device classes are renamed or moved during development.
1 Like
Of course it would help to link the post in right, Marko? 
I just voted and you can too at:
I’m too modest to vote my own feature requests 
I simply need this. Today I had to add some devices again, and old devices have a bug in that way that they try to keep their old node id’s. So when I added an old device again, it took the same node id as one newer. So I have the add that newer device again and before that do a full reset. Then there’s the newer devices that I removed&added just to check the secure connection works and when I did this, their node id’s changed even when their old node id’s were now free.
Then I moved one temp&humidity sensor to roof and simply named it again:hass thinks it another sensor and sees two sensors, the one with the old name and one with the new name. I can move these sensor around and hass just thinks some sensor went off and another on. In the long run I can use these recorded values for planning how to control temperature and air quality.
1 Like
I just upgraded to 0.31.1 and all of my (18) z-wave devices were renamed.
Some stability please.
2 Likes
This is why you should read release notes. The reasons and procedures were clearly laid out in the release notes and it was also mentioned again in the breaking changes section.
2 Likes
So, all openzwave device names are stored in an XML file, this is nothing to do with the devices themselves and can’t be written to them?
Are there any standards for such XML files, if i spend hours and hours renaming everything and keep backups of the XML will i always be able to use it?
I’m looking to buy 25 fibaro dimmer modules, so this seems like a must for me otherwise what a pain looking at 25 x “light.fibaro_system_fgd212_dimmer_2_level_2_0” !
thanks!
edit: Also i only have one switch installed but have two entries in HA with no differences in description?:
light.main_bathroom_light_level_2_0
light.main_bathroom_light_level_2_0_2
off friendly_name: main_bathroom_light Level
location: main_bathroom
node_id: 2
supported_features: 19
@sg86 You should have a look at the customize feature. You can change the names displayed, without needing to mess with the underlying files. https://home-assistant.io/getting-started/customizing-devices/
Customization will only solve the front end problems, and still would introduce problems writing automations. Distinguishing 20 almost identical entities.
1 Like
The point i’m making here is this is not a different device…
I have hidden it and 5 other elements from this single device that i don’t want displayed on the frontend using the customise feature, but its not a solution to what i’m reporting.
The above two Entities have the same node_id, does anyone with fibaro switches have this issue?
Yes. Every Fibaro dimmer i have puts these two entities. Only the _0_2 reports on off state and brightness - see below for 2_0_2
Dimmer 1
light.fibaro_system_fgd212_dimmer_2_level_2_0 off node_id: 2 supported_features: 19 assumed_state: false
light.fibaro_system_fgd212_dimmer_2_level_2_0_2 on brightness: 255 friendly_name: FIBARO System FGD212 Dimmer 2 Level node_id: 2 supported_features: 19
Dimmer 2
light.fibaro_system_fgd212_dimmer_2_level_3_0 off assumed_state: false node_id: 3 supported_features: 19
light.fibaro_system_fgd212_dimmer_2_level_3_0_2 off friendly_name: FIBARO System FGD212 Dimmer 2 Level node_id: 3
supported_features: 19
Hey, thanks for confirming that! However, i’m not sure what you are explaining with your logs of the _2, what exactly are they for? Do you use anything but the _0 entity in your HA?
Yes got it wrong myself. No use only _0 entity.
There is a whole bunch of stuff Fibaro reports and have no idea on the usage. For example
For example also have this
light.fibaro_system_fgd212_dimmer_2_step_size_2_6
supported_features: 19
light.fibaro_system_fgd212_dimmer_2_step_size_2_6_2
supported_features: 19
I’m actually pulling my hair out with the entity naming.
Today i replaced some halogen bulbs with LEDs, and of course i had to re-calibrate, however my fibaro dimmer went into alarm mode and so i factory reset it as per the instructions. Now my devices/entity names etc are wrong, so i have to edit my configurations again.
Why does HA/openzwave add node data to the “name”? I’ve set this device to be called “bedroom_1”, and if the node wasn’t added to the end (openzwave and HA append “_9_0”, all my configs would just work)
It seems like there isn’t a nice way to organise devices on a network at the moment, and I can’t figure out whos issue it is?
1 Like
That’s not OZW, that’s HA. It’s a change that was made in 0.31 and it’s actually the node index.