Author Topic: Vera 3: PIN restriction for Schlage BE469NX decided not to work today  (Read 539 times)

Offline darthray

  • Sr. Newbie
  • *
  • Posts: 25
  • Karma: +1/-0
I have a Vera 3 on the firmware 1.7.1017 (latest) controlling a Schlage BE469NX deadbolt. I have people coming in every work and as such, I set a PIN for them that is only enabled 9-to-5 on a particular day of the week. On that day, I usually get a notification at around 9AM when the restriction takes effect.

The past week I didn't receive the notification and, sure enough, I got a call from the folks coming in saying that could unlock the door. They left and I was away from home, so the only thing I could think of was to reset the restriction: I removed it and tried to the re-add it. Vera puts a note saying it can take up to 2min for the lock to receive the request and then it goes away and ... nothing happens. The restriction was not added. I tried this a couple more times with the same results. I then to try adding a new PIN and it took it just fine (verified by someone near my house).

What's going on? Who's at fault here? Vera or the lock? Why didn't the system take the new (well, removed and re-added) restriction?

Thanks!

Offline darthray

  • Sr. Newbie
  • *
  • Posts: 25
  • Karma: +1/-0
Re: Vera 3: PIN restriction for Schlage BE469NX decided not to work today
« Reply #1 on: April 05, 2018, 04:48:15 pm »
I think I found the reason. I noticed my Vera now thinks all pin codes are masked (they show up as '****'), even though not all of them were like that before. Then I looked at the logs and saw this:

