Switching from OpenZwave (Beta) to ZWave JS UI (formerly ZwaveJS2MQTT)

[nappyjim (Jim)]

@johntdyer

What is the difference between the “Official add-on” for Z-Wave JS and the community Z-Wave JS to MQTT add-on? Are there any considerations we should take when choosing one over the other ?

JS doesnt provide any UI or way to change configuration parameter. JS2MQTT does both of those and allows you to use MQTT as well if you want. I use MQTT so I can set parameter via Node red and not through the UI

[nappyjim (Jim)]

@BuilderTroy

Does the Network config need to be set to anything in this screen? I have a feeling this is blocking port 3000 and not allowing me to connect the ws://localhost:3000 in the Zwave JS integration config.

You are not supposed to connect to that address in the Zwave JS intergration. Re-read the Documentation in JS2MQTT.

Heres my configuration (didnt change anything)

[BuilderTroy (Troy Lykken)]

@nappyjim Thank you! Using ws://a0d7b954-zwavejs2mqtt:3000 worked perfectly!

@petro - We may want to think about adding these steps as substeps under step #10 in your walk through. I never would have guessed to use that connection address and was really stuck on that.

Thanks everyone! I am excited to start working with zwavejs2mqtt!

[petro]

You don’t even need to specify the container like the JS2mqtt documentation eludes to. The default ws://localhost:3000 should work, it’s what I’m using.

[BuilderTroy (Troy Lykken)]

Interesting - I wounder what was differnt in my installation. Every time I used localhost I got the same failed to connect error as @neliss. Using the contrainer string provided worked like a champ though.

[riddledaxis (PJ)]

Hi @petro

I have just finished setting up this add-on and the only way I could get the ZWave JS integration to talk to the ZwaveJS2MQTT server was to use the following:

ws://a0d7b954-zwavejs2mqtt:3000

When I used localhost, it would not connect, but as soon as changed it to the above it connected straight away and I could finish the setup.

Hope that helps

[petro]

Ok, others reported the same, I’ll add it to the docs

[HA_fanatic]

No it does not you have to just remove the , 0x for all of them.

[raman325]

Thanks so @petro you may want to mention that in the docs

[rpr (Tom Lichti)]

My OZW1.4 setup is on an RPi remote from my HA instance, is there a guide to integrate from a remote ZwaveJS2MQTT? I have ZwaveJS2MQTT installed on the remote RPi, and the MQTT events are being forwarded to my HA instance that is running MQTT, but I haven’t been able to figure out how to get HA to control devices. I can see my Schlage lock in HA, but the ‘lock’ service doesn’t do anything. For reference it did work with OZW on the remote RPi and MQTT and OZW inttegration on HA. I have put the network key into ZwaveJS2MQTT and it appears to work.

I assume I’m missing something, not sure where to go from here, appreciate any pointers, or is the HA side still a work in progress?

Thanks
Tom

[ptdalen]

Something simliar posted in another thread, but thought I’d put it here for those using docker compose

version: '2'
services:
  zwavejs2mqtt:
    image: zwavejs/zwavejs2mqtt:latest
    container_name: "zwavejs2mqtt"
    security_opt:
      - seccomp:unconfined
    devices:
      - "/dev/ttyUSB0"
    ports:
      - 8091:8091
      - 3000:3000
    volumes:
      - /yourlocaldockerpath/zwavejs:/usr/src/app/store
    restart: unless-stopped

This worked for me, use or modify as needed for your setup

[HA_fanatic]

Another good thing to mention is this does work with serial/by-id as well which is how I pass my devices to containers. You just don’t get an option for that inside the container so you have to copy the mount point and paste it in.

[DeltaNu1142]

@petro

8. Watch the device list and wait for the last node to be found.

Is this step taking an inordinately long time to complete for some people?

