@ady624 I noticed that you’ve recently added support for usedCode for Locks from the data field. This will be useful for users if they want to take action based on which user unlocked the code. While the stock DH only reports usedCode for keypad based unlocked entries the Enhanced Universal Z-Wave Lock DH also reports the usedCode for lock events (where a keypad is used). So I think that this functionality would be would be useful for those using the Enhanced DH.
However one of the serious shortcomings of the stock DH is that it doesn’t capture or report non keypad based events, with a slew of new technologies locks are now sending events for RFID and other technologies also. The Enhanced Z-Wave Lock DH does capture these events also and report them under an extension of the data field in a variable called type. If you added support (conditional because it would depends on the underlying DH, Enhanced or Stock) users can use this information to make decisions based on the type of event. The type field contains values to indicate the source of the event, e.g. manual, keypad, remote, rfid and auto (and may expand in future to encapsulate newer technologies).
For example locks have keypad, remote, auto and rfid types of lock/unlock events. User codes can be entered via RFID or Keypad to unlock and lock. This extension allows them to take actions based on a RFID user vs a keypad user or maybe an auto vs remote vs manual event.