TTLock Tips, Tricks and Hidden Features for Australian Users

Eleven things most McGrath, Lockton, and Austyle owners never discover — including a few that prevent the most common support calls.

TTLock is a deeper platform than most users realise. The official manual runs to 56 pages. Most people read none of it — and that's fine, until something stops working.

This guide is for people who already have a TTLock-platform lock installed and running — a McGrath, Lockton, or Austyle — and want to get more from it. It assumes the lock is set up and working. It is not a setup guide for beginners.

This guide covers:

• Why newly generated passcodes sometimes stop working immediately after creation
• The activation window that applies to each passcode type
• The one code type that deletes every credential on your lock simultaneously
• How to fix the most common cause of time-limited passcode failures on Bluetooth-only setups
• Which gateway to choose — and why that choice determines long-term reliability
• The fingerprint enrolment technique that dramatically improves read reliability
• When to disable Touch-to-Unlock, and how
• Two-factor unlock: which situations warrant it
• The lock transfer step that trips up every property handover
• Battery management for Airbnb and remote properties
• Cyclic passcodes: the scheduling feature most hosts never set up
• The Tamper Alert toggle: leave it off

For a full platform overview — how TTLock works, all six passcode types, and the complete security disclosure — see the TTLock Platform Guide in our Smart Lock Buyer's Guide. If you're using TTLock specifically for Airbnb, our guide to using TTLock for Airbnb in Australia covers PMS integration and automation in detail. If you are still weighing platforms rather than operating one, our five questions for choosing a smart lock platform is the better starting point.

If you prefer to work from the official source, the TTLock User Manual is available as a PDF download and is also indexed on our TTLock user manual reference page. An app overview video is also available, and Australian users may prefer the McGrath Locks App how-to video presented by a local expert.

The 24-Hour Activation Rule — Why New Codes Stop Working

This is the number one cause of "my code doesn't work" support calls. If you take one thing from this guide, make it this rule.

Three of TTLock's six passcode types — Permanent, Time-Limited, and Cyclic — must be used at least once within 24 hours of generation, or within 24 hours of the validity start date for time-limited and cyclic codes. If that window closes without the code being tested at the keypad, the code auto-expires permanently. The app shows no warning. The code cannot be reactivated.

Why TTLock enforces the window

The reason TTLock implements this rule: it prevents pre-generated codes from sitting in an unactivated state where they could be intercepted and used later. It is a deliberate security design choice with one specific, practical consequence. For the broader context of how PIN-based access works in smart locks, see Chapter 03 — Smart Lock Access Methods.

Activation windows by passcode type

The window is not the same length for every code type, which is where a lot of the confusion comes from. This is the practical summary for the code types most owners actually use.

The remaining passcode types, and the full behaviour of each, are set out in the passcode types section of the TTLock Platform Guide.

How to stop codes expiring

The fix is simple: generate the code, then walk to the keypad and test it immediately. Do not generate passcodes in advance and assume they will be ready when a guest arrives three days later.

The working routine, in order:

• Generate the code in the app on the day it first needs to work — not days ahead
• Walk to the keypad and enter it. The entry is the activation; nothing in the app substitutes for it
• Confirm the lock actually released, rather than assuming the beep meant success
• Only then share the code with the guest, cleaner or contractor

If you manage the property remotely:
Activation happens at the keypad, so someone has to be there. For a property you do not attend, ask the cleaner, the outgoing guest or a neighbour to enter the code once on the day it becomes valid. A gateway gives you remote management, but it does not activate a passcode on your behalf.

One-Time passcodes have a shorter window:
One-Time passcodes are valid for 6 hours from generation only — not 24 hours. If a one-time code has been sitting unused for more than 6 hours, generate a fresh one before sharing it.

The Erase Code — The One Code You Should Never Share

TTLock includes a passcode type called the Erase code (referred to as the Clear Code in some app versions). When entered at the keypad, it deletes every passcode stored on the lock simultaneously — guests, cleaners, family members, property managers, all gone in a single entry.

