Hello - currently running the built in / deprecated z-wave integration (waiting for migration path!). I have it configured using the front end configuration > integrations method.
presume you mean every time I update HA, my Zwave custom drivers get overwritten…
Yes, that happens if the directories are not created and referecned in the zwave yaml config using config_path (which you seem to indicate you do not want to do) or follow the guide which is easily found (Configuration - Home Assistant)
You’re saying I cannot change the config_path after the integration has been setup? Seems different from every other HA integration I’ve used - you can typically change variables freely and reload / restart HA to have them picked up.
I do not recall if the option was present when I initially setup zwave - I didn’t have a need for it then so if it was there I left it as default.
I really don’t want to delete the zwave integration and mess up my zwave devices and custom dashboard. Is there a “painless” way to do this?
I don’t know, it’s been 2 years since I switched from the UI to yaml in that integration. I don’t think there will be a smooth transition. Backup your instance with a snapshot. Then I’d probably delete the UI integration. Shutdown. Add the configuration.yaml and go from there. The zwave network key will be inside the hidden .storage folder and i believe it would be in the config_entries file. You can find more details about that file in the migration guides for zwavejs.
It is effectively the same thing. I was surprised to hear that was the only option and was seeking clarification.
For the record - I haven’t done anything yet (besides find my key). I’m thinking I might be better off just migrating to zwavejs than trying to keep the legacy zwave integration going.
If you look at the integration page for Z-Wave JS it specifies the following “we currently do not provide a full-fledged, worry-free, click-a-button, migration from old to new. We’re exploring options to provide this in the future.” I guess that is what I was hoping for based on the official documentation.