OH 5.0 Z-wave to Z-wave-JS-UI migration question

Setup, Configuration and Use Migration
,
1

This may be a dumb question, but it’s more of a clarification that I hope someone can shed light on to help me avoid creating a lot of extra work…

I’m looking at migrating to Z-Wave-JS-UI with OH 5.0. I have it installed via npm and running.

I’m using an Aeotec 5 stick, but am ultimately looking to move to a Zooz 800 series stick for the LR capability.

For the migration, in Zwave-JS-UI, the settings for values for S2 Unauthenticated, S2 Authenticated, S2 Access Control, S0 Legacy, and S2 Authenticated and Access Control for Long Range.

In my OH Z-Wave binding, there is only the “Network Security Key”. I have three door locks that use them, and are a huge pain to include/exclude. I’m trying to make sure I get this right so I don’t have to try and reinclude those locks again the hard way.

As far as I can tell, the “Network Security Key” is the same as the S2 Access Control key in Zwave-JS-UI. Is this correct?

Also, if I generate keys for the rest of the fields, I don’t think that will matter if I have to revert to the OH ZWave binding since, as I understand it, the binding itself handles the security.

Finally, with the official release of this binding, I believe I will need to activate the Home Assistant WS Server option to utilize the JS websocket server. Is that also correct?

Thanks for any input on the topic. I’m trying to minimize any include/exclude operations, especially for those door locks…

2

The OH ZW binding key is S0 legacy. And yes to the websocket.

3

Thanks!

4

As for unsolicited advice :wink:

If both ZUI and OH are on the same device, I would suggest removing the OH ZW binding (to remove the usb lock, then point ZUI to the Zstick. The idea is to make sure all your nodes are interviewed first (wake the battery ones). It is a very busy initial startup. Once all that is done open the port. Again there is a lot of initial OH activity. The developer likes to look at the trace log on startup, if something didn’t get setup okay.

5

I’m able to get Zwave-JS-UI to interrogate the network through just disabling the OH Zwave binding from the controller thing and enabling it from Zwave-JS-UI. I had to disable the soft reset because I’m on a Aeotec Z-Stick 5 w/ FW 1.0 (going to try and upgrade the firmware so I can ultimately use Zwave-JS-UI to take an NVM backup and move it to the Zooz 800 series replacement once everything is working).

I had to stop some testing, but for whatever reason, I wasn’t able to get the new OH Zwave-JS binding to connect to the websocket server. I may have to remove the binding, per your comments. Perhaps that’s the conflict. There’s no security set for Zwave-JS-UI at this stage, so I don’t know why the new OH Zwave-JS binding can’t get to the port (using default 3000). Since it was installed via npm, I’m assuming the server IP should just be 127.0.0.1, but I’ve also tried the actual IP address and localhost. Nothing seems to allow the new binding to communicate thus far. This evening I’ll try removing the binding and seeing if just the new OH Zwave-JS will work.

Thanks for the tip…

6

First and most important is that you get all devices up and running in ZUI. Do not remove or include devices. This way you can always revert.

Once all is fine. You can start using the zwave js binding. (Make sure to remove the native zwave binding.)

7

I also had to upgrade the firmware, scary though, but it all worked out well.