Beta testers wanted: scheduled SmartThings lock codes after Groovy

[Make_Sail]

If you used RBoy LUM or RLA, you may miss being able to give a guest or cleaner a named PIN that automatically appeared before their visit and disappeared afterwards. I definitely did, so I finally bit the bullet and built a web app to bring that useful capability back.

It lets you:

• create named PINs for guests, deliveries, cleaners and permanent access

• choose exactly when each PIN becomes active and expires

• automatically rotate recurring or permanent PINs

• connect an Airbnb, Booking.com or other iCalendar booking feed

• receive an email when a named code is used or a rotating code changes

• see which codes are on the lock, when they were created or last used, and whether SmartThings confirmed each change

I’m looking for a small number of SmartThings lock owners for a free private beta. Custom Edge drivers are especially useful, but I also need testers using the standard SmartThings Z-Wave Lock driver. If you manage more than one lock or property, I’d like to test that setup too.

This is an independent project and is not affiliated with Samsung, SmartThings, Yale or RBoy. It focuses on scheduling access codes reliably and with as little effort as possible.

Interested? Reply here or send me a private message with your country, lock model, hub and current driver.

Thanks!
Robert

[jkp]

Are you taking into account that SLGA will be discontinued in December 2026?

It's Official...Smart Lock Guest Access (SLGA) is being discontinued

As has been previously discussed in other topics, the official notice of the discontinuation of SLGA has been published. After December 2026, lock codes will be configured via the device card for each individual lock vs a centralized service within the mobile app. This will affect custom drivers that have been utilizing the lockCodes capability in order to provide per user unlock indications such as the Z-Wave Lock PH driver from @philh30 and likely the Universal Enhanced Z-Wave Lock Driver from @RBoy (he can comment on the status of his driver). [2026-07-23 08.47.03]

[Make_Sail]

Yes, that’s part of the longer-term plan rather than the initial beta.

Once SLGA goes, SmartThings will manage codes separately through each lock. When the time comes, this app will allow the same code and schedule to be applied across multiple locks from one place.

For now, the beta is concentrating on making scheduling reliable on individual locks using different drivers.

[h0ckeysk8er (Bruce Pinsky)]

@Make_Sail

Yes, that’s part of the longer-term plan rather than the initial beta.

Once SLGA goes, SmartThings will manage codes separately through each lock. When the time comes, this app will allow the same code and schedule to be applied across multiple locks from one place.

For now, the beta is concentrating on making scheduling reliable on individual locks using different drivers.

If you are using the lockCodes capability today for managing the PIN codes and code names, it is not clear whether that capability will be deprecated and therefore removed from the device’s capabilities. If that happens, you will have to rewrite your code to use the lockCredentials and lockUsers capabilities. Today all three capabilities live side by side. No telling what will happen when SLGA goes away.

[Make_Sail]

Thanks Bruce, that’s useful. I’ll make sure the app accommodates that change.

Right now, I’m particularly interested in testing the range of stock and custom driver setups people are using today. If anyone would like to try the beta, please send me your country, lock model, hub and current driver.