Would like to add some features, but would like to discuss first

[saltydressage]

I have 3 Schlage Touchscreen locks, 2 are installed and 'mostly' working.

I'd like to be able to do a few things, and don't mind going in and doing myself if you are open to that, however I'd like to talk about the design of them if you want to go that way. If a separate app is the way to do this, or if extending your stuff is the best way, let me know :)

Some of these may or may not be possible, but I'd like to explore. I'll put them in rough order of priority. Also assume that all features would be for a subset of the active locks. ie. Add new user and random code for locks 1 and 3, or for 2 and 3...but NEVER 1 and 3.

1. Ability to give a new user a random PIN that takes the current lock's pin length into account (or set pin length manually on the "lock" profile if it can't poll it)

2. Ability to set that user a start/end time with a calendar view. We'll be doing this a lot and the manual 'enter day/month/year' for start/end by hand is error prone. #wifefriendlyfeature

3. Ability to make a new user/random-code/start-end date via some sort of automation (python on google cloud, REST api call into a server, something). I don't know enough about this system yet to know how to do this (or if it's possible), but bypassing having to manually enter new codes (and remove old users) would be ideal.

4. Ability to pull all data (all locks, all users, all start/end days, # of uses, etc) for further manipulation/viewing (local web service, etc)

Advice? Thoughts?

[ethayer]

1. this is a good idea and something I've thought about doing myself. Would be a nice B&B feature, not necessarily nice for the private-use user in which I am mostly targeting for support.

2. Yeah I hate the interface too but I don't know about any ways to improve this using the current SmartThings platform.

3/4. This opens up pandora's box. One of the prime directives of this app is to have this run solely on the SmartThings platform, so that the security of the app is in the hands of SmartThings/Samsung. Opening up an API service for the app to handle third party actions, while a good feature request, opens up a gate for vulnerability outside of the SmartThings ecosystem. Perhaps this could be done using an optional oAuth system and a separate app.. but this is a tred-lightly topic as I have been happily running all logic and actions on the SmartThings platform as a rule.

[waxcorp]

Just passing through to +1 3 & 4 here as I independently brought up a very similar notion here:

https://community.smartthings.com/t/release-lock-manager/63022/666
https://community.smartthings.com/t/release-lock-manager/63022/669
https://community.smartthings.com/t/release-lock-manager/63022/680

SmartTiles (http://www.smarttiles.click/) appears to be a fairly mature web connector/interface on top of the SmartThings environment to allow tablets to expose physical access to control and visual status of arbitrary devices to bypass the SmartThings app / login requirement. It seems to work well in my experience dabbling around with it, and it appears to rely on an oauth mechanism (I think provided by SmartThings to app developers? I'm not sure...) to provide access control to various web clients you might have placed around your home (in SmartTiles' case it would be wall mounted tablets, most commonly.)

I'll try to follow up if I can make any progress on exploring how a SmartTiles-security-like integration might look within the lock-manager SmartApp suite.

Thanks for your time!

[ethayer]

I'm working on 3&4 now, I've got everything working but I'm not happy about secure requests TO my application server. I'll let you know when I have something to publish, but right now it's all proof of concept.

It's going well though. I'm happy with application secure requests TO smartThings but security of requests FROM smartThings.

See this post about it: https://community.smartthings.com/t/rest-http-endpoint-validation/85881

[waxcorp]

From the looks of [0] it seems like the security portion is all set? Very excited to give this a run for the first time if you have something available to try :)

Cheers,

[0] https://community.smartthings.com/t/rest-http-endpoint-validation/85881/4

[JBenson79]

Im also interested in option #2 or perhaps another variation.

We are using this with Airbnb. An idea might be if i enter a link to the (iCal format) Airbnb calendar, then enter my check in/checkout times and have Lock-manager generate the user and code based on the calendar settings.

I would like an easier way to enter users, codes, start and end dates for them. Even if i could login to the IDE and type in a list of 10 codes at a time would be fine, if i knew where to do it.

Any ideas?

[saltydressage]

Will this go anywhere? I've had zero time to investigate, alas.

[ethayer]

lockmanager.io is in development. I have a few things to do before I open a beta, mostly on advanced scheduling and group membership.