[RELEASE] Door lock code/lock user management (create, delete and schedule codes) with automatic lock/unlock, custom user actions and SHM/ADT integration

smartapp_alerts
dth_locks
smartapp_security
smartapp_locks
rboyapps

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

That depends up on the lock, this Yale model (if memory serves me correctly) does not support reporting or programming RFID cards/fob’s through the Z-Wave interface (some IDLock and Danalock models do). You can verify this easily.
You’re using the Enhanced Z-Wave DH so that good, open the IDE Live Logging, unlock your door using your RFID tag and look at what shows up on Live Logging. Filter the messages ONLY by those from the lock device (not the SmartApp or anything else, top row you can select the source of the logs in the IDE Live Logging).
PM me the messages (copy paste) and we’ll see what’s going on.

As for the reporting, yes you’re correct - we made a change some time ago to not allow only names to avoid confusion and improve reliability. For folks who just want reporting of the lock usage without the programming feature (intentional or not available, e.g. RFID programming), use this SmartApp


#1150

Just for the awareness of others - RBoy and I exchanged some logs from my lock via PM and he’s figured out how to report RFID usage, and that’s now available in the latest (v03.03.03) of the device handler. There are some things which need tweaking in the smart app - specifically, if you have tags and codes on the same slot number it can’t differentiate between them (so line up your slots across the two banks), but I’ve been super impressed with how quickly RBoy turned this around - thanks!


Unlocking Yale Keyless Connected Smart Lock with key tag doesn't send message to Z-Wave Lock device handler
(www.rboyapps.com - Make your home your butler!) #1151

The updated Device Handler release notes, the SmartApp is already equipped to report the usage and will report it as UserX unlocked via RFID or Keypad as appropriate.

As @robal pointed out the way the lock is designed it has overlapping slots (1-20 for keypad codes and 1-20 for rfid codes), so when you’re registering the rfid card make sure you don’t use the same slots as the keypad users if you want the App to report and operate separate actions for each user. So use slots 1-10 for keypad and 11-20 for RFID and it should work fine.

Meanwhile we’re in touch with Yale product development team to try and fix this in the next firmware release.


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

@RBoy,

I have been using your code with a Schlage BE469 for a while now, but sometime in the last few months of updates, I started to see this in my notifications:

<“Lock Name”> was locked by Master Code via keypad.

I can’t be sure, but I think this used to say something about being locked by the Schlage button, but I don’t have the logs from that long ago.

Can you confirm that something changed in your code causing this?

I wanted to check with you that this was the intended result of locking the door from the outside by pushing the Schlage button running under SA 05.05.01 and DH 03.03.01.


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

Thanks for reporting this, yes this was due to a recent change in the Device Handler while adding support for reporting Master Codes. We will patch this up in the next release of the DH.


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

###Door Lock Code Multi User Management with Notifications and Actions - Version 05.05.02

  • Update due to changes in the ST platform, now you can send SMS notifications to multiple numbers by separating them with a *

Recommend use the [Universal Enhanced Z-Wave Lock] ([RELEASE] Universal Enhanced Z-Wave Lock, Schlage Lock, Yale Lock, Kwikset Lock, IDLock, DanaLock and August Lock Device Handler with Alarm Control, Notification, RFID, Door Sensor and advanced features) device handler version 03.03.00 or newer for full SmartApp and automatic update notification functionality


#1155

Hello! @RBoy, I just installed both apps for my new Schlage BE469NX last night. Really great work and appreciate all the work you have put into this. Question, and perhaps I missed it and if I have I’m sorry. Is there anyway to input 6 digit codes? I tried last night but it said it wouldn’t take them that they have to me reduced to 4 digit codes. Thanks and if this has already been answered just ignore, I’m sure I’ll come across it as I continue to search.

So much searching and reading as I am new to all this!
Chad


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

Chad you can enter any number of digits, however as a safety mechanism, when possible, the SmartApp will check with the device handler to confirm what’s the code length programmed in your lock. Some locks like Schlage do report that information which is communicated to the SmartApp which then verifies it while you’re entering it so the programming doesn’t fail (the lock will reject any codes that dont’ match the configured length).

Basically what it is telling if you is that if you want to use 6 digit codes, reconfigure your lock (see your lock manual) to accept 6 digit codes. After reconfiguring the lock don’t forget to click on refresh on your device page in your ST phone so the device handler can get the updated settings from the lock and let the SmartApp know.


#1157

Indeed, worked perfectly! Thank you very much! Now for the rest of my things to show up…ha


(Dean McCracken) #1158

Steps to diagnose rapid battery drain?
I have a Schlage FE599 on a V2 hub at a seasonal rental home. It has been perking along well with your Smartapp for at least a year (two?). I changed the batteries six days ago and they already show the charge as having dropped to 83%.

