Yeah, I’ve been following this topic for a while, I have two houses both running the deprecated zwave, with the only issue being newer devices come up as unknown. This isn’t a big deal since I’ve gone to scripts anyways to configure the zwave parameters in the devices - to make it repeatable. Anyways, it’s been very reliable when running and had zero problems for a year plus. So,
“if it ain’t broke don’t fix it”
While I know I can run the old code as a custom component, I would like to experiment with migrating, but I am concerned about not be able to roll-back. I’m highly concerned with the opening statement here that says the zwave network would not start and roll back failed. Is there any insight into why that happened? Does zwave-js change the config on the stick or network Config on the nodes?
Thoughts on this being a backup strategy. Using HA container, MariaDB and Aeon Labs Gen 5 stick. This assumes I’ve already updated to latest HA.
- Backup the gen5 stick.
- Shutdown HA
- Duplicate the HA config folder
- Create a new container
- In new Config disable MariaDB (usually do this by editing connection string to be invalid)
- Startup JWAVEJS-MQTT container, get it setup with the stick and network key
- Wait for the interview process to complete / go around and wake up nodes
- Start up new HA and try migration
If it fails, I can go back to the old container and if zwave fails to start I can restore stick from backup,
Any other advice?