- Try to exclude the device
- Power cycle the hub (not just reboot)
they can be tricky to pair sometimes
@RBoy hello, question for you. How can I use this with your lock code manger using 4 digit codes for the keypad and 6 digit codes for the door locks Right now I Have the locks configued, but as soon as I add in the keypad it says my configuration will fail using a 4 digit code. I want to use 6 digits on the locks and 4 digits on the keypad, how do I make that work?
Most folks by default assign all users to all locks.
The app is basically informing you that trying to program a 6 digit code on a lock which is configured to accept 4 digits (or vice versa) will fail.
The right way to handle this is one of three ways:
- Install separate apps for each lock to program the user codes, since one lock only accepts 4 digits and the other 6
- Set all your locks to accept the same code length (most keypads are fixed at 4, but Iâm assuming youâre using a Schalge connect which can be configured to accept 4, 6 or 8 digits)
- If you want to use a single app control multiple locks but have different code lengths for each lock, you can create a user, under the user select which lock you want (e.g. keypad) and then assigned it a 4 digit code. Then create another user and select the other lock (e.g. Schlage) and assign it a 6 digit code. Basically youâre create a separate set of users for your keypad and lock. Rather inefficient way do it, itâs better to go with option 1 unless thereâs a specific reason to do is this way.
1 Like
This is exactly what I did, but on my 6 digit users it is still saying the codes will fail, even though I only selected the 2 locks with 6 digits. Any ideas?
In that case just ignore it. This is a very unique case where youâre trying to use locks with different hard coded pin lengths.
Itâs a better safe than sorry warning. It just checks the current configured length of all the main locks (doesnât check at an individual user level).
EDIT: Removed the extra warning messages in the next update.You will now see just one warning on the main page for safety and then it checks individual lock users and highlight them separately
2 Likes
ok, that is what I wanted to verify, thanks for your help, have a happy 4th!!!
1 Like
@RBoy got my Iris keypad today, and I think I have it added correctly. I used another slot in the Smart Lock SA to define the âopen/closeâ garage action when the code is entered, but when I enter the code on the keypad I get an error that says âToo many invalid user codes detected on lock Garage Door Openerâ and nothing happens.
Do I hit âonâ and then the code on the keypad? Just the number? Sorry for the stupid questions!
Edit - I think I figured it out that the âonâ means unlock and the âoffâ means lock.
But I have another question - is there a way to separate the actions for the same code depending on where the code is entered? For example, if my kid enters their code on the front door, it will unlock the front door but not open the garage door. But if they enter their code on the keypad it will open the garage door and not unlock the front door? Or is that inferred through the SmartApp?
Ok I think the best approach is to setup two different instances of the smartappâŠone for the locks and one for the keypad. I can duplicate the codes across the apps, but trigger different actions.
Or have two different entries in the same smartapp with different locks? Maybe that is better?
@RBoy can you tell me what field is missing? I canât change any value in the DH because it is asking for a field that is required.
@RBoy I also am still getting the âtoo many invalid user codes detectedâ error. This is a secondary code that I created to arm/disarm versus just opening or closing the garage door. Opening the door only works fine, but the code to arm the system is where I see the error
That message is coming from the keypad, you arenât entering the code properly (i.e keypad doesnât recognize a valid entry).FYI keypads only accept 4 digit codes
Thanks - I did verify that I was entering the code correctly and it is only 4 digits but I will try removing the code and adding another one to see if that helps.
@RBoy Is it possible for this DH to show correctly in the SmartLocks SmartApp from SmartThings? My Yale locks do with the tweak to the device name in the code, but can we do the same for this as well?
Same way, rename the DTH:
I couldnât get this to work with arnbâs SHM Delay 2.0 app. Is there something I should do to make it work?
https://community.smartthings.com/t/release-shm-delay-version-2-0/121800
Enhanced ZigBee Keypad Lock - Version 01.01.02
- Fix for deleteCode() not working as expected when code doesnât exist
@RBoy I just installed today an Iris Keypad and a Schlage door lock with your handlers and smartapp. Almost everything seems to be working perfectly except for the fact that I cannot disarm the SMH with the Iris keypad nor the Schlage door lock if the status is Armed (Away). It can be disarmed perfectly if the SMH status is Armed (Stay). Please take a look at these two short videos to see what I mean. Thank you.
I tested this about 20 times in different combinations and different keypads and itâs working fine here. It arms and disarms SHM as per the keypad buttons.
The option that was enabled was the Control SHM using the keypad in the User Management SmartApp
I did notice a few things however, sometimes the platform was slow to update the state (it would take up-to 5 seconds, most times it was instant). In one or two tries it didnât update to and I had to repeat the keypad before it updated the state.
So Iâm guessing this is a internal platform timing/issue, the app is sending the command to the platform.
I am unable to create new codes using Smart Locks. The Smart App shows "The Lock Code couldnât be created and the log shows âIris 3405-L Keypad is not ready for code creation as the lockCodes attribute is nullâ.
Same result but the logs now show this:
11:43:22 AM: debug Lock code set failedâŠ
11:43:22 AM: debug Sending lockCodeChanged event with name - lockCodeChanged12 and value - 1 set failed 12
11:43:22 AM: debug 6. Checking event history for 1 set
11:43:17 AM: debug 5. Checking event history for 1 set
11:43:12 AM: debug 4. Checking event history for 1 set
11:43:07 AM: debug 3. Checking event history for 1 set
11:43:02 AM: debug 2. Checking event history for 1 set
11:42:57 AM: debug 1. Checking event history for 1 set
11:42:52 AM: debug Event Type: Enhanced ZigBee Keypad Lock
11:42:52 AM: debug In codeChangedHandler with event value := 1 set, displayed: true
11:42:52 AM: debug Setting code slot 1 with code name Todd in Garage Keypad
11:42:52 AM: debug Garage Keypad is ready for code creation as the lockCodes attribute is already populated
Smart Locks lists the lock code but it doesnât seem to work on the keypad. I tried removing the device altogether and adding it back with the same result.