SmartThings Community

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

smartapp_security
smartapp_locks
project_locks
adt
rboyapps
#247

The ap did not upload the codes to my schlage Camelot with alarm??

(Never Trust @bamarayne) #248

Auto lock and unlock not working for me, using latest code.

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

See live logging to see what’s going on. Most likely it isn’t receiving notifications from the door sensors.

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

Change the delay and set it to what works best for your setup. Make sure you lock is not more than 15-30 ft from the hub otherwise use a repeater.

#251

I did no difference. Seems it wiped out the standard code though. It seems like its trying to keep me at 4 numbers when all the codes i used were 6

#252

I did no difference. Seems it wiped out the standard code though. It seems like its trying to keep me at 4 numbers when all the codes i used were 6
It also now says jammed all the time but before i added this code it never showed jammed

#253

Using several repeaters and have quick action times. I looked at log and ST keeps sending delete lock codes to the device?? So I assume that’s why none of the codes work. Also, it now shows jammed a lot yet it never showed that before and would at least lock and unlock with simple ST program. Also, this morning once I arrived and finally was able to get in my door the door kept on opening the lock even when I manually closed it or used the ap to close it. I know your stuff works I see the comments but right now I’m lost as to why this is going on.

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

The app is basically a Set if rules which execute based on event notifications it receives. So for some reason the app is receiving a whole bunch of incorrect events.

The question is why is ST or the device sending it all those notifications.

First up try to repair your z-wave network
Second make sure your code length matches the lock code length you cannot use a 6 digit code on a lock that is configured to only work with 4
Third check your activity log, is the door sensor sending it door open events and you’ve configured the app to send a door unlock command then it receives a door open event
Fourth for jam events again it’s subscribes and responds to what it receives. Why is lock sending Jam events? Does the lock need to be reset.
Finally try to delete the smart app and start over with a fresh install maybe it’s corrupted (this more likely with SmartDevices than SmartApps)

Essentially the question to ask is what’s different about your setup/ecosystem who his causing all these events to be generated (door jam, door open etc) when they should not be. The app is just responding to them.

Maybe your lock and sensors need to be reset. Some Schlege locks get stuck in a loop (see the IDE live logging and search this forum for details)

1 Like
(Tim Yuhl) #255

There does seem to be something funny going on with the latest version of your app, RBoy. I had been using a version from 11-21 and I updated to the latest version last Saturday.

The next time I left home, I found that I was locked out when I tried to unlock one of my locks. What I found was that my codes had been wiped. I didn’t have a lot of time to experiment, but what I saw in live logging when I reentered 2 codes was codes getting sent to the locks and then immediately deleted. Looked like messages getting out of sequence, so I cranked up the delay time to 60 sec. and things started working again. My delay previously had been set to the default.

If I have some free time, I’ll do some experiments and capture the logs. The thing is, that 11-21 version of the app had been rock solid since the day I added it.

By the way, don’t get me wrong, this is an awesome app.

1 Like
(James) #257

I was experiencing the same issues so I had to stop using the app. Codes kept getting deleted.

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

The jam event is a subscription event. If the app subscribes to it you get a notification, not all apps use it, this one does (the basic device doesn’t). If you don’t want the Jam event just turn the option off. That’s an issue with your lock sending Jam events. I’ve seen locks send Jam event if the lock is opened too slow or closed too slowly also. It’s very lock dependent, nothing to do with the app. The App just reports what it receives.

Coming to your codes, any code that isn’t used, as a safety measure it will send a delete command for that slot. So you have configured 8 slots and only entered codes for 2 of them, it will send the codes for those 2 and delete the remaining 6. The delay depends completely on your setup. As you can see from the above post @tyuhl found that 60 seconds worked for him. In our labs 5 - 15 second work best for us. Each setup if different, depends up on the layout of the house, devices, distance walls, reflections etc etc. This point has been repeated multiple times on this thread. There is no one answer for everyone. If the codes aren’t being programmed try different delay options, try 5, 30, 60, 120 seconds. See what works for you.

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

@Vessfamily4 @jnschemm see the post above from @tyuhl - you need to find what works for you.

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

Have you looked at live logging to see what’s going on when the device sends the codes to the lock to program it? Is it getting a confirmation from the lock? It’s pretty simple, the app tells the device to send the code to the lock. The rest is up to the SmartDevice and the lock. Maybe you need to repair your lock, some folks (see above) had a similar issue where the lock wasn’t being programmed (it was rejecting it due to an issue with the SmartDevice), delete the lock and re-paried it and it fixed the issue. Sounds like you have the same issue

