How do I switch to Zwave JS?

[chris4 (christian)]

Solved - Wrong network key!

[petro]

@ChaoticUnreal

If HA is running in a docker would restarting the docker be enough to get it to release?

From what I recall that did not work for me. But you have to remember, I switched from Zwave 1.4 to Openzwave a year ago. I’m going off memory on how to properly remove zwave 1.4.

[CO_4X4 (Colorado Four Wheeler)]

@GrizzlyAK

Every one of my devices is zwave, so this component is pretty critical for me. Very frustrating.

My Z-Wave is pretty critical as well, but I’m not frustrated at all. I knew what I was getting into when I loaded up open source as my home automation and, for all the other cool stuff that I get from HA that I didn’t from my last solution, this isn’t too big of a deal for me.

Depreciating it doesn’t bother me, plenty of folks are up and running in JS and it’s working fine. I gave serious consideration to moving to it as well, since the things that are missing from JS aren’t mission critical for me and it’s apparently lightning fast (my single biggest gripe about the baked in Z-Wave). It came down to just not wanting to rename my devices if the migration does it for me and, if it doesn’t, then I’ll bite the bullet.

[ffm777 (Carlo)]

Thanks. Took me a bit of reading in another thread, but I found it. Should be the following docker image:
https://hub.docker.com/r/zwavejs/zwavejs2mqtt

Will try out over the weekend…

[declankenny (Declan)]

Yes, you can run the ZWave JS server on a separate machine. You will need to assign that machine a static/reserved IP address so that you can reference that address when you are configuring the ZWave JS integration in you HA instance.

[ChaoticUnreal]

Just to circle back for others.
Restarting the docker seems to have released the Zwave portion of my Zwave/Zigbee stick.

I have it running on the ZwaveJS docker now. That docker seems to have other issues on unraid (it won’t let me set the path for logs and files but that isn’t HA related) and it picked up my hardwired devices without issue which are the big ones. I’ll go poke at my other devices later it sees them but listing them as unknown right now but since they are sensors and mostly temp I can let them sit for now.

[petro]

Whatever information you find, please consider adding it as a comment to the guides linked in the solution

[scottjones4k (Scott Jones)]

I’ve got the zwavejs/zwavejs2mqtt docker image deployed to my k3s cluster, and its talking to my zwave stick just fine. I’ve not yet been round and woken everything yet, but its picked up my stick and my doorlock fine so I know its working. However, It is crashing and rebooting every 90s or so by the look of it. When I’m debugging it I’m seeing a handful of /health checks coming back as a 500, but I’m not able to get any more information on the matter. Does anyone have any hints as to what to look at for this? For reference, its running on an RPI3 with this yaml: https://github.com/zwave-js/zwavejs2mqtt/tree/master/docker#run-as-a-kubernetes-deployment

[IanC (Ian)]

Well I decided to jump in the deep end and upgrade from the Zwave 1.4 integration to ZwaveJS and, after a bunch of renaming entities I now am up and running and all seems well so thanks to the team. My only comments so far are:

1. I run a number of Qubino dimmer & relay devices and not all of their previous entities or similar are restored (like power management, energy, exporting & interval). Its no big deal for me as I never used those particular entities that under 1.4 were present. Just wondering if more may appear in time or after some future updates.

2. Following any restart of HA or a complete reboot of HA, I see the following entry in the logs:

Logger: zwave_js_server
Source: /usr/local/lib/python3.8/site-packages/zwave_js_server/client.py:95
First occurred: 14:04:30 (1 occurrences)
Last logged: 14:04:30

Connected to a Zwave JS Server with an untested version, you may run into compatibility issues!

My setup:

HA 2021.2.0
Supervisor 2021.01.7
Running HA in a ProxmoxVM on an Intel NUC

[AGW (Andrew)]

I don’t suppose you know the syntax for the web socket url that the integration asks for?

I have installed the zwavejs2mqtt add-on on an instance of HA on a spare raspberry pi and want to run the integration on my main HA instance (Debian on a Synology NAS) but cannot work out what to replace ‘ws://localhost:3000’ with on installation of the ZWaveJS integration on the main box. I figured it would be ws://192.168.x.y:3000 but no joy.

