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

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

So, last night I reprogrammed the slot. This morning I get no more of the previous message repeating. Instead, I get:

Date Source Type Name Value User Displayed Text

2016-06-25 9:00:52.084 AM EDT
9 minutes ago APP_COMMAND setCode
2016-06-25 8:58:12.061 AM EDT
12 minutes ago APP_COMMAND setCode
2016-06-25 8:54:34.105 AM EDT
15 minutes ago APP_COMMAND setCode
2016-06-25 8:49:40.100 AM EDT
20 minutes ago APP_COMMAND setCode
2016-06-25 8:45:15.104 AM EDT
24 minutes ago APP_COMMAND setCode
2016-06-25 8:42:47.115 AM EDT
27 minutes ago APP_COMMAND setCode
2016-06-25 8:38:54.057 AM EDT
31 minutes ago APP_COMMAND setCode
2016-06-25 8:34:52.337 AM EDT
35 minutes ago APP_COMMAND setCode
2016-06-25 8:29:43.142 AM EDT
40 minutes ago APP_COMMAND setCode
2016-06-25 8:27:23.156 AM EDT
42 minutes ago APP_COMMAND setCode
2016-06-25 8:23:35.054 AM EDT
46 minutes ago APP_COMMAND setCode
2016-06-25 8:18:40.061 AM EDT
51 minutes ago APP_COMMAND setCode

This is what shows in my Device Handlers: “Universal Z-Wave Lock Device Handler v2.8.5”

The title doesn’t say “rboy : Universal…” but the code it displays when I looDo k inside has rboy all over it… Do you think I have something wrong there?

This is from the device handler:

def clientVersion() {
return “2.8.5”
}

