To elaborate a bit on what I was seeing:
Something hosed up the both logging settings. Despite them being enabled on the screen, they were clearly not in effect.
After rebooting AND re-saving the preferences, logging resumed as normal/expected.
The best I could tell from what was making it to the lock (and by watching the Z-Wave logging fly by), things WERE getting to the lock as expected.
From what I'm seeing there are likely multiple issues:
-
Some bug in the LCM is throwing an NPE during an "add" in some conditions (possibly, when the State variable codeFetchComplete=0
-
A bug in the LCM that sometimes happens when you look at a user entry without doing anything and just click "Done" (this appears to be a "Cannot get property 'user' on null object on line 460 (codeManagement)".
-
Possibly, some issue with tracking/setting logging in the "Schlage BE468/BE469 Lock" driver.
-
Some general issues with Z-Wave traffic that particularly impacts locks, possibly related to S0/S2-Access encrypted devices. I suspect the ACKs are not being managed properly because I notice this most acutely when I issue a lock or unlock command--it seems that the device is not receptive to further commands until some period of time passes (which is behavior that seems to occur when a device is stuck waiting on an ACK that never come).
About #4, I have issues with ALL of my locks where it can take several attempts to get the locks to lock or unlock from the hub. These issues are significantly worse with the legacy ZW/S0 locks, but even the ZWP/S2 one has issues (now, I have 2 ZWP/S2 ones, as this new lock replaced one of my S0 ones, specifically due to issues I was having with events from the S0 locks).
When @bcopeland made his big z-wave "re-write", things did get a lot better. Even with the S0 locks. What I notice then, however, was that the FIRST lock/unlock I'd issue would almost always work VERY quickly. However, if I issued the opposite command right away, the device wouldn't respond. I needed to wait a while or keep trying over & over before it eventually worked.
The more I think about it, the more I suspect there is something going on with the ACKs. This is very similar behavior to what I saw recently with my Ring Extender, where it would send an event when you unplugged it-but if you plugged it in before waiting a while, it never sent the "mains power" event. Again, that was an S2 device.
This thread discusses similar issues with my Ring Contact Sensors and the Ring Extender (with some other people's comments and issues in the mix):