You are responding to a part of my post, now it is out of context.
The assumption is if it will be the successor, not if it is there. (Which I obviously know).
+1 same here
As a user of Z-Wave for much to long and thought so many technologies; this week I encountered a polling issue with the ‘OpenZwave (Beta)’. My troubleshooting resulted in finding the z-WaveJS2MQTT project.
I run a PI3 with a docker container and a Aeontek Z-Stick. I updated my docker-compose to disable the openzwave container and load the new container.
On startup the application discovered and queried all the devices with no issues. A little more configuration as my MQTT was online again with HASS discovery
Next looking at polling I was disappointed to see it was not available. As I set to open an issue on GitHub i found I was late to the party and could see commits were being done to resolve the problem.
24 hours later pulled the latest dev container and polling is added to the UX and more importantly working perfectly
Finally I realized my TRV was exposing a sensor in a manner that I felt was a bug. Opened the issue and within a few hours learned about a customs devices configuration and with a sample that was shared reloaded the container after flushing my MQTT and smiled.
This has been the smoothest zWaze install I have ever experienced and it’s still very early code. In the last 24 hour I have also included about 12 new nodes to the network with no issues and extremely fast
The mesh view is cute but there is a feature request for a better experience
I am not using yet the home assistant integration or the web socket - that will come in a weeks time for me.
I want to applaud the devs on this implementation and am delighted to finally see the end of ‘open wave’ dependency
2 Likes
Polling is working for me in the Dev builds released since yesterday (Friday)
2 Likes
It’s just a container. I have a dedicated PI3 in the middle of the house with rasbian, docker, aeontech z-stick and this new container
Is there a guide somewhere for users rather new to Linux on how to set it up as I plan to do exactly the same? My problem is that the docs for the zwave-js-server (understandably) assume that the user is fluent in setting up a Linux distro, setting up and running docker, configuring network, etc.
My general idea was testing with a setup like this on a RasPi3b and later integrating it to HA using the new integration.
I don’t have a guide as such but
- Download Latest raspbain OS from raspberry pi - I don’t use the desktop version
- Installed docker using the official guide (arm64). https://docs.docker.com/engine/install/debian/
- Insert the z-Stick and used ‘dmesg’ to see the is report what port it assigned (I am using Z-Stick and it’s found on ‘ /dev/ttyACM0’
- Follow the zwavejs2mqtt readme to install the container
Done!
1 Like
I figured it would be but I was just surprised (especially after the last non-starter attempt) that there seemed to be a (possibly) premature announcement to deprecate the old integration.
It just makes people nervous…but it seems to be kind of another messaging snafu.
thanks for the link.
Honestly I think the new zwave-js integration is going to be the way to go. I started with the old zwave 1.4 integration, moved to ozw 1.6, and then when the beta came out, I moved over to zwave-js. I never really liked the openzwave integrations due to varying issues here and there but I’ve had very few with so far with the zwave-js integration. I’m thinking this is going to be the most stable and best integration there’s been for zwave. I know it’s hard to believe that with the change in direction. Plans change due to unforseen circumstances all the time and I’m glad they did as it really shows so far how much better it will be.
1 Like
Would you already switch over? I only have lights, dimmers, motions sensors. In total these are around 70 devices.
I cannot develop. But with joining the alpha I could give valuable feedback. But don’t want to kill the acceptance factor in my house. Even though I use OZW. It’s now stable-ish.
I hate to say it but I can’t make that call for you. If it’s stable, I would consider waiting to see if there is a migration path. For me, OZW was giving me so much trouble that I spent as much time switching as I did restarting the add-on multiple times a day. It was worth it to try something else. I warned my wife beforehand so WAF wasn’t an issue. Keep in mind, there are bound to be some bugs since it’s still early.
1 Like
I like the sound of that.
I have no major issues with 1.4 and never jumped on the 1.6 beta. I generally have no problem running beta software but with Z-Wave am looking for something more feature complete before I make the switch. For now I’m content to slap together config files for 1.4 if I buy a new release device.
2 Likes
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. So0x8D,0x02,0x03,0x03,0xD6,0xF9,0x6F,0xC0,0x0D,0x91,0xC1,0xD3,0x13,0x5B,0x04,0x9Cbecomes8D020303D6F96FC00D91C1D3135B049C
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
8 Likes
Assuming you are not running supervised version - this always started getting confusing due to the various flavors. I currently run python venv and it’s just becoming harder and harder to implement these various addons.
If I were you I would just install docker and go from there.
You don’t even need to move your HA to docker (But I definitely would 
) but having docker even without a supervised install makes running the extra things so much easier.
I’m running the zwavejs2mqtt in a container with no issues and no add-on required.
I imagine at some point in time someone will create a guide if you don’t want to run docker. For now it seems there are some steps to get started:
https://zwave-js.github.io/zwavejs2mqtt/#/getting-started/quick-start?id=nodejs-or-pkg-version
I loaded up the 1.0.0 of zwavejs2mqtt and it didn’t detect my kwikset lock correctly, nor did it detect my ZEN30 at all. Seems like it needs to import more configurations from OZW, which detects everything I use just fine.
**EDIT
Just noticed there was already a github isuse for the ZEN30 and it’s being addressed. Not sure why the kwikset lock isn’t registering properly, though
My kwikset 910’s needed to be re-paired after I moved to the nodejs server add-on. All is well since then.
But I really came here to say holy crap the nodejs server is soooooooooooo much more responsive compared to the old baked in OZW integration. I was in the process of pulling out all my zwave stuff due to how shitty my network performs, but gave this new add-on and integration a shot for the hell of it. I used to see at least a half second delay between a motion trigger and the lights turning on, but it is just as fast as my wifi stuff now. Amazing job, guys.
2 Likes
i think the team will need a device dump to help out
I have two nucs running docker swarm with shared (synchronised?) storage using gluster.
I run HassOS in a VM via KVM on one of the two nucs. But I run third party add-ons such as this outside of the VM in docker. That way a restart of HassOS doesn’t impact zwave or ZigBee.