We Feel Your Pain
If you're reading this, you probably had a perfectly working smart lock automation system. Your Yale, Schlage, or Kwikset locks connected to SmartThings. RBoy's Rental Lock Automater (RLA) synced with your calendar and automatically programmed guest codes. Life was good.
Then SmartThings pulled the rug out from under you.
When Samsung deprecated the Groovy platform at the end of 2022, RBoy's entire suite of apps—including the beloved RLA—stopped working overnight. Thousands of hosts were left scrambling mid-season, manually programming codes like it was 2015.
We built GuestsKey specifically for hosts like you. Same SmartThings locks you already own. Same automation you loved. But cloud-native architecture that won't break when platforms change.
What Actually Happened to RBoy Apps
RBoy Apps was a pioneer in vacation rental automation. Their Rental Lock Automater (RLA) was the go-to solution for SmartThings users who wanted automatic guest code management. For years, it worked beautifully.
The problem? RLA was built on SmartThings' Groovy platform—a local execution environment that ran custom "SmartApps" on Samsung's servers. When Samsung decided to modernize their platform and shut down Groovy in favor of "Edge Drivers," every Groovy-based app stopped working.
The Timeline of Disaster
- October 2022: Samsung announces Groovy shutdown
- December 2022: Groovy platform officially deprecated
- January 2023: RBoy apps stop working completely
- 2023-Present: RBoy releases Edge Drivers, but without calendar automation
While RBoy has released new Edge Drivers for lock management, they don't support the calendar-based automation that made RLA so valuable. You can program codes manually, but the automatic guest code generation based on your bookings? Gone.
Why GuestsKey is the Natural Successor
We watched the RBoy disaster unfold and saw an opportunity to do things differently. GuestsKey was built from the ground up with one principle: never depend on platform-specific code that can break.
Cloud-Native Architecture
GuestsKey runs in the cloud, not on SmartThings servers. We use OAuth to connect to your SmartThings account—the same way Netflix connects to your TV. Platform changes don't break us.
Native OwnerRez Integration
RBoy used iCal calendar feeds—a one-way sync that often lagged. GuestsKey connects directly to OwnerRez's API for real-time booking data, including guest phone numbers for memorable codes.
Automatic Cleaner Codes
GuestsKey automatically detects gaps between bookings and activates cleaner codes. No more texting your cleaners or worrying about overlapping access.
Memorable Guest Codes
Instead of random 6-digit codes guests forget, GuestsKey uses the last 4 digits of their phone number. They already know it, so no lockout calls at 11 PM.
Migration Guide: RBoy → GuestsKey in 5 Minutes
Ready to get your automation back? Here's exactly how to migrate—step by step.
- 1Sign Up for GuestsKey (2 minutes)
Create your account at guestskey.com. Enter your email, set a password, and you're in. No credit card required for the free trial. - 2Connect Your SmartThings Account (1 minute)
Click "Connect SmartThings" and authorize GuestsKey via Samsung's OAuth. This gives us secure access to control your locks—no credentials stored, no SmartApps to install. - 3Connect OwnerRez (1 minute)
Authorize your OwnerRez account. GuestsKey imports your properties and bookings automatically—past, present, and future. Guest contact info included. - 4Map Properties to Locks (1 minute)
GuestsKey shows all your SmartThings locations and locks. Simply match each property to its lock—dropdown menus make it easy. - 5Enable Automation—Done!
Toggle on guest automation and cleaner codes. GuestsKey immediately starts scheduling codes for all your upcoming bookings. That's it—you're automated again.
Feature Comparison: RBoy RLA vs GuestsKey
| Feature | RBoy RLA (Legacy) | GuestsKey |
|---|---|---|
| Status | Deprecated | Active |
| SmartThings Integration | Groovy (dead) | OAuth (modern) |
| Booking Sync | iCal feeds (delayed) | Native API (real-time) |
| Code Generation | Random codes | Guest phone (memorable) |
| Cleaner Codes | Manual setup | Auto gap-based |
| Platform Risk | High (local dependency) | Low (cloud-native) |
| Setup Time | 30+ minutes | 5 minutes |
What About Your Existing Locks?
Here's the good news: you don't need to buy new hardware.
GuestsKey works with the same Z-Wave and ZigBee locks you already have connected to SmartThings:
Your SmartThings hub stays in place. Your Z-Wave mesh network stays intact. GuestsKey simply sends commands through SmartThings' cloud API instead of running local Groovy code.
Ready to Get Your Automation Back?
Join thousands of hosts who've migrated from RBoy to GuestsKey. Same locks, better automation, 5 minutes to set up.
Start Your Free Trial14-day free trial · No credit card required · Cancel anytime
Frequently Asked Questions
Will my lock codes from RBoy still work?
Any codes currently programmed on your locks will remain until overwritten. When you set up GuestsKey, it will program new codes for upcoming bookings. We recommend clearing old guest codes for security.
Do I need to remove RBoy's Edge Drivers?
No. GuestsKey works alongside any Edge Drivers you have installed. We communicate through SmartThings' API, not through drivers. You can keep RBoy's drivers for manual code management if you want a backup option.
What if SmartThings changes their API?
Unlike Groovy SmartApps that ran on Samsung's servers, GuestsKey uses SmartThings' public OAuth API—the same API that Samsung provides to all partners. If they change it, we update our integration. Your setup stays the same.
Is GuestsKey more expensive than RBoy was?
RBoy charged $99 one-time per property. GuestsKey uses subscription pricing starting at $8/property/month for small portfolios, with volume discounts as you grow. The monthly model means you get continuous updates, support, and new features—plus you're never stuck on abandoned software.