TTLock Passcode Not Working? Here's Why

TTLock locks store passcodes on the lock itself, and they judge time using their own internal clock. A code fails when the lock has never received it, when the lock thinks it is outside its validity period, or when the keypad entry never completed.

• The passcode was never synced. Custom and permanent passcodes you create in the app are queued and transferred over Bluetooth on the next connection. Without a Wi-Fi gateway there is no other path to the lock. This catches out almost every new user who sends a code to a remote guest.
• The code expired — or hasn't started yet. Timed codes have both a start and an end. A code created for "tomorrow 3pm" is rejected today.
• It was a one-time code that has been used. One-time passcodes are valid for a single unlock, and they also expire unused once their validity period ends.
• It was a cyclic code outside its schedule. Cyclic passcodes only work on the chosen weekdays and inside the chosen hours — a cleaner's Monday 9–12 code does nothing on Sunday evening.
• The lock's clock has drifted. Over months the internal clock slips, so timed codes start and stop at the wrong moment — often by minutes, sometimes by hours.
• The entry was never confirmed. Many locks require the unlock key or # after the digits.
• The code was deleted or overwritten. Locks hold a finite number of passcode slots; a newer code can take over the slot an older one used.
• Keypad hardware. A worn or wet keypad can miss a digit consistently — usually the same one every time.

1. Sync the code to the lock. Stand next to the lock with the app open and connect over Bluetooth. Opening the lock's screen is enough to push queued passcodes and settings. If you have a gateway, confirm it is online first — then the sync happens remotely.
2. Open the passcode in the app and read its type and validity. Confirm whether it is permanent, one-time, timed or cyclic, and check the exact start and end times, including AM/PM.
3. Resync the lock clock. Connect over Bluetooth from the app; the time is corrected on connection. Do this before troubleshooting any timed code, because drift makes a valid code look broken.
4. Enter the code the way the lock expects. Wake the keypad with a touch, type the digits, then press the unlock key or # to submit. Type steadily — a long pause between digits can time the entry out.
5. Test with a known-good permanent code. Create a permanent passcode, sync it at the door, and try it. If it works, the problem is the original code's type or schedule. If it also fails, move on to the keypad and lock checks below.
6. Reissue the code. Delete the failing passcode, generate a new one, and sync it at the door before sending it to the guest.

• Check the lock's passcode list, not just the app's. If the lock is at its slot limit, delete stale codes and resync so the new one has room.
• Replace the batteries. Low power causes erratic keypad and motor behaviour, and it also blocks the Bluetooth connection you need to sync. See TTLock battery draining fast.
• Isolate the keypad. Press each digit and listen for the tone or watch the backlight. A digit that never registers means hardware, and no code containing that digit will ever work.
• Check for a passage or lockout mode. Some locks support a privacy/lockout state that rejects normal passcodes until it is cleared.
• Confirm you are the admin for that lock. Codes generated by a different account for a lock you only hold an eKey to may not be authorised to be created at all.
• Read the unlock records. The activity log shows whether the lock received and rejected an entry, or never saw one — that single detail separates a keypad problem from a code problem.

For remote guests, a Wi-Fi gateway is the durable fix: with one installed, new passcodes reach the lock without anyone standing at the door. See the TTLock gateway setup guide.