The Best Smart Lock Setup for Airbnb Self Check-In

Self check-in for short-term rentals fails whenever access depends on a person being physically present, or on a code that never changes. Lockboxes get lost, keys get forgotten at check-out, and a static code shared in a listing description is effectively public. Hosts running more than one property also need a way to manage access without driving to each door.

• No remote control. A standard keypad lock only accepts codes typed at the door, so issuing or changing a code requires someone on site.
• No natural expiry. A code that works forever is a liability once the guest checks out.
• No record of who came and went. Without logs, disputes over early arrivals or late departures are hard to resolve.

1. Install a TTLock-compatible keypad or keypad-and-deadbolt lock on the entry door. A keypad means the guest never needs app access, an eKey, or Bluetooth pairing — they just type a code.
2. Add a gateway near the lock. The gateway bridges the lock's Bluetooth to Wi-Fi, so codes can be created, changed or deleted remotely instead of requiring the host to stand at the door. Smart Lukko is an independent third-party app for TTLock-compatible locks, not affiliated with TTLock/Sciener, and it uses the same gateway mechanism to relay commands to the lock over the internet.
3. Generate a timed passcode for each booking. Set the validity window to start at check-in time and end at check-out time for that reservation. The code stops working automatically; nobody has to remember to delete it.
4. Send the code shortly before arrival rather than at booking time, through whatever messaging channel you already use with guests. This limits how long a working code exists unused.
5. Keep a permanent eKey or admin passcode for yourselfand any cleaning staff, separate from every guest code, so your own access never depends on a booking window.

Even a reliable lock benefits from a fallback. Keep a physical key or a second admin credential accessible to a trusted local contact in case the lock's battery dies or the guest's phone signal makes a call impossible. Batteries on keypad locks typically last many months under normal guest turnover, but a low-battery warning should never be ignored during a busy booking season.

Guest-facing instructions should be short and assume no prior experience with the lock:

• Which door and which keypad, if the property has more than one entrance.
• How to wake the keypad (usually a light touch on any key).
• The exact code, and whether to press a confirm key such as # afterward.
• What to do if the code is rejected — a phone number, not just an email.

• Back-to-back bookings with no buffer. If checkout and check-in are the same day, overlapping timed codes can let the previous guest linger into the next guest's window. Build in at least a short gap.
• Relying on the guest's phone for the code. Send the code as plain text early enough that the guest can write it down; do not assume they will have an eKey app installed.
• Gateway placement. A gateway that is out of Bluetooth range of the lock cannot deliver remote commands, so codes may be created in the app but fail to reach the lock. Keep the gateway within the same room or an adjoining wall.
• One code per booking, not one code forever. Reusing a single passcode across multiple guests removes the audit trail and means a former guest's code still works.