#263

This shows the code too.

Date

Source

Type

Name

Value

User

Displayed Text

2015-12-09 8:52:49.472 AM EST
2 hours ago DEVICE lockStatus Alarm tamper/low | Battery 100% Frnt Door lock status is Alarm tamper/low | Battery 100%
2015-12-09 8:52:42.240 AM EST
2 hours ago DEVICE lockStatus Alarm tamper/low | Battery 100% Frnt Door lock status is Alarm tamper/low | Battery 100%
2015-12-09 8:52:42.213 AM EST
2 hours ago DEVICE lock locked Frnt Door lock is locked
2015-12-09 8:52:35.573 AM EST
2 hours ago COMMAND setCode setCode(2, 120575) command was sent to Frnt Door
2015-12-09 8:52:35.230 AM EST
2 hours ago APP_COMMAND setCode Door Manager sent setCode command to Frnt Door
2015-12-09 8:52:23.306 AM EST
2 hours ago DEVICE lockStatus Alarm tamper/low | Battery 100% Frnt Door lock status is Alarm tamper/low | Battery 100%
2015-12-09 8:52:23.268 AM EST
2 hours ago DEVICE lock unlocked Frnt Door lock is unlocked
2015-12-09 8:52:20.343 AM EST
2 hours ago COMMAND unlock unlock command was sent to Frnt Door
2015-12-09 8:51:39.733 AM EST
2 hours ago DEVICE lockStatus Alarm tamper/low | Battery 100% Frnt Door lock status is Alarm tamper/low | Battery 100%
2015-12-09 8:51:33.746 AM EST
2 hours ago DEVICE lockStatus Alarm tamper/low | Battery 100% Frnt Door lock status is Alarm tamper/low | Battery 100%
2015-12-09 8:51:30.493 AM EST
2 hours ago COMMAND setCode setCode(1, 073170) command was sent to Frnt Door
2015-12-09 8:51:30.371 AM EST
2 hours ago APP_COMMAND setCode Door Manager sent setCode command to Frnt Door
2015-12-09 8:50:52.440 AM EST
2 hours ago DEVICE lockStatus Alarm tamper/low | Battery 100% Frnt Door lock status is Alarm tamper/low | Battery 100%
2015-12-09 8:50:45.541 AM EST
2 hours ago DEVICE lockStatus Alarm tamper/low | Battery 100% Frnt Door lock status is Alarm tamper/low | Battery 100%
2015-12-09 8:50:43.367 AM EST
2 hours ago COMMAND setCode setCode(1, 073170) command was sent to Frnt Door
2015-12-09 8:50:43.163 AM EST
2 hours ago APP_COMMAND setCode Door Manager sent setCode command to Frnt Door
2015-12-09 8:50:08.092 AM EST
2 hours ago DEVICE lockStatus Alarm tamper/low | Battery 100% Frnt Door lock status is Alarm tamper/low | Battery 100%
2015-12-09 8:50:01.207 AM EST
2 hours ago DEVICE lockStatus Alarm tamper/low | Battery 100% Frnt Door lock status is Alarm tamper/low | Battery 100%
2015-12-09 8:49:59.119 AM EST
2 hours ago COMMAND setCode setCode(1, 073170) command was sent to Frnt Door
2015-12-09 8:49:59.047 AM EST
2 hours ago APP_COMMAND setCode Door Manager sent setCode command to Frnt Door
2015-12-09 8:48:40.593 AM EST
2 hours ago DEVICE lockStatus

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

This isn’t Live Loggin and won’t show errors from your SmartDevice or lock. You need look at Live Logging from the IDE. According to this the command is being sent to the lock, so something is going wrong with communication with the lock. The Live logging will show what.

#265

Logs
Clear

1ee8af38-e0fc-4475-b298-cccecfbd3350 ‎1‎:‎01‎:‎22‎ ‎PM: debug Frnt Door was locked with description: Frnt Door was manually locked

1ee8af38-e0fc-4475-b298-cccecfbd3350 ‎1‎:‎01‎:‎22‎ ‎PM: debug Event name lock, value locked, device Frnt Door, data null

