Do all the rest of your Z-Wave inclusions under Z-WaveJS. It is to my experience smoother/better at excluding/including devices than ZipGateway.
Especially important if devices are used/came from another mesh - exclude each device before you include it, to ensure it's Z-Wave tables have been cleared
Things like locks, garage door openers ("barrier devices") must be included with security, if you are offered a choice always pick S2 rather than S0.
Lastly: IMPORTANT!! Stop after each inclusion to verify you have a functional device, shows up in Z-Wave Details page normally, and you can go to the Device page for it and it functions and reports status/state correctly.
-- If it doesn't join properly do the Refresh Removal right then and there.
Do all lights/mains powered Z-Wave devices before you include your locks. Work out from the hub as you go, joining farthest devices last.
I wasn't aware of this. So it restores everything except the radio data? Isn't the radio data interconnected/intimate with the rest of the system?
I didn't see any warning messages in the system area either such as Warning ..."this only backs up part of your system so basically you are stuffed if your problem is in the part we didn't choose to backup, Good luck."...
Yeah, I think it was the Schlage lock that hosed it all up the first time. Now that I have that resolved, everything else including the Ring sensor added perfectly. Gonna wait a few days or forever before adding the lock. Thanks again everyone!
In the future, any time you have a failed pairing, STOP! Check your z-wave details for a ghost, remove, reboot and try again. Schlage locks should be paired as close as possible to the hub do to the whisper encryption.
Yes agreed if you happen to scour the web page to see this. I any event I have the cloud subscription anyway as I find it a reasonable fee for all you get. So I am covered.
It's a pretty big pill to swallow if you only had local backups and you had to exclude/add some 50+ devices. Then finding a buried footnote noting "radio data not included", could trigger full cardiac arrest for someone who thought they were doing all the right things.
I would recommend modifying the warning in the backup tab within settings.
..."Restoring a backup does not change platform version. Use Diagnostics Tool to switch to a different platform version. Also local backups do not store radio data, subscribe to cloud services for a full system backup."...
This really needs to be bolded in red with a bright yellow background at the top of the documentation for adding devices (or at least at the top of the section for Zwave inclusion). The number of posts where people have had issues after having gone on past the first failed inclusion indicates that this would be better served as a pre-warning than rather than something to be found out through trial and error after you already have several ghosts.
Not everyone even reads the documentation. But, that is on them. I am the weirdo that reads all manuals before I start. But then, I work in an industry where you follow directions step by step or you could be fired, or worse - so habit. If it is in the documentation as a prominent warning, then maybe it helps prevent at least a few people some heartache.
There's nothing at all weird about sitting in your new car on the driveway for several hours going through the owners handbook while pressing buttons is there? Asking for a friend
I was on JS from its initial release until a month or so ago, when some device-level reporting issues started that were showstoppers for me (going back to legacy/ZIP resolved those).
Other folks are still happily running JS, so the device-level issues are going to depend on your mix of devices & those device configurations. You can always go back to ZIP, so it's worth a shot.
At some point over the holiday weekend here, I think I'm going to try JS again to see how it is now... Although I haven't seen any pointed evidence that the reporting issues have been fixed, perhaps updates since then have improved things. If I need to come back to ZIP again and continue waiting, then so be it.