The Erase code is valid for 24 hours from generation. After that window it becomes inert. Its legitimate use is narrow: clearing a lock before a property handover, or after a security incident where you need to wipe all existing credentials and start fresh.

Warning — the Erase code looks identical to any other code:
There is no visual indicator in the app that distinguishes an Erase code from a standard passcode. If you generate one "in case of emergency" and share it with a guest or cleaning team member, a single accidental entry at the keypad wipes every code from the lock. Label it explicitly in your own records. Never share it with anyone other than the lock's administrator.

A scenario that comes up more often than it should: a host generates the Erase code and stores it in a notes app "in case of lockout." A guest finds the note. The guest enters the code. Every credential is gone. Treat the Erase code with the same care as a master key that simultaneously changes every lock.

If an Erase code has already been used

The symptom is unmistakable and easy to misread as a lock fault: every PIN stops working at once, for everyone, with no warning and no pattern. If a single person's code fails, that is not an Erase event. If every code fails simultaneously and the lock still responds normally to Bluetooth and to the app, an Erase code is the first thing to check.

There is no undo. Recovery means re-issuing credentials from scratch:

• Check the event log in the app to see when the wipe happened and confirm what you are dealing with
• Re-issue the administrator's own code first and test it at the keypad, so you have guaranteed access
• Re-issue guest, cleaner and contractor codes, remembering that each one is subject to the activation windows above
• Re-enrol fingerprints and IC cards separately if they were also cleared

Keep a credential list:
Rebuilding access is far quicker if you already have a written record of who holds which credential and on what schedule. This matters most on multi-property portfolios, where the alternative is reconstructing the list from memory under pressure.

Safe use at a property handover

If you are doing a lock reset before a property handover, the correct sequence is: generate the Erase code yourself, test it at the keypad to confirm the wipe, then set up the new owner's credentials from scratch. Do not hand the Erase code to the incoming owner to use independently.

Clock Calibration — The Fix for Most “Valid Code” Failures

TTLock-platform locks have an internal clock that they use to validate time-limited and cyclic passcodes. If that clock drifts — even by a few minutes — codes that appear valid in the app fail at the keypad, because the lock and the app disagree on what time it is.

With a gateway connected, this is not a problem. The gateway calibrates the lock's internal clock automatically and continuously. This is one of the underappreciated benefits of adding a gateway to your TTLock property. For what happens to the lock if the internet goes down while a gateway is connected, see Chapter 08 — What Happens When the Internet Goes Down — local access is unaffected.

Symptoms that point to clock drift

Clock drift produces a very specific fault pattern, and recognising it saves a lot of wasted troubleshooting. It looks like this:

• Time-limited and cyclic codes fail, while permanent codes keep working normally
• A code works at some times of day and not others, particularly near the start or end of its window
• Codes started failing shortly after a battery change
• The event log timestamps do not match when things actually happened
• The lock is on a Bluetooth-only install with no gateway calibrating it

What it is not:
If every code fails including permanent ones, look at the Erase code or the batteries instead. If only one person's code fails, the activation window is the more likely explanation. Clock drift is specifically a time-validated-credential problem.

Calibrating without a gateway

Without a gateway, calibrate the clock manually. The path in the app is: TTLock app → Lock Settings → Diagnosis → Adjust Time. Calibration requires Bluetooth proximity, so it is done standing at the door, not remotely.

Run it at these points:

• After initial pairing, before issuing any time-limited credentials
• After every battery change, without exception
• Periodically on any Bluetooth-only install — folding it into a routine visit costs seconds
• Any time a time-limited or cyclic code fails and you have ruled out the activation window

Battery changes reset the clock — calibrate immediately after:
When batteries are replaced in a TTLock-platform lock, the internal clock may lose its calibration. If time-limited codes start behaving unexpectedly after a battery change, clock drift is the most likely cause. Go to Diagnosis → Adjust Time immediately after fitting new batteries, before testing any time-sensitive passcodes.

