I’m very appreciative of everyone’s work on apps, but I find it highly disappointing that the feature of remotely controlling PIN codes that I was told in 2013 “is on our roadmap” still hasn’t been built into the app natively.
Especially when ST sells the kwikset locks that have this feature. Yet they can’t support it. Only reason I bought ST was because this feature was coming soon.
Very disappointed in being misled every time I contacted ST before making my purchase.
I’m new to Smart Things and am interested in getting better control over a door lock (remote PIN admin). Your post makes it sound like I might be able to this without too much fuss (I’m not a coder). Can you point me in the best direction to get started? I’m an Android user btw.
To control them, I use @ethayer’s awesome User Lock Manager
There are a few others in the community here, but that is the one I settled on and use. Erik is quick to update and has done a great job with the app.
In addition, I also use @obycode’s SmartRules (iOS only at this point) to control my locks outside of Routines when needed. It’s a great app that is very easy to use.
There is an alternative to this - @bravenel’s Rule Machine
I personally don’t use that one, but Bruce is a great programmer and the app has a large following here. There are some issues with how Android renders the pages (I think they still exist), so you would have to configure them from a Mac/PC. Check that thread for more info.
In the end, the locks were the biggest selling point to the smart home install with the Mrs and the first thing I did. One of our doors unlocks automatically when we arrive, allowing someone to walk in the door with their hands full and not fumble for keys. I can also monitor them to ensure they are locked when we are gone. If a guest arrives and lets them selves in via a code, I have @ethayer’s app run a routine to turn lights on, etc that would normally occur when I arrive home and my presence runs a full routine.
One suggestion I would make, though. If you only use one smart lock, make sure you have a key for it if the battery dies and you didn’t replace them. Or, in my case, I have two doors with smart locks. They both have rechargeable batteries. I charge them on “alternating schedules” so that one always has more of a charge than another. I just have my iPhone remind me when I need to charge them, every month for each lock, but offset by two weeks between them.
Hi there. I’m getting a '404 Not Found" on the ‘here’ link for all other locks. I’m really hoping this will help me with my lock, as it works fine when I am home, but does not work as part of routines, or when I am using the main ST app away from home. Thanks so much.
Paste the code from the link (github) above into the text area:
if you have a schlage lock, use @garyd9’s handler: here
all other locks: here
Hi ethayer. First thank you for publishing this great app that I will probably need at some point. However, I was wondering if you knew of the possibility in groovy to set an event handler which relates to pressing the lock button of the lock/lever device? I would need to run a hello home action based the lock button being physically pushed.
Do you know if such an event exists? I could not find this action in capability reference ST documentation so I’m just giving it a last shot since I can see that you seem to know this device type pretty well.
I’ve seen that. But apparently wrongly thought that if it was supported, there would be the same device listed in the app under the MarketPlace. That’s where only the 916 for Zigbee is listed. And no Z Wave version.
However, finally got the 2nd one to pair. Wound up having to reboot the hub. Only then did it do the exclusion, and afterward the inclusion.
Welcome to the disappointed customers club! I literally have not found any features/functions in ST that work reliably, if they work at all. This statement is by not mean an exaggeration.
Samsung must regret the decision to purchase ST, let alone working to incorporate this THING (doesn’t qualify to be called a system or solution) with their other products.
ST’s support staff are very nice and try hard to be helpful; Unfortunately, they are stuck between a rock and a hard place because of ST’s crappy software/hardware design and unstable cloud infrastructure.
I’m glad that many ardent ST supports are finally getting tired of the platform problems and the company’s empty promises to address the same ongoing issues. Maybe a mass exodus will light a fire under ST (assuming they are capable) to deliver a properly functioning system.