TTLock App Not Responding: Why the Lock Won't Answer Commands

"Not responding" almost always means the command from your phone never reached the lock's motor, rather than the app being broken. A lock command has to survive a Bluetooth handshake, a permission check, and then a mechanical action, and any of those three stages can fail silently.

• The Bluetooth handshake times out. The phone connects but the authentication exchange with the lock stalls, often from distance, interference, or a stale cached connection.
• Another phone or the gateway is already connected. TTLock-compatible locks typically accept one active Bluetooth connection at a time; if a gateway or a second admin's phone is mid-session, your command queues or is dropped.
• The motor or clutch is jammed. A misaligned strike plate, a stiff deadbolt, or debris in the mechanism can prevent the motor from completing its turn even after it receives a valid command.
• Low battery. As batteries drain, the motor may not have enough current to throw the bolt even though the Bluetooth radio still responds to the app.
• Your eKey permission has expired or was revoked. A time-limited or revoked eKey lets the app connect but the lock silently refuses the unlock command.
• Remote unlock is disabled on the lock. Some admins turn off remote/app unlock as a security setting, which blocks app-based commands while leaving the keypad and cards working normally.

1. Force-close and reopen the app. This clears a stuck Bluetooth session more reliably than just backgrounding it.
2. Move within one to two metres of the lock. Stand on the same side as the keypad with a clear line of sight; retry the command.
3. Close other apps or devices connected to the lock. Ask anyone else nearby to close their TTLock app, and if a gateway is installed, note that some models briefly disconnect the gateway when a phone connects directly — give it a few seconds.
4. Check for a mechanical jam. Try turning the thumbturn or key manually. If it's stiff, the motor won't be able to move it either; realign the strike plate or lubricate the mechanism per the lock's manual.
5. Replace the batteries with a fresh matched set. Mixing old and new cells causes inconsistent power delivery to the motor.
6. Ask the admin to confirm your eKey is active and remote unlock is enabled. Both settings live in the admin's app under that lock's user list and settings.

Because a TTLock-compatible lock generally supports only one live Bluetooth session at a time, having a gateway, the stock TTLock app, and Smart Lukko all trying to talk to the same lock at once produces exactly this symptom: the app appears to send the command but nothing happens. If you have a gateway installed, most locks briefly favour a direct phone connection when one is requested, but there can be a short handoff delay. If commands consistently fail only when the gateway is present, try disconnecting it temporarily to confirm it is the source of the conflict before troubleshooting further.

• Test with a different phone. If a second device controls the lock normally, the problem is your phone's Bluetooth stack rather than the lock.
• Restart the phone's Bluetooth. Toggle it off and on, or reboot the phone, to clear a corrupted pairing cache. See the Bluetooth troubleshooting guide for deeper steps.
• Check the lock's own indicator. A red flashing LED or repeated beep pattern on the keypad usually signals low battery or a mechanical fault independent of the app.
• Re-add the eKey. If permissions look correct but the lock still refuses you, ask the admin to delete and re-share your eKey rather than editing the existing one.
• Smart Lukko is an independent third-party app for TTLock-compatible locks, not affiliated with TTLock or Sciener, so exact error messages and LED behaviour vary by lock manufacturer.