G2 vs G5 — Why Your Gateway Choice Affects Reliability

The G2 gateway is the most common choice in residential and Airbnb installs in Australia. It works reliably under simple network conditions. It has one significant limitation: it operates on 2.4GHz WiFi only.

Four gateway generations exist on the platform. If you want the full generation-by-generation breakdown rather than just the G2 and G5 decision, our G2, G3, G4 and G5 gateway comparison covers the PoE and 4G options as well.

The band-steering problem

Most Australian NBN-era routers broadcast a single SSID across 2.4GHz and 5GHz and steer devices between them automatically. The G2 can only connect to 2.4GHz. When the router steers the gateway to 5GHz, the G2 goes offline silently. The symptom is intermittent — the gateway appears online most of the time and drops out unpredictably, for no obvious reason. This is the band-steering problem, and it is the most common source of TTLock gateway complaints in Australia.

Because the failure is silent and intermittent, it is routinely misdiagnosed as a flat battery, a faulty lock, or an app problem. The tell is that local Bluetooth and keypad entry keep working perfectly while only the remote functions come and go. See our dedicated guide on why smart locks drop off WiFi. For a quick reference on the most common WiFi dropout scenarios, see the smart lock FAQ — WiFi connectivity section.

Two ways to fix it

Two solutions exist. Split your router into separate 2.4GHz and 5GHz SSIDs and connect the G2 to the 2.4GHz SSID only — see the hardware fix for persistent band-steering issues. Or upgrade to the G5, which is dual-band and handles both frequencies natively.

The G5 also supports up to 100 locks and uses USB-C power. For any new install, the G5 is the default recommendation — the band-steering relief alone justifies the modest additional cost. For the full gateway comparison across all four models, see gateway selection for TTLock properties.

Where to position the gateway

Placement rule: Position the gateway within 3–7 metres of the lock for reliable Bluetooth communication. 9 metres is the stated maximum; 4.5–7 metres is the reliable operational range in real-world installs. Avoid steel door frames and concrete walls between the gateway and the lock. See Chapter 08 — Gateway Placement for the full guidance.

Gateways we supply

For a new install, the gateway we recommend is the McGrath G5 gateway — dual-band, so the band-steering problem above simply doesn't arise. One G5 serves up to 100 locks, so a single unit usually covers a whole house or a small multi-door site.

The G2 needs one clarification. McGrath has dropped the G2 from its range, but demand for it hasn't gone away, so we supply the Lockton E-Series Wi-Fi Bridge (G2) in its place. It is the same hardware on the same platform — a different badge on the front, nothing more. It pairs with McGrath, Lockton and Austyle locks exactly as the McGrath-branded G2 did, and it carries the same 2.4GHz-only limitation described above.

Both sit in our modules and WiFi gateways range alongside the bridges used by other platforms.

Getting Fingerprints Right — The Enrolment Technique Most People Skip

TTLock supports multiple fingerprint entries per user account. Most people enrol one finger at one angle and accept whatever reliability they get. The platform is designed to do better than this. For the broader context of fingerprint access and its known failure modes, see Chapter 03 — Fingerprint Access.

The three-angle enrolment technique

The technique: enrol the same finger three times at slightly different angles — once straight on, once with a slight tilt to the left, and once with a slight tilt to the right. This covers the natural variation in how the same finger lands on the sensor under different conditions: hands full, slightly wet, cold, or placed at a hurried angle. Multiple enrolment angles give the sensor more reference points to match against.

As a practical backup, also enrol a finger from the non-dominant hand. If the primary hand is occupied — carrying bags, wearing gloves in winter, or holding a coffee — a registered backup finger on the other hand avoids the need to juggle.

What makes the difference in practice:

• Present the pad of the finger flat on the sensor, not the tip — the tip carries less usable ridge detail
• Enrol dry, clean and unhurried, then test wet and in a hurry — that is the real-world condition
• Avoid enrolling a finger with a cut, a callus or a healing blister; re-enrol once it settles
• Prioritise the finger you naturally reach with, not the one that seems tidiest
• Children and older users often need more enrolment attempts — shallower ridge definition, not user error

