No worries. I understand.
I’d rather have 6-digit codes but I’ll live with the 4-digit codes. At least the lock has individual buttons for each digit as opposed to the doubled-up buttons on the Kwikset it’s replacing. This reduces the chance of getting lucky with keypresses.
As for the 3-second auto lock, I think that’s OK too (since I have no choice). In addition, I note that by manually pressing the unlock button on the inside of the door/lock, the lock will stay unlocked indefinitely. So, I’ve written two webCoRE pistons:
- The first automatically relocks the door after 5 minutes of being unlocked. It then checks up to five times to ensure that the lock has actually been locked.
- I then created an ‘override’ virtual switch that keeps the door unlocked for two hours - relocking it automatically after the two hours expires. It also includes the 5x confirmation to ensure it’s been locked
So, I have a full range of security/convenience solutions in spite of the auto-locking inflexibility within the lock. An automatic 3-second locking when entering a user code and then the 5-minute and two-hour automatic relocking based in webCoRE.
Thanks again for your time and great apps and DTH’s.
BTW, I installed this lock on Friday and it has performed perfectly in every instance since then and hasn’t fallen offline at all. It’s a big change from the increasingly flaky Kwikset 912 I’ve been fighting with for many months - even after replacing the Z-Wave module.