Today I updated to latest versions of the Smartapp and your DH. I don’t recall which versions I was on. I tend not to make changes from afar, lest I cause a problem that requires a 400 mile round-trip to solve on site. THE QUICK DRAIN PREDATES THESE UPDATES.

I’m at a loss as to the fast drain, however there is one recent change which may be the culprit. I needed to increase the number of code slots. I increased by about three slots 3-4 weeks ago. When I look at the history, I frequently see “[Smartapp] sent deleteCode command to [the lock]” repeating every 1-5 minutes. In addition, once every 60 minutes I see a message: “Unlock using code” which makes no sense to me. Nobody is there to be meticulously entering a code every 60 minutes.

Given I have just updated the software (SmartApp and DH) how should I proceed to troubleshoot?


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

Follow the clear codes procedure on the website to start.

Couple of things to note:
That message your seeing it coming from a poll done by the platform. It’s
basically a setting saying the the keypad coxe unlock is enabled. The
platform polls every hour or so or sometimes more often. Enable the
battery saver option in the device handler settings.
Finally the FE599 has some very questionable quality. We have 3 of them in
our labs and they have drastically different battery lives. One of them
drops 1% a day while another last 1% a week. Neither are used while testing the drain.

Can’t explain it, identical firmware - manufacturing issues.

I would suggest contact Schlage support and request them to replace it.
They are extremely helpful.


(Dean McCracken) #1160

Is there a way to cut/paste the existing codes/configuration, then reset the lock/clear the codes, then paste the data back in?


(Lee Florack) #1161

Not that I’m aware of.


(Dean McCracken) #1162

Thank you for answering, and just to be certain my question is clear, is there a way to reset the lock then restore the names, codes, and access rules I presently have programmed into the lock?


(Lee Florack) #1163

I’m pretty sure that if you wipe out the names/codes, there is (first) no way to copy them or (second) to paste them back.


(Kevin Sime) #1164

Hello @RBoy I’m new to ST and have just installed your Lock Code User Man app and the Universal Extended DH with our new Schlage BE469 with some success. Able to do most of the user code management I need to except the One Time Code. I can set the code, use the code and the code is then deleted. However, a few minutes later the same code is added again by ST. The app states "One time code USED! but I’m able to use it time and again. Have tried re-installing ST app but behaviour remains.

Any idea what’s going on ?


(Dean McCracken) #1165

So, in effort to fully “clear” the configuration, I cleared the codes then reset to factory via lock-specific documentation (Schlage FE599). I excluded the lock then pulled batteries on everything then restarted. Re-included the lock, updated the Rboy device handler (Universal Enhanced…) and then the Rboy Smartapp (Lock Multi User Management…). The Smartapp proceeded to move through the formerly programmed slots and zero them out. I’ve not added any codes at this point.

I am getting an error on lock and one on unlock when using the ST app. Here they are, let me know if you would like the full sequence for context:

On Lock:
a00e3fa7-97c3-4b5c-82de-687e9012a1dc 3:24:12 PM: error groovy.lang.GroovyRuntimeException: Cannot compare java.util.ArrayList with value ‘[]’ and java.lang.Integer with value ‘0’ @ line 1255

On Unlock:
a00e3fa7-97c3-4b5c-82de-687e9012a1dc 3:25:09 PM: error org.codehaus.groovy.runtime.typehandling.GroovyCastException: Cannot cast object ‘[]’ with class ‘java.util.ArrayList’ to class ‘java.lang.Integer’ @ line 1073

Are these expected behavior in the lock’s current state of install? I want to make sure this configuration is airtight as I’ll be 200 miles away all summer with weekly renters needing reliable access!


(Ron) #1166

I’m still having an issue where for some reason I am no longer receiving any notifications when a lock code is used. Everything worked great until May 8th. I’ve uninstalled both the SmartApp and the DeviceHandler and reinstalled the latest versions, 5.05.02 and 3.03.03, and that did not solve the problem.

Anybody else not getting notifications any longer?


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

Thank you for pointing this out, this issue was introduced accidentally during the last release while adding support for master code reporting. We have patched it this up immediately as it’s a critical fix and it’s been released into production. Please update to the latest code and let us know.

@kevinGS@ @Ron_Lu please update to 05.05.03 and see if your issues are resolved (just incase it was a side effect) as then this error was thrown the rest of the code doesn’t execute. With the above resolved it should be rock solid stable again.


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

##Critical Update for users on version 05.05.01 or 05.05.02

###Door Lock Code Multi User Management with Notifications and Actions - Version 05.05.03

  • Fixed a bug which would cause lock/unlock actions to not execute under certain conditions

Recommend use the [Universal Enhanced Z-Wave Lock] ([RELEASE] Universal Enhanced Z-Wave Lock, Schlage Lock, Yale Lock, Kwikset Lock, IDLock, DanaLock and August Lock Device Handler with Alarm Control, Notification, RFID, Door Sensor and advanced features) device handler version 03.03.00 or newer for full SmartApp and automatic update notification functionality