can anyone tell me if you have to enter a valid pass code for the kwikset deadbolts? i like the design and the zwave functionality, but i am not crazy about the idea of the external keypad. is there anyway to not have a valid code, but instead trigger an alert when someone enters any code?
also i have read that you can use the exterior (outside half) piece of a regular kwikset lock with the interior part (inside with the motor and batteries) of the zwave lock. has anyone successfully done this?
You do not have to use the keypad if you do not want to. You do have to have one valid code. You can have notifications if a valid or invalid code is entered. The lock will also have a keypad lockout after so many failed attempts.
I never tried using the lock with the keypad disconnected. That defeats the purpose of my usage.
Also, interesting about the lack of need of the key pad. In the link above, having no code plate would remedy all the security issues - there could be kwiksets in the future of some clients home.
Also, interesting about the lack of need of the key pad. In the link above, having no code plate would remedy all the security issues - there could be kwiksets in the future of some clients home.[/quote]
No bias, turb0?
Ok, my Kwikset deadbold plate is secured with two screws, also you can restrict the codes so you cannot modify them anymore…
As written in the post u mentioned…
I’m brand new (hi, y’all!) and it just so happens I was setting up my kwikset lock just moments ago. In the process I reset it. It appeared to have no codes, yet worked with the remote lock/unlock just fine. I think you don’t have to set up codes to use the z-wave functionality. Though I have to wonder; what’s the hassle of having a code? I think it’s good to have one at least as a backup should wireless functionality fail.
As for setting it to send notification whenever someone tries to enter a code, you can do that; just set the notification to send whenever a bad pin code is entered. You can also set it to send a notification if the primary/secondary PIN codes are changed on the hardware, which is yet another security precaution to prevent the problems that turb0 brings up.
Here are the notification options in the MCV system for my Kwikset lock:
-a door is locked or unlocked
-bad PIN entered
-[specific good] PIN entered
-Lock button pushed
-lock fails to operate
-user code used outside of vaild date
-low battery
-very low battery
-battery level goes below [specific %]
-a lock code was changed using the keypad
Here are the reasons for why I think pin codes are worth while. I have family members who I have given pass codes to access my home when they need to. I also use my keypad almost every day to lock and unlock my door. My phone is not always available when I need to lock or lock the door.
[quote=“garrettwp, post:8, topic:173014”]Here are the reasons for why I think pin codes are worth while. I have family members who I have given pass codes to access my home when they need to. I also use my keypad almost every day to lock and unlock my door. My phone is not always available when I need to lock or lock the door.
Garrett[/quote]
My usage patterns are the same, and if anything I generally use a PIN more since its a little bit quicker than fishing a phone out of my pocket, unlocking (since its pin protected), opening the app (SQ remote), getting to the right control screen, and then waiting a few seconds for the lock to be hailed and unlock.
I echo the previous sentiments. The keypad is much quicker than a smartphone. Another good reason for the keypad: I routinely have a cleaning service and handymen in and out, and I feel it’s actually more secure to give somebody a code I can change than to give them a key they can take to the hardware store and copy (not that I’m really worried about that actually happening).
As for all the discontent with respect to the ease of changing pin codes, I feel the danger is a bit overstated. The fact that the system immediately notifies me when a code is changed, and the first two codes are the ones my wife and I use on a daily basis makes it practically impossible that a surreptitious code change would go unnoticed.