1ee8af38-e0fc-4475-b298-cccecfbd3350 ‎1‎:‎01‎:‎08‎ ‎PM: debug Lock Frnt Door Jammed!

1ee8af38-e0fc-4475-b298-cccecfbd3350 ‎1‎:‎01‎:‎08‎ ‎PM: debug Event name lock, value unknown, device Frnt Door, data null

1ee8af38-e0fc-4475-b298-cccecfbd3350 ‎1‎:‎01‎:‎07‎ ‎PM: debug Lock Frnt Door Jammed!

1ee8af38-e0fc-4475-b298-cccecfbd3350 ‎1‎:‎01‎:‎07‎ ‎PM: debug Event name lock, value unknown, device Frnt Door, data null

1ee8af38-e0fc-4475-b298-cccecfbd3350 ‎1‎:‎01‎:‎00‎ ‎PM: debug Frnt Door was unlocked manually

1ee8af38-e0fc-4475-b298-cccecfbd3350 ‎1‎:‎01‎:‎00‎ ‎PM: debug Event name lock, value unlocked, device Frnt Door, data null

1ee8af38-e0fc-4475-b298-cccecfbd3350 ‎1‎:‎00‎:‎19‎ ‎PM: debug Frnt Door was locked with description: Frnt Door lock is locked

1ee8af38-e0fc-4475-b298-cccecfbd3350 ‎1‎:‎00‎:‎19‎ ‎PM: debug Event name lock, value locked, device Frnt Door, data null

1ee8af38-e0fc-4475-b298-cccecfbd3350 ‎1‎:‎00‎:‎11‎ ‎PM: debug Frnt Door was unlocked manually

1ee8af38-e0fc-4475-b298-cccecfbd3350 ‎1‎:‎00‎:‎11‎ ‎PM: debug Event name lock, value unlocked, device Frnt Door, data null

1ee8af38-e0fc-4475-b298-cccecfbd3350 ‎1‎:‎00‎:‎10‎ ‎PM: debug Frnt Door was locked with description: Frnt Door was manually locked

1ee8af38-e0fc-4475-b298-cccecfbd3350 ‎1‎:‎00‎:‎10‎ ‎PM: debug Event name lock, value locked, device Frnt Door, data null

1ee8af38-e0fc-4475-b298-cccecfbd3350 ‎1‎:‎00‎:‎06‎ ‎PM: debug Frnt Door was unlocked manually

1ee8af38-e0fc-4475-b298-cccecfbd3350 ‎1‎:‎00‎:‎06‎ ‎PM: debug Event name lock, value unlocked, device Frnt Door, data null

1ee8af38-e0fc-4475-b298-cccecfbd3350 ‎12‎:‎59‎:‎50‎ ‎PM: trace Scheduled to run expireCodeCheck at Wed Dec 09 18:04:50 UTC 2015

1ee8af38-e0fc-4475-b298-cccecfbd3350 ‎12‎:‎59‎:‎50‎ ‎PM: trace Added Frnt Door id 63b4b843-0004-4785-8e6e-9e6128949758 back to unprocessed locks expire list [63b4b843-0004-4785-8e6e-9e6128949758]

1ee8af38-e0fc-4475-b298-cccecfbd3350 ‎12‎:‎59‎:‎50‎ ‎PM: trace Frnt Door id 63b4b843-0004-4785-8e6e-9e6128949758 code expire check complete, unprocessed locks [], reset next code update to 1

1ee8af38-e0fc-4475-b298-cccecfbd3350 ‎12‎:‎59‎:‎50‎ ‎PM: trace Checking expired updates for code 2 on Frnt Door

1ee8af38-e0fc-4475-b298-cccecfbd3350 ‎12‎:‎59‎:‎50‎ ‎PM: trace Checking expired updates for code 1 on Frnt Door

1ee8af38-e0fc-4475-b298-cccecfbd3350 ‎12‎:‎59‎:‎50‎ ‎PM: trace Check for pending expired code updates for Frnt Door

1ee8af38-e0fc-4475-b298-cccecfbd3350 ‎12‎:‎59‎:‎50‎ ‎PM: trace ExpireCodeCheck called

1ee8af38-e0fc-4475-b298-cccecfbd3350 ‎12‎:‎59‎:‎50‎ ‎PM: trace Frnt Door id 63b4b843-0004-4785-8e6e-9e6128949758 code updates complete, unprocessed locks [], reset next code update to 1

