TTLock Remote Unlock: How to Unlock Your Door From Anywhere

• A TTLock-compatible Wi-Fi gateway installed within Bluetooth range of the lock and connected to a working home Wi-Fi network.
• The gateway bound to the same account as the lock, so the app knows they belong together.
• An internet connection on both ends — the gateway's home network and the phone doing the remote unlocking.
• Remote unlock enabled for that user. Some admins restrict remote unlock to themselves and issue local-only eKeys to guests.

1. Set up the gateway near the lock. It needs to stay within stable Bluetooth range at all times, not just during setup.
2. Confirm the gateway shows as online in the app before relying on it; an offline gateway makes remote unlock unavailable.
3. Open the lock's settings and check the remote unlock toggle is enabled, since some apps or lock models ship with it off by default.
4. Unlock from the lock's detail screen while away from home. The request travels over the internet to the gateway, which relays it to the lock over Bluetooth.
5. Check the activity log after unlocking to confirm the action was recorded, which also confirms the round trip worked end to end.

Remote unlock is inherently slower and less predictable than standing at the door, because the command has to cross the internet twice and then complete a Bluetooth exchange with the lock.

• Expect a few seconds of delay, longer if the gateway's Wi-Fi or the phone's mobile connection is weak.
• A failed or timed-out request should never be assumed to have worked. Always check the log or listen for the lock's own feedback if you are on a video call with someone at the door.
• Remote unlock widens the attack surface compared with Bluetooth-only use, since it depends on account security and internet infrastructure rather than physical proximity. Use a strong account password and enable any two-factor option the app offers.
• Restrict remote unlock permission per user where the app allows it, so guests and short-term codes cannot trigger it even if their eKey is compromised.

• Expecting remote unlock without a gateway. Bluetooth alone has no way to reach the lock from outside its immediate range, regardless of app updates.
• Placing the gateway too far from the lock. Weak Bluetooth signal between gateway and lock causes remote commands to fail intermittently even when both show as online.
• Relying on remote unlock as the only way in. Keep a physical passcode, card or key as a fallback for when Wi-Fi, the gateway or the internet is down.
• Forgetting to re-enable remote unlock after a firmware or app update that reset lock settings to defaults.