Switching to z-wave js leaves six battery powered sensors, several different types, ages and brands, pending and non-functional. Switching back and they all work as expected. Will leaving them pending overnight allow them to drop back in? As suggested somewhere, shutting down the hub, pulling power made no difference. Refresh while activating them didn't help,
After switching to js.
Pre js for the same sensors.
z-wave device graph:
Tagging @bcopeland
Added z-wave device graph to first post.
I sporadically have this same issue with locks. Sometimes even though the locks say they are pending, they can be controlled from the device page. Other times, I have to pull/reseat the battery.
This doesn't happen with Z/IP.
I tried that with several and they did not respond. First clue was the garage tilt sensors that create a notification when a door opens or closes. This morning when one of the doors went up there was no notification it got me to wondering why. After fiddling for an hour or so I went back to legacy and all of those devices immediately returned to normal. They obviously work and it seems like they should continue to do so without jumping through a bunch of hoops.
That normally won't (nor would the shutdown), but what might is a wake up. The procedure for this varies by device but should be found in the manual for each. The alternative is waiting, perhaps a day or so, as most devices wake on their own once or twice a day by default. (If you are not familiar, "wake up" is is a specific Z-Wave term; it is not related to whether the device just sent something to the hub.)
How long ago did you move to Z-Wave JS, or if you've moved back, how long were you on it before doing that?
The "Pending" status alone isn't a problem, but the security "Unknown" thing is, as Z-Wave JS needs to re-interview each node, and this is one way to tell that the re-interview has not been completed. The device is unlikely to work before that. You'll see the same thing on any mains-powered devices that were offline when you moved, too (maybe because they were unplugged?), but they should just come back. Battery devices are just a bit trickier because of the sleep thing. Hopefully that's all it is for you! (Although, of course, if Legacy is working, that's a perfectly valid way to stay.)
All the mains devices had no issues. Just checked an the problem battery devices report at least twice a day. I'll switch it back to js late this afternoon and then check them in the morning. That should be sufficient time for all of them to wake and report.
I can't comment on other devices, but I have left Kwikset locks in the "pending" state for ~2 days, and they never leave that state. They stop being responsive to the hub after about 24 hours in the "pending" state.
Pulling/reseating the batteries fixes it immediately. Until it happens again after a few days.
Doesn't happen with any of my other FLiRS/LSS devices. And there's no specific lock that it happens with every time.
So these days, if I've leaving town, I leave the hub with Z/IP, and switch back to ZWaveJS upon my return. I have re-paired one lock to an HA Yellow, and I didn't see that happen for a week. But there are so many variables (number of devices, position/distance relative to the hub) that it is not possible to conclude that ZWaveJS works differently on the HA Yellow v/s Hubitat.
That's interesting! Have you tried forcing a re-interview (easy enough but might not help...) or doing an exclusion and re-inclusion on the device? I'd be curious if it's something related to the migration or just something weird with this particular model of device and ZWJS on Hubitat.
I did have a couple FLiRS devices that never re-interviewed after I migrated (blinds, not locks) and can't remember everything I tried aside from the fact that a re-inclusion eventually seemed easier in some sense than additional time or troubleshooting, so that is what I did. 
(Also something I learned, apparently forgot, and then re-learned: if you're thinking about it, make it easier on yourself and don't use Z-Wave Replace on Z-Wave JS yet -- but regular hub "replace" or swap is fine.) Guessing you've already considered or tried some of this, but it might be worth seeing if it's something just related to the Z-Wave move.
Same might help the OP if time and a manual wake or re-interview doesn't help, even though you shouldn't need to...
Yes. Didn't help.
Yes, I did this with a Kwikset HomeConnect 620 deadbolt. Didn't change anything.
I also paired a brand-new Kwikset Smartcode 912 leverlock using ZWaveJS. The issue continues.
Perplexingly, for at least the last 3 months, I have not observed this with any other FLiRS/RSS device.
I should also add - I see this issue with both the Kwikset HomeConnect 620 deadbolt, of which I have 5, and the Kwikset SmartConnect 912 leverlock, of which I have 2.
Update: Waiting overnight allowed all of the battery devices to check in on their normal schedule. They have all now reconnected and seem to be solid on js.
Download the Hubitat app
