Host Portal
Provider Connections
Hosts connect their lock and access platforms here. Once a provider account is connected, OpenSlot can ingest available devices so they can later be mapped to properties and used in booking-driven access flows.
Demo Host
demo-host-001
Active Providers
...
Providers currently in active state for this host.
Shelly Status
Loading...
First live provider path for relay and garage-style access.
TTLock Status
Loading...
Lock-code provider path still being built out.
TTLock Account Updated
Not available
Latest TTLock provider-account timestamp.
Launch-Path Priority
The current priority is the real host onboarding path: connect provider, import devices, map devices, then let booking flows use mapped access.
Current live deployment path
Shelly is the first real-world deployment target because it fits OpenSlot's access flow cleanly and you already have the hardware ready to test.
Why TTLock still matters
TTLock remains the first serious lock-code path for Airbnb and standard deadbolt workflows, but it does not need to block the first live deployment.
Shelly
Relay and garage trigger platform aligned with OpenSlot's first real-world access deployment path.
Status
Loading...
No Shelly integration record exists yet for this host.
External Account ID
Not available
Last Updated
Not available
Shelly guidance
This is the first live deployment path. The host should connect Shelly, import the shared relay device, map it to a property, and then test guest-triggered access through the booking flow.
This is the first live provider path to prove real access flows before deeper keypad-code rollout.
TTLock
Primary lock-code provider path for Airbnb, short-term rental, and regular deadbolt workflows.
Status
Loading...
No TTLock provider account exists yet for this host.
External Account ID
Not available
Last Updated
Not available
Connected Accounts
No TTLock accounts connected yet.
TTLock guidance
TTLock remains the first serious lock-code path, but it should not block the first live deployment. Keep this clean and ready while Shelly proves the access flow.
Keep building this cleanly, but Shelly is the faster first live deployment.
Yale
Residential lock platform support for broader compatibility across host properties.
Connection Status
Loading...
No integration record exists yet for this provider.
Planned after the first provider auth and ingest pattern is stable.
Schlage
Future support path for Schlage and Allegion-connected residential environments.
Connection Status
Loading...
No integration record exists yet for this provider.
Will be added after the first provider flows are proven cleanly.
Recommended Build Order
Shelly should prove the first live access flow. TTLock should keep maturing as the first lock-code path.
First live deployment
Connect Shelly, import the device, map it to a property, and prove guest-triggered access end to end.
Next lock-code milestone
After the first live access path is stable, keep pushing TTLock toward real account-linked lock-code generation and ingestion.