Timing and conditions matter in coastal Queensland: Fingerprint sensors read differently under varying humidity and temperature. For locks in high-humidity coastal locations — common across South-East Queensland — enrolling at the same time of day you will typically use the lock captures more representative skin-surface data. Coastal conditions affect the hardware too, as our guide to electronic locks in coastal environments sets out.

Touch-to-Unlock — When to Disable It

Touch-to-Unlock is enabled by default on TTLock-platform locks. When active, touching the keypad while the TTLock app is open and your phone is within Bluetooth range unlocks the door without entering any code. This is part of the Bluetooth access mode and is convenient for regular residents at their own front door.

It becomes a problem in several situations. In an office or commercial setting, a phone carried past the door with the app open can trigger an unintended unlock. In properties where the Bluetooth range of the lock or gateway overlaps with a neighbouring door, a neighbour's phone with the app installed can trigger the same. In any environment where reliable keypad-only entry is required, Touch-to-Unlock should be off.

How to turn it off

To disable: TTLock app → Settings (gear icon) → Touch to Unlock → toggle OFF. The setting can be changed remotely with a gateway connected.

When to keep it on: For a residential front door used by regular occupants with the app installed, Touch-to-Unlock works as intended. For an Airbnb property where guests should use a PIN, consider whether explaining the feature to each new guest is worth the occasional unintended unlock. Many Airbnb operators disable it and rely on passcodes alone.

Two-Factor Unlocking — The Security Feature Nobody Enables

TTLock supports requiring two credentials simultaneously to unlock. One credential alone is not sufficient — both must be presented in sequence. Examples: fingerprint followed by PIN, or IC card followed by PIN.

The setting is under Lock Settings → Security Settings → Two-Factor. Exact wording varies by firmware version.

When two-factor makes sense

Two-factor unlock is appropriate in specific contexts: NDIS or disability housing where staff access should be doubly verified and logged, commercial doors where a single compromised credential should not grant entry, or safe rooms. See Chapter 09 — DDA, NDIS & Accessibility for context on how TTLock fits into disability housing applications.

The test to apply before enabling it: is every person who needs to get through this door enrolled, trained, and reachable if something goes wrong? Where the answer is yes — a staffed site, a known team, a controlled roster — two-factor is a genuine security gain at almost no operational cost. Where the answer is no, it converts an ordinary access problem into a lockout.

2FA is Not suitable for Airbnb or short-stay rentals:
Two-factor unlock is not appropriate for guest-facing doors. A guest arriving at 2am who cannot get a fingerprint to register, or who has not enrolled an IC card at this specific lock, will be locked out with no fallback. The Airbnb risk of complex lock configurations is well documented — for short-stay rentals, a single reliable PIN is the right choice. Reserve two-factor for controlled environments where users are trained and enrolled in advance.

Transferring or Re-Adding a Lock — The Step That Trips Up Property Handovers

Once a TTLock-platform lock is paired to an account, it cannot be paired to a new account until the current administrator deletes it from their account while physically at the lock via Bluetooth. The deletion requires Bluetooth proximity. It cannot be done remotely, even with a gateway connected and active.

This catches people out at property sales, rental changeovers, and secondhand lock purchases with more frequency than you would expect. The reason it hurts is timing: the constraint only becomes visible after the previous owner has left, at which point the one action that resolves it — standing at the door with their phone — is the hardest thing to arrange.

Before you hand over the property

The rule: delete the lock from your TTLock account before you vacate the property or hand over the hardware. Do this while physically at the door, before you leave for the final time. The process takes approximately thirty seconds.

The complete handover sequence, in order:

• Wipe stored credentials at the keypad with an Erase code, so no old PIN survives the handover
• Delete the lock from your TTLock account, standing at the door with Bluetooth in range
• Delete or transfer the gateway as well — a gateway left on your account is the second most common handover snag
• Remove any IC cards and fobs from the property, or hand them over deliberately with the keys
• Confirm with the incoming owner that they can add the lock to their own account before you leave the area

