How to read TTLock unlock records and access logs

Smart Lukko is an independent third-party app for TTLock-compatible smart locks, not affiliated with TTLock or Sciener, and unlock records are read the same way across locks built on this platform. To review them you need:

• Admin or eKey access to the lock in the app; the level of detail shown can depend on your permission level.
• A recent sync — Bluetooth range at some point, or a paired gateway online, since the lock stores events locally until they are pulled into the app.
• Named users and passcodes set up in advance if you want records to show who did what rather than just a code number.

1. Open Smart Lukko and select the lock.
2. Tap Records or Unlock history (naming varies slightly by version).
3. If your phone is in Bluetooth range, the app usually syncs automatically on opening the screen; if not, connect once or wait for a paired gateway to relay stored events.
4. Scroll the list, which typically shows timestamp, method (passcode, card, fingerprint, app/eKey, or mechanical key) and, where identifiable, the name or label of the credential used.
5. Tap an entry for more detail if the app supports it, such as the specific passcode name used.
6. For auditing, filter or scroll to the relevant date range and cross-reference with your passcode/eKey list to match anonymous-looking entries (like a bare code number) to a person.

The lock logs every unlock event to its own internal memory regardless of whether a phone or gateway is nearby. Those events only become visible in the app once they are pulled off the lock: opening the app within Bluetooth range triggers a sync of pending records onto your phone, and a paired gateway does this automatically and continuously by relaying data between the lock and the cloud over Wi-Fi. Without either, records can sit on the lock for some time, and the app's history will lag behind reality until the next sync happens. A lock's internal memory for storing events is also finite, so very old entries can eventually be overwritten if the lock goes a long time without syncing.

To make records genuinely useful for accountability, set access up so each person's entry is distinguishable rather than anonymous:

• Give each person their own passcode or eKey rather than sharing one code among several people; shared codes only tell you that someone used it, not who.
• Name passcodes and eKeys descriptively (e.g. "Cleaner — Tue/Thu") so records reference something meaningful instead of a raw digit string.
• Register fingerprints and cards per person where the lock supports it, since these are inherently individual credentials.

Depending on the app version, unlock records can be viewed on-screen and, on some builds, exported for record-keeping. There is no universal guarantee of export support across every lock and app combination, so check the Records screen for a share or export option before relying on it for formal audits. Retention itself is bounded by the lock's onboard memory capacity, which varies by model; syncing regularly (via Bluetooth visits or a gateway) is the most reliable way to preserve a complete history in the app rather than risk older entries being overwritten on the lock.