02      04/05/18 13:20:15.103   ZWaveDoorlock::ProcessLockCodeSchedules node 7-1 code 1=1 <0x2bbf4680>
02      04/05/18 13:20:15.103   ZWaveDoorlock::ProcessLockCodeSchedules node 7 no restrictions <0x2bbf4680>
02      04/05/18 13:20:15.104   ZWaveDoorlock::ProcessLockCodeSchedules node 7-3 code 3=1 <0x2bbf4680>
02      04/05/18 13:20:15.105   ZWaveDoorlock::ProcessLockCodeSchedules node 7 no restrictions <0x2bbf4680>
02      04/05/18 13:20:15.105   ZWaveDoorlock::ProcessLockCodeSchedules node 7-4 code 4=4 <0x2bbf4680>
02      04/05/18 13:20:15.106   ZWaveDoorlock::GetTimeRestrictionActive weekly for 27 dow 4/9:0/18:0 ret 1/1522976400 <0x2bbf4680>
02      04/05/18 13:20:15.107   ZWaveDoorlock::GetTimeRestrictionActive weekly for 27 dow 5/9:0/18:0 ret 0/1523030400 <0x2bbf4680>
02      04/05/18 13:20:15.108   ZWaveDoorlock::ProcessLockCodeSchedules node 7 GetTimeRestrictionActive code CODE1 active sb 1 is 4 next event 1522976400 #ofrest: 2 <0x2bbf4680>
02      04/05/18 13:20:15.108   ZWaveDoorlock::ProgramUserCode node 7 code 4 now 1 <0x2bbf4680>
01      04/05/18 13:20:15.109   ZWaveNode::ReceivedMessage_SetDoorLockPin_CreateCommand node 7 non-numeric pin **** <0x2bbf4680>   <<<<<< Failed to create PIN?
01      04/05/18 13:20:15.109   ZWaveDoorlock::ProgramUserCode node 7 code 4 failed to create <0x2bbf4680>
02      04/05/18 13:20:15.110   ZWaveDoorlock::ProcessLockCodeSchedules node 7-5 code 5=4 <0x2bbf4680>
02      04/05/18 13:20:15.111   ZWaveDoorlock::GetTimeRestrictionActive weekly for 27 dow 3/9:0/18:0 ret 0/1523462400 <0x2bbf4680>
02      04/05/18 13:20:15.111   ZWaveDoorlock::ProcessLockCodeSchedules node 7 GetTimeRestrictionActive code CODE2 active sb 0 is 4 next event 1523462400 #ofrest: 1 <0x2bbf4680>
02      04/05/18 13:20:15.112   ZWaveDoorlock::ProcessLockCodeSchedules node 7-6 code 6=1 <0x2bbf4680>
02      04/05/18 13:20:15.113   ZWaveDoorlock::ProcessLockCodeSchedules node 7 no restrictions <0x2bbf4680>
02      04/05/18 13:20:15.134   ZWaveDoorlock::ProcessLockCodeSchedules node 7-7 code 7=1 <0x2bbf4680>
02      04/05/18 13:20:15.135   ZWaveDoorlock::ProcessLockCodeSchedules node 7 no restrictions <0x2bbf4680>
02      04/05/18 13:20:15.136   ZWaveDoorlock::ProcessLockCodeSchedules node 7-8 code -1=-1 <0x2bbf4680>
02      04/05/18 13:20:15.136   ZWaveDoorlock::ProcessLockCodeSchedules node 7-9 code -1=-1 <0x2bbf4680>
02      04/05/18 13:20:15.137   ZWaveDoorlock::ProcessLockCodeSchedules node 7-10 code -1=-1 <0x2bbf4680>
02      04/05/18 13:20:15.137   ZWaveDoorlock::ProcessLockCodeSchedules node 7-11 code -1=-1 <0x2bbf4680>
02      04/05/18 13:20:15.138   ZWaveDoorlock::ProcessLockCodeSchedules node 7-12 code -1=-1 <0x2bbf4680>
02      04/05/18 13:20:15.138   ZWaveDoorlock::ProcessLockCodeSchedules node 7-13 code -1=-1 <0x2bbf4680>
02      04/05/18 13:20:15.139   ZWaveDoorlock::ProcessLockCodeSchedules node 7-14 code -1=-1 <0x2bbf4680>
02      04/05/18 13:20:15.140   ZWaveDoorlock::ProcessLockCodeSchedules node 7-15 code -1=-1 <0x2bbf4680>
02      04/05/18 13:20:15.140   ZWaveDoorlock::ProcessLockCodeSchedules node 7-16 code -1=-1 <0x2bbf4680>
02      04/05/18 13:20:15.141   ZWaveDoorlock::ProcessLockCodeSchedules node 7-17 code -1=-1 <0x2bbf4680>
02      04/05/18 13:20:15.141   ZWaveDoorlock::ProcessLockCodeSchedules node 7-18 code -1=-1 <0x2bbf4680>
02      04/05/18 13:20:15.142   ZWaveDoorlock::ProcessLockCodeSchedules node 7-19 code -1=-1 <0x2bbf4680>
02      04/05/18 13:20:15.143   ZWaveDoorlock::ProcessLockCodeSchedules node 7-20 code -1=-1 <0x2bbf4680>
02      04/05/18 13:20:15.183   ZWaveDoorlock::ProcessLockCodeSchedules node 7-21 code -1=-1 <0x2bbf4680>
02      04/05/18 13:20:15.184   ZWaveDoorlock::ProcessLockCodeSchedules node 7-22 code -1=-1 <0x2bbf4680>
02      04/05/18 13:20:15.184   ZWaveDoorlock::ProcessLockCodeSchedules node 7-23 code -1=-1 <0x2bbf4680>
02      04/05/18 13:20:15.185   ZWaveDoorlock::ProcessLockCodeSchedules node 7-24 code -1=-1 <0x2bbf4680>
02      04/05/18 13:20:15.186   ZWaveDoorlock::ProcessLockCodeSchedules node 7-25 code -1=-1 <0x2bbf4680>
02      04/05/18 13:20:15.186   ZWaveDoorlock::ProcessLockCodeSchedules node 7-26 code -1=-1 <0x2bbf4680>
02      04/05/18 13:20:15.187   ZWaveDoorlock::ProcessLockCodeSchedules node 7-27 code -1=-1 <0x2bbf4680>
02      04/05/18 13:20:15.188   ZWaveDoorlock::ProcessLockCodeSchedules node 7-28 code -1=-1 <0x2bbf4680>
02      04/05/18 13:20:15.188   ZWaveDoorlock::ProcessLockCodeSchedules node 7-29 code -1=-1 <0x2bbf4680>
02      04/05/18 13:20:15.189   ZWaveDoorlock::ProcessLockCodeSchedules node 7-30 code -1=-1 <0x2bbf4680>
02      04/05/18 13:20:15.189   ZWaveDoorlock::ProcessLockCodeSchedules node 7 next active at 2018-04-05 18:00:00 <0x2bbf4680>

Does anybody know how to recover the pin codes that are now masked? I have the "Show pin codes in clear" checkbox already checked.

Thanks!

Offline rigpapa

  • Beta Testers
  • Hero Member
  • *****
  • Posts: 758
  • Karma: +115/-1
Re: Vera 3: PIN restriction for Schlage BE469NX decided not to work today
« Reply #2 on: April 05, 2018, 06:23:03 pm »
I ran into this today, too, although I didn't spend much time on it, I just cleared the code entirely and reprogrammed it.

Do you recall, was the code you were modifying completely expired (daily schedules, and all had passed), at the time you attempted to add the new restriction?
Author of Reactor, DelayLight, SiteSensor, Rachio, Deus Ex Machina II, Intesis WMP Gateway, Auto Virtual Thermostat and VirtualSensor plugins. Vera Plus w/100+ Z-wave devices. Vera3 sandbox.

Offline darthray

  • Sr. Newbie
  • *
  • Posts: 25
  • Karma: +1/-0
Re: Vera 3: PIN restriction for Schlage BE469NX decided not to work today
« Reply #3 on: April 05, 2018, 08:56:43 pm »
Yeah, I thought I could just delete all PINs and recreate them -- I'll do that later -- but figured I would ask in case someone wanted me to pull up any logs.

I do not recall for sure, but if I had to guess the particular PIN was completely expired (the PIN was not in effect at the time).