Z-wave JS just a disaster with system updates

I’m beyond frustrated…every time I do an update to HA system or core, I lose my zwave devices. I am running supervised under proxmox. The latest mystery/glitch is that I can’t uninstall zwave JS Add on…when I uninstall it, it disappears as if it’s uniinstalled, but then on the next system boot, it’s back…and I didn’t reinstall it. That means that I can’t reinstall the addon…huh???

I’m using an anotec V5 stick on a usb2 port/nuci5…

Home Assistant Core 2022.5.5

Home Assistant Supervisor 2022.05.2

Home Assistant OS 8.0

Kernel version 5.15.38

Agent version 1.2.1

how am I supposed to update and not lose z-wave…and now that I’ve updated, how do I get z-wave back???

I’m not sure I can help you with the ultimate issue (getting your devices back) but I can tell you why this is happening.

The zwavejs official add-on is totally controlled from the supervisor since you likely picked the supervisor add-on when installing the zwavejs integration.

So now whenever you delete it the supervisor notices and then re-installs it.

the only way I know to get rid of the add-on now is to delete the zwavejs integration.

You might be able to select a different add-on from the integration configuration. But be aware that if you either delete the existing add-on or change to a non-supervisor add-on any zwavejs configuration (renaming devices/entities/etc) that you’ve done will be wiped out.

Again there are ways to fix that so it doesn’t happen but it’s not straight-forward. There are community guides written for doing it tho.

I just posted a similar thread here: Need to Heal Network After Every Home Assistant Core Upgrade

Mine reappear after healing my network (sometimes it takes 2-3 healings). It’s beyond frustrating.

There’s no reason to uninstall the integration. Just turn off the supervisors addon use in the integration. Devices and services > configure zwave js > re configure server > turn off the toggle for supervisor zwave js addon. When that toggle is off, the supervisor won’t reinstall the zwave js addon and you can freely use zwavejs2mqtt without any issues.

That will solve @ghstudio s problems.

Well, I did say this:

so that kind of covered it but obviously in less detail. :wink:

I haven’t looked at the supervisor stuff in a while and couldn’t quite remember the options.