/*

  • Modified by RBoy, SmartThings Z-Wave lock base code as of 2015-12-19
  • Changes Copyright RBoy, redistribution of any changes or modified code is not allowed without permission
  • Change Log
  • 2016-4-20 -

This is from “My Devices”

Main Door Universal Z-Wave Lock With Alarms for Schlage, Yale and Kwikset Bear Lake Bear Lake Hub 04 ACTIVE 5 minutes ago

326

Looks like your lock is stuck in a loop. The FE599 firmware has a bug (see the FAQ’s). Remove the batteries and reset the lock and start over.

327

Ah, crapola. It is a rental cabin and I have renters booked there for the next two months. Drive 200 miles, reset lock, configure, drive 200 miles back.

I think I already know the answer, but do you have any (remote-access) band-aid suggestions to limp along for the next two months?a

In case it adds any further clarity, here is a log:

c0174d36-e16a-4dc0-81f1-b1015c800943 9:36:39 AM: debug deleting code 20
c0174d36-e16a-4dc0-81f1-b1015c800943 9:36:39 AM: debug setting code 20 to 9518
c0174d36-e16a-4dc0-81f1-b1015c800943 9:35:48 AM: debug deleting code 20
c0174d36-e16a-4dc0-81f1-b1015c800943 9:35:48 AM: debug setting code 20 to 9518
c0174d36-e16a-4dc0-81f1-b1015c800943 9:31:53 AM: debug deleting code 20
c0174d36-e16a-4dc0-81f1-b1015c800943 9:31:53 AM: debug setting code 20 to 9518
c0174d36-e16a-4dc0-81f1-b1015c800943 9:31:39 AM: trace Poll called again to soon, skipping poll to save battery
c0174d36-e16a-4dc0-81f1-b1015c800943 9:31:39 AM: debug Poll called, Device MSR is 003B-634B-504C
c0174d36-e16a-4dc0-81f1-b1015c800943 9:27:18 AM: debug deleting code 20
c0174d36-e16a-4dc0-81f1-b1015c800943 9:27:18 AM: debug setting code 20 to 9518

328

Sorry unfortunately no. This is a firmware bug and not an issue with the app or handler. We have two of these locks in our lab and only one of them seems to exhibit this problem so it is likely to be lock related. I would highly recommend that you contact Schalge have to have the lock replaced. They have excellent customer service.
We have tried but haven’t found any way to remotely hard reset or reboot the lock. Even if you do reset the lock physically given that’s it a rental property with frequent code changes it may crop up again in future. The trigger symptom we found is when there are a burst of commands are sent to the lock, the firmware may get stuck into this programming loop (it could be a set or delete or any command but the symptom is a infinite repeat of the same command). We have reported the issue to Schalge. That’s why I suggested a 60 second programming interval.

There is one thing you can try. Send me a PM and I can send a “special” version of the DH which can perform a “soft” reset of the lock remotely but cannot guarantee it will bring the lock out of the loop.

329

I have a Yale YRD220 and am not getting anything other then lock unlock to actually work keep getting the following error.

6580de20-112d-4aac-8b3c-deec37539d14 2:31:13 PM: trace Battery 91%
6580de20-112d-4aac-8b3c-deec37539d14 2:31:08 PM: debug "zw device: 0D, command: 9881, payload: 00 80 03 5B " parsed to [‘name’:‘battery’, ‘unit’:’%’, ‘value’:91, ‘isStateChange’:false, ‘displayed’:false, ‘linkText’:‘Front Door (Yale)’, ‘descriptionText’:Front Door (Yale) battery is 91%]
6580de20-112d-4aac-8b3c-deec37539d14 2:31:08 PM: trace Battery 91%
6580de20-112d-4aac-8b3c-deec37539d14 2:31:04 PM: trace Battery 91%
6580de20-112d-4aac-8b3c-deec37539d14 2:31:03 PM: debug "zw device: 0D, command: 9881, payload: 00 62 03 00 00 02 FE FE " parsed to [‘name’:‘lock’, ‘value’:‘unlocked’, ‘isStateChange’:false, ‘displayed’:false, ‘linkText’:‘Front Door (Yale)’, ‘descriptionText’:Front Door (Yale) lock is unlocked]
6580de20-112d-4aac-8b3c-deec37539d14 2:31:03 PM: trace Battery 91%
6580de20-112d-4aac-8b3c-deec37539d14 2:31:03 PM: debug DoorLockOperationReport DoorLockOperationReport(doorCondition: 2, doorLockMode: 0, insideDoorHandlesMode: 0, lockTimeoutMinutes: 254, lockTimeoutSeconds: 254, outsideDoorHandlesMode: 0)
6580de20-112d-4aac-8b3c-deec37539d14 2:31:02 PM: trace Battery 91%
6580de20-112d-4aac-8b3c-deec37539d14 2:30:58 PM: debug "zw device: 0D, command: 9881, payload: 00 70 06 01 01 00 " parsed to [‘name’:‘beeper’, ‘descriptionText’:‘Audio Mode’, ‘displayed’:true, ‘isStateChange’:true, ‘value’:‘unknown’, ‘linkText’:‘Front Door (Yale)’]
6580de20-112d-4aac-8b3c-deec37539d14 2:30:58 PM: trace Battery 91%
6580de20-112d-4aac-8b3c-deec37539d14 2:30:58 PM: debug Processing Yale Configuration Report
6580de20-112d-4aac-8b3c-deec37539d14 2:30:58 PM: debug ConfigurationReport ConfigurationReport(configurationValue: [0], parameterNumber: 1, reserved11: 0, size: 1)
6580de20-112d-4aac-8b3c-deec37539d14 2:30:53 PM: debug "zw device: 0D, command: 9881, payload: 00 70 06 02 01 00 " parsed to [‘name’:‘autolock’, ‘descriptionText’:‘Auto lock’, ‘displayed’:true, ‘isStateChange’:true, ‘value’:‘disabled’, ‘linkText’:‘Front Door (Yale)’]
6580de20-112d-4aac-8b3c-deec37539d14 2:30:53 PM: trace Battery 91%
6580de20-112d-4aac-8b3c-deec37539d14 2:30:53 PM: debug Processing Yale Configuration Report
6580de20-112d-4aac-8b3c-deec37539d14 2:30:53 PM: debug ConfigurationReport ConfigurationReport(configurationValue: [0], parameterNumber: 2, reserved11: 0, size: 1)
6580de20-112d-4aac-8b3c-deec37539d14 2:30:50 PM: trace Battery 91%
6580de20-112d-4aac-8b3c-deec37539d14 2:30:43 PM: debug "zw device: 0D, command: 9881, payload: 00 70 06 08 01 00 " parsed to [‘name’:‘codeunlock’, ‘descriptionText’:‘Unlock using code’, ‘displayed’:true, ‘isStateChange’:true, ‘value’:‘enabled’, ‘linkText’:‘Front Door (Yale)’]
6580de20-112d-4aac-8b3c-deec37539d14 2:30:43 PM: trace Battery 91%
6580de20-112d-4aac-8b3c-deec37539d14 2:30:43 PM: debug Processing Yale Configuration Report
6580de20-112d-4aac-8b3c-deec37539d14 2:30:43 PM: debug ConfigurationReport ConfigurationReport(configurationValue: [0], parameterNumber: 8, reserved11: 0, size: 1)
6580de20-112d-4aac-8b3c-deec37539d14 2:30:38 PM: debug "zw device: 0D, command: 9881, payload: 00 70 06 07 01 3C " parsed to [‘displayed’:false, ‘descriptionText’:Front Door (Yale): Parameter 7 configuration [60], ‘isStateChange’:false, ‘linkText’:‘Front Door (Yale)’]
6580de20-112d-4aac-8b3c-deec37539d14 2:30:38 PM: trace Battery 91%
6580de20-112d-4aac-8b3c-deec37539d14 2:30:38 PM: debug Processing Yale Configuration Report
6580de20-112d-4aac-8b3c-deec37539d14 2:30:38 PM: debug ConfigurationReport ConfigurationReport(configurationValue: [60], parameterNumber: 7, reserved11: 0, size: 1)
6580de20-112d-4aac-8b3c-deec37539d14 2:30:35 PM: trace refresh sending [‘988100700507’, ‘delay 5000’, ‘988100700508’, ‘delay 5000’, null, ‘delay 5000’, ‘988100700502’, ‘delay 5000’, ‘988100700501’, ‘delay 5000’, ‘9881006202’, ‘delay 5000’, ‘9881008002’, ‘delay 5000’]

330

I dont’ see any error, everything looks good. It seems to be fine. It’s reporting battery, unlocked with code, your beeper status etc.

331

But everything other then lock and unlock are unsupported on the device screen? is this normal

332

According to your logs it’s reporting the information. For some reason your ST phone app is not showing it. Trying killing the app and restarting it.

333

No ggod from any device it is the same.

6580de20-112d-4aac-8b3c-deec37539d14 11:37:42 AM: trace Battery 90%
6580de20-112d-4aac-8b3c-deec37539d14 11:37:37 AM: trace refresh sending [‘988100700507’, ‘delay 5000’, ‘988100700508’, ‘delay 5000’, null, ‘delay 5000’, ‘988100700502’, ‘delay 5000’, ‘988100700501’, ‘delay 5000’, ‘9881006202’, ‘delay 5000’, ‘9881008002’, ‘delay 5000’]
6580de20-112d-4aac-8b3c-deec37539d14 11:37:37 AM: debug Found Yale Touch Deadbolt
6580de20-112d-4aac-8b3c-deec37539d14 11:37:37 AM: debug Getting audio/beeper state
6580de20-112d-4aac-8b3c-deec37539d14 11:37:37 AM: debug Found Yale Touch Deadbolt
6580de20-112d-4aac-8b3c-deec37539d14 11:37:37 AM: debug Getting auto lock state
6580de20-112d-4aac-8b3c-deec37539d14 11:37:37 AM: debug Lock Alarm mode not configured or not supported, deferring getting Alarm sensitivity level.
6580de20-112d-4aac-8b3c-deec37539d14 11:37:37 AM: debug Unsupported device with MSR 0109-0002-FFFF, Alarm Sensitivity feature may not be available
6580de20-112d-4aac-8b3c-deec37539d14 11:37:37 AM: debug Getting Sensitivity Level
6580de20-112d-4aac-8b3c-deec37539d14 11:37:37 AM: debug Found Yale Touch Deadbolt
6580de20-112d-4aac-8b3c-deec37539d14 11:37:37 AM: debug Getting keypad code unlock state
6580de20-112d-4aac-8b3c-deec37539d14 11:37:37 AM: debug Unsupported device with MSR 0109-0002-FFFF, Alarm feature may not be available
6580de20-112d-4aac-8b3c-deec37539d14 11:37:37 AM: debug Getting Alarm Level
6580de20-112d-4aac-8b3c-deec37539d14 11:37:37 AM: debug Front Door (Yale) is associated to 1
6580de20-112d-4aac-8b3c-deec37539d14 11:37:37 AM: debug Found Yale Touch Deadbolt
6580de20-112d-4aac-8b3c-deec37539d14 11:37:37 AM: trace Identifying specific lock model from database of known models
6580de20-112d-4aac-8b3c-deec37539d14 11:37:37 AM: debug Refresh called, Device MSR is 0109-0002-FFFF

334

@RBoy I noticed the lock shows up as a motion detector in ST. Is the motion tied to lock/unlock of the deadbolt or is there actually a motion sensor on it?

335

###Universal Enhanced Z-Wave Lock and Schlage Lock, Yale Lock and Kwikset Lock Device Handler - Version 2.9.0

  • Added support for external keypad button locked attribute outsideLockEvent

This allows the lock to report if the external lock button was pressed on the keypad and SmartApps to use that functionality to take actions. E.g.

2 Likes
336

I don’t know about everyone else but this functionality is going to be huge for me!

1 Like
337

Instead of relying on the geofencing hokey pokey you now have both sides covered based of keying code or locking the door.

The only thing better would be to specialize by user.

1 Like
338

In the next version…

2 Likes
339

Its motion detection I believe based on the alarm being enabled. I don’t see it reporting motion otherwise but will test further tonight and respond back.

Further, I want to give props to RBoy on this app. It is great for code managemet which is not inherant in the default handler. I tried a couple of the other smartapps posted on here and they were hit and miss.

The ability to set the alarm for my schlage locks that have alarms, control sensitivity of the alarm, vacation mode as well as codes is huge.

I was even able to set it up so when a code is input and its after dark the inside light is turned on as well.

I was able to comment out the unlock code so “remote unlock” is not possible. Anyone interested in that as an alternate handler should message rboy to let him know.

1 Like
340

###Universal Enhanced Z-Wave Lock and Schlage Lock, Yale Lock and Kwikset Lock Device Handler - Version 2.10.2

  • Improved support for Yale locks, added ability to configure auto relock time and wrong entry tamper alert limits in the configuration page
  • Added support for Yale user code based locks
  • Added support for Yale external one touch lock
  • Fixed issue with base ST device handler sending tamper instead of invalid code alerts

This allows the lock to report if the external lock button or a code was used to lock via the keypad and SmartApps to use that functionality to take actions. E.g.

Thanks to @Horse3109 for his time and lock :slight_smile:

EDIT: 2.10.2 fixes a issue with 2.10.1 Yale locks’ not reporting code locks from the keypads correctly

2 Likes
341

after installing both the DH and SA i am getting constant code limit reached alarms when no one touching the lock.

342

In order to replace my current device handler, do I need to import the code in and assign the handler to the device?

Also,once that is done I assume I will need to reconfigure all my codes again? Will those old codes just be wiped from the device?

343

You should just be able to replace the code for the current handler, save and publish

344

All my settings and associated rules will continue to work?