New ZWave entity ids in 0.47

Hi,

I just upgraded to 0.47 and saw the new node_ids (I still have new_entity_ids: false in my zwave config).
From what I read in the corresponding blog post, it’s not entirely clear to me, how this is supposed to work.

For example, I have five Danfoss zwave thermostats, currently named:

climate.danfoss_z_thermostat_014g0013_heating_1_2_1
climate.danfoss_z_thermostat_014g0013_heating_1_3_1
climate.danfoss_z_thermostat_014g0013_heating_1_4_1
climate.danfoss_z_thermostat_014g0013_heating_1_5_1
climate.danfoss_z_thermostat_014g0013_heating_1_6_1

With 0.47, the new_entity_id: attribute for each of those is the same: climate.danfoss_z_thermostat_014g0013_heating_1.

I assume they will be assigned an additional _2, _3, … when I switch to the new naming scheme.
But how can I tell which will be which before the change, so I can modify my config accordingly?

Sebastian

You can rename your z-wave nodes in the Z-wave manager in HA now to avoid having the same name for multiple units of the same type.

I would rename the nodes to for example “danfoss thermostat kitchen” and “danfoss thermostat room1” etc

Then you have to edit your configuration to the new name that will probably be: “climate.danfoss_thermostat_kitchen_heating_1” or similar and “climate.danfoss_thermostat_room1_heating_1” with the new node_ids

/Mattias

Yeah, you’re right - that will probably be the best solution.
Thanks!

Sebastian

Hi, I have a similar problem. My Roller Shutter has two power Outputs, but Home Assistant named both the same. How can I separate or rename then?


1 Like

Something I just found that will cause issues. Make sure you haven’t used customize.yaml to rename Zwave devices. HA will see that as two devices with the same name and add those _51_0 like tails to the entity_id.

Hey,

I’m know sure what you mean by “not using customize.yaml”. Is there another way for rename zwave devices?

In your previous post you are in the right section. Use the line just above Rename Node to enter a name that makes sense to you and then click Rename Node.
I have changed the new_entity_ids: to true in configuration.yaml and begun changing all my scripts, automations etc. Big job and you can’t go half way.

Yes I know, I already change all IDs to the new form. And change the node name. Everything works fine. But some nodes have more outputs like my post above.
Its a fibaro Rollershutter with cover and sensors. 2 Sensors of the same node (node 2) have the same name. So I cant rename, or hide them.

I think that is where HA will add the _0_1 and _0_2 or whatever it needs to keep them straight. That is where I discovered with an identical name in my customize.yaml file HA added the tail, in my case _51_0 and _51_1. They were the same device just referenced twice.
There just haven’t been that many takers yet and I think we will find out more as people stumble across oddities. I would expect a .47.1

Ok solved,

after adding new_entity_ids: true to the configuration, Home Assistant named all entity IDs correctly, with a counting number at the end.
I think the HA guys have to add this to the documention.

I think they mentioned it in the blog post:

Moving forward, if there is a conflict when generating entity_ids, a suffix will be added, and it will be the responsibility of the user to rename their nodes and values to avoid the conflict. This is the same as any other platform in Home Assistant where two devices are discovered with the same name.

But apparently you now need to rename your nodes in a “conflict-free way”, because otherwise you might end up with different suffixes (suffices?) after each reboot since there is no defined order in which nodes are named.

Sebastian

Well I just renamed all of mine, adjusted groups, scenes, HADashboard entries, and all seems to be working fine. Took me maybe 45 mins for about 150 total entities. I used Notepad++. opened all my yaml files and used “Replace in all open windows” for each entity. worked pretty well.

1 Like

I just removed a remote then added it back again. I renamed the remote to what it was before removing and all the automations worked. This will make life sooooo much easier when you need to replace or move a switch which I seem to quite regularly.

Yes - painful to make yet another change but this one is really worthwhile and I applaud the devs for getting to this point!

2 Likes

I just did the same thing and had it working perfectly…then I rebooted my RPI3 for other reasons and upon restart all of my zwave devices were renumbered and the node names were gone, breaking everything in my setup.

The problem I am having now is remember what zwave device was what. HA literally named them zwave._, zwave._1, zwave_2 and so on. Frustrating…

@brett5150 if you click on any of your zwave devices in the zwave list you should see both the old entity id and the new id

Did you tried to restart HA twice?

Everytime i add a new zwave device to HA i need to restart twice! Otherwise the zwave device will be named like you mentioned.

My old id is blank too. It’s just “zwave.__#”. Where the # is the original node number. All of the device type and manufacturer is missing too so I have no idea what these devices are. In some case I have multiple devices that are the same (aeotec water sensors).

The way I renamed nodes/ids after .47 basically eliminated the node id from the entity id so then knowingly I had to change all of my automation files, customizations etc, which I understand. But now I have no real way of figuring out which device is which without going around to each one and either waking it up or excluding them and starting over.

I’ve restarted a bunch of times.

This is a fresh install of hasbian/0.47 on Saturday. I had a similar thing happen with .46 so sat I just started fresh.

Luckily you have backups of your HA configuration files and can just consult them and rename your devices.
Seriously, if you have backups, I would try replacing your current files with an earlier version. See what you get. You may be able to cut and paste things once you have the devices identified. I would run heal a few times??
Moving forward it will be really important to keep good backups especially the zwcfgxxx.XML file.

partially. Unfortunately I added the aeotec water sensors (4 of them) after my last backup so I will have to redo them. I just hope this is not a common occurrence everytime I reboot the pi.

Also - I cannot just cut/paste or edit the zwcfgxxx.xml file. It always gets overwritten by HA upon restart from what I’ve seen.