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

Thanks for the reply!

Ah, that’s a diplomatic way of saying I may have pasted in the new version code without removing the old code first. Totally possible, and I will make sure to be more careful next time!

1 Like

After I updated to the new handler and AP I lost the a lot of the controls Kwikset 914 series locks I did a reboot a repair on Zwave reloaded the handler and the smart AP same result ! Suggestions?

Is there bug with the UK Yale Keyless Lock regarding the battery level?

I’ve had mine for a about a year and the battery status has always stayed at 90% until yesterday when it dropped to 10% !!!

I’ve changed the batteries as a precaution even though it was operating fine, and I’ve had no notification from the actual lock itself that the batteries were low.

I found that the default DH was incorrect, so I switched it through the IDE and everything populated correctly.

1 Like

Thank you I tried that the looks show the correct device handler!

You have a screenshot of the device Laundry Door in IDE showing the Type?

I am in the same boat as Misterfinewine (a couple posts above)… I have a Yale 246 that’s been working great for over a year with RBoy’s goodies, but this latest update to the DH/SA gives me the same results as Misterfinewine’s screenshot…

Only the lock/unlock options show near the top, but if I scroll down that screen a bit, I also have the batt-level indication and a refresh button.

I have triple-checked that I have the proper/latest DH and SA loaded (and not cross-loaded!) - I’ve tried reinstalling both of them multiple times, and I’ve now waited ~24 hours for a settling-in period, but still no joy.

I want to be clear that everything still works great - no problems there - it’s just odd that none of the other usual options are populating on that lock info screen within the app

FWIW, those other options were all populating appropriately prior to this latest update.

Not really any big deal for me, just an oddity.

Thanks!

Have you opened the device in Things and selected gear icon and then hit save?

Then hit the refresh a few times.

And if that doesn’t work, clear cache and Force stop ST app.

Yep, roger that on all fronts - I should’ve mentioned that I did all of those things as troubleshooting steps too. I don’t claim to be a ST wizard, but I consider myself pretty darn savvy with navigating the various ST ism’s we all inevitably encounter, and I’m definitely comfortable using RBoy’s stuff - I’ve been using a number of his SAs and DHs for a while now.

Once again, this “issue” isn’t a big deal for me since everything otherwise works great, but it would seem that something is a bit off with this latest update. Who knows though - I’ll go through your suggestions again to today to see if something shakes loose!

Thanks!

I hate to ask - but did you double verify that you loaded the SA code to the SA and the DH code to the DH?I had copied the SA code to the DH so the default DH loaded, and only shows the buttons you note above.

And again - is this the device type that is selected through IDE?

Type: Universal Z-Wave Lock With Alarms

Yep, I saw your earlier post about that yesterday, so I double-checked yesterday for that too… I even tried reloading both the DH and SA a couple of times, but still same results.

Thanks!

1 Like

One other thing. Look to see if all the additional functionality shows on the device in IDE. If all your additional features show in there, then there is some sort of caching issue with it not showing in the mobile app:

1 Like

Ah-ha – now we’re cookin’ with butter! I do indeed have a few blanks there…

Do you have any recommendations for how to clear up a caching issue?

52

This tells me that it hasn’t read the lock to populate the current information.

Go open the SmartApp in the mobile app and perform a Next/Save/Save all the way through until it takes you out of the SmartApp. See if that refreshes everything appropriately.

1 Like

Just tried that again, but no change. I did that numerous times yesterday as well. Have done a few z-wave repairs also (they went fine - no errors).

After all my troubleshooting efforts yesterday, I thought giving the setup a day or so to settle down may allow it to sort itself out, but I guess not.

The lock seems to be communicating fine - I get timely notifications of unlock/lock status, etc.

I think I’ll just chalk this one up to a gremlin that maybe will sort itself out in the next release. This is definitely nothing I’m gonna lose sleep over, since the all the main functionality still works great!

Thank you for all of your help!

Folks if you’re seeing a bunch of “blank tiles” check your device’s raw description in the IDE under My Devices → click your lock. If it looks something like this:

Raw Description zw:Fs type:4003 mfr:0000 prod:0000 model:0000 ver:0.00 zwv:0.00 lib:00 cc:85,73,72,98

pay close attention to the mfr, prod and model, if they all’ zero’s that’s why the device handler isn’t able to identify your lock and the tiles are blank.

This indicates a pairing problem between the lock and the hub. Likely an issue/bug with the firmware. This had happened a few months ago and ST had patched it up, looks like the issue is back but it’s only affecting some users. We have reported the issue to ST’s engineers.

This bug affects the stock and custom device handlers as that information is used by all device handlers.
Report it to ST support if you’d like, however if the current solution from ST is to exclude and repair the device until it doesn’t show 0000.

Meanwhile we’ll be releasing an updated device handler shortly to workaround this issue.

1 Like

Good call - yep, that nailed it!!!

Thank you so much for your prompt & very thorough response. Subscribing to your services is the best $35 I’ve spent in Home Automation, no doubt!!

Thanks again!

2 Likes

To update the rest of the community here, RBoy’s newly updated DH fixed the issue for me - all the tiles are now back displaying properly!

Thank you RBoy and team for your awesomeness!

3 Likes

Update with patch for ST firmware bug:

Universal Enhanced Z-Wave Lock and Schlage Lock, Yale Lock, Kwikset Lock, IDLock, DanaLock, August Pro and Samsung Lock Device Handler - Version 04.00.02

  • Now supports integration with Smart Locks
  • Added support for Samsung Z-Wave locks
  • Fixed audio on/off tiles for Yale commercials/residential locks
  • Various improvements to improve code programming reliability and reporting

Schlage Lock Alarm Mode and Sensitivity Change and Monitor - Version 01.02.02

  • < no change >

Please refer to the previous posts for details on 03.xx.xx releases

This Device Handler has been tested and verified and optimized on the following lock models:

  • Yale Z-Wave locks (Assa Abloy, YRD2xx, YRD4xx, YRL2xx, YRC2xx, B1L, T1L, Keyfree, Assure, Conexis, Touchscreen, Deadbolt, RealLiving, nexTouch)
  • Schlage Z-Wave locks (FE469, BE469, BE468, FE599, BE369)
  • Kwikset (910, 912, 914, 916)
  • DanaLock (V2/V3)
  • August Pro
  • IDLock (101)
  • Samsung
  • Monoprice

Key features include automatic discovery of lock features:

  • Lock/Unlock
  • Privacy/keypad control
  • Autolock
  • Audio control
  • One touch/Lock n leave
  • Alarm mode
  • Alarm sensitivity
  • DPS/Door sense
  • Fire/smoke alarm
  • Tamper/motion alerts
  • Emergency alerts (police/fire)
  • Battery life optimization
  • Configuration of parameters
    • Yale -> relock timeout, wrong code reporting limit and dps
    • Danalock ->turn speed, brake n go, turn n go and relock timeout

NOTE: After updating to this version of the device handler, click on the device preferences (gear icon) on the top right corner of the device page and then click Done/Save for the device handler to register with Smart Locks. For best performance please exclude and re-pair the lock after upgrading the code.

Copyright © RBoy Apps

4 Likes