Most of my devices lost S2 Authenticated status in Z-Wave Details after upgrade to 2.2.9.129. Is this a bug in display or do I have to exclude and re-include about 30 devices to get them back to S2 Auth?
Devices still seem to have props which suggest that they are still on S2:
zwaveSecurePairingComplete: true
S2: 3
I have four Ring contact sensors G2 that were paired as S2. This was the only way to pair these Ring devices. Since the update to 2.2.9.129, they are shown on the Z-wave details page as paired without security.
They all work so it is not a problem. I am going to leave them alone. Just seems interesting.
I didn't look far, but found that at least one of my devices is showing correctly:
Obviously if there are more, and not showing...
I looked at all my Device Info pages and I do see 2 devices that have SecurePairing as TRUE but not displaying correctly.
Which makes it even more confusing... one is correct, 2 are not.
You certainly don't have to do that. Does hitting refresh button on the Z-Wave Details page for the device, fixes the S2 flag?
Does nothing for me. 
AND
The community tool ZWave Mesh Details gets the same result.
That worked for me on the Ring contact sensors.....hitting refresh corrects the Z-wave details page.
Ok, after going though each device info page AND TAKING NOTES, I found that the ones that were mis-displayed were S0 and the refresh did fix that.
I really have 5 joined as S0 and only 1 joined as S2 Auth. 
Hitting Refresh (multiple times) didn't help. Hub shutdown-unplug-wait-plug-back (multiple times) didn't help. 
Ok.. Who still is have issues with this? .. After reboot and refresh button on nodes? ..
And is it affecting the actual function of the devices, or is it cosmetic?
And how many devices are affected?
My devices finally got refreshed. I guess I have some noise/unexpected traffic/other interference on my z-wave network. I waited overnight and was able to get all my mains-powered devices back on S2 Auth. With shutdown-power-cycle and then Refresh. In fact it went very smooth after overnight wait.
I noticed this after the ZWave SDK update as well. After the devices refreshed it eventually came back with the proper info.
yes just updated to 2.2.9.130
all but one ring extender did not show s2.
fx does not seem to be affected.
refresh fixed all but one which is a homseer battery device.. which is probably why it didnt fix it.
i have 11 s2 devices as far as i can tell by going through each driver and looking.. only one was correct..
I largely had the same experience, though I only noticed after the most recent upgrade to 2.2.9.146, with all but two of my devices showing no security. For me the devices all still worked. Manually refreshing each device fixed it for all but 3 (out of ~40 devices). After waiting a couple days, one GE and one Zooz switch I had to remove and repair to get security back. One of my Zooz outdoor motion sensors I'll need to repair as well. I'm guessing this is because it's battery operated.
For me, it is concerning that my Schlage door lock is showing Security "None" in the Z-wave settings. However, in the actual device it is showing S2=4, but I am not sure what that means.
Don't think 4 is a valid value. IIRC it should be one of:
131 → S2 Authenticated
129 → S2 Unauthenticated
128 → S0
Wonder what the result would be if you could requery the data from the device...
0=no security
1=S2 unauth
2=S2 auth
(3=S2 unauth + auth)
4=S2 access control
128 = S0
It is really S2=3 that there shouldn't be one of. Unless @bcopeland is doing voodoo again (or something else like reporting bit #, 1 referenced, instead of the bitmask value in decimal). I was wrong again, see 2 posts below.
I.imagine its.incorrect b?cause if the device was joined with s2 and thinks it has it and the hub.is.not using it I.imagine things wouldn't work?
S2 =3 is authenticated and unauthenticated grants
Curses. Multiple bits gets me again. 
Download the Hubitat app
