Name change on Z-wave nodes has no effect on entity id

Configuration
1

Hello!
Due to a SD-card failure I had to reinstall home assistant and reconfigure all my Z-wave devices. I have noticed a strange issue. If I change the name of the Z-wave node and values the entity_id of still remains the same.

Entity_id still the same in dev tools, but looks changed if I click on the node:

24
242880×1800 666 KB

Calling light.turn_on → light.sovrum_taklampa has no effect. But calling light.turn_on → light.fibaro_system_fgd… works.

Config.yaml:

homeassistant:
  # Name of the location where Home Assistant is running
  name: Home
  # Location required to calculate the time the sun rises and sets
  latitude: 57.3167
  longitude: 13.8667
  # Impacts weather/sunrise data (altitude above sea level in meters)
  elevation: 173
  # metric for Metric, imperial for Imperial
  unit_system: metric
  # Pick yours from here: http://en.wikipedia.org/wiki/List_of_tz_database_time_zones
  time_zone: Europe/Stockholm
  # Customization file
  customize: !include customize.yaml

# Z-Wave
zwave:
  usb_path: /dev/ttyUSB-zwave
  network_key: XXX
  

# Enables the frontend
frontend:

neato:
  username: XXX
  password: XXX

volvooncall:
  username: XXX
  password: XXX

# Enables configuration UI
config:

http:
  api_password: XXXX
  # Secrets are defined in the file secrets.yaml
  # api_password: !secret http_password
  # Uncomment this if you are using SSL/TLS, running in Docker container, etc.
  # base_url: example.duckdns.org:8123

# Checks for available updates
# Note: This component will send some information about your system to
# the developers to assist with development of Home Assistant.
# For more information, please see:
# https://home-assistant.io/blog/2016/10/25/explaining-the-updater/
updater:
  # Optional, allows Home Assistant developers to focus on popular components.
  # include_used_components: true

# Discover some devices automatically
discovery:

# Allows you to issue voice commands from the frontend in enabled browsers
conversation:

# Enables support for tracking state changes over time
history:

# View all events in a logbook
logbook:

# Enables a map showing the location of tracked devices
map:

# Track the sun
sun:

# Weather prediction
sensor:
  - platform: yr

# Text to speech
tts:
  - platform: google

# Cloud
cloud:

group: !include groups.yaml
automation: !include automations.yaml
script: !include scripts.yaml
2

This might have something to do with entity_registry.yaml … this has been added recently. Search the forums and you’ll find some posts that deal with that issue (bug?).

3

Running sudo rm entity_registry.yaml and a reboot fixed the issue.

Thanks!

4

I had the same problem after adding a new zwave device.

Deleting the file solved the bug.

Thanks a lot.

5

Me too, exactly same problem with FIBARO, solved after delete this file and restart HA.

Thanks!