I wasn’t suggesting cutting and pasting to the zwcfgxxx.xml file, but rather more selectively restoring bits of scripts, automations etc.
According to the blog post the file will be important. The overwriting has been my experience as well but according to the blog post "Among these new features is support for renaming of ZWave nodes and their underlying values. (These renames are persisted in zwcfg_*.xml) This is important, because these items are combined to form the Home Assistant entity name, which is used to generate the entity_id. "
I would like to have some clarification on where these names are stored if indeed the zwcfgxxx.xml is still recreated each reboot. Perhaps @turbokongen could comment.
new_entity_ids: true was already added to configuration.yaml and HA has been restarted. The sensor being used is FIBARO FGBS001 Universal Binary Sensor
Do I have to perfom any actions / renames? The “new_entitiy_ids” are all the same (in the attributes column (right)), but the entity column (left) shows unique names.
Can / should / must entities be renamed, too? If so: how?
So I just jumped into the cold water, switched over to the new entity id scheme and renamed all my nodes.
The danfoss thermostats mentioned in the first post all received names like "danfoss_<room>", e.g. danfoss_livingroom.
I now have zwave.* entities matching the new names, as expected.
But the climate.* entities are now called e.g. climate.danfoss_livingroom_heating_1.
I was hoping we finally got rid of the added index numbers.
And also the added “_heating” at first caused a bit of confusion on my side.
Aside from that (and also the fact the entity id change causes a restart in collecting history data in my InfluxDB instance), everything went well and it does look a lot cleaner.
I do hope, though, that we don’t see any more entity id changes (at least not before v1.0)…
I was confused as well. But its simple. The “new” Entitiy ID is the blue one! You dont need to rename anything. Simply use the Entity ID with the number at the end.
