RM 4 Possible Bug with Lock Code Trigger


I may or may not be able to fix this without one of these locks in hand, I need to have a look at the code first...

Given the lock joined and selected Device as its driver, did you click configure in the Lock driver after switching it?


Yes I did click configure. FWIW in the hub logs the code used is logged:

Maybe it is something simple like ensuring a device event is captured?


The only thing I see that's perhaps not correct being we're sending two unlock events it seems, the first with no user info, the second with the correct info, whilst this isn't quite correct it should still work...
If you could enable debug logging in the driver, the unlock it with one of the codes, then PM me the live log results, then maybe it is something simple...


@mike.maxwell done! Thanks.


Has there been any progress on this issue, I have a couple of Kwikset 914 Zigbee units that the lock code events were triggering RM rules fine, but no longer are, the logging shows both the unlock and the unlock by xx but the device event log isn't showing a user at all and the RM rule isn't triggering.


@mike.maxwell Were you able to determine the issue? I am have a dev hub and happy to temporarily pair the lock to that hub and load beta/test firmware to help you with this issue. Please let me know how I can help.


We may have to do that as the only zigbee locks I have on hand are Yale, and they will now have a dedicated driver in 2.1.4


Just don't break it for the rest of us... My kwikset 914 and my two 916 all are working perfectly with the zigbee modules. They report user codes when unlocked as expected, and I don't get any duplicate events in the event list.

It might be something device-specific in his install.


That's exactly why I spun up drivers just for Yale, you're seeing the trend no?


Cool, let me know how I can help.