zwaveJS controller question/s

[gwp1]

The docs state "substituting your site's IP address and Authorization Key:" I have replaced the IP, np, but am uncertain what "Authorization Key" is expected here.

My Home Assistant setup is using zwaveJS UI (the new name for zwavejs2mqtt).

[toggledbits]

The authorization key was from the preview/development cycle, to limit access to just a handful of people that were working closely with me to get the first version going. You can omit it. I'll update the docs.

[toggledbits]

Where are you seeing this, by the way? Specific link/page please.

[gwp1]

@toggledbits /docs/ZWaveJSController/

[gwp1]

@toggledbits Unfortunately, this means I have something else afoot. Let the log-diving commence!

[toggledbits]

Did you get it going?

[gwp1]

@toggledbits I did not yet (silly day job, getting all in the way of the REAL work...)

I did get as far as log-diving:

[latest-22308]2022-11-08T22:06:50.268Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs connecting to ws://192.168.1.198:3000
[latest-22308]2022-11-08T22:06:50.272Z <ZWaveJSController:WARN> ZWaveJSController#zwavejs websocket error during open/negotation: [Error]Error: connect ECONNREFUSED 192.168.1.198:3000
[latest-22308]2022-11-08T22:06:50.273Z <ZWaveJSController:WARN> ZWaveJSController#zwavejs ws error code ECONNREFUSED
[latest-22308]2022-11-08T22:06:50.274Z <ZWaveJSController:NOTICE> ZWaveJSController#zwavejs websocket to ws://192.168.1.198:3000 closed during open/negotiation
[latest-22308]2022-11-08T22:06:50.275Z <ZWaveJSController:NOTICE> ZWaveJSController#zwavejs connection to ws://192.168.1.198:3000 failed; will retry
[latest-22308]2022-11-08T22:06:50.276Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs retry 912 delay 120000

My initial thought is something is competing for that port - but, again, that's with little to no research beyond pulling the logs.

[toggledbits]

How are you running ZWave JS UI? (how is it installed, started, etc.?)

[gwp1]

@toggledbits Using the Home Assistant add-on.

[toggledbits]

@gwp1 Open its Web UI and make sure the WebSocket (WS) server is enabled... looks like it may not be...

[gwp1]

@toggledbits It is.

EDIT: I even cleared the 0.0.0.0 from the Server Host field just in case it was causing something wonky.

[toggledbits]

0.0.0.0 is another way of saying "any address", so that's OK. Looks like HassOS, then?

[gwp1]

@toggledbits Yessir on both points.

[toggledbits]

It's the devil.

Try this: https://github.com/home-assistant/core/issues/63670#issuecomment-1008624418

[gwp1]

@toggledbits So this is interesting (to me)...

This isn't running. Should it be? In my initial install of Z-Wave JS UI it seemed to point toward that NOT running, it was handling everything and that just needed to be installed (which it prompted for IIRC.) I do have three devices on and running.

EDIT: started Z-Wave JS, third tab Configuration and added this:

Z-Wave JS keeps stopping after I access Z-Wave JS UI which further supports my recollection that they don't both RUN, but both need to COEXIST.

[toggledbits]

I have no idea... you can try it. HassOS is, to me, the devil incarnate, and I don't use it. Others here do, I suspect, and maybe they have some experience to offer. I would take the auto-updates, at least, because HA itself often requires new/latest versions of Z-Wave JS, and everything goes away on that integration when it doesn't get it.

[Pabla]

You can only run one or the other. Uninstall whichever add on you don't need and try again, I ran into the same issue.

[gwp1]

@pabla That did it! Uninstalled one, rebooted the other and applied the tweak that @toggledbits noted previously. Works like a champ - thank you both!

[gwp1]

Quick question @toggledbits : in looking at my iblinds, I see the ability to call for recalibration. The Hubitat community driver has surfaced this. HASS has not (not a surprise, they're quite conservative in what they surface), MSR's zwaveJS controller does not. Is there a way to do so manually (editing a config, for instance)? These blinds wander over time and a scheduled recalibration is very helpful.

[toggledbits]

I would have to look at the device data for the iBlinds devices you have, but I believe that you can access any feature of any device via ZWaveJSController, it just may not be a declared action on a native Reactor capability (in the same way you can call any service in HassController, even if it's not a declared service on the Reactor entity). We just need to figure out what that mechanism is for the iBlinds devices, and either use it as offered, or decide to bring it forward as a simplified action.

Can you point me to online docs for iBlinds that describe how to start (via Z-Wave) the calibration process?