1ee8af38-e0fc-4475-b298-cccecfbd3350 ‎12‎:‎59‎:‎50‎ ‎PM: trace Check for pending code updates for Frnt Door

1ee8af38-e0fc-4475-b298-cccecfbd3350 ‎12‎:‎59‎:‎25‎ ‎PM: trace Scheduled to run updateCodes at Wed Dec 09 17:59:50 UTC 2015

1ee8af38-e0fc-4475-b298-cccecfbd3350 ‎12‎:‎59‎:‎25‎ ‎PM: trace Scheduled next code update in 25 seconds

1ee8af38-e0fc-4475-b298-cccecfbd3350 ‎12‎:‎59‎:‎25‎ ‎PM: info Frnt Door added user: 2, code: 120575, name: Christina

1ee8af38-e0fc-4475-b298-cccecfbd3350 ‎12‎:‎59‎:‎25‎ ‎PM: debug Updating code 2 on Frnt Door

1ee8af38-e0fc-4475-b298-cccecfbd3350 ‎12‎:‎59‎:‎25‎ ‎PM: trace Check for pending code updates for Frnt Door

1ee8af38-e0fc-4475-b298-cccecfbd3350 ‎12‎:‎59‎:‎00‎ ‎PM: trace Scheduled to run updateCodes at Wed Dec 09 17:59:25 UTC 2015

1ee8af38-e0fc-4475-b298-cccecfbd3350 ‎12‎:‎59‎:‎00‎ ‎PM: trace Scheduled next code update in 25 seconds

1ee8af38-e0fc-4475-b298-cccecfbd3350 ‎12‎:‎59‎:‎00‎ ‎PM: info Frnt Door added user: 1, code: 073170, name: Steven

1ee8af38-e0fc-4475-b298-cccecfbd3350 ‎12‎:‎59‎:‎00‎ ‎PM: debug Updating code 1 on Frnt Door

1ee8af38-e0fc-4475-b298-cccecfbd3350 ‎12‎:‎59‎:‎00‎ ‎PM: trace Check for pending code updates for Frnt Door

1ee8af38-e0fc-4475-b298-cccecfbd3350 ‎12‎:‎58‎:‎59‎ ‎PM: debug Initialization complete, scheduling code updates starting with code 1 in 1 second

1ee8af38-e0fc-4475-b298-cccecfbd3350 ‎12‎:‎58‎:‎59‎ ‎PM: trace Added Frnt Door id 63b4b843-0004-4785-8e6e-9e6128949758 to unprocessed locks update list [63b4b843-0004-4785-8e6e-9e6128949758] and expire list [63b4b843-0004-4785-8e6e-9e6128949758]

1ee8af38-e0fc-4475-b298-cccecfbd3350 ‎12‎:‎58‎:‎59‎ ‎PM: trace Found attribute ‘invalidCode’ on lock Frnt Door, enabled support for invalid code detection

1ee8af38-e0fc-4475-b298-cccecfbd3350 ‎12‎:‎58‎:‎59‎ ‎PM: debug Update Settings: [userNotify4:false, userType2:Permanent, userType10:Permanent, userCodes1:073170, userType12:Permanent, disableAllNotify:true, userType1:Permanent, userType8:Permanent, jamNotify:false, userType5:Permanent, userType4:Permanent, lockNotify:true, userNotify13:false, userType13:Permanent, maxUserNames:2, userNotify11:false, userNotify2:true, userNotify8:false, userNotify9:false, userNotify1:true, userType15:Permanent, userNames2:Christina, userNotify6:false, locks:[Frnt Door], userNotify15:false, homeDisarm:false, userNotify5:false, userType11:Permanent, userNotify12:false, sms:(813) 416-7698, userType14:Permanent, userNotify7:false, sendDelay:25, userCodes2:120575, userType7:Permanent, userNotify10:false, userType3:Permanent, manualNotify:true, userNotify14:false, userNames1:Steven, userNotify3:false, userType6:Permanent, userType9:Permanent]

1ee8af38-e0fc-4475-b298-cccecfbd3350 ‎12‎:‎58‎:‎56‎ ‎PM: debug Initial 2 Name: Christina, Code: 120575, Notify: true, ExpireDate: null, ExpireTime: null, StartDate: null, StartTime: null, UserType: Permanent, UserDayOfWeek: null, UserStartTime: null, UserEndTime: null