[declankenny (Declan)]

Is there a reason why you need to run a separate instance of HA on the PI?
I think it would be to just run the zwavejs2mqtt as a docker container on that machine.

Here is my docker-compose entry, you would need to change the network mode to host and expose ports 8091 (web interface) and 3000 (websocket)

  zwavejs2mqtt:
    container_name: zwavejs2mqtt
    image: zwavejs/zwavejs2mqtt:latest
    restart: ${RESTART_MODE}
    tty: true
    stop_signal: SIGINT
    devices:
      - '/dev/zwave:/dev/ttyACM0'
    volumes:
      - ${DOCKERDIR}/zwavejs2mqtt:/usr/src/app/store
    networks:
      macvlan:
        ipv4_address: 192.168.0.61

Once you have the zwavejs2mqtt server up and running you will need to go to the web interface http://192.168.x.y:8091 and in the settings page you can enable the webserver.

[arkoko (Arthur Kono)]

Nice! Moved (and renamed) all my 10 devices to the Zwave-JS addon + Zwave-JS integration. So far so good.
If I later decide to replace the Zwave-JS addon with ZwaveJS2MQTT (for the GUI), do I need to reconfigure all devices again, or will everything be fine without it?

[petro]

You will, but… there’s a way to transfer the cache file so you don’t have to. I’ll be investigating that later. You’ll need to have access to the container files though. So if you aren’t running docker or supervised, it’ll be a chore.

[arkoko (Arthur Kono)]

Docker and supervised.

docker exec -it addon_core_zwave_js bash
bash-5.1# ls -l /data/*

-rw-------    1 root     root           107 Feb  4 13:01 /data/options.json

/data/cache:
total 236
-rw-r--r--    1 root     root         44895 Feb  4 17:00 <homeid>.json
-rw-r--r--    1 root     root         66534 Feb  4 20:26 <homeid>.metadata.jsonl
-rw-r--r--    1 root     root        118852 Feb  4 20:41 <homeid>.values.jsonl

Is it this?

[petro]

I haven’t done it myself, i was planning on doing it this weekend. I believe it’s the homeid.json one.

[xman111 (Craig)]

I have the same LZW36 switch and it isn’t working after updating to the new zwave js. All i get is a few entities for power monitoring.

[GrizzlyAK]

@Soccs

i actualy then installed the community one because it give alot more fuctions and deleted the official one i love the graph there! ( on addon ons)

Are you talking about the zwavejs2mqtt version, instead of the brand new zwavejs? I saw a discussion on Github about why create the new version if the zwavejs2mqtt is already there and working. I wasn’t too hip on the mqtt part, but apparently you don’t need it, and it can be disabled.

Also, it seems like the new integration isn’t aiming to have a very robust UI control panel (compared to zwavejs2mqtt), and one recommendation was to use the control panel UI in zwavejs2mqtt to manage things in the zwavejs integration! So the question is becoming for me, which path to take?

I’m weary of choosing anything but the “official” version, if there is a possibility that the community version ends support and will just have to rebuild everything from scratch AGAIN. I’d much prefer to do this once, so the decision of which road to take is crucial to minimize work and disturbance. From what I’ve been able to glean, why wouldn’t they just work to integrate zwavejs2mqtt into the core, and make the mqtt more optional and separate (like they’re doing with the new integration)?

[Canedje]

Will there also a zwcfg.xml file with Zwave JS?
If not how to make the Remotec ZRC-90 usable in Zwave JS?

like:

Z-Wave Device Specific Settings

It also need a posibillity to check on: zwave.scene_activated
Will that be possible also in Zwave JS?

[Soccs]

yeah thats the path i took and its working great, other than one door sensor that is not awaking…

[GrizzlyAK]

@llevering

You will need to reconfigure anything and wait for the devices to send their discovery information to the zwave server again. Also the ‘profiles’ are different. In my case for a smoke detector it went from one sensor with different values that represented different states, to multiple binary sensors. So it is quite a bit of fiddling, however I do like the profile in zwavejs better, as it is much clearer (to me).

Am I correct in believing that since both the zwavejs and zwavejs2mqtt integrations use the zwavejs library (server), that the “profiles” and/or naming conventions used by both are the same?