If you are taking on management of a property with an existing TTLock lock and you are not sure whether it is registered to another account, test it: try to add the lock in the TTLock app. If it refuses, the lock is still registered and you need to track down the previous account holder. If you need professional help with a lock handover situation, see our professional installation and setup service.

Battery Management — The Silent Reliability Factor

Low battery in a TTLock-platform lock affects remote functions before it affects local functions. The lock may still open reliably at the keypad while the gateway has already lost communication with it. From the outside — and from the outside is how an Airbnb host typically monitors their property — everything appears to be working. Remote unlock stops responding and push notifications stop arriving with no obvious indication of why. This is one of the most common causes of what actually fails in electronic locks in real-world operation.

Reading a low-battery fault correctly

Because the remote side fails first, a flat-ish battery and a WiFi problem look identical from your phone. The two are told apart at the door, not in the app:

• Remote commands fail but the keypad opens the door normally — suspect battery before network
• Both remote and local are unreliable, and the motor sounds slow or laboured — battery, clearly
• Local access is flawless and only remote is intermittent, on a G2 with a single-SSID router — suspect band steering rather than power
• Nothing responds at all — the batteries are flat, and the mechanical key override is the way in

That last case is worth preparing for before it happens. Our guide to what to do when the battery dies covers where the override keyhole is hidden on each style of lock and where to keep the key.

Monitoring and choosing batteries

For Airbnb properties or any lock in an access-critical role: check the battery level in the app weekly. The TTLock home screen shows battery level for every connected lock. Replace batteries at 20% remaining — don't wait for keypad warning beeps, which occur much later in the discharge cycle. For realistic battery life expectations, see our guide to battery life — the truth, not the marketing version.

Battery choice and cold weather: Use quality AA alkaline batteries — Duracell or Energizer are the standard recommendation. Cheap cells underperform, particularly in cold temperatures. For locks at regional, highland, or mountain properties, battery output drops noticeably in winter. Budget for more frequent replacement from June through August and replace proactively. For a full picture of realistic lock lifespan expectations, including battery factors, see our guide to realistic digital lock lifespan expectations.

After every battery change: calibrate the clock at Lock Settings → Diagnosis → Adjust Time before testing any time-limited passcodes. As described in the clock calibration section above, battery replacement is the most commonly skipped calibration step.

Cyclic Passcodes — The Scheduling Feature Most Hosts Overlook

TTLock's cyclic passcode type repeats on a set schedule: daily, weekdays only, weekends only, or a specific day of the week. The code is valid within a defined time window on each qualifying day — for example, 9am to 3pm every Tuesday.

The weekly cleaner use case

The most practical use case: a cleaner on a fixed weekly schedule. Generate a cyclic passcode once, set it to Tuesday 9am–3pm. The code is available every Tuesday morning and usable at no other time. No weekly regeneration, no shared master code, no need to remember to update anything. This is how TTLock's passcode scheduling genuinely separates itself from competing platforms that offer fewer scheduling types.

Two details make the difference between this working and quietly failing. Set the window wider than the appointment — a cleaner booked for 10am who arrives at 8:45am on a 9am code is a phone call you did not need. And keep one cyclic code per person rather than one shared code for "cleaners", so that removing one person's access does not disrupt everyone else's.

Other recurring access patterns

The same pattern works for: property managers with a fixed monthly inspection day, regular contractors on a specific weekly pattern, gardeners and pool servicing on a set day, or any recurring access requirement where a time-limited passcode would otherwise need regenerating repeatedly. For how these integrate into a fully automated Airbnb PMS workflow, see PMS platforms that integrate with TTLock, and Chapter 07 — Property Management Systems for the broader context.

The 24-hour activation rule applies here too:
Cyclic passcodes are subject to the same activation requirement as permanent and time-limited codes — the code must be used at least once within 24 hours of the first validity window opening, or it expires permanently. After generating a cyclic passcode, use it yourself on its first scheduled day to activate it, then hand it over. See the 24-hour activation rule section above for full detail.

