SmartThings Community

[RELEASE] Universal Enhanced Z-Wave Lock, Schlage, Yale, Kwikset, IDLock, DanaLock, August Pro, Samsung, Locstar, Delaney, KeyWe, Philia Locks and Popp Z-Wave Keypad Device Handler with Alarm Control, Notification, RFID, Door Sensor and advanced features

smartapp_alerts
dth_locks
smartapp_security
smartapp_locks
rboyapps
(Head of Support (rboyapps.com)) #1309

You can set it up any way you like, one LUM instance to control all your locks, garages, doors etc or a separate instance for each device.
The advantage with a single instance is that you can do it all in one place. Once you add a user it can automatically be sent to all the locks (assuming they all are configured to use the same pin length). You can setup different actions for each lock. You can restrict users to specific locks from the users page, create custom user specific actions for each lock and so on. It’s very flexible and about personal preference.

While one app can control multiple locks, the only thing to note is that one lock should not be controlled by more than one app to avoid conflicts like the one you saw above.

(Angie Guedry) #1310

Thanks alot Maddie, I was making it way too hard!
Angie

(Joe) #1311

Last week my Schlage tiles disappeared (to defaults), so I lost all its specific features. I had to reset the lock and reconstitute all the configurations. This week, the same has happened to my father’s house, with the added frustration that it now relocks automatically, even though it’s not configured that way. He uses a Kwikset 910 (see below).

With my Schlage, I had to exclude, re-attach, and then reconstitute all the smart app configurations. He loves the app, but not with tech issues. Is there any why I can avoid 60 minutes of his complaining while I fix his setup?. lol :joy:

(www.rboyapps.com - Make your home your butler!) #1312

A few folks have reported this happening randomly recently and it’s appears to be happening due to a corruption in the platform backend data where the lock model identification numbers are replaced with 0000 as reported in one of the posts above. The best solution is to exclude and re pair like you’ve done. You can also try to update your DTH to the latest version. We’ve put in a work around which tries to read an alternative source of the lock model information. If the alternative data in the platform isn’t corrupted the tiles will show up again when you tap refresh. If both the sources of data are corrupted you’ll have to exclude and re pair it.

(Erik) #1313

@RBoy before I go about resetting and repairing the lock…I am curious if you know what might be happening

Basically - the Classic app will read the status (locked or unlocked) if I manually lock or unlock, but trying to lock it to unlock it from the app does not do anything. This is new from the last few days. I did replace the batteries (which they just stay at 79% in device screen) and the SmartLock app shows the lock as “unknown” but then goes back to showing its correct status at some point.

  1. I have the most current DTH (4.03.05)
  2. I replaced the batteries
  3. I ran the Z-Wave Repair

When I try to unlock or lock from the app, this is the last log in the device itself:

effe4bf6-5e8b-436f-a4ec-73afe1ee23ed
10:19:10 AM: trace [DTH] Executing unlock() for device Security - Garage Door Lock

Nothing else shows up in the logging after that, until I unlock it manually, and then I get:

effe4bf6-5e8b-436f-a4ec-73afe1ee23ed 10:23:42 AM: info [DTH] parse() - returning result=[[name:lock, value:unlocked, data:[method:manual, lockName:Security - Garage Door Lock], descriptionText:Unlocked manually, isStateChange:true, displayed:true, linkText:Security - Garage Door Lock]]

effe4bf6-5e8b-436f-a4ec-73afe1ee23ed 10:23:42 AM: debug [DTH] zwaveEvent(physicalgraph.zwave.commands.alarmv2.AlarmReport) returning with result = [[name:lock, value:unlocked, data:[method:manual, lockName:Security - Garage Door Lock], descriptionText:Unlocked manually, isStateChange:true, displayed:true, linkText:Security - Garage Door Lock]]

effe4bf6-5e8b-436f-a4ec-73afe1ee23ed 10:23:42 AM: trace [DTH] Executing ‘handleAlarmReportUsingAlarmType’ with cmd = AlarmReport(eventParameter: , numberOfEventParameters: 0, zensorNetSourceNodeId: 0, zwaveAlarmType: 0, alarmLevel: 1, zwaveAlarmStatus: 0, zwaveAlarmEvent: 0, alarmType: 22)

effe4bf6-5e8b-436f-a4ec-73afe1ee23ed 10:23:42 AM: trace [DTH] Executing ‘zwaveEvent(physicalgraph.zwave.commands.alarmv2.AlarmReport)’ with cmd = AlarmReport(eventParameter: , numberOfEventParameters: 0, zensorNetSourceNodeId: 0, zwaveAlarmType: 0, alarmLevel: 1, zwaveAlarmStatus: 0, zwaveAlarmEvent: 0, alarmType: 22)

