[EDGE] Universal Enhanced Z-Wave Lock Driver for Schlage, Yale, Kwikset, IDLock, Popp, Danalock, August Pro, Keywe, Philia, Samsung

Yes but bring the lock closer to the hub before clicking refresh.

@RBoy - I installed a second Yale touchscreen lock in the garage door this weekend and added it to the SmartApp that you created. Now I get a notification every five minutes that it is attempting to adding the User 1 number to the lock, but it never seems to work. What would you recommend? It seems like an endless loop to me.

Did the follow the instructions on the website to clear all codes before
programming new ones?

Well - I didn’t want to program new ones, I only wanted to add the second lock without changing any codes. But I did what you recommended, and how ST is notifying me every minute that it has successfully deleted and added users. I deleted all of the codes in the app and waited for a few minutes before adding some back in.

The second lock does not work even though ST tells me it was successfully added (when I say this I mean the code generation does not work. The ST integration works fine where I can lock and unlock the door through the app), and the first lock still works.

Thoughts?

Thanks, reset the lock, removed it from the zwave network, then added it back and now I am seeing all the tiles.

1 Like

Click refresh and if it doesn’t populate then you will need to bring the lock closer and then pair it again. Also do you see the mfr, prod and model as 0000 in the raw description? If so that’s likely an issue after a recent hub update that we’re seeing. You would want to report it here to @nastevens

That’s an issue with the pairing or the distance of the lock from the hub. Try to exclude and repair the lock closer to your hub. Then run the clear codes procedure once (as it’s a new pairing). If that solves the issue then your z-wave mesh is weak. Try to run reboot the hub, run a Z-Wave repair and possibly add an active device between the hub and lock.

Thanks @RBoy.

I apologize for my lack of expertise, as I am not as well verse as some in this forum.

  • Can pairing be an issue even though I am able to use the lock through ST? Lock/Unlock works fine. The codes do not, or they are in the circular loop. The codes have been deleted and added dozens of times this morning already.

  • I don’t think distance is an issue. The hub is less than 6 feet away. I have a Wemo in-wall switch less than one foot from the lock and the door has an Aero open close sensor that is a repeater, which is less than 4 feet away.

  • The clear codes procedure is pretty painful. I have at least a dozen codes since we have 24 hour nursing care for my son and it is painful to remove all of them. Each time I click in the field it has to do some validation requiring me to click twice. Sometimes my changes don’t stick thereby causing an error when trying to save. Then I have to add each one back individually. I have done this twice and it goes into the circular loop I state above.

Is my solution to remove both locks from my network, reset them, reset a master code, repair them with the network and then add them to the app? I sure hope not, as starting over like that is a lot of work!

It’s supposed to be a very simpleprocess. Looks like your setup is good if it’s that close.

Yes you can have pairing issues even if some functions work.

Do these steps and it should resolve any issues

  1. Reboot the hub
  2. Do a z-wave repair
  3. Exclude and re pair the lock
  4. Open the SmartApp - set your number of users click next and then click done (keep all names and codes empty). Give it 10 minutes

From now on you should never have to clear anything or do anything. This is a fully clean setup.

Now just enter the codes in the SmartApp or change as required.

Also you can enable the option to disable verification on the first page of the SmartApp and you can skip all the above steps as a short cut.

The verification is a security measure that we have implemented. However is requires a very stable network and clean database to work effectively. It’s not mandatory and you can disable it if you’d like.

I was going to mention some difficulty with AutoLock no longer having the same time settings and seeing DANALOCK and Yale settings for my Schlage lock, however I believe the door AutoLock isn’t what was being used and that it is the Schlage Lock Users & Actions where you can configure granular settings. Not sure when or why it reset, but I’ve made changes and will see if that fixes the issues that were occurring.

@Rboy are there any plans to update this DH with the new color scheme that ST has been rolling out? So instead of Green for locked use Blue instead and Orange for unlocked?

1 Like

Yes it’s on our todo list for all our device handlers.

Thanks @RBoy. I will give that a try. Just for clarification, does “exclude” mean “remove”? Like I remove the lock from ST and then set it back up again?

That’s correct, exclude = remove

I have a Schlage FE469 installed, using this DH and CoRE. I am not using RBoy’s user management App. I have a CoRE piston set up to provide notification anytime one of the programmed users enters, but I want to add one for when an invalid code is entered (preferably entered 3 times). I have tried to set the piston using the “invalidCode” attribute, but nothing works. I believe that it is an issue with the DH, as when I look at the “Recently” tab for the lock, it shows nothing when I put in an invalid code (but acknowledges when I use a correct one). As this is the entire reason I got a “lifetime pass,” I am really hoping that I am just missing something here.

Thanks

I have a Yale YRD120 Touchscreen T1L with Z Wave. I am using the DH and the Smart App.

When I had first installed everything several months ago, I had the same question about entering an invalid code and getting a notification. OOTB, the invalid code for the Yale Lock was 5 and I had no way of changing that. So, the only way I could get a Notification was if I entered an Invalid Code in succession 5x. This would send a notification through ST and also disable the keypad on the lock for 60 seconds.

Since that time, it appears that RBoy has update the DH so when I look at my Device in ST and goto Configuration, there is now a “Wrong code entry limit” which is defaulted to 3. So I just went and tested and sure enough, after 3 invalid attempts, I receive a message “Too many invalid user codes detected on lock Garage” and the keypad locks for 60 seconds. I attempted to change the “Wrong code entry limit” to 1 and 2 from my Device in ST and this had no effect on the number of invalid attempts. I still had to enter an invalid code 3 times. So not sure if there is something internal to the lock that has a minimum number threshold built in, or if the DH is not specifically updating the locks “invalidcode” number.

Additional Note - Not relevant to Invalid Codes - I see that the DH now handles “Code Entry on”, “Code Entry off” which allows me to disable the Keypad from the configured users from entering a code (Exception - Admin password still works) - I had to go in and manually disable this from the lock itself prior to the updated of the DH.

Anyway, I throw these comments out to you because I’m not sure if that has something to do specifically with the default configuration of your “Schlage” or if the DH handles/deals with Invalid Codes differently for Schlage versus Yale.

I’m sure RBoy will chime in with comments as to why.

1 Like

I have installed a Kwikset914 and your app and used it for a while. Currently using 5.5.1.

Problem: Received a battery dead today and replaced the battery (about an hour ago). I tested by locking and unlocking. Battery (quite a bit later) still indicates battery at 0%.

Other concern. The DH appears to be setting the device codes every 5 or less minutes. It seems this would integrate into a significant drain on the battery.

@RBoy Hello, having an issue. I have a kwikset and the code at the door works fine, what does not work is the disarm of SHM or Modes. I have it setup on the master code, do I need to setup the disarm on the individual users?

Your setup is correct. The issue is with the Schlage lock. It doesn’t send an invalid code notification for every invalid code entered. If you enter the an invalid code four times in succession it will send one invalid code notification. This cannot be changed as Schlage has hard coded it.
However Yale does allow for this parameter to be customized which can be done through the device handler settings.

That’s right you can configure the attempts but the thresholds vary from lock to lock.

Important point to note after you change the device settings in the settings page you need to hit the refresh button for the changes to take effect.

Feel free to PM me the logs from IDE Live Logging after you hit refresh. It will show what settings are being sent to the lock and what the lock is accepting / returning.