I would like ‘incorrect code’ notifications too. Sonos support would be nice.
Coding is the not the issue, it’s keep the app relevant and simple for all users is the priority
There already exists the functionality to turn on switches after dark but you’re right on the money for turning it on before dark. I’ll the functionality to turn on 1 hour before sunset which should work for everyone. I don’t think it warrants another input hereby making it more complex
There already exists an option to turn on switches and turn off switches. I see the logic behind assigning switches to doors. However a contradicting view would be to assign switches to users. They can’t both exist without creating confusion and complexity for the end user. So logically I think either switches should be tied to user codes or to locks. I would say user codes but then that increases complexity of programming. Assigning switches to locks reduces that complexity, but the simplest is the current form, it applies to all doors and user codes.
Can’t do it because the base ST device doesn’t support those notifications, I would need to write a custom device (which I have) but then it won’t work with the stock device type and I’m trying to avoid that. However I can put it conditionally that will work if using my device type.
Hello-
Agreed with the complexity issue. I would think that it would be most useful to be able to control the lights separately by each lock (only from keypad) so that people could turn on a basement light with basement door and foyer light with front door. Maybe the individual users are overkill. 
Do you think this stuff might be better suited as like a companion app to the existing one rather than all in one so that, like you mentioned, it wouldnt be wouldn’t be too complex for some users?
I do think other users would like these options because I had a few PM me about that app I shared a screenshot of asking what it was called because they like the idea of it.
Let me know if I can be of any help.
Sounds like a good option.
- Added support for Code Type ‘Inactive’ to allow users to keep the Username/Code for a slot in the app but not have it active
- Added support to notify user when too many invalid codes have been entered. This ONLY works if the underlying SmartDevice supports this attribute (the default ST Z-Wave Lock SmartDevices does NOT support this attribute but the custom Schlage Z-Wave Lock with Alarm Notification SmartDevice does).
Sunset now refers to 30 minutes before sunset to turn on lights (not configurable to keep complexity low, you can change it manually if you’d like). It’s not something that will likely change between seasons or regions
1 Like
Awesome!
I just thought of something that may be a work around for my specific request with controlling different lights with different door locks. Could i just install you app 2x with everything matching except the locks i select and the lights they control (i.e. keep user names and code all in the same slots, etc)? If so, that would solve almost everything. The only thing would be to not have it turn the lights on if you manually unlock the door because most likely if you are manually unlocking the door you are already inside (unless you batter died on you keypad), but that would prevent lights from coming on when you are already inside and probably don’t want to to come back on.
Thanks again for making the requests, they are really appreciated!!
-Jason
I updated the device type, do I also need to update the smartapp?
Have you tried it? Dont’ assume.
1 Like
Yes you need to update the SmartApp and SmartDevice for the recent changes
Added support for individually configuring actions for each door when multiple locks are selected (turn on lights, switches, phrases, disarming etc)
1 Like
Wow, thanks so much! I figured IF you did any of these it would be weeks, not hours.
Off subject question, is there a way to know when you make updates to the app or device type automatically? Like an rss feed or something from you site or do i just need to monitor this thread?
Like our Facebook page and you’ll subscribe to updates.
RB - Your app is working beautifully, would gladly contribute to other developers for the same level of reliability.
A feature request, just because I know if you do this, it will work. ----
I have your app installed and another that is straight from SmartThings. The ST app is just designed to automatically lock and unlock the door in certain conditions. For example if the door is in the closed position, per the door sensor, for a set value in minutes then the lock automatically locks. When the door is open, per the sensor, for a set value in seconds then the lock automatically unlocks to prevent it being closed on an extended deadbolt.
The ST app seems to work most times to lock the door when its closed, I haven’t timed it but its satisfactory. The ST app doesn’t seem to work at all when the door is in an open state, in fact it will lock the lock extending the deadbolt while the door is in the open position.
Again, love the app, thank you
1 Like
Thanks @Nomad33fw appreciate the support. It’s definitely a LOT of effort to keep up with the community and the two dozen odd apps hosted.
What you’re asking for a simple fix to the ST code, help me understand the use case for integrating this into the user management app. I agree the scope has extended beyond just user into managing events based on user codes. How would this extend to lock and sensor management.
Are you saying just a simple, if the door has been closed for X minutes then lock it while the hub is in certain modes?
Again the devil is the details so please detail out the use case. I love to poke holes for no other reason than it helps create a great user experience at the end. Nothing is worse than overly complicating apps.
Fairly simple (Says the guy who isn’t writing the code), there is another app that is in the Top SmartApps section that is supposed to do this already called Enhanced Auto Lock Door, it just doesn’t work well at the retract portion.
The use is when the door is in the closed position it will automatically be locked for security, but the user can set how long to wait for this to occur so that the door isn’t automatically locking if making trips out to the car for groceries etc… The second use is to protect the lock and door frame from being damaged if the deadbolt is inadvertently extended with the door is open, pushing it closed would leave a dent in the door frame and could damage the locking mechanism.
More details:
Allow user to select which lock
Allow user to select which sensor
Allow user to input how long to wait to lock the door if the sensor shows the door is in the closed position
Sense if deadbolt has been extended when door is in the open position and send command to retract (unlock) door.
Allow user to select Send push/SMS notifications of events
Allow user to select which modes the commands are applicable to
1 Like
Version 2.3.2 - Added support for differentiate between manual lock and electronic lock (keypad/remote) while notifying user
Hmmmm… i liked this a long time ago. I just looked and i see all the updates, but they aren’t showing up in my Facebook feed. I am not sure why. Thanks though!
When you release a new version of the app, is there an easier way to get the latest version updated without having to uninstall and reinstall the app again (after updating and republishing the code) then going through setting up all the users and settings again?