I have 2 identical Weiser Z-Wave+ locks. They both say S2 -128 in the device info.
But one doesn't have 0x5E in the clusters and they both say S0 in the Z-Wave Details page.
I can try to re-pair the Back door lock to see if the 0x5E shows up but why the S0?
Unless it's Z-Wave Plus, it can't support S2. I suggest you exclude, reset the lock, include again. Perhaps it's not Z-Wave Plus. Does it have the Z-Wave Plus logo on it?
May have something to do with how you are pairing, or perhaps the lock doesn't support S2. Note that the Front Door Lock, which shows as Z-Wave Plus, is paired as S0. What security box comes up when you are pairing?
Edit: I just looked at the Z-Wave Conformance Statements for all of the Weiser locks (I don't know which one you have). None of them support S2. All are Z-Wave Plus Version 1.
I paired them 6 weeks ago so I don't remember, I know it came up with the security pairing options.
Ok, Ver 1 doesn't do S2 but it's confusing as the driver info says S2 - 128.
I'll repair the one lock and see if I get 0x5E at least as it should be there.
It is confusing, but "S2: 128" means S0, so that much isn't a problem.
I'd expect to see "0x5E" for any Z-Wave Plus device, but S0 is supported by both "classic" and Plus devices, so that alone is not necessarily a problem, either. What is odd is that if the first two locks in that table are indeed identical (and both Z-Wave Plus, as the first is), then why is the second not reporting the same command classes? You could try a re-pair to see if it changes anything, but if you aren't having any problems, I'm not sure I'd trouble myself with doing so, much as the oddities in the table would bother me...
Thanks for clearing up the S2 S0 confusion.
I'll re-associate the lock and see if it clears up, I don't like leaving oddities around as I'll forget next year and wonder what's going on
Well solved one strange issue. One of my 2 Z-wave plus locks isn't! I pulled the card and it's just Z-Wave.
Good thing I happened to have a spare Plus card in a box of parts so it's now reporting as expected.