Incorrect entity ID's from node

Configuration Z-Wave
1

Hi guys,

Having a strange issue here with a Fibaro Universal Binary Sensor (FGBS001). I added a DS18B20 temp sensor to the module and needed to exclude/include the FGBS001 node for the temp sensor to be recognized in HASS. The FBGS001 has 2 pushbuttons hooked up to the inputs.

I’m running Hassbian with HomeAssistant version 0.63.3 on a Rpi 3.

I see the 2 binary sensors and the temperature sensor in the home view, these work when I activate the switches and the temperature is measured correctly:
tempsenssensors
When I open the badge for each sensor I see:

old entity id: sensor.fibaro_system_fgbs001_universal_binary_sensor_temperature_35_1
new entity id: binary_sensor.fibaro_system_fgbs001_universal_binary_sensor_temperature

old entity id: binary_sensor.fibaro_system_fgbs001_universal_binary_sensor_sensor_35_0
new entity id: binary_sensor.fibaro_system_fgbs001_universal_binary_sensor_sensor

old entity id: binary_sensor.fibaro_system_fgbs001_universal_binary_sensor_sensor_35_0_2
new entity id: binary_sensor.fibaro_system_fgbs001_universal_binary_sensor_sensor

In the dev-state window, I see following entity’s (in the same order as above). This is incorrect compared to the working sensor at the bottom of this post.

sensor.fibaro_system_fgbs001_universal_binary_sensor_temperature_3
binary_sensor.fibaro_system_fgbs001_universal_binary_sensor_sensor_3
binary_sensor.sensor_2

I tried excluding and including again, the number of the first 2 entity ID’s increment:

sensor.fibaro_system_fgbs001_universal_binary_sensor_temperature_4
binary_sensor.fibaro_system_fgbs001_universal_binary_sensor_sensor_4
binary_sensor.sensor_2

When I look in the zwave window and list the entities of the node, I get:

friendly_name: FIBARO System FGBS001 Universal Binary Sensor Sensor
new_entity_id: binary_sensor.fibaro_system_fgbs001_universal_binary_sensor_sensor
node_id: 35
old_entity_id: binary_sensor.fibaro_system_fgbs001_universal_binary_sensor_sensor_35_0
value_id: 72057594630111232
value_index: 0
value_instance: 1

friendly_name: FIBARO System FGBS001 Universal Binary Sensor Sensor
new_entity_id: binary_sensor.fibaro_system_fgbs001_universal_binary_sensor_sensor
node_id: 35
old_entity_id: binary_sensor.fibaro_system_fgbs001_universal_binary_sensor_sensor_35_0_2
value_id: 144115188668039168
value_index: 0
value_instance: 2

friendly_name: FIBARO System FGBS001 Universal Binary Sensor Temperature
new_entity_id: sensor.fibaro_system_fgbs001_universal_binary_sensor_temperature
node_id: 35
old_entity_id: sensor.fibaro_system_fgbs001_universal_binary_sensor_temperature_35_1
unit_of_measurement: °C
value_id: 72057594630127634
value_index: 1
value_instance: 1

I have another FGBS001 which is working perfectly fine, I see these sensors:

sensor.fgbs001_deurbel_temperature
binary_sensor.fgbs001_deurbel_sensor
binary_sensor.fgbs001_deurbel_sensor_2
2

I just renamed the node and did a reboot:
rename

Zwave entity attributes:

friendly_name: FGBS001 David Bed Sensor
new_entity_id: binary_sensor.fgbs001_david_bed_sensor
node_id: 35
old_entity_id: binary_sensor.fgbs001_david_bed_sensor_35_0
value_id: 72057594630111232
value_index: 0
value_instance: 1

friendly_name: FGBS001 David Bed Sensor
new_entity_id: binary_sensor.fgbs001_david_bed_sensor
node_id: 35
old_entity_id: binary_sensor.fgbs001_david_bed_sensor_35_0_2
value_id: 144115188668039168
value_index: 0
value_instance: 2

friendly_name: FGBS001 David Bed Temperature
new_entity_id: sensor.fgbs001_david_bed_temperature
node_id: 35
old_entity_id: sensor.fgbs001_david_bed_temperature_35_1
unit_of_measurement: °C
value_id: 72057594630127634
value_index: 1
value_instance: 1

Nothing changed in dev-state:

sensor.fibaro_system_fgbs001_universal_binary_sensor_temperature_4
binary_sensor.fibaro_system_fgbs001_universal_binary_sensor_sensor_4
binary_sensor.sensor_2
3

I just finished up my first 2-3 weeks with HA, I’m running ver 0.63.1
If nothing is showing changed in entity_registry, look at the node listing in zwave configuration gui. Does it say
YourNodeName (Node:xx CacheLoad)?
I found if it says CacheLoad, the best way to change entity names is to edit the entity_registry file directly and
modify it there. Restart HA or reboot afterwards to pick up the changes.
If your node reports (Node:xx Probe ) or something else, the zwave controller thinks this node is not fully setup with the controller. With my system, I had issues with nodes not showing up in entity_registry. Changing the
zwcfg_0xd3a76624.xml fixed that.
See Can't get Zwave binary sensor to update GUI for the writeup on that.

4

Thanks a lot! :grinning:

I solved my problem by manually changing the zwcfg_***.xml file.

5

Correction:

I fixed it in the entity_registry.yaml file.