1ee8af38-e0fc-4475-b298-cccecfbd3350 ‎12‎:‎58‎:‎56‎ ‎PM: debug Initial 1 Name: Steven, Code: 073170, Notify: true, ExpireDate: null, ExpireTime: null, StartDate: null, StartTime: null, UserType: Permanent, UserDayOfWeek: null, UserStartTime: null, UserEndTime: null

1ee8af38-e0fc-4475-b298-cccecfbd3350 ‎12‎:‎58‎:‎11‎ ‎PM: trace [userNotify4:false, userType2:Permanent, userType10:Permanent, userCodes1:073170, userType12:Permanent, disableAllNotify:true, userType1:Permanent, userType8:Permanent, jamNotify:false, userType5:Permanent, userType4:Permanent, lockNotify:true, userNotify13:false, userType13:Permanent, maxUserNames:2, userNotify11:false, userNotify2:true, userNotify8:false, userNotify9:false, userNotify1:true, userType15:Permanent, userNames2:Christina, userNotify6:false, locks:[Frnt Door], userNotify15:false, homeDisarm:false, userNotify5:false, userType11:Permanent, userNotify12:false, sms:(813) 416-7698, userType14:Permanent, userNotify7:false, sendDelay:25, userCodes2:120575, userType7:Permanent, userNotify10:false, userType3:Permanent, manualNotify:true, userNotify14:false, userNames1:Steven, userNotify3:false, userType6:Permanent, userType9:Permanent]

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

Are you filtering these logs? Because I don’t see the command being sent by the hub to your lock after the app is sending the command to set the code. If you’re filtering, please don’t, you need to see the logs for the door lock which is where you’ll see the issues, not in the app. Again I think you’re misunderstanding the issue here.

there is NO issue with the app. Problem is lying between the SmartDevice, Hub and Lock.

#267

Non filtered. I also just changed the timing on sending the codes so that it would send information to the lock for you to see… see below.

1ee8af38-e0fc-4475-b298-cccecfbd3350 ‎3‎:‎34‎:‎56‎ ‎PM: trace Scheduled to run expireCodeCheck at Wed Dec 09 20:39:56 UTC 2015

1ee8af38-e0fc-4475-b298-cccecfbd3350 ‎3‎:‎34‎:‎56‎ ‎PM: trace Added Frnt Door id 63b4b843-0004-4785-8e6e-9e6128949758 back to unprocessed locks expire list [63b4b843-0004-4785-8e6e-9e6128949758]

1ee8af38-e0fc-4475-b298-cccecfbd3350 ‎3‎:‎34‎:‎56‎ ‎PM: trace Frnt Door id 63b4b843-0004-4785-8e6e-9e6128949758 code expire check complete, unprocessed locks [], reset next code update to 1

1ee8af38-e0fc-4475-b298-cccecfbd3350 ‎3‎:‎34‎:‎56‎ ‎PM: trace Checking expired updates for code 2 on Frnt Door

1ee8af38-e0fc-4475-b298-cccecfbd3350 ‎3‎:‎34‎:‎56‎ ‎PM: trace Checking expired updates for code 1 on Frnt Door

1ee8af38-e0fc-4475-b298-cccecfbd3350 ‎3‎:‎34‎:‎56‎ ‎PM: trace Check for pending expired code updates for Frnt Door

1ee8af38-e0fc-4475-b298-cccecfbd3350 ‎3‎:‎34‎:‎56‎ ‎PM: trace ExpireCodeCheck called

1ee8af38-e0fc-4475-b298-cccecfbd3350 ‎3‎:‎34‎:‎56‎ ‎PM: trace Frnt Door id 63b4b843-0004-4785-8e6e-9e6128949758 code updates complete, unprocessed locks [], reset next code update to 1

1ee8af38-e0fc-4475-b298-cccecfbd3350 ‎3‎:‎34‎:‎56‎ ‎PM: trace Check for pending code updates for Frnt Door

f8eecbae-1e6a-403b-9e76-22e02ea9138f ‎3‎:‎34‎:‎49‎ ‎PM: trace getPhrases(), state.welcomeIssue = null

f8eecbae-1e6a-403b-9e76-22e02ea9138f ‎3‎:‎34‎:‎48‎ ‎PM: trace getPhrases(), state.welcomeIssue = null