I migrated from OpenZWave (Beta) to ZwaveJS yesterday, but then realized I didn’t have any of the network tools that OZWAdmin gave me, so today I’m giving ZwaveJS2MQTT a try. My nodes are coming through at a really sluggish pace. I have not reinstalled the ZWaveJS integration yet as I’m still waiting for all of the node info to appear. Several are in status Complete, but many of the remainder are in either NodeInfo or ProtocolInfo. It’s been chugging along for an hour or so now. The battery-powered motion sensors appeared after I woke them up, and the remainder are hardwired switches.

[petro]

What’s in the logs? Not HA logs, the Addon Logs.

[DeltaNu1142]

@petro

What’s in the logs?

Good question. I just did a reboot at around 9:55am:

2021-02-12 09:48:56.924 INFO ZWAVE: Node 24: metadata updated: 112-0-33
2021-02-12 09:48:56.926 INFO ZWAVE: Node 24: metadata updated: 112-0-34
2021-02-12 09:48:56.929 INFO ZWAVE: Node 24: metadata updated: 112-0-40
2021-02-12 09:48:56.932 INFO ZWAVE: Node 24: metadata updated: 112-0-31-1
2021-02-12 09:48:56.935 INFO ZWAVE: Node 24: metadata updated: 112-0-31-2
2021-02-12 09:48:56.938 INFO ZWAVE: Node 24: metadata updated: 112-0-31-4
2021-02-12 09:48:56.940 INFO ZWAVE: Node 24: metadata updated: 112-0-31-8
2021-02-12 09:48:57.377 INFO ZWAVE: Node 23: value updated: 112-0-1 1 => 1
2021-02-12 09:48:58.022 INFO ZWAVE: Node 24: value updated: 112-0-1 1 => 1
2021-02-12 09:55:53.842 INFO ZWAVE: Node 50: value updated: 50-0-value-65537 0.078 => 0.078
2021-02-12 09:55:53.847 INFO ZWAVE: Node 50: value updated: 50-0-deltaTime-65537 0 => 0
2021-02-12 09:55:53.927 INFO ZWAVE: Node 50: value updated: 50-0-value-66049 0 => 0
2021-02-12 09:55:53.931 INFO ZWAVE: Node 50: value updated: 50-0-deltaTime-66049 0 => 0
2021-02-12 09:56:50.702 INFO ZWAVE: Node 52: value updated: 50-0-value-65537 0.245 => 0.254
2021-02-12 09:56:50.714 INFO ZWAVE: Node 52: value updated: 50-0-previousValue-65537 0.237 => 0.245
2021-02-12 09:56:50.718 INFO ZWAVE: Node 52: value updated: 50-0-deltaTime-65537 1587 => 2013
2021-02-12 09:56:50.791 INFO ZWAVE: Node 52: value updated: 50-0-value-66049 17.2 => 17
2021-02-12 09:56:50.796 INFO ZWAVE: Node 52: value updated: 50-0-deltaTime-66049 0 => 0
2021-02-12 09:57:03.023 INFO ZWAVE-SERVER: Client disconnected

Disconnected, huh…? That’s strange.

EDIT: more logs starting at the last entry above:

