How to set up a TTLock cyclic passcode for staff

Smart Lukko is an independent third-party app for TTLock-compatible smart locks, not affiliated with TTLock or Sciener; cyclic passcode support depends on the specific lock model and firmware, so confirm the option appears in your passcode menu before planning around it. You will need:

• Admin access to the lock in the app.
• A keypad-equipped lock with cyclic passcode support.
• Bluetooth range or a paired gateway to sync the new code onto the lock.
• An accurate lock clock, since cyclic windows are enforced by the lock's own internal time, not the phone's.

1. Open Smart Lukko and select the lock.
2. Tap Passcodes, then Add passcode.
3. Choose Cyclic (sometimes labelled Recurring) from the passcode type list.
4. Select the days of the week the code should work — for example, Monday through Friday for a weekday cleaner, or Saturday and Sunday for weekend-only staff.
5. Set the daily start and end time for the window, such as 9:00am to 1:00pm. The code only works inside this window on the selected days.
6. Save, then sync it to the lock over Bluetooth or let a paired gateway push it.
7. Send the code to the person and confirm the schedule with them, including which days it does not work.

Cyclic codes suit anyone with a predictable, repeating schedule better than a timed or permanent passcode:

• Weekly cleaners: restrict the code to the specific weekday and a couple of hours around the expected visit, rather than leaving it valid all week.
• Weekend-only staff: select just Saturday and Sunday, with a window matching working hours, so the code is dormant the rest of the week.
• Daily service visits: select every day with a tight morning or evening window if someone (such as a caretaker) needs brief daily access.

Because the schedule repeats indefinitely until you edit or delete it, cyclic codes save you from recreating a timed passcode every single week for ongoing arrangements.

A cyclic passcode's window is enforced against the lock's own internal clock, not your phone's clock at the moment you set it up. That clock is normally set once when the lock is initialised and kept roughly accurate afterward, but it can drift over time on locks that go without a Bluetooth or gateway sync for long stretches, since some models only correct their clock during a sync with the app. If a cyclic code starts working a few minutes early or late, or on what looks like the wrong day near a boundary, check that the lock has synced recently and that the property's timezone matches what you configured — this matters especially for locks managed remotely across timezones, where the app might show one local time while the lock itself is still running on another.

• Not universally supported. Some lock models or older firmware do not offer cyclic passcodes at all; check the Add Passcode menu for the option before relying on it.
• No holiday exceptions. A cyclic code keeps running on its set days indefinitely; it will not automatically skip a single week off unless you manually disable it beforehand.
• Clock drift risk. Because enforcement depends on the lock's own clock, infrequently synced locks can develop timing inaccuracies that shift when the window actually opens and closes.
• One schedule per code. If someone works split shifts on different days with different hours, you may need more than one cyclic passcode rather than a single code covering irregular patterns.