Homatic.ai
Integration
Schlage Airbnb automation
A Schlage Encode or Sense on a rental gives you the two things that matter most: codes the lock enforces itself, and a door history that tells you what actually happened. Most software uses neither.
Homatic drives the lock from your booking calendar — a code per stay, live before check-in, gone after checkout — and reads the lock’s own history for the events a status check cannot see: a jam, a forced-entry alarm, a keypad lockout, and which credential opened the door.
Start free — no credit card Why jam detection matters
What you get
- Per stayA code cut from the reservationGenerated for that guest, checked against the codes already on the lock so it cannot collide with a live one.
- Lock-enforcedA real start and end timeSchlage accepts a schedule the lock applies itself, so the code stops working at the end of its window even if nothing reaches the lock afterwards.
- ConfirmedThe guest is told only when it is liveA create returns a command id, not an access-code id — the code exists once the command settles. Reading the id off the acknowledgement gives you nothing to remove the code with later.
- ContinuousDoor history into the property logWhich credential opened the door, plus jams, forced-entry alarms and keypad lockouts.
- After checkoutRemoved, and the removal verifiedBefore the PIN is marked revoked — otherwise you believe an old guest’s code is gone when it is still on the lock.
A Schlage lock has seven states, and three of them are not “unlocked”
This is the detail that decides whether lock automation is worth having. Schlage reports lock state as an enumeration, and a boolean cannot express it:
| State | What it means for you |
|---|---|
| Locked, Deadlocked | Secured. |
| Unlocked | Not secured, normally. |
| Jammed | Not secured. The bolt tried to throw and could not — usually against the strike plate. Someone has to go and look. |
| Motor failure | Not secured. Same practical consequence, different cause. |
| Passage mode | Genuinely unlocked — the latch is held back deliberately. |
| Unknown | We cannot say. Treated as not-secured wherever a single answer is required. |
Collapsed into a boolean, a jam and a motor failure both read as an ordinary open door — which is how they end up buried in a list of doors that are open for good reasons. Homatic keeps them distinct, and never renders a reassuring “Locked” for a door that is not.
Automate your guest codes → Connect the lock and a calendar; the next booking gets a confirmed, lock-enforced code.
Why the door history is the interesting surface
A status check tells you what the lock is doing now. The history tells you what happened while nobody was looking, and it is the only Schlage surface that reports:
- a jam, at the moment it occurred rather than if it happens to still be jammed when you look;
- a forced-entry alarm;
- a keypad lockout after repeated wrong codes;
- which credential opened the door — the guest’s code, the cleaner’s, or a physical key.
Homatic reads it into the property’s physical-action log, watermarked so events are folded in once. A property newly connected takes a small bounded window of history rather than replaying months of door events stamped as just-observed, because a trail that lies about when things happened is worse than a short one.
The timezone trap, and why we refuse rather than guess
Schlage’s schedule format carries no timezone. A UTC instant written into it verbatim shifts a guest’s access window by the property’s entire offset — which, for a code that should go live at 4pm, is a guest at a door with a code that does not work yet.
Homatic reads the offset the device reports and shifts the window accordingly. Where that offset is spelled ambiguously, the code is refused rather than issued on a guess, because guessing wrong produces exactly the failure the whole system exists to prevent, and does it silently.
Which Schlage locks
Schlage locks reachable through Allegion’s partner API — the Wi-Fi Encode family and Sense. A Bluetooth-only lock with no bridge cannot be reached by any cloud service, ours included; that is a property of the hardware rather than of the software.
If a lock is on your SmartThings hub instead, codes work when the lock reports a lock-codes capability. Where both routes exist, the direct one is generally better for rentals precisely because of the lock-enforced window and the history above.
When a name clashes
Schlage rejects a duplicate code name and a duplicate PIN with different errors, and they deserve different handling. A name clash is retried with a disambiguated label, because the name is cosmetic. A PIN clash is surfaced rather than worked around, because silently programming a different number than the one a guest was told is the same failure in a quieter coat.
Related
How guest codes work across every lock → · Checkout automation →
Common questions
Which Schlage locks does this cover?
Schlage locks reachable through Allegion’s partner API — the Wi-Fi Encode family and Sense. A Bluetooth-only lock with no bridge cannot be reached from any cloud service, by anyone.
Does the lock enforce the code window itself?
Yes. Schlage is one of the platforms that accepts a start and end time the lock applies, so a guest code stops working at the end of its window even if nothing reaches the lock afterwards.
Does Homatic know if the deadbolt jams?
Yes, and it does not report a jam as "unlocked". Schlage reports seven lock states, and three of them — jammed, motor failure, deadlocked — cannot be expressed as a boolean. A jam and a motor failure both mean the door is not secured and someone has to go and look.
Can I see which code opened the door?
The door history names the credential that was used, and it is the only Schlage surface that reports a jam, a forced-entry alarm or a keypad lockout. Homatic reads it into the property’s physical-action log.
See Homatic on your own properties
Connect a property and the dashboard fills in from your real devices — your locks, your thermostat, your calendar. Free for 30 days on Starter, no card required.