@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.
I donāt get it. I gave all my zwave nodes a Name and a Location in OZW, in HA they still show up like this:
switch.qubino_zmnhadx_flush_1_relay_switch_23_0
In my config i usualy try to not use this nameā¦I mostly use homeassistant.turn_on and the the group name. But when a device fails and I have to exclude/include i need to reconfigure all my groups and customize settings.
How can I rename the entity name so i donāt have to change my config all the time?
It is possible that ozwcp and HA are looking at two different xml files. You might (as root) change directory to / and then run a find comand see how many and where the files are located.
AFAIK they are two different XML files. I generally copy the one from the ozcp directory into the .homeassistant directory when Iām finished making changes and saved in ozwcp. None of this stops homeassistant from appending node IDs to the end of the names though.
They had to do that though. It was updated in 0.31 to prevent a very nasty bug; if you had multiples of the same model Z-Wave device there was a good chance that both would try to use the same entity IDs which would be a bad thing.
To fix the issue the internal Z-Wave index is now appended to the end of all Z-Wave entity IDs going forward.
The other option is to remove the one that ozwcp uses and replace it with a symbolic link which points to the copy in .homeassistant.
Iām not sure if I am doing this right? but I update all my zwave devices in ozwcp using names like Bathroom, kitchen, kitchen switch etc and then copy the zwcfgxxxxx.xml file into homeassistant folder and now I get
binary_sensor.bathroom_sensor_2_0
binary_sensor.kitchen_sensor_3_0
switch.kitchen_switch_switch_4_0
this is ok to do isnāt it? Just so I can get real names on the devices so I know at a glance which is which.
Cheers
Mark
1 Like
Does it work for you? Thatās really the only concern in naming.
Iām having the same issue. Heck - I canāt even find the zwcfgxxxx.xml . Once I update the names in OZW web client, save.
I have a HASSBIAN installā¦
I do the same as @MarkR, as in: naming the devices through OZWCP so it makes sense what they are in Home Assistant. Sure, the node idās and indexes are still a pain, but I understand theyāre a necessary evil.
The only difference in my case is that I deleted the zwcfg_xxxxxxxxxx.xml file in my .homeassistant directory, and recreated it as a softlink pointing to the original zwcfg_xxxxxxxxxx.xml in the OZWCP directory. I didnāt come up with this myself, but saw other users report about this as a way to make sure that Home Assistant is using an up-to-date configuration. It saves me the trouble of having to copy the file over every time I make a change.
mine is in
/srv/homeassistant/src/open-zwave-control-panel
I use the all in one.
and the reason I ask, is should I be doing it this way? It does appear to work fine, automations etc.
Try this:
$ cd /
$ sudo find -name zwcfg*.xmlI executes the find command only file that came back was in the .homeassistant directory.
When Iām in Open Zwave control panel change the names and location, then click save but where does this actually save to? It doesnāt change in my home assistant directory. Any thoughts?
My goal is I want to rename my devices
I am using HASSBIANk