Is there really no way to log/notify PIN info ?

I searched forums and found a couple of different discussions about this. I thought back in UI2 you got the PIN info as part of either the notification or the log that you could view via the web. It seems like the basic stuff that one really needs to know is not there. I am sure its the same for all locks, but in my case its the Schlage deadbolt.

I have tried a couple of different scenes, basically just get Door Lock or Unlock

Anyone got some code that would work some magic?

According to [tt]http://wiki.micasaverde.com/index.php/Luup_UPNP_Files#Variables_12[/tt] there are the following UPnP variables for locks:

#define DL_STATUS                       "Status"
#define DL_TARGET                       "Target"
#define DL_MIN_PIN_SIZE                 "MinPinSize"
#define DL_MAX_PIN_SIZE                 "MaxPinSize"
#define DL_KEEP_PIN_CODES               "KeepPinCodes"
#define DL_SL_USER_CODE                 "sl_UserCode"
#define DL_SL_PIN_FAILED                "sl_PinFailed"
#define DL_SL_LOCK_BUTTON               "sl_LockButton"
#define DL_SL_LOCK_FAILURE              "sl_LockFailure"
#define DL_SL_UNAUTH_USER               "sl_UnauthUser"
#define DL_SL_LOW_BATTERY               "sl_LowBattery"
#define DL_SL_VERY_LOW_BATTERY          "sl_VeryLowBattery"
#define DL_SL_CODE_CHANGED              "sl_CodeChanged"

#define DL_PIN_CODES                    "PinCodes"      // DEVICEDATA_PIN_Codes_CONST
#define DL_NUM_SCHEDULES                "NumSchedules"  // DEVICEDATA_PIN_Codes_CONST

I don’t own a Z-Wave lock, so I can only speculate that [tt]sl_UserCode[/tt] might contain the PIN.

Edit:
[tt]http://forum.micasaverde.com/index.php/topic,7176.msg45592.html#msg45592[/tt]

1 Like

Any updates on this? Really want to see PIN info in the logs

I reported it as a ‘feature request / bug’ for UI4. It was closed 11 April with this comment.
"Issue resolved in UI5 build 1.5.346. Bug closed. "

Maybe I should give UI5 a try and see…

I am using UI5. I have notifications set on my locks to inform me when certain codes are entered. I receive the notification via SMS and email. Additionally, the Vera will log the code being entered.

Has worked very well for me.

Had been holding off upgrading my vera2 from ui4 to ui5 as it looks like there are still problems with the 3-in-1 sensors…

I have two Vera 2’s in different houses, both running UI4. One location uses Kwikset locks, the other Schlage. The Kwikset locks will send an SMS or email notification every time. The Schlage locks never talk to me (although I can control them remotely).

What is the trick to getting the Schlages to communicate (via SMS or email)? All the notification settings look correct.

I concur with others who would like to see a log feature for UI4. I’m holding off upgrading to UI5 because of all the other scary posts.

I too would be very interested if anyone has any code I could drop in to give me names/number used/tried. I will stay on UI4 until UI5 is a lot more stable. Too many things to go wrong when the unit is hours away at a vacation rental.