Before I upgrade I would love to know what the below change in .40 means. Does this mean that all Vera entity names in HA will change ? e.g. my lights.bathroom will now become lights.bathroom_xx ?
From release notes:
Vera entity ids have changed. This is a one time change to migrate to a model that will prevent future conflicts.
Do you know if the final implementation was only to add the vera_ID if there was a duplicate or always for any vera device? If it’s always, this is a huge change for me, I have over 60 vera devices…
Its for all devices
Im just about too fix all of my groups etcstrong text
Ouch… holding off on upgrade as I will need to reserve some time for that one…
It’s worth looking at this config, since it looks like @jnewland’s gone to the effort of scripting the required changes. That should make your life a lot easier.
I did it manualy, but gonna try that script also. Its easy to miss something
I’m still on .39 due to this change. Dragging my feet… Did you ever run the script?
I’m trying now (first with just one devive to test) but can’t get it working. I can generate the needed first part but then get stuck as I need to modify some of the sed instructions to make it work on my all in one jnstaller.
My assumption was that I could go into the PI with putty (logging in as Admin, the user make all my changes with to the YAML files). Change to the /home/hass/.homeassistant directory and then execute sed -i "" "s/switch.kitchen_co/switch.kitchen_co_349/g" /home/hass/.homeassistant/*.yaml
But this throws:
pi@raspberrypi:/home/hass/.homeassistant $ sed -i "" "s/switch.kitchen_co/switch.kitchen_co_349/g" /home/hass/.homeassistant/*.yaml
sed: can't read s/switch.kitchen_co/switch.kitchen_co_349/g: No such file or directory
sed: couldn't open temporary file /home/hass/.homeassistant/sedsv3hmA: Permission deniedHi
I did not run the script I had too rename it all
Ok, in the end I did the same. Ouch! But at least back to the latest version.