63b4b843-0004-4785-8e6e-9e6128949758 ‎3‎:‎34‎:‎38‎ ‎PM: debug "zw device: 08, command: 9881, payload: 00 63 03 02 00 " parsed to [[‘name’:‘codeReport’, ‘value’:2, ‘data’:[‘code’:’’], ‘descriptionText’:Frnt Door code 2 is not set, ‘displayed’:true, ‘isStateChange’:false, ‘linkText’:‘Frnt Door’]]

63b4b843-0004-4785-8e6e-9e6128949758 ‎3‎:‎34‎:‎38‎ ‎PM: trace Alarm tamper/low | Battery 100%

63b4b843-0004-4785-8e6e-9e6128949758 ‎3‎:‎34‎:‎38‎ ‎PM: debug code report parsed to [[‘name’:‘codeReport’, ‘value’:2, ‘data’:[‘code’:’’], ‘descriptionText’:Frnt Door code 2 is not set, ‘displayed’:true, ‘isStateChange’:false, ‘linkText’:‘Frnt Door’]]

63b4b843-0004-4785-8e6e-9e6128949758 ‎3‎:‎34‎:‎30‎ ‎PM: debug "zw device: 08, command: 9881, payload: 00 63 03 02 FE " parsed to [[‘name’:‘codeReport’, ‘value’:2, ‘data’:[‘code’:’’], ‘descriptionText’:Frnt Door code 2 is not set, ‘displayed’:true, ‘isStateChange’:false, ‘linkText’:‘Frnt Door’]]

63b4b843-0004-4785-8e6e-9e6128949758 ‎3‎:‎34‎:‎30‎ ‎PM: trace Alarm tamper/low | Battery 100%

63b4b843-0004-4785-8e6e-9e6128949758 ‎3‎:‎34‎:‎30‎ ‎PM: debug code report parsed to [[‘name’:‘codeReport’, ‘value’:2, ‘data’:[‘code’:’’], ‘descriptionText’:Frnt Door code 2 is not set, ‘displayed’:true, ‘isStateChange’:false, ‘linkText’:‘Frnt Door’]]

1ee8af38-e0fc-4475-b298-cccecfbd3350 ‎3‎:‎34‎:‎27‎ ‎PM: trace Scheduled to run updateCodes at Wed Dec 09 20:34:50 UTC 2015

1ee8af38-e0fc-4475-b298-cccecfbd3350 ‎3‎:‎34‎:‎27‎ ‎PM: trace Scheduled next code update in 23 seconds

1ee8af38-e0fc-4475-b298-cccecfbd3350 ‎3‎:‎34‎:‎27‎ ‎PM: info Frnt Door added user: 2, code: 120575, name: Christina

1ee8af38-e0fc-4475-b298-cccecfbd3350 ‎3‎:‎34‎:‎27‎ ‎PM: debug Updating code 2 on Frnt Door

1ee8af38-e0fc-4475-b298-cccecfbd3350 ‎3‎:‎34‎:‎27‎ ‎PM: trace Check for pending code updates for Frnt Door

63b4b843-0004-4785-8e6e-9e6128949758 ‎3‎:‎34‎:‎27‎ ‎PM: debug setting code 2 to 120575

63b4b843-0004-4785-8e6e-9e6128949758 ‎3‎:‎34‎:‎13‎ ‎PM: debug "zw device: 08, command: 9881, payload: 00 63 03 01 00 " parsed to [[‘name’:‘codeReport’, ‘value’:1, ‘data’:[‘code’:’’], ‘descriptionText’:Frnt Door code 1 is not set, ‘displayed’:true, ‘isStateChange’:false, ‘linkText’:‘Frnt Door’]]

63b4b843-0004-4785-8e6e-9e6128949758 ‎3‎:‎34‎:‎13‎ ‎PM: trace Alarm tamper/low | Battery 100%

63b4b843-0004-4785-8e6e-9e6128949758 ‎3‎:‎34‎:‎13‎ ‎PM: debug code report parsed to [[‘name’:‘codeReport’, ‘value’:1, ‘data’:[‘code’:’’], ‘descriptionText’:Frnt Door code 1 is not set, ‘displayed’:true, ‘isStateChange’:false, ‘linkText’:‘Frnt Door’]]