(www.rboyapps.com - Make your home your butler!) #1314

Nothing shows up in response to the command sent to the lock means either the command never reached the lock or the response never reached the hub.

I generally advise folks to avoid debugging stuff on a weekend as the platform crawls on the weekend causing timeouts, lost commands and makes it more difficult to figure out stuff.

For Z-Wave issues the best solution is to add a repeater within 20ft if the lock:

http://community.smartthings.com/t/faq-why-would-i-need-another-beaming-repeater-if-my-zwave-lock-is-already-close-to-my-hub/137629

1 Like
(Erik) #1315

@RBoy ha that’s the one thing I forgot to add - I have an Aeotec Z-Wave repeater about 4 feet from the lock and a Z-Wave outlet right on the other side of the wall, so I think the signal is pretty decent.

I have never, ever, ever had this type of issue since installing the locks a couple of years ago so something is definitely different. And it started happening Wednesday so it wasn’t the weekend. I will see if it works tomorrow and update on this thread.

Thanks!

1 Like
(Drlungbarrow) #1316

This application appears to have a multitude of functions for locks and I have been debating if it will meet my use case. I am trying to obtain some additional information regarding the capability of this application to control some of the settings of the Schlage Z-Wave Connect Century (BE469).

Can this application allow the disabling and enabling of the Lock and Leave (I.E. One Touch) setting based on user codes entered onto the keypad?

Example: Having a guest code inputted turns on a guest mode for the home and disables lock and leave so that when the guest leaves they have to input the code again (Not simply hit the Schlage button on outside) to lock the door. The code being input again by the guest would turn off guest mode and re-enable lock and leave setting. As a daily user I like the one touch lock settings, but I want that to automatically be disabled if a guest code is entered.

(www.rboyapps.com - Make your home your butler!) #1317

This is device type handler (DTH), i.e. it allows SmartThings to access/control the features of your lock through SmartApps.

Apps like LUM provide many advanced features for lock management and user programming. You can use a SmartApp like CoRE or WebCoRE to issue commands to the DTH to create your own custom scenarios.
In your case you would be issuing the commands enableOneTouchLock and disableOneTouchLock to enable/disable the Schlage lock n leave feature. You can refer to this post for more details on how to use CoRE/WebCoRE to trigger the above commands when a user pin code is detected to unlock the door.

(Erik) #1318

@RBoy - I am still not having any luck getting the lock to actually lock from the app command. I can manually lock it and the status will immediately change in the app, but sending the command does nothing.

I get this:
effe4bf6-5e8b-436f-a4ec-73afe1ee23ed
4:38:20 PM: trace [DTH] Executing lock() for device Security - Garage Door Lock

But then literally nothing after that. The locks also show as unknown in the SmartLocks Smartapp.

I have also tried changing the DTH from yours to the stock local DTH and no change to the outcome.

Can you please help me out? Do I really need to reset both my locks? I have no idea what has changes as it has never done this before.

#1319

Iris refugee here. I just got the Rboy stuff going, and really like the ADT intergration so far. Luckily the instructions on the site are easy to understand, as I was super confused on device handlers/smart apps, and so far it seems to be worth the lifetime subscription. I have my kwikset lock arm the ADT system when I lock the door from the outside, and disarm via the keypad on the lock as well, which is perfect. I just can’t seem to figure out how to get the door to unlock, when disarming the ADT system via my phone. I really want it to unlock the door when I disarm it via my phone. It’s especially handy when coming home, with groceries and what not, and just opening the door.

I also really like that I can differentiate between a keypad unlock, and a manual keyed unlock. That way if someone were to break the door, and rotate the tumbler on the lock, it wouldn’t see that in a way to disarm the whole house.

1 Like
(Alex) #1320

I am currently using the freely available Lock Manager and custom DTH for my 3 Schlage locks. The locks worked fine until recently when I realized that the locks were no longer reporting their status, and if they did, it would be with extreme delay (I believe, but hard to say, even hours). Would changing to the @RBoy DTH and SmartApp make this more reliable? I am tired of finding my house unlocked since the system never knew the lock had been manually unlocked. In order to force it to get a lock/unlock update, I have to press the refresh button in the DTH more than once…

(Erik) #1321

How recent is recently? There were some Z-Wave issues over the last few days causing the commands to be severely delayed and report improper status of the locks.

It shouldn’t matter which DTH you use to get the proper status. If you use the local DTH supplied by SmartThings it will run locally, but all other DTH run off the cloud, which will improperly report the status in the SmartLocks SmartApp unless you make an update to the DTH code to run locally. The Rboy DTH is FANTASTIC and can be integrated with the stock SmartLocks SA as well.

