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

Devices & Integrations Community Created Device Types
, , , ,
474

Basically, the person at support who was very nice asked me what I already did and then what I did not really want to do, unpair the devices…
I did unpair / pair the Ecobee Thermostat and that went fine, all sorted out.

That did not work for the Lock though even with the official DTH integration, so he asked me to replace the batteries.
I knew the batteries were recent so, long story short after hanging up, I decided to delete every Lock’s DTH and App, do a hard reset of the lock, reload RBoy’s DTH and App in the Dashboard, and paired again.
I believe the Hard Reset step might have been enough to solve the issue and I’m back now with RBoy’s DTH and it’s still working fine.

So maybe unpair the Lock via the Zwave utilities in the App, Hard reset the lock and Pair it back and check if this solve your issue.

1 Like
475

I just installed this on a Kwikset 910, and so far have been very happy.

I do have a question though, in the event my Internet or ST connection goes down, are the codes that I have setup in the smart app programmed into the lock locally? In other words, do I need to carry a key with me as a backup?

Thanks!

476

They are programmed in the lock locally. Some special features may not work, such as disable after use and other enable/disable code features.

477

Cool! Thanks

478

Does the Enhanced Universal Z-Wave Lock device handler have all the features of the Lock User Code Manager + more? I have 4 Schlage Camelot Touchscreen Deadbolts in my home and wondering if I should do the Enhanced device handler ONLY or if I also need to install the Lock User Code Manager as well.

479

I think you’re confusing the role of a Device Handler (DH) and SmartApp (SA). The DH is responsible for creating an interface to the lock and exposing the ability to use all it’s features (this is what this Universal Z-Wave Lock DH does, it exposes the ability to use all the features on the various Z-Wave locks).
The SA creates use cases/stories that allows the users to make meaning use of devices, in your case the ability to program/schedule/manage users on locks. The SA you’re looking for to this is here:

1 Like
480

@RBoy does this DH support reporting whether the door was unlocked manually from the inside (knob) or outside (key) on Schlage’s BE469?

Thanks.

481

Yes both are reported as “manual” locks (the lock can’t differentiate between inside manual and key as they’re physically connected to the same hardware).

482

Nuts :frowning: Thanks for the confirmation.

483

Got it. Thanks. I went for the Lifetime Package and installed this over the weekend. Is there a way in the app to set each lock to “Auto-Lock” after a certain time period after it’s unlocked (rather than if a door is closed) or do I need to go through the lock settings itself?

1 Like
484

Lock settings, it’s not advisable to auto lock without a sensor as it may end up damaging the door frame (for deadlocks).

1 Like
485

I’m back with that issue again where communication between the Lock and Smartthings seems good (lot of things going on in the logs) but cannot unlock or lock from the app.
Is there anything I should try before again hard reset evrything?

Edit:
Locking / unlocking manually is correctly logged and reported back to the app
Locking / Unlocking from the App generates NO logs
Enabling Autolock is logged but has no effect on the App (have the blue …) and refreshing will restore whatever status it was.
Same for Alarm Off, Audio On, Logged but nothing happens

Here an example of the logs

