Here’s the log entry for the Master User:
eaca288c-cd72-45b4-8a92-ae6d958300a3 10:17:21 AM: debug "zw device: 02, command: 9881, payload: 00 71 05 13 FB " parsed to ['name':'lock', 'value':'unlocked', 'descriptionText':Front Door was unlocked with code 251, 'data':['usedCode':251, 'type':'keypad'], 'isStateChange':true, 'displayed':true, 'linkText':'Front Door']
eaca288c-cd72-45b4-8a92-ae6d958300a3 10:17:21 AM: trace Battery 90%
eaca288c-cd72-45b4-8a92-ae6d958300a3 10:17:20 AM: debug AlarmReport AlarmReport(alarmLevel: 251, alarmType: 19, eventParameter: , numberOfEventParameters: 0, zensorNetSourceNodeId: 0, zwaveAlarmEvent: 0, zwaveAlarmStatus: 0, zwaveAlarmType: 0)
Is it possible to to the auto lock an “if” feature? That if being that doors sensor reads as closed?
Yes this feature is already present and requires a door sensor to work. Don’t mix this up with the native lock autolock. Some locks have native autolock built into them. The SmartApp has no control over that. The SmartApp uses the door sensor to create an autolock use case but make sure you’ve disabled native autolock on your device
@cscheiene thanks for the logs, so to summarize for the benefit of the community and @Trond_Dyskeland, you’re using IDLock, use following this process:
- Use the Enhanced Z-Wave Device Handler (to support the IDLock lock)
- In the SmartApp enable the option to
Disable Retry and Code Verification (this is because IDLock doesn’t do code programming verification which is an issue with the lock firmware)
- Make sure you clear the codes the first time you install the lock, the procedure is given on the website (www.rboyapps.com), in short enter maximum users 2 for IDLock, click Next, leave the names and codes blank and click Done. Then wait for 5 minutes
- After 5 minutes go in and enter the codes for the 1st user (Master) and 2nd user (Service), click Done and then wait 5 minutes to complete the programming process.
Waiting for 5 minutes is important because the SmartApp uses a dual programming mechanism, the fast programming and then slow programming. IDLock does not support fast programming and hence you need to wait until the slow programming is complete for it to work properly.
Hi and thanks for remembering me.
I was just posting in the Norwegian facebook group that the lock works perfectly now after updating to the latest device handler and Smartapp from you !
The Smartapp reports correct name linked with correct PIN now !
I`ve also tried changing the PINs and names without any issues.
Thanks again for great support.
##door Lock Code Multi User Management with Notifications and Actions - Version 05.05.01
- Added support to report Master Code usage for supporting locks (e.g. Yale, IDLock etc)
Recommend use the [Universal Enhanced Z-Wave Lock] ([RELEASE] Universal Enhanced Z-Wave Lock Driver for Schlage, Yale, Kwikset, IDLock, Popp, Danalock, August Pro, Keywe, Philia, Samsung) device handler version 03.03.00 or newer for full SmartApp and automatic update notification functionality
I am a new user, I hooked up a schlage be469. After setting up your app and entering user names I’m getting these messages in my “recently” tab. They are occurring every minute. The lock and codes appear to be working.
It’s normal for it to verify codes as part of these security feature. If it
continues for more than 30 minutes then you probably didn’t follow the
instructions to clear all codes before programming the new codes after a
fresh install. You can find the procedure listed on our website. (www.rboyapps.com) This only
needs to be when you install the SmartApp for the first time.
How can I receive a notification if an invalid code is entered?
I cleared all the codes and reinstalled the app, still happening.
Is it possible to run a routine if the door is unlocked using the mobile app
It’s automatic. When the lock send the notification to the hub the app will push it to the user. It depends on the lock. Some locks send one notification for each invalid entry (e.g. Yale) while others send one for every X number (e.g. Schlage) of invalid entrees.
You can create a rule in CoRE to detect if it was unlocked with type “remote” and then run a routine.
What does this actually mean?
Some locks support unlocking and locking using the Master Code (e.g. IDLock and Yale), while other like Schlage don’t allow “use” of the locking/unlocking using a Master Code. So now when you have a lock that supports unlocking and locking using the Master Code the app will recognize the user as a Master User. If there are global unlock/lock actions configured it will execute those as well. This notification cannot be turned off for security reasons, you don’t want to miss if anyone uses the Master Code to operate the lock.
Tried an incorrect code but didn’t receive any notification. Any tips? Thanks
Also, how do I specify only remote unlocks?
See my previous post
Some locks send one notification for each invalid entry (e.g. Yale) while others send one for every X number (e.g. Schlage) of invalid entrees
You need to look into your lock’s design, Yale allows you to configure it (which you can do through the Enhanced Z-Wave lock device handler) while others don’t (e.g. Schlage, it send one notification for every 4 invalid codes entered)
It’s the schlage connect, thanks. And how do I specify Core to only run routines with remote unlock? And lock manager will handle the imputed codes for routines
@RBoy I recently purchased your subscription and installed the lock SmartApp for my two Schlage locks. I have been using ST for over 2.5 years and have a great zwave mesh, however I keep getting the verify codes messages in recent history. Here is what I did for the installation:
- Using the Schlage keypad I manually reset all codes.
- Installed the SmartApp and set that I wanted 5 codes but left those blank. Did this before I went to bed knowing it may take time for the SmartApp to clear the codes again.
- Checked recent history this morning and confirmed that the continuous messages went away and that all the codes were cleared.
- Setup 5 codes around several hours ago this morning.
As of this post, several hours later, I am still getting the “code X is not set” messages on both locks. None of the codes work on the lock. Any ideas how to solve this?