How to send a TTLock temporary passcode to a guest

Smart Lukko is an independent third-party app for TTLock-compatible smart locks, not affiliated with TTLock or Sciener, and it generates codes the same way the official app does for locks that use this platform. Before creating a temporary code, make sure you have:

• Admin access to the lock in the app, either as the original owner or as an admin eKey holder.
• A working keypad on the lock. Codes only work on locks with a keypad; keypad-less models rely on cards, fingerprints or the app instead.
• A way to sync the code to the lock — Bluetooth range at the time of creation, or a paired gateway if you want to set the code while away from the door.
• A delivery channel for the guest — text message, chat app, or a printed note left for check-in.

1. Open Smart Lukko and select the lock from your device list.
2. Tap Passcodes, then Add passcode.
3. Choose Timed passcode for a code that works repeatedly within a date and time range (ideal for a guest's whole stay), or One-time passcode for a code that works exactly once and then deactivates itself.
4. Set the start and end date/time for a timed code. Keep the window as tight as the stay requires — check-in day to check-out day is usually enough.
5. Optionally name the code (e.g. "Guest — weekend") so you can identify it later in the list.
6. Tap Save/Send. If your phone has an active Bluetooth connection to the lock, the code syncs immediately. If not, keep the app open near the lock once, or let a paired gateway push it over the internet.
7. Copy the generated digits and send them to the guest by text or message, along with the keypad's wake instructions (tap the keypad, then enter the code followed by the unlock key, typically # on most models).

Two different mechanisms produce a working temporary code, and it matters which one your lock uses:

• Synced codes. The app writes the code directly onto the lock's memory over Bluetooth, or via a gateway relaying the command over Wi-Fi. The lock then checks the entered digits against its own stored list — it works even if the lock has never been online, as long as the code was synced at least once.
• Offline (algorithm-based) codes. Some locks can generate a code mathematically from the current time and a secret key, without ever connecting to a phone. The lock validates the code's time-derived pattern rather than a stored list. This is useful when you cannot get close enough to sync, but it depends on the lock's internal clock staying accurate and on firmware support for offline codes — not every model offers it.

If a guest reports that a freshly created code does not work, the most common cause is that it never reached the lock: sync it once more within Bluetooth range, or confirm the gateway is online, before troubleshooting further.

• Sending the code before it syncs. Creating a code in the app does not put it on the lock instantly unless you are in Bluetooth range or a gateway is online. Always confirm the sync succeeded before handing the code over.
• Setting a validity window in the wrong timezone. The lock uses the time it was last synced with, so double-check the window against local time at the property, not your own if you are managing it remotely.
• Reusing the same one-time code for two guests. A one-time code deactivates after its single use; issue a fresh code for the next guest instead of resending the old digits.
• Forgetting to delete expired codes. Timed codes stop working automatically at the end of the window, but tidying the passcode list makes it easier to audit who had access and when.