Perfect – I used the script and am now up and running. For some reason compiling my own bundle didn’t work (it finally recognized the lock, but none of the commands worked).
So now that I’ve been playing with it, I’ve noticed an issue that perhaps is specific to these locks.
OH2 doesn’t get lock status updates. Other sources online indicate that the Yale locks uses an alarm notice to report a lock change instead of the “correct” method. When that lock states change, entries such as the following show up in the log:
NODE 9: Device message contained nonce that is unknown to us, id=0x05, table={}, expiredList=[], usedList=[-67, 99, -78, -126, -30, 0, 104]
NODE 9: Unknown Alarm Type = 24, ignoring report.
NODE 9: Timed out waiting on response for encapsulated message Message: class=SendData[0x13], type=Request[0x00], priority=High, dest=9, payload=09 17 98 81 08 B7 5D CA BC 56 22 44 FD 91 7F 40 BB 51 9B B7 33 C0 BB 12 AD encapsulates: Message: class=SendData[0x13], type=Request[0x00], priority=Set, dest=9, payload=09 03 62 01 FF
NODE 9: Unknown Alarm Type = 22, ignoring report.
2016-03-27 03:58:11.981 [ERROR] [col.security.ZWaveSecureNonceTracker] - NODE 9: Device message contained nonce that is unknown to us, id=0xFE, table={}, expiredList=[], usedList=[-118, -88, -87, -21, -115, -56, 26, 74, -29, -123]
I see other alarm types such as 21 (Lock?), 22 (Unlocked?), 24 (??), and 25 (??).
Should I open an issue on GitHub?