SmartThings Community

[RELEASE] Universal Enhanced Z-Wave Lock, Schlage, Yale, Kwikset, IDLock, DanaLock, August Pro, Samsung, Locstar, Delaney, KeyWe 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

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

Check with the company, they may provide a OTA update to ST to push out or they may swap out the lock for you.


(Joe) #467

Ok I’ll call them. I have three lol


(Simon) #468

Thanks, I will also contact them :slight_smile:

But really great doorlock I must say.


(Joe) #469

Yes I love them. You can hear when the battery is getting low. Lol


#470

I have my BE469. Working fine since a year or so. But since several days I cannot remote Lock or Unlock anymore.
What’s weird is that his status is still reported back in the log (when locked and unlocked manually) but no remote control anymore.

Is anyone else having that?


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

Another user recently reported the same issue not just with locks but with
other devices also. He spoke to ST support and they suggested doing a 30
minute cold boot. (Unplug hub for 30 min) and then restart the hub and
repair the network. That seemed to solve the issue (note a simple reboot
didn’t fix it for him). Support is still investigating why it’s happening.


#472

Ok thanks I think that’s what is happening I find out this morning my Ecobee thermostat have the same behavior…
Yesterday I did a simple reboot and ZWave repair without success.
I just tried the cold reboot thing (and of course removing the batteries) but it didn’t help… I guess I need to open a ticket now…


(JTB) #473

I have the same problem. Let me know what happens!


#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.


(Christopher Hubbard) #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.


(Christopher Hubbard) #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.


(www.rboyapps.com - Make your home your butler!) #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:


(Archetyped) #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.


(www.rboyapps.com - Make your home your butler!) #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).


(Archetyped) #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?


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

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


#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