Tamper Alert — Leave It Off

Every TTLock-platform lock shows a Tamper Alert toggle in the app. The toggle is present because the TTLock platform supports tamper detection when the connected lock hardware includes the required sensor. On the TTLock-platform locks sold in Australia, that hardware is not present.

Enabling the toggle causes phantom alert notifications — the app reports tamper events for no physical reason, because the software is polling a sensor circuit that exists in the platform design but is not populated in the hardware of these models. The alerts look real, occur randomly, and provide no useful information.

Leave the Tamper Alert toggle OFF.

Which locks this applies to

More badges run on TTLock than most owners realise, and the guidance is the same across all of them. Leave Tamper Alert off on:

• McGrath Locks, Lockton and Austyle smart locks
• Vault smart locks, which run on a rebranded TTLock platform under the Vault app
• Zanda Stealth smart locks, which are also a TTLock-platform range

Not every intrusion alarm is a phantom:
Locks from other platforms — Yale, Lockwood and Carbine among them — have genuine break-in and tamper alarms backed by real hardware, and those should be left enabled. This guidance is specific to the TTLock Tamper Alert toggle on the ranges listed above. If you are not sure which platform your lock runs on, Chapter 15 — Smart Lock App Platforms identifies each one.

If you are already receiving phantom tamper alerts and want the step-by-step procedure to stop them, see how to turn off Tamper Alert in three steps, and what to do if the alerts continue afterwards. For the technical explanation of why the toggle exists when the hardware doesn't support it, see Tamper Alert on Smart Locks — What It Is and Why You’re Getting Phantom Alerts. For a quick FAQ answer, see the smart lock FAQ — tamper alert section.

Frequently Asked Questions

Why does my new TTLock passcode not work?

Almost always the 24-hour activation rule. Permanent, Time-Limited and Cyclic passcodes must be entered at the keypad once within 24 hours of generation — or within 24 hours of the validity start date — or they expire permanently, with no warning shown in the app. One-Time passcodes have a shorter 6-hour window. Generate the code on the day it is needed and test it at the door before sharing it.

All of my codes stopped working at once — what happened?

If every PIN fails simultaneously and the lock still responds to Bluetooth and to the app, an Erase code has most likely been entered at the keypad. The Erase code deletes every stored passcode in a single entry. There is no undo — check the event log to confirm the timing, then re-issue the administrator code first, test it, and rebuild the remaining credentials from there.

What is the Erase code in TTLock and is it dangerous?

The Erase code, called the Clear Code in some app versions, deletes every passcode stored on the lock when entered at the keypad. It is valid for 24 hours from generation. It should never be shared with guests or cleaning staff, because a single accidental entry wipes every credential at once. Its legitimate uses are narrow: clearing a lock before a property handover, or after a security incident.

My time-limited codes fail but permanent codes work — why?

That pattern points to clock drift. The lock validates time-limited and cyclic codes against its own internal clock, so if that clock has drifted the lock and the app disagree about what time it is. Permanent codes are unaffected because they carry no time condition. Calibrate at Lock Settings, Diagnosis, Adjust Time, standing at the door with Bluetooth in range. A connected gateway calibrates the clock automatically and prevents the problem entirely.

Do I need a gateway for my McGrath or Lockton smart lock?

Not for basic operation. Without one, the lock works over Bluetooth when you are nearby, and passcodes and cards work with no internet connection at all. A gateway adds remote lock and unlock, real-time notifications, remote passcode management, automatic clock calibration, and voice control. If you manage access from a distance — Airbnb, a holiday home, an office — a gateway is worth having. On an Australian NBN home, choose the dual-band G5 over the 2.4GHz-only G2 to avoid band-steering dropouts.

My gateway keeps dropping offline for no reason — what is causing it?

