Please look at the posts in the past week or so. This is NOT an app issue, it's an issue with the platform or issue with the communication / lock. There is no problem with the app (it was working earlier and not working now, it's not an app issue since nothing has changed with the app)
[RELEASE] Door lock code/lock user management (create, delete and schedule codes) with automatic lock/unlock, custom user actions and SHM integration
I've posted an update, version 2.4.6 in an attempt to work around the broken platform issue where timers are dying. It seems to be impacting v2 hub users so if you're facing the issue that the app suddenly stops working (update to locks) after a few hours/days, then try this new version. Also don't forget to report to ST support that you're facing issues with timers dying in your apps.
@RBoy How do I get notified when someone puts an invalid code in my locks? I tried your Schlage device type code and also my original zWave lock device type code, and I don't see anything in the IDE logs or device logs or in the mobile app about bad codes being entered. I recall when using Lock Manager from @ethayer, I used to see bad attempts in the mobile app logs. However, I would think the mobile app logs for the device have nothing to do with the smartapp that sets the codes, right? That should be related to the device type, correct?
It depends upon your lock implementation, as I had mentioned earlier if you lock sends the invalid code notification to the ST platform and SmartDevice captures those codes and reports it as the attribute "invalidCode" to the ST platform, this SmartApp will capture it and notify the user. You'll have to debug your lock in live logging to see if it is receiving the invalid code notification from your lock and how your SmartDevice is handling it. The Schlage SmartDevice written by me is for Schlage devices, so it may or may not capture the event (if your lock is sending it). You'll need to debug and see what ZWave codes your lock sends for invalid codes. Once you have the codes you can PM me with the live logging and I'll see how to adapt the SmartDevice to capture those.
I'm new to this app, and might not have seen it, but is it possible to link the alarm that's built into my lock (Schlage Connect BE469) so that when my Home Monitor detects unauthorized entry (via door sensors/motion sensors) it triggers the alarm on the door? In other words, can I use my lock's alarm as my security alarm so I don't have to buy a separate one? Thanks!
No, the lock doesn't allow external triggering of the alarm, but that's discussed on this thread since it's a hardware feature.
I am moving from Nexia to ST. I have a Schlage deadbolt and a Schlage FE599 keypad lever lock. The deadbolt seem to work ok, it report back the user that entered a user code to unlock the deadbolt. However the FE599 is not reporting the user. The codes are getting programmed in and work to unlock the lock, there is not a message being logged by ST. Any suggestions?
It worked great with Nexia, was just tired of paying the monthly fee. It stopped working when I enrolled it into ST. As part of debugging, I enrolled it back in Nexia and also noticed no user codes being reported. Next, I did a factory reset, enrolled it back into Nexia and it works. I enrolled it back in to ST and it did not work. I did another factory reset and enrolled it back in to ST and it still don't report user codes. (yes, before I enrolled it each time, I un-enrolled it first) My guess is I need an updated device driver, but not sure. From what I read earlier, the updated device driver was for the deadbolt, not for the FE599. Anyone else having a similar problem?
If you aren't seeing any messages in live logging when the you use a code then there's a communication problem with your lock and ST hub. Irrespective of your driver you should see debug messages coming into live logging. It could be a defective lock.
Just wanted to say thank you for this SmartApp, it's amazing! Just what I needed.
@RBoy thanks for the response. Live logging has user open code for the deadbolt but not the FE599. The FE599 has other messages, just not reporting when a user code is entered:
2015-12-22 12:07:42.360 PM UTC
moments ago DEVICE lock unlocked Basement Door lock is unlocked
2015-12-22 12:07:41.639 PM UTC
moments ago COMMAND unlock unlock command was sent to Basement Door
2015-12-22 12:07:30.113 PM UTC
moments ago DEVICE lock locked Basement Door lock is locked
2015-12-22 12:07:29.399 PM UTC
moments ago COMMAND lock lock command was sent to Basement Door
In the above, "Basement Door" is the FE599.
I was thinking like you, that it was a communication problem. However, when I switched it back to Nexia, it works so I don't think it is a defective lock. Question, should the FE599 work with your SmartApp using the default driver, I do I need toI update to a different driver? Thanks.
RBoy, yesterday I was about to return my FE599 lock, as I was disappointed that with the ST hub I could only lock/unlock it... and I needed more... Luckily I stumbled upon your SmartApp... a 10$ very well spent, I highly recommend it, good job, thanks!
I do have one question though, when i get the SMS message on unlock I get a message like this:
"Z-Wave Lock was unlocked by Eduardo"
however when I look at the logs in the smarthings app i dot get the name but user number:
"Z-Wave lock was unlocked with code 3"
Is there anything I can do to get the name instead of the code?
@ealdaz if you're looking at the device activity log that's controlled by the device and not smart app can post to it.
However if you're looking at the General Recent Log you'll see the message. Don't look at the device logs.
Just got access to this app. Quick question; Is it safe to install this if I have another lock manager currently installed? I'm having issues with it and want try this one out. Problem is I am 1300 miles away from the lock and want to make sure this wouldn't wipe out any existing codes the other app set.
The short answer is yes. You can have multiple apps manage separate locks. I was using three separate apps to manage my three locks while I decided which one I liked. During the process of switching back and forth I did manage to 'hose' my locks. There were a few times I had to reset the locks because I couldn't get any of the codes to work. I'm sure this was user error on my part but unless you are absolutely sure of what you are doing you could end up having to reset your locks. This was not an issue for me because I could just yell at my locks and the computer before going over and resetting them. If I were 1300 miles away I'm not sure I would take the chance unless I had someone onsite to assist me. I'm sure you could work this out if you were willing to put in the time to figure out the nuances of each app.
Take it for what it's worth. You may have a different experience.
Quick point, yes it will wipe out all existing codes and replace them with those you specify in the app. There is not way for the app to "read" existing codes. So before you start make sure you have the codes you want to program in (again it will only overwrite the first X codes depending upon how many max codes you specify in the app).
Hi @RBoy - quick question. Last weekend Installed a brand new FE599 using your device type and app. (I also have a BE469 that works perfectly with your app/device).
Both last weekend and now I have tried to set the codes but only the first one takes. I have swapped slot 1 and slot 2, so i know it is not the code itself - and frankly I am trying to set the codes the same as my BE469. I increased the code update time to 60 seconds and that still didn't work.
Any other ideas? here is some of my live log
4:15:23 PM CST: trace Check for pending code updates for Garage Service
55fe2c77-a1f4-4be5-9f08-94e25393db1a 4:14:13 PM CST: trace Scheduled to run updateCodes in Wed Dec 30 22:15:13 UTC 2015 seconds
55fe2c77-a1f4-4be5-9f08-94e25393db1a 4:14:13 PM CST: trace Scheduled next code update in 60 seconds
55fe2c77-a1f4-4be5-9f08-94e25393db1a 4:14:13 PM CST: info Garage Service added user: 4, code: xxxx, name: bbbb
55fe2c77-a1f4-4be5-9f08-94e25393db1a 4:14:12 PM CST: debug Updating code 4 on Garage Service
55fe2c77-a1f4-4be5-9f08-94e25393db1a 4:14:12 PM CST: trace Check for pending code updates for Garage Service
55fe2c77-a1f4-4be5-9f08-94e25393db1a 4:13:12 PM CST: trace Scheduled to run updateCodes in Wed Dec 30 22:14:12 UTC 2015 seconds
55fe2c77-a1f4-4be5-9f08-94e25393db1a 4:13:12 PM CST: trace Scheduled next code update in 60 seconds
55fe2c77-a1f4-4be5-9f08-94e25393db1a 4:13:12 PM CST: info Garage Service added user: 3, code: xxxx, name: aaaa
55fe2c77-a1f4-4be5-9f08-94e25393db1a 4:13:10 PM CST: debug Updating code 3 on Garage Service
55fe2c77-a1f4-4be5-9f08-94e25393db1a 4:13:10 PM CST: trace Check for pending code updates for Garage Service
55fe2c77-a1f4-4be5-9f08-94e25393db1a 4:12:10 PM CST: trace Scheduled to run updateCodes in Wed Dec 30 22:13:10 UTC 2015 seconds
55fe2c77-a1f4-4be5-9f08-94e25393db1a 4:12:10 PM CST: trace Scheduled next code update in 60 seconds
55fe2c77-a1f4-4be5-9f08-94e25393db1a 4:12:10 PM CST: info Garage Service added user: 2, code: xxxx, name: zzzz
55fe2c77-a1f4-4be5-9f08-94e25393db1a 4:12:08 PM CST: debug Updating code 2 on Garage Service
55fe2c77-a1f4-4be5-9f08-94e25393db1a 4:12:08 PM CST: trace Check for pending code updates for Garage Service
55fe2c77-a1f4-4be5-9f08-94e25393db1a 4:11:08 PM CST: trace Scheduled to run updateCodes in Wed Dec 30 22:12:08 UTC 2015 seconds
55fe2c77-a1f4-4be5-9f08-94e25393db1a 4:11:08 PM CST: trace Scheduled next code update in 60 seconds
55fe2c77-a1f4-4be5-9f08-94e25393db1a 4:11:08 PM CST: info Garage Service added user: 1, code: xxxx, name: yyyy
55fe2c77-a1f4-4be5-9f08-94e25393db1a 4:11:05 PM CST: debug Updating code 1 on Garage Service
55fe2c77-a1f4-4be5-9f08-94e25393db1a 4:11:05 PM CST: trace Check for pending code updates for Garage Service
55fe2c77-a1f4-4be5-9f08-94e25393db1a 4:11:04 PM CST: debug Initialization complete, scheduling code updates starting with code 1 in 1 second
55fe2c77-a1f4-4be5-9f08-94e25393db1a 4:11:04 PM CST: trace Scheduled to run updateCodes in Wed Dec 30 22:11:05 UTC 2015 seconds
55fe2c77-a1f4-4be5-9f08-94e25393db1a 4:11:04 PM CST: trace Added Garage Service id 4087b15e-5f31-40ca-af2f-950136372618 to unprocessed locks update list [4087b15e-5f31-40ca-af2f-950136372618] and expire list [4087b15e-5f31-40ca-af2f-950136372618]
55fe2c77-a1f4-4be5-9f08-94e25393db1a 4:11:04 PM CST: trace Found attribute 'invalidCode' on lock Garage Service, enabled support for invalid code detection
55fe2c77-a1f4-4be5-9f08-94e25393db1a 4:11:04 PM CST: debug Update Settings: [userType4:Permanent, userNotify4:true, userNames3:aaaa, userType3:Permanent, userCodes4:xxxx, userCodes1:xxxx, disableAllNotify:false, userNames2:zzzz, userType2:Permanent, userCodes2:xxxx, userNotify2:false, maxUserNames:4, userNotify3:true, userCodes3:1423, jamNotify:false, manualNotify:false, userNames1:yyyy, lockNotify:false, locks:[Garage Service], homeDisarm:false, userNames4:bbbb, userType1:Permanent, sendDelay:60, userNotify1:false]
55fe2c77-a1f4-4be5-9f08-94e25393db1a 4:10:47 PM CST: debug Initial 4 Name: bbbb, Code: 0218, Notify: true, ExpireDate: null, ExpireTime: null, StartDate: null, StartTime: null, UserType: Permanent, UserDayOfWeek: null, UserStartTime: null, UserEndTime: null
55fe2c77-a1f4-4be5-9f08-94e25393db1a 4:10:47 PM CST: debug Initial 3 Name: aaaa, Code: xxxx, Notify: true, ExpireDate: null, ExpireTime: null, StartDate: null, StartTime: null, UserType: Permanent, UserDayOfWeek: null, UserStartTime: null, UserEndTime: null
55fe2c77-a1f4-4be5-9f08-94e25393db1a 4:10:47 PM CST: debug Initial 2 Name: zzzz, Code: xxxx, Notify: false, ExpireDate: null, ExpireTime: null, StartDate: null, StartTime: null, UserType: Permanent, UserDayOfWeek: null, UserStartTime: null, UserEndTime: null
55fe2c77-a1f4-4be5-9f08-94e25393db1a 4:10:47 PM CST: debug Initial 1 Name: yyyy, Code: xxxx, Notify: false, ExpireDate: null, ExpireTime: null, StartDate: null, StartTime: null, UserType: Permanent, UserDayOfWeek: null, UserStartTime: null, UserEndTime: null
It's a communication issue with your lock, see my first post.
General Troubleshooting Tips
The programming to user codes is a communication between the Hub and the Lock. If there is an issue with the programming it's because of communication issues between the lock and hub and you can use the below step to troubleshoot it. Please remember that Z-Wave is generally a slow high latency network with VERY limited distance. Multiple factors can affect the performance and stability of a Z-Wave network including distance between the hub and Z-Wave devices, location of "active" Z-Wave repeater devices, walls/objects (reflections) in between, the order in which the "active" repeater devices can online and registered with hub (yes this is a factor too!) etc.
- Restart the ST hub (unplug and replug it, not a reboot). This resolves 50% of issues
- Change the programming delay in the SmartApp (on the first page at the bottom, last option). The default is 15 seconds between codes, some folks have success with 5, some with 10, some with 30 and some with 60. This number depends on a variety of factors (listed in the para above including distance, type, order, location etc). It will vary for EACH user and EACH lock sometimes depending upon your setup. Experiment and see what works!. This resolves another 45% of issues.
3. Sometimes the locks are stuck on a loop (defective firmware especially FE599) jamming the network. Remove the batteries from your lock and reset it.
- If the gap between the hub and lock is too much it may not be able to reliably communicate. Try to bring your hub closer or install a "active" Z-Wave repeater device in between them.
- Click on repair Z-Wave network in the Hub utilities (through your ST smartphone or the IDE). This can help reconfigure the network to take care of active devices which came online and are "out of order" and helps optimize the network. This can take 10-15 minutes while the hub reconfigures and optimizes the Z-Wave network.
- Please MAKE SURE you've configured the lock to use the same code length as the number of digits you're you're entering for each code in the app. If the number of digits in the code entered in the app does not match the code length configured on the lock it WILL NOT work.
Thanks for your quick reply - I tried a couple of your troubleshooting methods with no success. I ended up removing the lock (just 2 screws, no big deal) and bringing it closer to the hub just to get the codes set.
My confusion was why the first code was being set but none of the others. Oh well, got it set up now. Thanks!
Okay revamped the code to make it HUGELY more reliable in coding now. Starting version 3.0.0 the SmartApp will work closely with the Lock to ensure that the "programming" of the codes are successful and if not (for whatever reasons) it will keep trying indefinitely until the programming is successful. This is an incremental approach, so say if out of 20 codes 2 didn't program correctly, it will only retry those 2 and not all 20.
This should resolve most issues users face due to communication problems between the hub and the lock.
After you update the code make sure you reinitialize (open and hit done) the app for it to work correctly.