Customized Zwave entity_id names, but zwave_device_config.yaml still shows original name

I have been trying to find out exactly what the zwave_device_config.yaml does after renaming entity_id and Friendly names. I have renamed all my entities and gave them friendly names. But today was looking in the zwave_device_config and noticed all the old names were still there. So for example:

zwave_device_config.yaml:

# Middle Bedroom Window Sensor Node 26  
sensor.linear_nortek_security_control_llc_wadwaz_1_door_window_sensor_battery_level_5:
  ignored: false
  polling_intensity: 1
  refresh_value: true

has been renamed to (from core.entity_registry):

            {
                "entity_id": "sensor.middle_bedroom_window_sensor_battery_level",
                "config_entry_id": "cb27034bd49c9ce32cb5b33ac2882af2",
                "device_id": "94a6ebae13ba48c7d25627afd4a99fcc",
                "area_id": null,
                "unique_id": "26-72057594480427009",
                "platform": "zwave",
                "name": "Middle Bedroom Window Battery Level",
                "icon": null,
                "disabled_by": null,
                "capabilities": {},
                "supported_features": 0,
                "device_class": "battery",
                "unit_of_measurement": "%",
                "original_name": "Linear (Nortek Security Control LLC) WADWAZ-1 Door/Window Sensor Battery Level",
                "original_icon": null
            },

I do have this in my configuration.yaml:

zwave:
   usb_path: /dev/ttyACM0
   polling_interval: 60000
   device_config: !include zwave_device_config.yam

I am sure there is some association the system confers from the Z-Stick Gen5+, but if go to Developer Tools and try to look up the OLD Name nothing comes up.

So will I get any benefit and/or possible cause harm if rename all the devices in the ‘zwave_device_config.yaml’?? Almost seems like the file isn’t really of use anymore, but I just don’t know!

Has the polling, refresh_value,… followed the new name? Any insights if worth my time to fix or possibly exclude from the configuration.yaml. Don’t want to screw up all the work already completed.

And YES, everything seems to be working fine!
Thanks

In my experience the Z-Wave config file won’t be updated until you stop the Z-Wave network. I learned this when I had to make changes to a new device I added and it wasn’t in the config, upon stopping Z-Wave it showed up instantly.

Hmmm, that doesn’t happen here. Knew that had stopped it before, so decided to test it. Just stopped and original names are still there. I guess since it changed on yours it wouldn’t hurt to change them manually then. Of course will take a full snapshot first and try it in a couple days when have the time to deal with the aftermath if doesn’t work. Thanks.

You need to update the file yourself, or re-apply the settings in the control panel to the new entity names.

That seems to work, at least no errors, but if go to Configuration/Server Controls/Check Configuration get these errors:

Invalid config for [zwave]: expected a dictionary for dictionary value @ data['zwave']['device_config']. 
Got 'switch.computer_room_light_switch switch.garage_door_receptacle 
switch.livingroom_alarm_siren_switch switch.livingroom_light_switch 
switch.master_bedroom_light_switch'. (See /config/configuration.yaml, line 7)

Get less errors cause got a lot at first. Then just put the switches in there, took the sensors out. Guess Check Configuration only likes the original names.
Even with the above issues, stopped and restarted the Zwave Network with no problems, but this. Weird!

Looks like a syntax error in the file. Post the contents of that section.

You’re correct, my omission! Forgot the colon at the end of each entity.

sensor.kitchen_motion_alarm_battery_level:
  ignored: false
  polling_intensity: 1
  refresh_value: true
sensor.kitchen_motion_burglar:
  ignored: false
  polling_intensity: 1

Appreciate you guys help. Thanks!