So I don’t think it would be more reliable, but if the issues were over the last few days it was more the Z-Wave platform than any specific device.

(Alex) #1322

I have always had an issue with very slow status reporting for the locks and never figured out why. I have door announcements that say door open, closed, locked and closed which is what tipped me off as it kept saying closed and locked when I knew it was not locked. I did notice zwave issues these past few days but things seem to be better now. If Rboy’s DTH works in the new app, I will likely subscribe. Does it use a custom DTH or the standard one which will run locally?

(Erik) #1323

I know it works in the new app, but I am not sure how much works in the new app. You might want to try running a Z-Wave network repair to see if that changes anything, or make sure that you have a repeater within a few feet of the lock as the mesh tends to be an issue with Z-Wave locks.

And it is a custom DTH and doesn’t run locally.

1 Like
(Manie) #1324

Has anyone ever had an issue with their Schlage Connect locks that won’t allow you to add custom user codes? These locks have always worked perfectly for me until recently. I tried a full factory reset on the locks and completely defaulting out the smartapp (removed all users etc). I re-added everything and it still doesn’t work. This is the error I’m seeing in the app. Any ideas? I have the latest device handler and smart app installed and i also renamed the device handler to “Z-Wave Lock” as suggested.

(www.rboyapps.com - Make your home your butler!) #1325

You asked the same question on the LUM topic and I had answered the same question 2 posts before your post. Assuming the battery is good, your hub/lock are having trouble with the mesh.

To answer your other question, yes this DTH supports Schlage Z-Wave Plus modules.

(Manie) #1326

Thank you for the detail. That’s pretty interesting. My house has 38 z-wave plus light switches throughout with tons of them all around the locks and not too far from the hub. Maybe it’s getting to be too much. I’ll reboot the hub and try to do a z-wave repair and see what happens.

1 Like
(www.rboyapps.com - Make your home your butler!) #1327

If the hub is closer to the lock than the buffering devices, then the lock will connect directly to the hub and the devices won’t help with the buffering/mesh. See the 2nd post on the FAQ link above, it talks about positioning of the repeaters vs the hub and it’s impact when the lock is too close to the hub.

(Head of Support (rboyapps.com)) #1328

NOTE: You should be on version 04.03.00 or newer to be compatible with the new 25.x firmware for V2 and V3 hubs

Universal Enhanced Z-Wave Lock for Schlage, Yale, Kwikset, IDLock, DanaLock, August Pro, Samsung, Locstar, Delaney, KeyWe, Philia and Popp Z-Wave Keypad Device Handler - Version 04.03.08

  • Added support for more KeyWe and Locstar models
  • Added support for Phialia locks with door sensors
  • Improved support for Yale Keyfree/Keyless models
  • Improved compatibility with IDLock 101
  • Alternative identification of lock model if lock has pairing has errors (missing NIF reporting all 0’s)

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

  • < no changes >

A SmartApp like Lock User Management (LUM) or SmartLocks is required for programming user codes.


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) (DPS sensor)
  • Schlage Z-Wave locks (FE469, BE469, BE468, FE599, BE369)
  • Kwikset Z-Wave locks (910, 912, 914, 916)
  • DanaLock Z-Wave locks (V2/V3)
  • August Pro Z-Wave locks (door sensor)
  • IDLock Z-Wave locks (101/150) (door sensor)
  • Samsung Z-Wave locks (SHP-xxx, SHS-xxx)
  • Delaney (ZWxxx)
  • Locstar Z-Wave locks
  • Monoprice Z-Wave locks
  • KeyWe Z-Wave locks (door sensor)
  • Philia Z-Wave locks (door sensor)
  • Popp Z-Wave keypad

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 one time parameters
    • Yale -> relock timeout, wrong code reporting limit, volume level and dps
    • Danalock ->turn speed, brake n go, turn n go and relock timeout
    • IDLock -> volume level, unopened relock
  • Enhanced programming communication for a weak mesh
  • Handling of missing information while pairing locks

Tap the refresh button in the Classic ST app to query the locks capabilities and the supported tiles will show up.

You can find the installation instructions here.

If you’re looking to capture specific events (e.g. invalid codes) and create custom actions/rules in CoRE/WebCoRE refer to this post.

To enable real time updates with the Smart Locks dashboard

Change the name of the device handler in metadata section around line 152 from

name: “Universal Z-Wave Lock With Alarms”

to

name: “Z-Wave Lock”

Click Save -> Publish

Copyright © RBoy Apps