Z-Wave JS Supervisor will not die - the great undead. Z-Wave JS MQTT installed

Configuration
1

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.

Many thanks :smiley:

2

When you reconfigure the integration you need to uncheck the checkbox that tells it to use the official addon.

1 Like
3

ā€œReconfigureā€? Is that possible without deleting and reinstalling? I might have missed it, but I couldnā€™t find a way to do that when I tried?

(Just reverted to a Snapshot I took immediately prior, so I can have another go)

4

Just add the integration again w/o deleting it, it will re-configure it.

1 Like
5

Ooooohhhh

Hold onā€¦

6

Mate: that worked beautifully. Iā€™ll not apologise for failing to guess that (itā€™s not totally intuitive), but thanks for your tip :+1::+1::smiley:

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.

Brilliant! Thanks again. Saved me a bit of work :smiley::smiley:

7

Itā€™s not obvious at all that this process would result in a re-configuration, especially since you get an error. :laughing: 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.

1 Like
8

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,

9

This part was missing from your list above, and is the critical part.

1 Like
10

Pretty sure I did - but let me rever to my snapshot and have another go later this eveningā€¦ Have to cook supper in a minute.

11

Further, you need to stop and uninstall the zwave_js addon (or at least make sure that it isnā€™t set to start on boot).

1 Like
13

Hi Rob,

Iā€™ve run the process again really carefully - and itā€™s worked :+1:
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.

Cheers :smiley:

14

Sorry, probably shouldnā€™t have quoted you when I was just emphasizing what you said in reply to Tim :slight_smile: . That was probably confusing.

15

I blame Discourse. :sweat_smile:

16

At least you havenā€™t blamed my appalling typos :joy: