Kwikset vs Schlage locks Code complexity

[Raptor]

Hi guys,

I have been searching for a while for an answer to this one and i can't find anything...

I am looking to buy the Kwikset z-wave lock however i have a question about the code complexity.

The Kwikset lock has 5 buttons labeled: 1-2 3-4 5-6 7-8 9-0

it seems to me that there are only 5 inputs to the lock vs the schlage that has 10 buttons 1-10.

that seems like a huge difference in the code complexity, 5 vs 10.

I realize that eitherway you can have 4-8 digits but still.

Does anyone have any input here?

Raptor

[Rupp]

What are your concerns exactly? If someone wants in they are not going to press the buttons until they figure out the code, they will kick in the door.

[Raptor]

Yes that is true,

do the locks have some kind of lockout feature if the code is entered in incorrectly X number of times?

Raptor

[rmasonjr]

I've been pretty happy with the Schlage door lock. The only thing I dont like is that the handle opens always from the inside - not good when you have a toddler

[rmasonjr]

Yes that is true,

do the locks have some kind of lockout feature if the code is entered in incorrectly X number of times?

Raptor

I know the Schlage will lockout for ~30 seconds after 4 incorrect tries...

[twa8000]

the kwikset locks out for 30 seconds on 3 incorrect attempts, you can also setup an event based on this. After 3 incorrect attempts the system sends me a txt if im not home

I was also worried about the 5 keys as opposed to 10.. but i have all 8 digit codes.. so there are 40320 combiniations of just 8 digit codes

So if someone was trying only 8 digit codes.. it would take 524160 seconds at 3 seconds per code which would take just over 6 days.

I think that is right????, lol either way, its alot

-Tom-

[kaffeene]

I have the Schlage but is there any way to lock-out even people with user codes on the Kwikset. Just temporarily of course, to keep people out until de-activated.

[drozwood90]

-only way I can think of is to have an event trigger on a code change
-in script, read the value in the device that holds
-in script, send the unlock to the lock
-in script, wait 7 seconds
-in script, re-lock the lock
-in script, disable that event (or start ignoring THAT code).

--Dan