Z-wave JS won't stop running when stopped

Configuration Z-Wave
1

Hi - I’m new. I’ve taking in about a month’s worth of knowledge over the last 7-10 days. HA is amazing compared to SmartThings in what it can do! I never thought this level of control/flexibility was possible.

I successfully moved all of my Z-wave devices over to the Z-wave JS add-on (via HUSBZB-1 USB), except for two nodes which didn’t get “seen” correctly and therefore I had to re-include them again. Now the Z-wave JS module keeps looking for them and reports them as dead. I want to prune them out of the database, but don’t know how.

I read somewhere (can’t find it now) that I could use ZWaveJS2MQTT to possibly see or edit these entries and perhaps remove the bad nodes.

So… I thought that I’d stop the normal Z-wave JS add-on first and then install the ZWaveJS2MQTT add-on. But when I stop the existing Z-Wave JS add-on it keeps restarting itself. Even after I uncheck both ‘start on boot’ and ‘Watchdog’. Even after I have these both unchecked and reboot the host.

21-04-22 21:40:40 INFO (SyncWorker_4) [supervisor.docker.addon] Starting Docker add-on homeassistant/aarch64-addon-zwave_js with version 0.1.20

TLDR:

  1. How can I stop Z-wave JS from running if at all? (or maybe I shouldn’t?)
  2. Is there an easier way to edit the Z-wave database to remove the dead entries?

Thanks for reading and any suggestions you may have.

2
3

Thanks for pointing me to that thread and back to the add-on doc.

I tried to reload the Z-wave JS Integration while unchecking the box and entering the address of the new add-on (ws://a0d7b954-zwavejs2mqtt:3000) but it would not take it. It kept saying that it wasn’t valid, and then my RPi3 started to max out with swap and then memory going to 100% and then it would lock up. I’m obviously doing something in the wrong order. I’ll come back to this again after doing some more research.