[OBSOLETE] Lock User Management (LUM)

[h0ckeysk8er (Bruce Pinsky)]

@h0ckeysk8er

@rcbjr2

I set up a SharpTools rule to send a Pushover notice when I unlocked my front door so I now know that the one user I was looking for is slot 7 even though the user is 5th is my list of users. I’d like to do more with that info, but I can’t get to the routine in SmartThings where I was using that info to turn on a virtual switch. Oh well. I assume they’ll come back eventually…

Unfortunately, lockcodes are not exposed in the ST App for routines so they can’t be used as triggers (apparently they are defined as a capability but have no capability presentation defined). Also, the lock itself only stores code1, code2, etc for the codeName so you have figure out your lock code to user mapping and do as @Babar_Khan suggests and use codeId to set a variable to a friendly name that is easier to use in other routines. You may be able to get the lockCodes array via the API which would have the mappings as defined by SLGA or whatever lock manager you are using.

Turns out there is a bug in the default Z-Wave device handler in the stock Z-Wave Edge driver that was causing code names to be reset to the default periodically. @philh30 has released an updated beta Edge driver of his Z-Wave Lock Edge driver that supplies the proper codeName upon unlock and also prevents the periodic resetting of the lock code names to the defaults. I’ve been using it for around a week now and getting solid results. I’ve now set up Rules in Sharptools that evaluates the $context.event.data.codeName variable and performs per user actions based on who unlocked the door.

The updated beta version of his lock driver is in the same channel as the original.