Add me to the list of mildly worried 1.4 users (not ozw 1.4, whatever that is), but ones who have “transitioned”, or at least played with that before. I went through a mess playing with ozw when it was first released, renaming a bunch etc… gave up because my battery powered devices were not working until waking for their 5hr report. So things like door sensors did not work after a reboot until I removed them and hit a button, or up to 5hrs went by. AFAIK this was never resolved in OZW. No biggie as 1.4 was working fine, but I had to rename 4 times going back and forth testing (yeap… fun fun). I headed wise advice to hold off until it officially replaced 1.4 and there was a migration tool.
Now, I’m technically running “deprecated” software and looking to join in on the renaming excitement. Being an HA user, I suspect I’m not alone in that it’s not the end of the world to rename sans migration tool magic, as long as it is just once and it works well. That leaves me with what I feel are reasonable worries… will my battery devices will also stop working again? are any devices/features I have that are not yet supported? S2 sounds like it will be cool, but I’m not jumping in headfirst before everyone this time around lol.
zwavejs2mqtt addon → provides MQTT and/or zwave-js-server, with a nice management UI
zwave-js addon → provides zwave-js-server but no management UI
zwave-js integration talks to a zwave-js-server, take your pick which one
None of that makes sense to me, coming from zwave 1.4. Is zwavejs2mqtt yet ANOTHER zwave integration, like OZW beta 1.6 and now zwave-js? So we just ‘pick one’? It’s daunting enough to consider starting all over again ONCE, much less trying out three alternatives so we can ‘pick one’. I’m assuming that the new zwave-js is the recommended zwave integration going forward, or am I wrong? How many more different zwave integrations are there going to be in HA? I was just hoping for something that provided everything zwave 1.4 does, just updated for 1.6.
This is going to be a LONG, PAINFUL slog. It’s not just renaming, but retesting every automation, sensor, script… everything.
What would be nice is if someone could provide us with an idea of what things look like in zwave-js vs the original integration, like the differences in UI, managing devices/entities, setting parameters, will zwave-graph still work, and most importantly, how to effectively transition from one to the other without having to trial-and-error. I suppose some of that is coming, so I’ll be waiting for a while, again.
Agree, CO_4x4, I have to say that it feels extremely premature to be deprecating the only stable, completely operational version of zwave (1.4) before a fully operational replacement is in place. Looking at the zwave-js page there are quite a few pretty critical components still missing, such as polling and setting parameters via services (the latter which I currently use), that currently don’t work. Perhaps most people have already migrated to one of the other zwave forks. Every one of my devices is zwave, so this component is pretty critical for me. Very frustrating.
Hi all, I’m sure this is a stupid question, but I’ve researched and can’t find the answer…
I’ve installed Deconz on a separate Pi that runs in the middle of my house, means if I restart HA no issue with reconnecting, it’s so much better.
At the moment my Zwave controller is in my HASSIO pi, but it would be so much better with the new ZWAVEJS to move this across to my separate pi running deconz. It looks like this is possible, but I’ve tried to install (installed npm and then server etc) but everytime I run ts-node src/bin/server.ts /dev/tty0 it gives me an error, first it was typescript missing, but now it’s just saying the server.ts script isn’t installed.
Is there an idiots guide of how to install this on a separate pi as I just can’t get this working.
Gave the new Z-Wave JS Integration a spin around the block. Came from OZW and this new integration is extremely responsive and fast! Easily half the response time of OZW, and that one wasn’t slow either.
I am trying to figure out if there’s an event that I can build an automation around to trigger the start of homekit when the zwave network is ready. For OZW I used an mqtt event, but not sure how to do this with Z-Wave JS. Any guidance?
Since quite a few releases (6 months or more) that isn’t needed anymore. Previously one needed that to prevent HomeKit from starting before all entities loaded. Nowadays, Home Assistant restores all entities on start instantly. Hence, that problem is non-existing.
Awesome work! Very excited for the new ZWave JS integration. I’m a little confused how to get the Zwave JS server up and running though. I’m running HA in a Docker container so I’m going the container route. In the documentation ( Z-Wave JS - Home Assistant (home-assistant.io)) it says the if i’m not going the add-on route, I can install the Z-Wave JS 2 MQTT project as a Docker image which contains the Zwave JS server. So am I understanding it right I need to install that whole project just for the server part? I don’t have use for the rest I guess so I’m a little confused.
Anyone else having problem with zwave js where door sensors aren’t reporting? I’ve checked and they’re all just listed as “Node ##” and asleep. So the entities don’t generate.
I would love to know as well, the zwave changes surprised me today… and it seems none of my zwave devices are working. Even if I make the switch to zwave js, it doesn’t look like my garage door sensor would work.
Its quite simple!
Just stop the old zwave, dont delete anything just yet. install the zwave js addon, after you will be prompted to go into configuration and then integrations, and install the z-wave JS ( for me it was automatic, just need to activate). and then, go fro a coup of coofee or beer, and wait for like 5 minutes and voila!
Wish there was a migration for the device/entity names. Going to take some time to identity and name my 83 devices. Still better than repairing them all
Did anyone get a remote with buttons working? In the add-on log I see: 23:46:23.689 CNTRLR « [Node 005] received CentralScene notification { "nodeId": 5, "ccId": "Central Scene", "ccCommand": "0x03", "payload": "0xa20001" }
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).
i love the graph there! ( on addon ons)