The Future of Z-Wave in HA - QT-OpenZWave

blhoward2 · January 22, 2021, 1:47am

Edit: wrong

FreelancerJ · January 22, 2021, 2:04am

Just gave a shot at exclusion, but using the external switch doesn’t seem to trigger it, whether I triple press quickly or slowly. Rechecked the guide and it definitely doesn’t specify if there is a time limit like there is for inclusion.
I’m thinking maybe it only works on standard toggle switches. Mine are Momentary press…
So I’ll get properly into it tonight or tomorrow.

Would it be helpful at all to raise an issue running rc.0? Or definitely build off the master?

And while I’m thinking about it, what logs and levels should I set running to be useful, but not overloading of data? I take it ZWave-JS but should I also get ZWave-JS2MQTT as well?
_{I do enjoy that one of the log levels is called silly…}

blhoward2 · January 22, 2021, 2:19am

Silly or debug is best. Logging has been improved so you should get both to file in the store folder.

FreelancerJ · January 22, 2021, 2:23am

Damn right silly is best! I mean… ahem.

One last q, just glanced through the docker page, were you directing me to “Custom Builds” or " Building a container using Dockerfile.contrib"?

Edit: Oh and would it be under Node or MQTT?

blhoward2 · January 22, 2021, 2:29am

Don’t worry about it, I was looking at the old project. You can just pull the dev image.

FreelancerJ · January 22, 2021, 2:33am

And should I submit an issue under node-wave-js or zwavejs2mqtt?

blhoward2 · January 22, 2021, 3:08am

I’d guess the node level. Both maintainers are active in both projects so it’ll get figured out.

FreelancerJ · January 22, 2021, 4:50am

Ok, gave it a shot.
Seems there is fallback behaviour now. When I start Secure Inclusion, it fails and just includes as insecure. I’ve posted a bug describing what originally happened, and the new behaviour, with logs.

JumpMaster · January 31, 2021, 9:46am

I bit the bullet this weekend and moved over to zwavejs using HA beta 2021.2.0b1. Gotta say it’s working well and the web interface is awesome. It gives me a really good insight into the zwave network that I’ve been missing with all previous ZWave integrations.

I used docker-compose to deploy zwavejs2mqtt. You can use it without mqtt for Home-Assistant

Backup your existing config! Take a snapshot. I highly recommend using “Home Assistant Google Drive Backup” to name snapshots by date/time and upload them to Google.
Go to integrations and remove the existing Z-Wave integration.
If you have an existing Z-Wave docker container make sure it’s stopped.
Deploy ZWaveJS2MQTT. I used the following docker compose file. Replace the device config with the path to your own ZWave stick.

version: '3'
services:
  zwavejs2mqtt:
    image: zwavejs/zwavejs2mqtt:latest
    container_name: "zwavejs2mqtt"
    security_opt:
      - seccomp:unconfined
    devices:
      - "/dev/serial/by-id/usb-0658_0200-if00:/dev/ttyACM0"
    ports:
      - 8091:8091
      - 3000:3000
    volumes:
      - /srv/zwavejs/store:/usr/src/app/store
    restart: unless-stopped

Start the new container.

docker-compose -p zwavejs2mqtt -f zwavejs2mqtt.yml up -d

From a browser visit http://youDockerHost:8091
a. Go to settings and select your ZWave stick from the “Serial Port” drop down.
b. If you have an OZW_NETWORK_KEY configured you will need to paste it into the “Network Key” box. Remove all commas and 0x. So 0x8D,0x02,0x03,0x03,0xD6,0xF9,0x6F,0xC0,0x0D,0x91,0xC1,0xD3,0x13,0x5B,0x04,0x9C becomes 8D020303D6F96FC00D91C1D3135B049C
c. Enable “WS Server”. This runs on port 3000 and is how Home Assistant will connect to the container.
d. “Disable Gateway”. We only need the WS Server.
Lastly go back to Home Assistant and add the ZWaveJS plugin from the integrations screen. Make sure to untick “Deploy ZWaveJS Server” which will allow you to enter the IP:Port of your container http://youDockerHost:3000
Spend the next hour renaming your devices and figuring which of your many dimmers is upstairs/downstairs/living room/dining room

Madj42 · January 31, 2021, 4:18pm

Retracted.

bedo2405 · February 1, 2021, 11:03am

Why would the zwave JS add-on be unavailable on my system? “This add-on is not available on your system”. I’m running the full home assistant os on proxmox.

gcoupe · February 1, 2021, 11:16am

Because it’s currently only available to load on beta versions of the OS. I believe it will be released to the stable OS stream soon, and become available to add then.

finity · February 1, 2021, 7:31pm

Would you mind posting this in the other zwavejs dedicated thread, too? that way we keep everything zwavejs related in one spot. Thanks!

Also to point out that the integration (not only the add-on) is also only available in the dev version of HA right now and isn’t generally available yet either.

JumpMaster · February 1, 2021, 7:55pm

Both ways are fully supported and either is recommended.

The Z-Wave JS 2 MQTT project also includes the Z-Wave JS Server (you can enable it in the settings) and they provide a Docker image.

Madj42 · February 1, 2021, 9:14pm

Yeah, I stand corrected. I didn’t see that when I looked at this when originally installing the beta. Thanks.

brendan · February 6, 2021, 1:14am

I use to really like OpenZWave, It’s a pity it is only maintained by one person and the negativity has hit him a bit. OZW 1.6 had such potential.
That said, I am looking forward to see how Z-Wave JS matures.

lifeisafractal · November 30, 2021, 5:40pm

I never got an answer. I ended up using the HA built in entity naming system which is pretty cumbersome when you have a large number of things to rename.

petro · November 30, 2021, 6:06pm

If you rename the device it passes the name to the entities.

Klugheim · October 9, 2024, 2:37pm

Are you able to change the wakeup intervall?

Guff666 · October 9, 2024, 5:20pm

Sorry, I can’t answer that. I gave up on the Horstmann thermostat some time ago. I replaced it with virtual thermostats in each room plus room temperature sensors and driving the enable line on the boiler via a Shelly switch.