TTLock Delete Lock Failed: How to Unpair a Lock That Won't Remove

Deleting a lock is not just a cloud-side database change — the app has to actually connect to the physical lock and tell it to clear its admin binding. If that connection can't be established, or the lock has dependent data still attached, the delete request fails or hangs.

• The phone isn't in Bluetooth range as the admin. Deleting a lock typically requires the admin's phone to connect directly and confirm the removal on the lock itself.
• Sub-eKeys haven't been revoked first. Some locks or app versions require every shared eKey to be revoked before the lock itself can be deleted, since deleting the lock also invalidates any keys still pointing to it.
• The lock is bound through a gateway that's also offline. If you're trying to delete remotely through a gateway and the gateway itself has lost connection, the delete command never reaches the lock.
• You're trying to delete a lock that's currently offline. A lock with dead batteries or one that's been physically removed can't confirm the delete, so the app request stalls or errors out.
• The lock is still bound to a former owner's account. If you never actually completed adding it under your own account, you may be trying to delete a lock you don't truly control — the request fails because the backend rejects it, not because of a connection issue.

1. Revoke all shared eKeys first. Open the lock's user/eKey list and remove every shared user before attempting to delete the lock itself.
2. Stand within Bluetooth range as the admin. Get within a metre or two of the lock, on the keypad side, and make sure you're logged in as the account that added it.
3. Wake the lock before deleting. Touch the keypad so it's actively advertising over Bluetooth, then immediately attempt the delete in the app.
4. Check the gateway's status if deleting remotely. If the gateway shows offline, resolve that first, or move within direct Bluetooth range instead of relying on the gateway path.
5. Confirm the batteries are working. A lock with dead batteries can't respond to a delete command at all; replace them and retry.
6. Retry after a few minutes. Occasionally a stuck cloud-side state resolves itself; force-close and reopen the app before trying again.

Sometimes you need to remove a lock from your account even though it's gone for good — destroyed, discarded, or otherwise unreachable. Because the standard delete flow expects to talk to the physical lock, this scenario often fails with a normal in-app delete. If the app offers a "force delete" or "remove offline device" option in the lock's advanced settings, that path removes the cloud record without needing a live connection. Where no such option exists, the lock's record may need to stay in the account until support tooling clears it, since the app generally can't fabricate confirmation from hardware that no longer exists.

• Factory reset the lock as a last resort. A physical reset via the battery-compartment button clears the admin binding on the lock directly, which effectively unpairs it even if the app-side delete kept failing. See the reset guide for steps.
• Still shows in someone else's account? If a lock is bound to a former owner and you can't reach that account, a factory reset is generally the only way forward, since only the admin account or a physical reset can release the binding.
• Delete keeps timing out over the gateway? Try disconnecting the gateway temporarily and deleting directly over Bluetooth instead.
• Sub-eKeys won't revoke? Confirm you're logged in as the original admin account — only the admin, not a shared user, can revoke other users' eKeys.
• Smart Lukko is an independent third-party app for TTLock-compatible locks and is not affiliated with TTLock or Sciener; exact delete flows and error messages can differ slightly by hardware manufacturer.