RBoy
(www.rboyapps.com - Making SmartThings Easy!)
21
That’s correct, SmartApps are isolated in SmartThings and due to lock firmware limitations codes cannot be read back from locks.
I understand where you’re coming from but RLA isn’t designed to support API access. You can use this app instead if you need API access to managing users on locks. It’s designed to be an easy way to manage users via a REST API and the app will manage the lock communications and mesh errors, your own app can then decide which users to program with expiration dates/times etc. Note that you cannot use RLA and LMAPI at the same time on the same lock due to the SmartApp isolation restrictions otherwise they will conflict with each other.
Maybe in future there could a new hybrid app or a plug-in for this app which will bridge the two features.
(fix) Check if the door selection was accidentally left out for notifications and relocks
(enhancement) Support for new platform garage door capabilities
(fix) Various minor fixes, enhancements and UI improvements
(new) “lock status” adds connection member to the response JSON which reports the lock connectivity state
The connectivity status for each lock can contain the following values:
online - The platform is able to communicate with the lock
offline - The hub cannot communicate with the lock (mesh problems, lock batteries etc)
hub disconnected - The platform cannot communicate with the hub (power failure, internet connectivity etc)
Please ensure that your lock is within 20ft of a buffering/beaming repeaterfor the best experience (the buffering device should be between the hub and the lock for maximum effectiveness).
We’re using the Lock Manager API to integrate our PMS with zwave locks at a small hotel property. We have a combination of Yale locks (up to 200 user codes possible per lock) and Locstar locks (up to 30 user codes possible per lock). Everything worked well in testing, but as we approached opening date we noticed that the maximum user slots allowed in the LM app are 30. That means we can only have 30 unique users for the entire property.
So, If my property has 50 rooms, does that mean I can not use the LM API to manage my locks (since that means we will potentially need at least 50 user slots for 50 individual guests)?
We tested by setting 30 users and distributed them among the rooms. No single lock has more than two or three users already in it. Each room lock has a guest code, a housekeeping code and a management code. Once we reached the 30 user limit, we sent one more user code through the API and received an error indicating we’ve reached the max user number.
Is there a work around the user limit in the API? Why are we limited to 30 users in total for all locks on the property?
This app is essentially dead. Samsung has transitioned away from Groovy Smartapps as of mid October and this app will no longer function in two weeks (12-31-2022). Unfortunately the developer has not communicated their transition plan to the new system, but they do claim to be working on it.
If this is how you operate your business, you’ll need to find a new solution ASAP.
Thank you. Yes we’re noticing the app is no longer communicating with the locks or setting pins properly anymore. We’re moving to Vera’s ezlo hub for now.
I’m also willing to pay for a developer to create our own app/api using the new smartthings platform/Lua. It’s just hard to figure out who knows how to communicate with zwave locks.