Thanks for the real world examples. I have a couple of devices that occasionally don't respond to a command, but will on a second attempt. This alone might make it worth switching.
Most likely not. There is a lag between platform releases, and a given solid version getting into the product itself. And, there is existing inventory out there. So, you will most likely have to update to the latest platform software after you get the hub.
4 Likes
After switching to Z-waveJS, all of my SmartStart info is gone. Is there a way of getting it back?
It wont help now if it is gone, but you may want to load the app from this thread.
It will allow you to backup the data to a file on the hub. Then in cases like this you could simply restore the file.
1 Like
This is expected, but not communicated anywhere.
Switch back to ZIP, install my SmartStart Manager app (linked above) and then run the full backup option. Switch back to JS and then load the backup.
They will come in as disabled, and if you enable them they wont link up the nodes anymore but you at least have the info ready in case you need to pair anything again.
3 Likes
Is it my imagination, or is ZWJS faster than the legacy libraries?
I’m almost certain that the delay between a motion sensor triggering and lights turning on seems to be reduced…
1 Like
That's been my experience since moving to ZWaveJS. I did the "control experiment" of moving back to z/ip gateway for 5-6 days during the beta test period.
1 Like
Nice! Great work work Hubitat team! 
1 Like
@bcopeland the only outstanding issue I’m seeing since the ZWJS upgrade is with Aeotec Dual Nano switches (single nano and dimmers are fine).
Everything works, they operate digitally and manually without issue, however the status doesn’t update unless I go into the child device and hit refresh.
I’m using the HE driver:
1 Like
Thanks everyone for the info. I had 30 minutes of terror when ALL my Z-Wave devices disappeared from the settings sheet. A hard reboot and a prayer got them all back though. Yikes.
Everything is slowly coming back now and I've managed to find the SmartStart entries thanks to that handy app!
Now look here you two! Stop teasing us C-8 Lite owners with your musings of reduced latency. It's just not fair!
2 Likes
I have the same observation with aeotec dual nano child devices not updating their current state values until you manually go into the child device and click on refresh
2 Likes
Nice to have it confirmed that it isn’t something I’ve done. @bcopeland sounds like we’ve found a minor bug / compatibility issue.
1 Like
Incorrect. I am running ZwaveJS on a standard C8, however it is a memory hog. I reboot about every two to three days. It is definetly doable, but there are issues to be aware of.
Edit:
The Devics Hub (blue) is the one running Z-waveJS. Even on Z/ip this hub was always a bit behind the curve on Free memory.
2 Likes
You technically can enable ZWJS on C7 or C8 devices and you're welcome to run your hub however you wish - but during the beta (which you're a member of), I'm sure you saw the notes from HE staff to restirct the ZWJS library to C8P models, and they intentionally removed the "friendly buttons" to enable it on C7 and C8 hubs on the Zwave settings page. The endpoints remain to manually enable it, but I'm not sure if those have been (or will be) made public.
This does work on lightly loaded on a hub with little besides ZWave. But load Matter, HomeKit Integration, RM apps, and LAN apps, and your going to likely run into issues - as both the staff and other beta testers reported. My sense, is without additional tuning or memory optimizations, devices before the C8P running ZWJS may require "flipping back" to ZIP to help with debugging complex interactions. I'm sure the HE staff didn't really want to add the complexity that this restriction brings - so I would assume that this restriction, was based on testing they performed.
You're comfortable rebooting your production hub every few days, that's OK with me (not an approach I endorse, but YMMV). - FYI, I'll running ZWaveJS on my C7 dev/test system - But I'm not using that in Prod, per the HE staff recommednation.
As long as your willing to support the consequences, you can load whatever ZW gateway, user apps, or drivers that you want. - That's one of the main benefits of HE, IMHO - But saying "oh this works just fine", is definitely overstating & ignoring HE staff's specific guidance.
4 Likes
Has anyone observed the below error with aeotec dual nano device not being activated when using new JS zwave libraries?
Not exactly, but now that you mention it, I’m seeing this on my dual nano’s and Aeotec smart switches:
I've just reverted to legacy ZW, between the status updates on dual nano's and the community fibaro smart implant driver not working, I was just having too many issues that were annoying my wife, and therefore me. 
1 Like
I would make a new post in either Feedback or Get Help/Devices for driver/device issues on ZwaveJS. Devices - Hubitat
Both of those errors shown are indicative that the command class is missing some of the values. We caught a lot more of this during beta but obviously a few got missed.
3 Likes
That error is from an app, not a driver. Where does the Dual Nano fit into this? From just that, I suspect you're dealing with a different problem and one unrelated to Z-Wave, but knowing more about that app would be helpful to troubleshoot the actual problem.
(Likely guess: did you remove a device from your hub that was in use by what appears to be a Room Lighting instance without removing it from the app first?)
2 Likes
