Unless I missed it, it seems ST still doesn’t fully support any door locks?
It seriously disturbs me we’re using code created by a unknown person to provide functionality of something as important as a DOOR LOCK. Had I known ST was so behind in basic support of devices I’d never have bought multiple hubs for various locations. There should be a process where code like this needs to be vetted by ST and then implemented into their stack if it’s approved.
This is a lock… not a lightbulb… a malfunction gives access to your home, and your family??? Some reasonable consideration should be given to safety items. Same issue with the Nest Smoke Alarm, code by some random person … not ST.
2 Likes
@shylok my friend, we in this community always help each other out in any possible way in any small or big way we can contribute and even though we rant and scream at ST support they are also us. We all got into this knowing what we are getting into. And above all I think (even though you may consider this to be naive) we trust each other and that’s what differentiate this community from others. We are not perfect neither is ST but I am sure they are trying and so does this community. And please don’t take this otherwise, you are we too… 
I sure do appreciate your concern, if you don’t trust it, don’t use it for critical things. That’s the reason I pay 50$ to ADT still… 
Cheers, buddy!
2 Likes
@Shylok - Also, the code is completely open for everyone to see. So, by going with one of the smart apps that are used by many people here and talked about a lot, like Home on Unlock, Too or on of the apps that sets the codes…you can pretty much be assured that people who program have looked over the code. If anything, I may trust this a bit more. It is similar to an Open Source approach.
On top of that, many of ST’s apps are listed on the IDE for people to use as a starting point…so we can review those as well. And, one more thing - I have seen ST developers enhance apps that are created by the community and post the changes here.
So, although I agree with part of that you are saying - basic device support - I feel the community has all our backs. In addition, there are so many different devices out there it is hard to keep up to speed. ST has recently been adding more people during they explosive growth. I assume we will start seeing more traction on this soon.
1 Like
I finally got around to updating the Smart App code to work with the default zwave lock device type created by Smart Things. You no longer need to create a custom device type just use the Smart App.
I’m working on updating the app for multiple users and notifications.
1 Like
I updated the code again to add a notification option that will let you choose to be notified if code is used to unlock door and when code is deleted and set.
I’m now working on multiple users in a single smartapp
6 Likes
multiple users in a single smartapp… will that include options such as allowing access to some locks by certain users but not others, not giving ever user full access to every lock? that would be great, I have some locks to keep the kids out of stuff like my garage and my studio, but yet I want them to be able to have access to use their code to unlock the front door.
@Spyder, you’re already able to specify which user codes you want to be active for each individual lock with this SmartApp. I installed two instances of the app; one instance for one of my locks, and a second for my other lock. Then you just adjust the settings of each lock-specific version of the app to the user codes you want each to have access.
Fantastic work, especially for gratis, many many thanks BP6!
Any plans to add a scheduling feature for times to be active/disabled?
I have the Kwikset Smartcode lock, using the default zwave device type created by ST, any reason I’m not able to see battery level?
Thank you thank you again!
Thanks for the code!
You need to change line 60 in the codereturn method to something like:
if (evt.value == Integer.toString(user)) {
That will get the comparison to happen properly so you can get notifications when a code is changed or deleted.
Does this smart app (or could it in the future) support scheduling when codes should be active? IE setting a date/time when the code is added and another when it should be removed?
This would be a very helpful feature for assisting with rental properties.
Thanks.
I fixed that a couple of days ago. Did you look on gethub?
I added a multi user app that is beta quality and not thoroughly tested.
It only supports 6 users until i add dynamic pages to the app.
The code is also very sloppy and needs to be cleaned up but i figured i post what i got for now. If anyone wants to help feel free.
1 Like
Greetings! I have taken bigpunk6’s single-user code and expanded on it a bit.
- Support Multiple Locks (a PR to bigpunk6 adds this to his code too, and he seems to have incorporated it into his multi-user version)
- Add Scheduling Access to delete and activate codes at specific times
- At this time only supports a single code/user slot at at time. Must create multiple installs of the app in order to manage different users. I’ll add multi user support to the app later if ST UI ever gets a repeatable field or there seems to be a want for it.
** Future planning: Single use codes, Actions on user entry IE: Turn on/off a light, lock/unlock other locks ect…
NOTE: I’ve only done light testing on the lock scheduling functionality. It seems to work as expected, though I would NOT trust this as a user’s single point of access. Have a backup if relying on schedule add/delete of codes, be available to your users to hit the unlock button on your smart device if someone complains that their code isn’t working.
That being said, I’d love some user testing. Does it work every time? Does it fail to work on Sundays?
2 Likes
Those are good points to make, Shylok. That’s where the beauty of open source comes in. It both sets out to solve problems, but comes with a whole set of problems in it’s own right.
You can review the entire piece of software in it’s entirety to make sure it’s not sending info to la-la land. Even if it’s all over your head and you can’t make heads or tails of it, you can watch how the community responds to the code and decide if you want to use it or not.
The open source community is cutting edge. It moves faster than the bureaucracy that SmartThings/Samsung/Ect proper would have to go through in order to vet it’s products. If you want to fully rely and trust in them, wait for them to come up with their own solution, but as of right now, they don’t offer one. The problem with that is every John Dick and Jane has a patent on every idea imaginable, and apps that SmartThings/Samsung release will most likely have to abide by those sets of rules. I know if SmartThings/Samsung ever closes their developer APIs or stops innovating, I’m switching to another solution. The community supplied apps have made my life a whole lot move convenient.
You are currently in a forum that is geared to the open source community. That’s what SmartThings was originally created about, and created for. If you want everything to be vetted, stick with the apps that you’re able to install directly from your device, and you’ll be fine. If you wanted a bureaucratic product, try Lowes’ Iris system.
When you purchased a SmartThings hub, all this information was readily available. SmartThings never surprised anyone with thier opensource and opengraph mission.
"A malfunction gives access to your home and family"
Yes and no. It’s your responsibility to keep tabs on the status reports that the application gives to you. Don’t create any rules inside of apps that if they failed to execute, would create a security vulnerability. Bottom line is, a good developer will keep failure in mind, and fail gracefully
A failure should leave your house more difficult to get into… not easier. I tell all my tenants not to rely on the codes that I give them, and to keep a traditional key on them if all else fails. The battery can die in the unit and you’d be locked out, no app can fix that.
When all else fails, ask the community. Is this app doing something nefarious with my device? I’m with you, better safe than sorry. I would not install anything that was in a private repository, or something that you would have to pay to get access to. The community is your friend, obscurity is your enemy.
guys im planing on buying a smart lock, can you tell me wich locks are supported by this SmartApp? i would like something like the schlage connect
Any lock that is supported by SmartThings and also has a code interface will likely be supported by the apps that are in this thread, I believe Kwikset Z-wave locks and Yale and Schlage locks all support the same SmartThings commands that these apps use.
Is there a particular lock you’re looking at getting? I have three Kwikset 910 locks that I’m pretty happy with.
im looking to buy the schlage connect, has anyone tried it??
Based on the product page, it looks like these apps would work great with that lock. The Schlage connect lock supports up to 30 users just like the Kwikset lock does. That lock is also the one that’s featured on the SmartThings shop. I can’t say for certain that it would work, but I would be very surprised if it didn’t!
Good luck.
I have 3 of the Schlage Camelot touchpad locks and they are my favorite thing about home automation. I’ve not had a bit of trouble and they’ve been so convenient. I’m very pleased with the community apps that control them as well.
1 Like