On a G2, band steering is the usual answer. Most Australian routers broadcast one network name across 2.4GHz and 5GHz and move devices between them automatically; the G2 can only use 2.4GHz, so when the router steers it to 5GHz it drops offline silently. The tell is that keypad and Bluetooth access stay perfect while only remote functions come and go. Either split the router into separate 2.4GHz and 5GHz network names, or move to the dual-band G5.

Should I turn Tamper Alert on?

No. Leave it off on every TTLock-platform lock sold here, including McGrath, Lockton, Austyle, Vault and Zanda Stealth. The toggle appears because the TTLock platform supports tamper detection, but the required sensor hardware is not fitted to these models, so enabling it produces random phantom notifications that carry no information. Genuine intrusion alarms on other platforms, such as Yale and Lockwood locks, are a different feature and should be left enabled.

How do I transfer a TTLock lock to a new owner?

The current administrator must delete the lock from their TTLock account while physically at the lock, over Bluetooth. This cannot be done remotely, even with a gateway connected. Do it before you vacate the property: wipe the stored codes with an Erase code, delete the lock, delete or transfer the gateway too, and confirm the new owner can add the lock before you leave. Once deleted, the new owner pairs it to their own account.

I bought a secondhand lock and it will not pair to my account — can it be fixed?

The lock is still registered to the previous owner's TTLock account. The only clean fix is for that account holder to delete it while standing at the lock with Bluetooth in range; failing that, Sciener support has to be approached directly. Neither route is quick, which is why the deletion step belongs in the handover rather than after it. Before buying a secondhand TTLock-platform lock, ask the seller to delete it from their account in front of you.

Can I use TTLock without WiFi?

Yes. TTLock-platform locks operate fully over Bluetooth with no gateway and no WiFi. Passcodes and IC cards work with no internet connection. What you give up is remote lock and unlock, real-time notifications, remote passcode management and automatic clock calibration — and you must calibrate the internal clock manually after setup and after each battery change. If reliable access with no internet at the property is the priority, Igloohome's algoPIN technology validates time-limited codes on the lock itself and may suit better.

How do I tell whether my lock is TTLock or another platform?

The app is the giveaway, not the badge on the door. McGrath, Lockton, Austyle, Vault and Zanda Stealth locks all run on TTLock, sometimes through a manufacturer-branded version of the app. Tuya sits behind a different set of brands and apps entirely, and Carbine Connect is a separate platform again — a white-labelled Sunion Technology system, not TTLock and not Tuya. Chapter 15 — Smart Lock App Platforms maps each platform to the brands that use it.

Where does my TTLock data actually go?

Event logs and remote commands transit Sciener's servers, which are hosted in China. Local Bluetooth access and keypad entry involve no cloud connection at all, so a lock with no gateway fitted sends nothing anywhere. Whether that matters depends on the property and the operator — our guide to where each platform hosts its data compares the major platforms side by side.

How many fingerprints should I enrol per person?

Three entries of the same finger, at slightly different angles, plus one finger from the other hand as a backup. TTLock allows multiple fingerprint entries per user, and each additional angle gives the sensor more reference points to match against — which is what carries read reliability through wet hands, cold mornings and hurried arrivals. Enrolling one finger once is the single most common reason a fingerprint reader feels unreliable.

Remote unlock has stopped working but the keypad is fine — battery or WiFi?

Both produce that exact symptom, because remote functions fail before local ones in each case. Check the battery level in the app first and replace at 20% remaining. If the batteries are healthy and the gateway is a 2.4GHz-only G2 on a single-name home network, band steering is the more likely cause. If the motor also sounds slow or laboured at the door, it is the batteries.

Related Guides in This Series

Something Not Working the Way It Should?

If a setting isn't where this guide describes it, or a problem doesn't match any of the scenarios above, our team can walk you through it.

Disclaimer: App interface wording, menu locations, and feature availability change with TTLock firmware and app updates. The steps described in this guide reflect the TTLock app as reviewed in August 2026. Verify current behaviour in your installed version before acting on any of the settings described here.