That could be done depending upon the lock, if it supports disabling the keypad. I guess this could be looking into as a feature enhancement but what’s the use case. When in mode Away disable keypad entry? Isn’t that that point of the keypad codes is to allow folks to enter when away? I’m trying to see the practical aspect of it, it could be done very easily using CoRE but to build it into the app we need to understand how it will be used so that it can be designed effectively.
[RELEASE] Lock User Management: Door lock code manager (create, delete and schedule codes) with automatic lock/unlock, custom user actions and SHM/ADT integration
Ok - understood and thanks for the advice.
On a related note - can you programme RFID tags on a Yale Keyless Connected Smart Lock using the app?
Also, the lock specification says it can have up to 20 tags or codes. If I set the app to manage 20 slots, does it erase/overwrite the RFID tags programmed directly on the unit?
Programming RFID tags depends upon the device handler (the SmartApp only sends and received programming notifications).
If you’re using the Enhanced Z-Wave DH it supports reading and notifying RFID tags but not programming them (yet). RFID programming is very complicated so we decided not to implement it through ST for the simple reason that once tags are programmed you don’t normally un-program them hence you can it manually through the lock directly which will be an easier solution than trying to read the card numbers, entering it into ST and then having ST program them (and if you enter one incorrect number it won’t work etc) - hence the decision to have users program them directly.
Once programmed the Enhanced Z-Wave DH can read and report them and this SmartApp can also report and take action accordingly (it will notify the user that a RFID tag was used to unlock the door as reported by the DH).
Some locks like IDLock/Yale/Danalock support both keypad codes and RFID codes. The Enhanced Z-Wave Device Handler will take care of that, so when you’re programming the codes through this SmartApp the DH will only program the codes for the keypad and will not overwrite the codes for the RFID part. So if you lock supports 20 RFID tags and 2 keypad codes, the SmartApp program program the 2 users but will be able to report if the users used any of the 20 RFID tags to unlock the door. The user slots will depend upon your lock configuration, you can figure it our quite easily by entering names in your slots (e.g. User 1, User 2 etc) and then unlock the door using the RFID tags and keypad tags and see what the SmartApp reports for the user slots. It’s possible that keypad users slot number and RFID slot number may overlap (e.g. master code may be user 1 where as service code may be user 2 but RFID tags also start from user 1), in that case while entering the codes just don’t use 1 and 2 slots for RFID and start from User 3 for the RFID users.
For RFID users just enter the names and leave the codes blank (and also make sure you’re
Enabled the option to Disable code verification/retry on the first page). This will allow the SmartApp to report the users using RFID tags but won’t overwrite the programming done on the lock.
Hope this helps.
Thanks for the detailed reply.
the main advantage is the ability to schedule RFID tags. Is it possible?
I’m using this one: https://smartthings.rboyapps.com/Devices/Z-Wave%20Lock%20with%20Alarm.groovy.txt
The lock seems to have 40 slots, 20 for tags and 20 for codes, and you can use up to 20 (mixed across the two sets of slots) at a time. I also have a couple of RFID tags programmed directly on the lock. I have the app set to “number of users” = 5. I get notifications when the codes are used, but not RFID tags. So reading your reply, I believe I need to increase the “number of users” to 40 - correct?
I’ve set “Enable incremental updates only and disable re-verification” to “on” on the first page, but when i go to the second page and try to save entries with names but no code value, i get the message
Oops! Looks like you need to double-check some inputs.
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
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
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, Delaney, KeyWe Locks and Popp Z-Wave Keypad Device Handler with Alarm Control, Notification, RFID, Door Sensor and advanced features
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.
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.
###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
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 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.
Indeed, worked perfectly! Thank you very much! Now for the rest of my things to show up…ha
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?
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.
Is there a way to cut/paste the existing codes/configuration, then reset the lock/clear the codes, then paste the data back in?
Not that I’m aware of.
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?
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.
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 ?