TTLock Bluetooth Not Connecting: 7 Fixes That Work
In most cases the lock is simply out of range, or another phone still holds the Bluetooth connection. Walk within one metre of the lock, close the app fully (don't just background it), and try again. If that doesn't work, the next most likely causes are a missing permission on your phone and low batteries in the lock.
Why this happens
TTLock locks have no Wi-Fi radio of their own. Every command from your phone travels over Bluetooth Low Energy, which means the connection depends on three things: the lock has enough power to run its radio, your phone is allowed to scan for nearby devices, and no other device is already connected.
The usual culprits, roughly in order of how often they occur:
- Bluetooth is off, or the phone is in airplane mode. Airplane mode disables Bluetooth on many phones even when the Bluetooth toggle looks enabled.
- You're out of range. Bluetooth on these locks reaches roughly 3–5 metres in open air, and considerably less through a solid door or a metal frame. Standing inside while the lock faces outward can be enough to break it.
- Missing permission on Android. Android requires Location permission for Bluetooth scanning. Without it the app can connect to nothing at all — this is the single most common Android cause.
- Missing permission on iOS. The app needs Bluetooth access granted under Settings > Privacy & Security > Bluetooth.
- Another device already holds the connection. Only one phone can be connected to the lock at a time. A family member standing nearby, or the stock TTLock app still open on another device, will block you.
- Low batteries. The Bluetooth radio fails before the motor does, so a lock with tired batteries can still open by keypad while refusing every connection attempt.
- Stale app state. A backgrounded app can keep a half-open Bluetooth session that the operating system never tears down.
How to fix it: 7 fixes that work
- Turn airplane mode off and Bluetooth on. Open your phone settings, confirm airplane mode is off, and confirm the Bluetooth toggle is on — not just visible in the control centre.
- Stand within one metre of the lock, on the same side as the keypad. Open the door if you can, so the door leaf isn't between your phone and the lock.
- Grant Location permission on Android. Go to Settings > Apps > Smart Lukko > Permissions and allow Location (and Nearby devices on Android 12 and newer). Android blocks all Bluetooth scanning without it.
- Grant Bluetooth permission on iOS. Go to Settings > Privacy & Security > Bluetooth and enable Smart Lukko. If the app never appears in that list, reinstall it and accept the permission prompt on first launch.
- Disconnect every other device. Force quit the stock TTLock app and Smart Lukko on any other phone within range, and ask anyone standing nearby to close their app. Then retry from your phone alone.
- Force quit the app completely. Swipe it out of the app switcher — backgrounding it is not enough — then reopen it and connect.
- Reset the phone's Bluetooth stack. Toggle Bluetooth off, wait a full 10 seconds, and turn it back on. If the connection still fails, restart the phone, which clears the cached Bluetooth device state entirely.
Work through them in order. Fixes 2, 3 and 5 resolve the large majority of cases on their own.
If that didn't work
- Replace the batteries. If the keypad opens the door but no phone can connect, that pattern points squarely at power. Fit a fresh matched set of AA cells — lithium if the door is outdoors or cold.
- Wake the lock first. Touch the keypad so it lights up, then immediately try to connect. A sleeping lock advertises less frequently.
- Remove the phone's stale pairing. If the lock appears under your phone's system Bluetooth list, choose "Forget this device". TTLock locks are managed inside the app, not through system pairing.
- Test with a second phone. If another phone with an eKey connects fine, the problem is on your handset: permissions, Bluetooth cache, or an OS-level power saver throttling background radios.
- Turn off aggressive battery saving. Battery optimisation on some Android skins suspends Bluetooth scanning for apps that aren't in the foreground. Exclude the app from optimisation.
- Check whether you still have access. If your eKey was revoked or expired, the app can see the lock but not open it. Ask the lock admin to reissue your key.
Still stuck? A lock that refuses every phone at close range with fresh batteries needs a hardware check — contact your lock's manufacturer, since the Bluetooth module is part of the lock, not the app.
Frequently asked questions
What is the Bluetooth range of a TTLock smart lock?
Expect roughly 3 to 5 metres in open air. A solid door, a metal frame or a thick wall can cut that to a metre or less, which is why standing right at the lock is the first thing to try.
Why does the app need Location permission on Android?
Android treats Bluetooth scanning as location-capable, so it blocks all scanning for apps without Location permission. Granting it lets the app discover your lock; it is not used to track you.
Can two phones connect to the same lock at once?
No. A TTLock lock accepts one Bluetooth connection at a time. If someone nearby has the app open, or the stock TTLock app is connected on another device, your phone will fail to connect until they disconnect.
Why does the keypad work but Bluetooth doesn't?
The Bluetooth radio needs stable voltage and gives up before the motor does. When the keypad still opens the door but no phone can connect, low batteries are the most likely explanation.
Do I need a gateway to fix Bluetooth connection problems?
No. A gateway adds remote control over the internet, but Bluetooth is still used for nearby operation and for syncing settings. A gateway will not repair a failing Bluetooth link at the door.
Related feature: TTLock Wi-Fi gateway setup guide (remote unlock without Bluetooth)
Keep reading
- TroubleshootingLock Not Found in the TTLock App: What to Check
- TroubleshootingTTLock Battery Draining Fast: Causes and Fixes
- TroubleshootingTTLock Passcode Not Working? Here's Why