63b4b843-0004-4785-8e6e-9e6128949758 ‎3‎:‎34‎:‎08‎ ‎PM: debug "zw device: 08, command: 9881, payload: 00 63 03 01 FE " parsed to [[‘name’:‘codeReport’, ‘value’:1, ‘data’:[‘code’:’’], ‘descriptionText’:Frnt Door code 1 is not set, ‘displayed’:true, ‘isStateChange’:false, ‘linkText’:‘Frnt Door’]]

63b4b843-0004-4785-8e6e-9e6128949758 ‎3‎:‎34‎:‎08‎ ‎PM: trace Alarm tamper/low | Battery 100%

63b4b843-0004-4785-8e6e-9e6128949758 ‎3‎:‎34‎:‎08‎ ‎PM: debug code report parsed to [[‘name’:‘codeReport’, ‘value’:1, ‘data’:[‘code’:’’], ‘descriptionText’:Frnt Door code 1 is not set, ‘displayed’:true, ‘isStateChange’:false, ‘linkText’:‘Frnt Door’]]

f8eecbae-1e6a-403b-9e76-22e02ea9138f ‎3‎:‎34‎:‎07‎ ‎PM: trace getPhrases(), state.welcomeIssue = null

1ee8af38-e0fc-4475-b298-cccecfbd3350 ‎3‎:‎34‎:‎04‎ ‎PM: trace Scheduled to run updateCodes at Wed Dec 09 20:34:27 UTC 2015

1ee8af38-e0fc-4475-b298-cccecfbd3350 ‎3‎:‎34‎:‎04‎ ‎PM: trace Scheduled next code update in 23 seconds

1ee8af38-e0fc-4475-b298-cccecfbd3350 ‎3‎:‎34‎:‎04‎ ‎PM: info Frnt Door added user: 1, code: 073170, name: Steven

1ee8af38-e0fc-4475-b298-cccecfbd3350 ‎3‎:‎34‎:‎04‎ ‎PM: debug Updating code 1 on Frnt Door

1ee8af38-e0fc-4475-b298-cccecfbd3350 ‎3‎:‎34‎:‎04‎ ‎PM: trace Check for pending code updates for Frnt Door

63b4b843-0004-4785-8e6e-9e6128949758 ‎3‎:‎34‎:‎04‎ ‎PM: debug setting code 1 to 073170

1ee8af38-e0fc-4475-b298-cccecfbd3350 ‎3‎:‎34‎:‎03‎ ‎PM: debug Initialization complete, scheduling code updates starting with code 1 in 1 second

1ee8af38-e0fc-4475-b298-cccecfbd3350 ‎3‎:‎34‎:‎03‎ ‎PM: trace Added Frnt Door id 63b4b843-0004-4785-8e6e-9e6128949758 to unprocessed locks update list [63b4b843-0004-4785-8e6e-9e6128949758] and expire list [63b4b843-0004-4785-8e6e-9e6128949758]

1ee8af38-e0fc-4475-b298-cccecfbd3350 ‎3‎:‎34‎:‎03‎ ‎PM: trace Found attribute ‘invalidCode’ on lock Frnt Door, enabled support for invalid code detection

1ee8af38-e0fc-4475-b298-cccecfbd3350 ‎3‎:‎34‎:‎03‎ ‎PM: debug Update Settings: [userNotify4:false, userType2:Permanent, userType10:Permanent, userCodes1:073170, userType12:Permanent, disableAllNotify:true, userType1:Permanent, userType8:Permanent, jamNotify:false, userType5:Permanent, userType4:Permanent, lockNotify:true, userNotify13:false, userType13:Permanent, maxUserNames:2, userNotify11:false, userNotify2:true, userNotify8:false, userNotify9:false, userNotify1:true, userType15:Permanent, userNames2:Christina, userNotify6:false, locks:[Frnt Door], userNotify15:false, homeDisarm:false, userNotify5:false, userType11:Permanent, userNotify12:false, sms:(813) 416-7698, userType14:Permanent, userNotify7:false, sendDelay:23, userCodes2:120575, userType7:Permanent, userNotify10:false, userType3:Permanent, manualNotify:true, userNotify14:false, userNames1:Steven, userNotify3:false, userType6:Permanent, userType9:Permanent]

1ee8af38-e0fc-4475-b298-cccecfbd3350 ‎3‎:‎34‎:‎00‎ ‎PM: debug Initial 2 Name: Christina, Code: 120575, Notify: true, ExpireDate: null, ExpireTime: null, StartDate: null, StartTime: null, UserType: Permanent, UserDayOfWeek: null, UserStartTime: null, UserEndTime: null

