I don't really understand why and how Z-Wave JS is important. I have a C7 with 40 devices and rules that haven't changed in 2 years. I don't use any external/cloud services like Alexa. Everything works with no problems. What would Z-Wave JS do for me?
yea i'm curious if there's any benefits currently.
C7 doesn't support it, so it is a moot point for you.
There are various benefits to those that can run it in terms of speed, backup reliability, long term code support (legacy/ZIP is end of life and is not actively being developed or improved by SiLabs), pairing/removal logic improvements, Zwave LR support in Europe frequencies, etc.
That said, though, if everything is fine with your system using the legacy/ZIP stack, then it is perfectly OK to leave it as-is (even if you are on a C8 Pro).
Does that mean at some point those of us without a C8 pro will have some problems?
We already have some problems, like hard-to-remove ghosts (from failed pairings) and not being able to avoid pairing devices as S0 security. Z-WaveJS does fix these.
However, the legacy/ZIP stack should continue to function as-is.
With existing devices and existing features? Probably not.
With newest devices or new features? Probably or maybe.
There is no reason to think that it won't keep working as is for the existing set of devices though.
I did not kept zwavejs because doing so on my C8-Pro broke a bunch of devices and I did not want to spend several hours figuring out why or if there was a fix. Hopefully that will be considered serious enough to add a fix into the change to js and reboot process.
Have you posted what the issues are that you encountered? Because I'm not finding it easily in your post/comment history.
Please describe.
If you have battery powered devices, you're going to have to wait until they wake up and get re-interviewed in order for them to work again with Z-Wave JS (really applicable to all devices, but the mains-powered ones should be awake and listening for it all the time, anyway, and non-secure devices might still work without this but S2 devices will definitely need it). Without more information about what problems you were actually experiencing, I cannot say for sure if that was your problem, but it's a common cause of "problems" immediately after switching that will be resolved on their own or with manual wake-ups if you want it to go faster. There isn't anything that can be done to fix this, as it's just how it works, but it is mentioned in the notes on switching.
This describes what happened more.
From the manual for the Zen37:
Click the lower left button 6 times as quickly as possible to wake the device up.
After this, it should complete the re-interview and function normally.
The solution is directly below your post in that thread. As @bcopeland indicated, you need to reinterview those devices. Here's a slightly more detailed description of how to do the reinterview.
Also, be sure to wake up the ZEN37 scene controllers before re-interviewing them, as indicated by @bertabcd1234 in the post directly above yours. As he also mentions, the need to wake battery-powered devices up is indicated in the ZWJS migration documentation.
Got ninja'ed by @bcopeland. But he describes the wake up procedure for the ZEN37.
The key thing to note is that you do NOT have to exclude and re-include any devices.
The device should automatically re-interview immediately after the wakeup, since it hasn't been interviewed by ZWaveJS yet.
Yup.
But his Leviton switches will need to be reinterviewed - if they show up as S2 unauthenticated.
I have it running on three C-8's and one C-7 with no more issues than I had with zip gateway... So I'm sticking with JS on all my hubs until something breaks... But I was not one of those that had memory issues, so JS was an easier option...
There are manual endpoints to switch your hub, but I haven't seen them posted outside of the beta and not sure if that is a no no.
I thought JS was only on C8 Pro???
Officially, yes.
Beta testers were able to test on other hubs.
With the official release, C8 Pro is the only supported hub.