2021-02-12 09:58:13.728 INFO ZWAVE: Node 40: value updated: 50-0-value-65537 10.843 => 10.901
2021-02-12 09:58:13.735 INFO ZWAVE: Node 40: value updated: 50-0-previousValue-65537 10.802 => 10.843
2021-02-12 09:58:13.739 INFO ZWAVE: Node 40: value updated: 50-0-deltaTime-65537 607 => 855
2021-02-12 09:59:21.835 INFO APP: GET / 200 59.233 ms - 1875
2021-02-12 09:59:22.017 INFO APP: GET /static/css/app.fdb61245954270e06feb.css 200 45.112 ms - 640650
2021-02-12 09:59:22.097 INFO APP: GET /static/js/app.30b0f469d1365694e17a.js 200 15.812 ms - 1686076
2021-02-12 09:59:23.060 INFO APP: GET /static/logo.png 200 8.634 ms - 10014
2021-02-12 09:59:23.183 INFO APP: GET /static/fonts/MaterialIcons-Regular.fa3334f.woff2 200 10.920 ms - 82492
2021-02-12 10:00:13.273 INFO ZWAVE: Node 23: value updated: 112-0-33 960049460 => 960049460
2021-02-12 10:00:15.172 INFO ZWAVE: Node 24: value updated: 112-0-33 960049460 => 960049460
2021-02-12 10:00:15.802 INFO ZWAVE: Node 23: value updated: 112-0-34 808464697 => 808464697
2021-02-12 10:00:16.442 INFO ZWAVE: Node 24: value updated: 112-0-34 808464697 => 808464697
2021-02-12 10:00:17.059 INFO ZWAVE: Node 23: value updated: 112-0-31-1 1 => 1
2021-02-12 10:00:17.064 INFO ZWAVE: Node 23: value updated: 112-0-31-2 0 => 0
2021-02-12 10:00:17.069 INFO ZWAVE: Node 23: value updated: 112-0-31-4 1 => 1
2021-02-12 10:00:17.074 INFO ZWAVE: Node 23: value updated: 112-0-31-8 0 => 0
2021-02-12 10:00:17.795 INFO ZWAVE: Node 24: value updated: 112-0-31-1 1 => 1
2021-02-12 10:00:17.801 INFO ZWAVE: Node 24: value updated: 112-0-31-2 0 => 0
2021-02-12 10:00:17.806 INFO ZWAVE: Node 24: value updated: 112-0-31-4 1 => 1
2021-02-12 10:00:17.810 INFO ZWAVE: Node 24: value updated: 112-0-31-8 0 => 0
2021-02-12 10:00:20.435 INFO ZWAVE: Node 23: interview completed, all values are updated
2021-02-12 10:00:40.497 INFO ZWAVE: Node 37 is asleep
2021-02-12 10:00:40.622 INFO ZWAVE: Node 37: value added 37-32-0-currentValue => undefined
2021-02-12 10:00:40.627 INFO ZWAVE: Node 37: value added 37-32-0-targetValue => undefined
2021-02-12 10:00:40.630 INFO ZWAVE: Node 37: value added 37-48-0-Any => false
2021-02-12 10:00:40.633 INFO ZWAVE: Node 37: value added 37-112-0-99 => 0
2021-02-12 10:00:40.636 INFO ZWAVE: Node 37: value added 37-113-0-alarmType => undefined
2021-02-12 10:00:40.639 INFO ZWAVE: Node 37: value added 37-113-0-alarmLevel => undefined
2021-02-12 10:00:40.642 INFO ZWAVE: Node 37: value added 37-113-0-Home Security-Cover status => 3
2021-02-12 10:00:40.645 INFO ZWAVE: Node 37: value added 37-114-0-manufacturerId => 330
2021-02-12 10:00:40.647 INFO ZWAVE: Node 37: value added 37-114-0-productType => 1
2021-02-12 10:00:40.650 INFO ZWAVE: Node 37: value added 37-114-0-productId => 1
2021-02-12 10:00:40.653 INFO ZWAVE: Node 37: value added 37-128-0-level => 80
2021-02-12 10:00:40.656 INFO ZWAVE: Node 37: value added 37-128-0-isLow => false
2021-02-12 10:00:40.659 INFO ZWAVE: Node 37: value added 37-132-0-wakeUpInterval => 14400
2021-02-12 10:00:40.661 INFO ZWAVE: Node 37: value added 37-132-0-controllerNodeId => 1
2021-02-12 10:00:40.664 INFO ZWAVE: Node 37: value added 37-134-0-libraryType => 6
2021-02-12 10:00:40.666 INFO ZWAVE: Node 37: value added 37-134-0-protocolVersion => 3.40
2021-02-12 10:00:40.669 INFO ZWAVE: Node 37: value added 37-134-0-firmwareVersions => 2.0
2021-02-12 10:00:40.673 INFO ZWAVE: Node 37 ready: Ecolink - PIRZWAVE1 (Z-Wave PIR Motion Sensor)
2021-02-12 10:00:40.805 INFO ZWAVE: Node 24: interview completed, all values are updated
2021-02-12 10:01:08.994 INFO ZWAVE: Node 25 is asleep
2021-02-12 10:01:09.028 INFO ZWAVE: Node 25: value added 25-48-0-Any => false
2021-02-12 10:01:09.041 INFO ZWAVE: Node 25: value added 25-112-0-1 => 255
2021-02-12 10:01:09.044 INFO ZWAVE: Node 25: value added 25-112-0-2 => 0
2021-02-12 10:01:09.047 INFO ZWAVE: Node 25: value added 25-113-0-alarmType => undefined
2021-02-12 10:01:09.050 INFO ZWAVE: Node 25: value added 25-113-0-alarmLevel => undefined
2021-02-12 10:01:09.053 INFO ZWAVE: Node 25: value added 25-113-0-Home Security-Cover status => 0
2021-02-12 10:01:09.056 INFO ZWAVE: Node 25: value added 25-113-0-Home Security-Motion sensor status => 0
2021-02-12 10:01:09.059 INFO ZWAVE: Node 25: value added 25-113-0-Power Management-Battery maintenance status => 0
2021-02-12 10:01:09.062 INFO ZWAVE: Node 25: value added 25-114-0-manufacturerId => 330
2021-02-12 10:01:09.065 INFO ZWAVE: Node 25: value added 25-114-0-productType => 4
2021-02-12 10:01:09.068 INFO ZWAVE: Node 25: value added 25-114-0-productId => 1
2021-02-12 10:01:09.070 INFO ZWAVE: Node 25: value added 25-128-0-level => 80
2021-02-12 10:01:09.073 INFO ZWAVE: Node 25: value added 25-128-0-isLow => false
2021-02-12 10:01:09.075 INFO ZWAVE: Node 25: value added 25-132-0-wakeUpInterval => 14400
2021-02-12 10:01:09.078 INFO ZWAVE: Node 25: value added 25-132-0-controllerNodeId => 1
2021-02-12 10:01:09.081 INFO ZWAVE: Node 25: value added 25-134-0-libraryType => 6
2021-02-12 10:01:09.083 INFO ZWAVE: Node 25: value added 25-134-0-protocolVersion => 4.5
2021-02-12 10:01:09.086 INFO ZWAVE: Node 25: value added 25-134-0-firmwareVersions => 10.1
2021-02-12 10:01:09.088 INFO ZWAVE: Node 25: value added 25-134-0-hardwareVersion => undefined
2021-02-12 10:01:09.092 INFO ZWAVE: Node 25 ready: Ecolink - PIR Motion Sensor v2.5 (Z-Wave Motion Sensor)

[petro]

did you do a reboot or a restart of HA? Because according to your logs, a reboot did not happen anytime between 9:48 and 9:57.

reboot = rebooting the device.
restart = restarting home assistant or the software.

[DeltaNu1142]

Oops, you’re right. I restarted HA. I did a reboot of the host device this morning, but not since starting to add node names in the add-in…

[petro]

Well looking at your logs, it’s still doing it’s work.

[DeltaNu1142]

It looks that way.

This one bugs me a bit: node 52 previously had a manufacturer and product identified, which is why I named it. It’s an Inovelli Red Series switch which supports beaming, but it’s now showing that it doesn’t, and the mfr info is now gone.

I suppose I’ll just try to re-interview it when all of this node polling is done.

[petro]

Did you switch from ZwaveJS to ZwaveJS2MQTT? If so, just be patient, when it’s complete restart the addon, not home assistant.