Does that mean that when I connect a second controller I can install easily 2 zwave-js installations? No specific settings needed?
I’ll try tomorrow…
Yes, you need two installations of Z-Wave JS. The second integration server URL should point to the second instance of Z-Wave JS. The “already installed” message means you configured the second instance with the URL of the already configured one.
In HAOS you cannot run the same add-on twice, so you would need to install both add-ons, official and ZUI.
Thank you. That is the sort of plain English language that helps dummies like me. I have not seen it written like that in the documentation but I wish it was. Sometimes the documentation is written assuming that only experts will need to understand it.
From your response, I now understand that I DO have a Z-wave JS server installed with the URL of ws://core-zwave-js:3000.
I have also installed Z-Wave JS UI and it looks like this. I have also managed to pair (include?) a Z-wave sensor to that controller.
BUT, I cannot see either the controller nor the sensor under devices and entities in HA.
If I need to install a second Z-Wave JS server, how do I know what the URL should be? Apologies, I cannot for the life of me find that in any documentation. It defaults to ws://localhost:3000 but I assume that is incorrect for a second server.
Please point me in the right direction, I have read and read and still none the wiser.
Yes, this is the official add-on. Stick A is being controlled here with one instance of Z-Wave JS, and this add-on provides a Z-Wave JS server. It’s already integrated with HA.
Stick B here is controlled by the second instance of Z-Wave JS, and the ZUI add-on also provides its own Z-Wave JS server. Now you need to integrate it with HA (hence “integration”), it’s not automatic.
If I need to install a second Z-Wave JS server, how do I know what the URL should be?
You already installed the second Z-Wave JS server, it’s provided by the ZUI add-on. The ZUI Add-on docs here, which are also accessible from the add-on page itself, give you step-by-step instructions on how to setup the integration, along with the required server URL.
The HA docs that I also previously linked, and which you literally quoted, have the same instructions and provide the explicit server URL to use with the ZUI add-on:
Community Guide
Straight from these forums:
Integration Architecture
Integration documentation: Z-Wave JS Architecture
Z-Wave JS UI Docs
1 Like
Fantastic, done!
I apologise; I though that the ws://a0d7b954-zwavejs2mqtt:3000 URL was an example.
All good now, thank you again.
1 Like
I just saw something in the document that sounds concerning;
Can I switch between the Official Z-Wave JS add-on and the Z-Wave JS UI add-on?
You can, but you cannot run them both at the same time. Only one of them can be active at the same time.
I seem to have both running at the same time and they look like they are both working. Or am I missing something again?
That is referring to using two add-ons with the same controller, since they compete for access over a single serial port (hence the “switch between add-ons”). It is not a problem to run them with two different controllers.
Makes sense, thanks.
just buy a hubitat hub, use it for thr 2nd z wave network, it will adjust the frequency automatically based in your location.
Thanks for this topic.
I helped me to setup a new Z-Wave network next to my old one, to make it possible to switch over some devices to a new stick.
Does this mean if I add a second Nortek HUSBZB-1 stick to a USB port that I can also add a second instance of ZUI to HA? (Or just add the hub directly?) I need to integrate a ZNET + ZWave sensor device that is remote and accessible only via IP.
No, you cannot run two instances of the same add-on. You can run one instance of ZUI and one instance of the core add-on. The latter does not support TCP serial ports. You will need to run ZUI outside of HAOS, or create your own version(s) of the add-on that have unique IDs.
Re-reading, you can use ZUI with Z-NET, and core add-on with the Nortek.
1 Like
Hmm…can I revert to my original installation (ZWave JS core) running all the “local” stuff on the HUSBZB-1 and install ZUI just to run the TCP ZNET?
Sure, you can export your driver cache from ZUI and import it into the core-addon. Effectively, you’ll need to do the reverse of Switching Z-Wave JS Addons with Minimal Downtime! Z-Wave JS (Official) to Z-Wave JS UI (Community) but it’s fewer steps. I can’t really spend the time to create a guide to do that, but the core add-on exposes the cache directory to users so you can directly copy the files over after installing. Feel free to drop by the zwave channel in Discord if you need more guidance.
If you have another server though, it might be easier to install Z-Wave JS UI there and connect to it remotely via HA.
Thanks - appreciate the guidance!! I originally tried following the instructions at Install and setup Zwave JS UI with Snap on a Raspberry Pi to put ZUI on a spare RPi, but it failed. 
So a bit stuck, sigh.
May try doing it again, but with Ubuntu on the RPi instead of Raspbian.
Not sure what your problem was exactly, but I personally would not use Snap. Either Docker or run the binary directly.
1 Like
OK - will see if I can figure that out! I’m Linux…kinda noob, kinda not. Definitely Docker-dumb though. But I can research well – appreciate your time and patience!! Thanks.
You can have a look at the Zwave UI official docs, it has several different ways of installation
1 Like
Thanks - will do! This has been a bit of a frustrating trek…I got the ZNET just because it could be run over IP and pick up the ZWave device at the far end…wasn’t expecting quite this journey!!
I did suggest to HomeSeer that they prebuild their image on the RPi/ZNET with an instance of ZUI installed, and available at a given port … just to make it easier for HA users - and probably get some extra sales from it for the convenience.
1 Like