Will Lock Orchestrator work with my setup?

Pick your hub, your lock and where your bookings come from. You'll get a straight answer, including a plain "no" when something isn't supported, before you create an account.

1. Your hub Samsung SmartThings Hubitat Elevation (cloud Maker API URL) Hubitat Elevation (local Maker API URL only) Home Assistant Other hubs (Homey, Vera/Ezlo, Z-Wave JS, Wink) No hub, lock uses its own app

2. Your lock Z-Wave keypad locks (Yale Assure / YRD, Schlage Connect & BE469, Kwikset SmartCode) Zigbee keypad locks (Yale, Kwikset and others) Locks fixed to 5, 6 or more digits Matter over Thread keypad locks Wi-Fi or Bluetooth-only locks (August, Wyze, Level, Wi-Fi Schlage Encode and similar) Locks without a keypad

3. Your bookings Airbnb VRBO Booking.com PMS & channel managers (Hospitable, Guesty, Lodgify, OwnerRez and others) Direct-booking sites and shared calendars (.ics link) No calendar export (email confirmations only)

Choose one option in each column.

Or read the full lists below.

The full lists

Supported, check first, and not supported.

Lock Orchestrator talks to your hub, and the hub talks to the lock. So the real test is simple: if your hub's own app can add a code to the lock, Lock Orchestrator can too.

Hubs

Hub	Status	Details
Samsung SmartThings	Supported	Connect with your SmartThings sign-in. No subscription and nothing to install on the hub. Works with any lock the SmartThings app can set codes on.
Hubitat Elevation (cloud Maker API URL)	Supported	Add Hubitat's built-in Maker API app, select your locks, and paste its cloud URL and token. No custom Groovy code.
Hubitat Elevation (local Maker API URL only)	Check first	A local address such as http://192.168.1.20/apps/api/42 only works from inside your network, so the hosted service cannot reach it. Use the cloud URL from the same Maker API page instead; nothing else changes.
Home Assistant	Not supported	Not supported today.
Other hubs (Homey, Vera/Ezlo, Z-Wave JS, Wink)	Not supported	Not supported today. If your locks are Z-Wave or Zigbee they can usually be moved to SmartThings or Hubitat.
No hub, lock uses its own app	Not supported	Lock Orchestrator programs codes through a hub. For a Wi-Fi or Bluetooth lock managed only in its own app, use the brand's own integration.

Locks

Lock	Status	Details
Z-Wave keypad locks (Yale Assure / YRD, Schlage Connect & BE469, Kwikset SmartCode)	Supported	The most common rental setup. Schlage BE469/BE469ZP firmware that falsely reports every code wiped is detected: you get an email and slot handling turns cautious until the hub's list recovers.
Zigbee keypad locks (Yale, Kwikset and others)	Supported	Supported whenever the hub exposes code management for the lock.
Locks fixed to 5, 6 or more digits	Check first	Guest PINs are 4 digits. Many locks let you change the code length from the hub or keypad; if yours cannot accept 4-digit codes, the write is refused and reported to you.
Matter over Thread keypad locks	Supported	Supported when SmartThings or Hubitat exposes lock-code management for the lock. The lock must accept 4-digit codes; confirm you can add and delete codes through your hub before starting a trial.
Wi-Fi or Bluetooth-only locks (August, Wyze, Level, Wi-Fi Schlage Encode and similar)	Not supported	These usually keep codes in the brand's cloud, not on a hub, so there is nothing for Lock Orchestrator to program. Their own rental integrations are the better fit.
Locks without a keypad	Not supported	There is nowhere for a guest to enter a PIN.

Booking calendars

Booking calendar	Status	Details
Airbnb	Supported	Paste the listing's calendar export link. Airbnb includes the last 4 digits of the guest's phone, which becomes the PIN.
VRBO	Supported	Paste the calendar export link. When no phone is in the feed, a PIN is derived from the booking and stays stable for it.
Booking.com	Supported	Paste the calendar export link from the extranet's calendar sync page.
PMS & channel managers (Hospitable, Guesty, Lodgify, OwnerRez and others)	Supported	Anything that can export an iCal link works. One link per property.
Direct-booking sites and shared calendars (.ics link)	Supported	Any publicly reachable iCal URL. Links to private network addresses are refused.
No calendar export (email confirmations only)	Not supported	Lock Orchestrator learns about bookings from an iCal link. Most booking platforms and PMS tools offer one under calendar sync or export settings.

Matter over Thread devices, too.

Prepare the home before arrival and save energy after checkout with compatible thermostats, switches and dimmers, including Z-Wave, Zigbee and Matter over Thread devices. SmartThings or Hubitat must expose the controls needed for each action. You can also schedule hub mode changes. Unlimited check-in and checkout automations are included in your plan.

Hubitat

Cloud or local Maker API URL?

Hubitat's Maker API app shows two sets of links for the same devices. Lock Orchestrator is a hosted service, so it reaches your hub from the internet. That decides it:

URL type	Looks like	Use it?
Cloud	`https://cloud.hubitat.com/api/HUB_ID/apps/APP_ID`	Supported
Local	`http://192.168.1.20/apps/api/APP_ID`	Check first Only for installations on the hub's own network

Both use the same access token and expose the same devices, so switching is just pasting the other link. Codes already on your locks keep working if the hub loses internet; only new changes wait until it's back.

Full Hubitat walkthrough

Before you start the trial

Five-minute pre-trial checklist.

Seven days goes quickly. Tick these off first and your first verified code can happen in the first session.

The lock is paired to SmartThings or Hubitat and shows up in the hub's app.
You can add a test code from the hub's own app, and it opens the door. This is the single best predictor of success.
The lock accepts 4-digit codes. If it's set to 6, change it from the keypad or hub first.
You have the iCal export link for each listing. Where to find it.
Hubitat only (skip for SmartThings): Maker API is installed, your locks are ticked in it, and you've copied the cloud URL and token.
You know which slots your own codes use (owner, cleaner). Lock Orchestrator won't overwrite them, but it helps to recognise them.

FAQ

Questions, answered.

Which smart locks are supported?

Compatible Z-Wave, Zigbee and Matter over Thread keypad locks that your SmartThings or Hubitat hub can manage codes on. Lock Orchestrator talks to the hub, not the lock, so if the hub can manage the lock's codes, it works. The lock must accept 4-digit codes.

Does Lock Orchestrator work with Wi-Fi or Bluetooth locks?

Usually not. Lock Orchestrator programs codes through a SmartThings or Hubitat hub, so the lock has to be paired to that hub with code management exposed. Wi-Fi and Bluetooth-only locks normally manage codes in their own app; use that brand's integration for those.

Should I connect Hubitat with the cloud or the local Maker API URL?

Use the cloud URL. The hosted service reaches your hub from the internet, and the local URL (http://your-hub-ip/...) only resolves inside your home network. The local URL is only for installations running on the same network as the hub.

Does it need a SmartThings subscription?

No. It uses the standard SmartThings API through a normal SmartThings sign-in.

What do I need before starting the trial?

A SmartThings or Hubitat hub that can already set a code on your lock from its own app, the lock paired to that hub, and the iCal export link from your booking platform. With those ready, setup takes about five minutes.

Try every lock free for 7 days.

Every lock and every feature, with no limits and no card. Connect a hub, pick your locks, paste a calendar link, and activate your next booking early to see its code verified on the door. About five minutes per property.

Start your free trial $2/lock · no card · cancel anytime