1ee8af38-e0fc-4475-b298-cccecfbd3350 ‎3‎:‎34‎:‎00‎ ‎PM: debug Initial 1 Name: Steven, Code: 073170, Notify: true, ExpireDate: null, ExpireTime: null, StartDate: null, StartTime: null, UserType: Permanent, UserDayOfWeek: null, UserStartTime: null, UserEndTime: null

a380bb36-676e-4018-bc33-ed72a48e668e ‎3‎:‎33‎:‎38‎ ‎PM: debug Parse returned Richard’s iPhone has arrived

1ee8af38-e0fc-4475-b298-cccecfbd3350 ‎3‎:‎33‎:‎37‎ ‎PM: trace [userNotify4:false, userType2:Permanent, userType10:Permanent, userCodes1:073170, userType12:Permanent, disableAllNotify:true, userType1:Permanent, userType8:Permanent, jamNotify:false, userType5:Permanent, userType4:Permanent, lockNotify:true, userNotify13:false, userType13:Permanent, maxUserNames:2, userNotify11:false, userNotify2:true, userNotify8:false, userNotify9:false, userNotify1:true, userType15:Permanent, userNames2:Christina, userNotify6:false, locks:[Frnt Door], userNotify15:false, homeDisarm:false, userNotify5:false, userType11:Permanent, userNotify12:false, sms:(813) 416-7698, userType14:Permanent, userNotify7:false, sendDelay:25, userCodes2:120575, userType7:Permanent, userNotify10:false, userType3:Permanent, manualNotify:true, userNotify14:false, userNames1:Steven, userNotify3:false, userType6:Permanent, userType9:Permanent]

f8eecbae-1e6a-403b-9e76-22e02ea9138f ‎3‎:‎33‎:‎36‎ ‎PM: trace getPhrases(), state.welcomeIssue = null

f8eecbae-1e6a-403b-9e76-22e02ea9138f ‎3‎:‎33‎:‎35‎ ‎PM: trace getPhrases(), state.welcomeIssue = null

ee64bdaf-ce48-4ddd-a004-5326f703cdf7 ‎3‎:‎33‎:‎34‎ ‎PM: debug summaryData: [[icon:indicator-dot-gray, iconColor:#878787, value:Disarmed], [icon:indicator-dot-green, iconColor:#79b821, value:Everything OK]] - [[icon:indicator-dot-gray, value:Disarmed, iconColor:#878787], [icon:indicator-dot-green, value:Everything OK, iconColor:#79b821]]

1ee8af38-e0fc-4475-b298-cccecfbd3350 ‎3‎:‎33‎:‎13‎ ‎PM: trace Scheduled to run expireCodeCheck at Wed Dec 09 20:38:13 UTC 2015

1ee8af38-e0fc-4475-b298-cccecfbd3350 ‎3‎:‎33‎:‎13‎ ‎PM: trace Added Frnt Door id 63b4b843-0004-4785-8e6e-9e6128949758 back to unprocessed locks expire list [63b4b843-0004-4785-8e6e-9e6128949758]

1ee8af38-e0fc-4475-b298-cccecfbd3350 ‎3‎:‎33‎:‎13‎ ‎PM: trace Frnt Door id 63b4b843-0004-4785-8e6e-9e6128949758 code expire check complete, unprocessed locks [], reset next code update to 1

1ee8af38-e0fc-4475-b298-cccecfbd3350 ‎3‎:‎33‎:‎13‎ ‎PM: trace Checking expired updates for code 2 on Frnt Door

1ee8af38-e0fc-4475-b298-cccecfbd3350 ‎3‎:‎33‎:‎13‎ ‎PM: trace Checking expired updates for code 1 on Frnt Door

1ee8af38-e0fc-4475-b298-cccecfbd3350 ‎3‎:‎33‎:‎13‎ ‎PM: trace Check for pending expired code updates for Frnt Door

1ee8af38-e0fc-4475-b298-cccecfbd3350 ‎3‎:‎33‎:‎13‎ ‎PM: trace ExpireCodeCheck called

(James) #268

@Vessfamily4 You do realize you just posted all your lock codes. You should delete this post.

#269

Thank you… Yes, once I have it working I will be changing them… currently nothing works.