9:33:04 PM: debug Disabling keypad code unlock
9:32:19 PM: debug deleting code 2
9:32:19 PM: debug setting code 2 to
9:32:04 PM: trace Alarm off | Battery 87%
9:31:59 PM: debug Getting user pin code length
9:31:59 PM: trace refresh sending [‘988100700507’, ‘delay 5000’, ‘988100700504’, ‘delay 5000’, null, ‘delay 5000’, ‘98810070050F’, ‘delay 5000’, ‘988100700503’, ‘delay 5000’, ‘988100700510’, ‘delay 5000’, ‘9881006202’, ‘delay 5000’, ‘9881008002’, ‘delay 5000’]
9:31:59 PM: trace Current user pin code length 4
9:31:59 PM: debug GetSensitiveLevel Current Alarm mode is off -> 0
9:31:59 PM: debug There is no sensitive level when alarm is in off mode
9:31:59 PM: debug Getting auto lock state
9:31:59 PM: debug Getting Sensitivity Level
9:31:59 PM: debug Found Schlage FE/BE469
9:31:59 PM: debug Found Schlage FE/BE469
9:31:59 PM: debug Getting keypad code unlock state
9:31:59 PM: debug Found Schlage FE/BE469
9:31:59 PM: debug Schlage Touchscreen Deadbolt FE469NX Z-Wave Lock is associated to 1
9:31:59 PM: debug Getting Alarm Level
9:31:59 PM: debug Refresh called, Device MSR is 003B-6341-5044
9:31:29 PM: debug Disabling audio/beeper
9:31:19 PM: debug deleting code 1
9:31:19 PM: debug setting code 1 to
9:30:56 PM: debug GetSensitiveLevel Current Alarm mode is alert -> 1
9:30:56 PM: debug Found Schlage FE/BE469
9:30:56 PM: debug Getting Sensitivity Level
9:30:56 PM: debug AlarmToggle Setting Alarm mode to alert -> 1
9:30:56 PM: debug AlarmToggle Current Alarm mode is off
9:30:56 PM: debug Set Alarm Toggle
9:29:36 PM: debug Enabling auto lock
9:27:47 PM: debug "zw device: 11, command: 9881, payload: 00 71 05 00 00 00 FF 06 01 00 " parsed to [‘name’:‘lock’, ‘value’:‘locked’, ‘descriptionText’:Schlage Touchscreen Deadbolt FE469NX Z-Wave Lock was manually locked, ‘data’:[‘type’:‘manual’], ‘isStateChange’:true, ‘displayed’:true, ‘linkText’:‘Schlage Touchscreen Deadbolt FE469NX Z-Wave Lock’]
9:27:47 PM: trace Alarm off | Battery 87%
9:27:47 PM: debug AlarmReport AlarmReport(alarmLevel: 0, alarmType: 0, eventParameter: [], numberOfEventParameters: 0, zensorNetSourceNodeId: 0, zwaveAlarmEvent: 1, zwaveAlarmStatus: 255, zwaveAlarmType: 6)
9:27:32 PM: debug deleting code 2
9:27:31 PM: debug setting code 2 to
9:27:25 PM: debug "zw device: 11, command: 9881, payload: 00 71 05 00 00 00 FF 06 02 00 " parsed to [‘name’:‘lock’, ‘value’:‘unlocked’, ‘descriptionText’:Schlage Touchscreen Deadbolt FE469NX Z-Wave Lock was manually unlocked, ‘data’:[‘type’:‘manual’], ‘isStateChange’:true, ‘displayed’:true, ‘linkText’:‘Schlage Touchscreen Deadbolt FE469NX Z-Wave Lock’]
9:27:25 PM: trace Alarm off | Battery 87%
9:27:25 PM: debug AlarmReport AlarmReport(alarmLevel: 0, alarmType: 0, eventParameter: [], numberOfEventParameters: 0, zensorNetSourceNodeId: 0, zwaveAlarmEvent: 2, zwaveAlarmStatus: 255, zwaveAlarmType: 6)
9:27:14 PM: debug "zw device: 11, command: 9881, payload: 00 71 05 00 00 00 FF 06 01 00 " parsed to [‘name’:‘lock’, ‘value’:‘locked’, ‘descriptionText’:Schlage Touchscreen Deadbolt FE469NX Z-Wave Lock was manually locked, ‘data’:[‘type’:‘manual’], ‘isStateChange’:true, ‘displayed’:true, ‘linkText’:‘Schlage Touchscreen Deadbolt FE469NX Z-Wave Lock’]
9:27:14 PM: trace Alarm off | Battery 87%
9:27:14 PM: debug AlarmReport AlarmReport(alarmLevel: 0, alarmType: 0, eventParameter: [], numberOfEventParameters: 0, zensorNetSourceNodeId: 0, zwaveAlarmEvent: 1, zwaveAlarmStatus: 255, zwaveAlarmType: 6)
9:27:05 PM: debug "zw device: 11, command: 9881, payload: 00 62 03 00 00 00 FE FE " parsed to [‘name’:‘lock’, ‘value’:‘unlocked’, ‘isStateChange’:false, ‘displayed’:false, ‘linkText’:‘Schlage Touchscreen Deadbolt FE469NX Z-Wave Lock’, ‘descriptionText’:Schlage Touchscreen Deadbolt FE469NX Z-Wave Lock lock is unlocked]
9:27:05 PM: trace Alarm off | Battery 87%
9:27:05 PM: debug DoorLockOperationReport DoorLockOperationReport(doorCondition: 0, doorLockMode: 0, insideDoorHandlesMode: 0, lockTimeoutMinutes: 254, lockTimeoutSeconds: 254, outsideDoorHandlesMode: 0)
9:27:00 PM: debug "zw device: 11, command: 9881, payload: 00 71 05 00 00 00 FF 06 02 00 " parsed to [‘name’:‘lock’, ‘value’:‘unlocked’, ‘descriptionText’:Schlage Touchscreen Deadbolt FE469NX Z-Wave Lock was manually unlocked, ‘data’:[‘type’:‘manual’], ‘isStateChange’:true, ‘displayed’:true, ‘linkText’:‘Schlage Touchscreen Deadbolt FE469NX Z-Wave Lock’]
9:27:00 PM: trace Alarm off | Battery 87%
9:27:00 PM: debug AlarmReport AlarmReport(alarmLevel: 0, alarmType: 0, eventParameter: [], numberOfEventParameters: 0, zensorNetSourceNodeId: 0, zwaveAlarmEvent: 2, zwaveAlarmStatus: 255, zwaveAlarmType: 6)
9:26:30 PM: debug deleting code 1
9:26:30 PM: debug setting code 1 to
9:25:46 PM: debug Disabling keypad code unlock
9:25:39 PM: debug Disabling keypad code unlock
9:25:25 PM: debug GetSensitiveLevel Current Alarm mode is alert -> 1
9:25:25 PM: debug Found Schlage FE/BE469
9:25:25 PM: debug Getting Sensitivity Level
9:25:25 PM: debug AlarmToggle Setting Alarm mode to alert -> 1
9:25:25 PM: debug AlarmToggle Current Alarm mode is off
9:25:25 PM: debug Set Alarm Toggle
9:24:49 PM: debug Enabling auto lock
9:24:38 PM: debug deleting code 2
9:24:38 PM: debug setting code 2 to
9:23:38 PM: debug deleting code 1
9:23:38 PM: debug setting code 1 to

