I migrated from Z-Wave-JS + its Supervisor to having Z-Wave JS MQTT manage the Z-Wave USB stick.
Is there a way to kill the Supervisor add on without uninstalling and reinstalling the Z-Wave Integration (which loses some entity name changes if doing that)?
Just turning off the Supervisor service has it coming back and re-starting after every reboot - which means it may claim the stick and break the Z-Wave network.
Mate: that worked beautifully. Iāll not apologise for failing to guess that (itās not totally intuitive), but thanks for your tip
Just for the archive, I:
1 Backed up a snapshot and downloaded off the Pi
2 Stopped and manually uninstalled the Z-Wave JS Supervisor underthe Supervisor tab, to free port 3000
3 Configured Z Wave JS MQTT to listen on port 3000 and restarted.
4 Reinstalled the Z Wave Integration like you said. BE CAREFUL to untick the āInstall Supervisorā tick box!!! It found the service on 3000 and seemed to just work
Names of entities have not, as far as I can see, been buggered up.
Itās not obvious at all that this process would result in a re-configuration, especially since you get an error. Make sure you actually unchecked that checkbox about the addon, otherwise the official addon will be re-installed.
I believe an upcoming release will support a proper re-configuration.
Oops - the Supervisor component just came back on a reboot. And runningā¦ Iāll have to untick the āSolvedā knobs hereā¦
Push comes to shove, I can take a dump of my entities and fix the names - only a very few had the entitie strings changed from the default thatās inferred from the device name,
Iāve run the process again really carefully - and itās worked
Rebooted twice toi be sure. No entity renaming problems. No spurious supervisor module. Z Wave devices working.
I guess I must have had a click spasm on the installer dialogue.
Thanks ever so much - all is good - I shall edit posts accordingly in case anyoen else has a problem.