486

Likely due to the hub firmware update, getting reports of all kinds of issues with existing devices that have stopped working. The typical symptom is communication from device -> hub works but hub -> device does not work. Also a Z-Wave network repair would fail on such devices.

Try these 2 options (your choice):

  1. Cold reboot - unplug and remove batteries from hub for 30 minutes
  2. Exclude and repair the device
487

anyone able to see the website to download the handler?

488

You need to subscribe to RBOYAPPS to download the device handler. I did and have installed the handler, it works well and there is nothing else similar. It’s not cheap but it does work and if you compare the time to write it yourself it is very cheap.
Jon

489

The website is back up now, had an ISP issue. Thanks for your patience.

490

I unplugged my hub for an hour, and still the same issue…
I guess I should unpair / pair like I did last week .

Even my thermostat is not responding anymore… great… so fed up with Smartthing at the moment… between the routines not triggering and my devices working half way… it’s really annoying.
I guess this is down to the update they did.

491

Frustrating! Please report it to ST support. Until enough folks report it
they won’t accept the firmware has an issue. Right now they are treating it
like independent anomalies

Also if you have a v2 hub you need to remove the batteries also in addition
to unplugging it.

492

Sorry for the basic question but I am new to Smarthome and I am not a developer. This is all very interesting to me and I would like to start learning and setting my home up. Do any of the Smart locks work by detecting you phone and opening automatically when you get near the lock?

493

The only two I know of right now is the Yale Assure lock line and Danalock BTZU (Bluetooth w/Z-Wave). For the Yale lock there is a Z-Wave or ZigBee module you can buy to integrate with SmartThings.

Though it is pricy, I’d recommend the Yale over Danalock.

http://www.yalehome.com/en/yale/yalehome/residential/yale-real-living/yale-real-living-assure-lock-with-bluetooth/

1 Like