McGrath, Lockton and Austyle all run on TTLock. Here is what that means for how you manage access, what the six passcode types actually do, how gateways fit in, and what the platform's security disclosures say.
Most Australian buyers first encounter TTLock through a brand name — McGrath, Lockton, or Austyle. These are the hardware brands. TTLock is the platform behind all of them: the software, the cloud, and the access management system that makes the hardware work.
Understanding the platform, not just the lock, helps you make a better purchase decision and avoid the most common setup mistakes. This chapter explains what TTLock is, how its access system works, and where it fits best — and where it doesn't. If you are already using a TTLock-platform lock and want operational tips, the TTLock tips, tricks, and hidden features guide covers the practical side. For the Airbnb automation workflow, see using TTLock for Airbnb in Australia. The complete official source — the TTLock User Manual PDF — is also available, alongside an app overview video and the McGrath Locks App how-to video presented by an Australian expert.
TTLock is a cloud-based smart lock management platform developed and operated by Sciener, a company based in Beijing, China. Sciener does not manufacture the lock hardware themselves — they build and maintain the platform that hardware brands license and build upon. In Australia, the brands running on TTLock include McGrath, Lockton, and Austyle, plus the Vault range. There are dozens of other TTLock-compatible hardware brands sold globally, making it one of the two dominant smart lock platforms on the world market alongside Tuya.
The platform works in two stages. The first is a direct Bluetooth connection between the lock and your phone via the TTLock app. Within Bluetooth range, you can lock and unlock, manage credentials, and view activity logs. The second stage adds a gateway — a small device that bridges the lock to your home WiFi network. With a gateway, you gain full remote management from anywhere in the world.
The McGrath Locks app is an Australian-branded version of the TTLock app. Same platform, same Sciener backend, same feature set — with Australian-facing branding and support. Australian McGrath customers can use either the TTLock app or the McGrath Locks app interchangeably. The decision to use McGrath's branded app reflects the distribution and support relationship with LSC, not a separate technical platform. Australian users may find the McGrath Locks App how-to video the most practical starting point — it covers the same platform with local context.
Some locks in the broader GCSL range run on entirely separate platforms. Hafele digital locks use the Hafele app or proprietary firmware. Dormakaba products use their own platforms. Carbine's Bluetooth CEL2-BT models use the Carbine Connect app — a Bluetooth-only, no-cloud platform with a fundamentally different architecture. These are not TTLock-compatible and are not covered in this chapter. For a full platform comparison, see Chapter 15 — Smart Lock App Platforms Guide.
TTLock is an open platform. Hundreds of hardware brands globally manufacture TTLock-compatible locks covering a wide range of form factors: door locks, padlocks, safe locks, cabinet locks, bicycle locks, cylinders, and parking bollards. In Australia, Gold Coast Smart Locks carries three TTLock-compatible brands:
What this breadth means practically: whatever door type you have — timber, aluminium, sliding, narrow stile, fire-rated — there is likely a TTLock-compatible product that fits. For help matching a product to your specific door, see the nine-door-type compatibility matrix in Chapter 04.
TTLock offers six distinct passcode types — more scheduling granularity than any competing platform in the Australian market. Understanding what each type does and what its constraints are is one of the most practically useful things to know before you start using the platform. See Chapter 03 — Access Methods for the broader context of PIN-based access in smart locks.
| Type | How it works | Best used for |
|---|---|---|
| Permanent | Must be used once within 24 hours of generation. After first use, valid indefinitely until revoked. | Regular family members, permanent staff. |
| Time-Limited | Valid between two timestamps. Accurate to the hour if under 1 year; month-accurate only beyond 1 year. Must be used within 24 hours of the start date. | Airbnb guests, short-term contractors, maintenance workers. |
| One-Time | Single use only. Valid for 6 hours from generation, then expires. | Delivery drivers, emergency access, one-off visitors. |
| Cyclic | Repeats on a schedule: daily, weekdays, weekends, or a specific day. Valid within a set time window on each qualifying day. Must be used within 24 hours of first validity window. | Regular cleaners, property managers, recurring contractors. |
| Customised | User-defined code (4–9 digits) with a custom validity window. Can be set remotely via a connected gateway. | Where a memorable code is needed rather than an auto-generated one. |
| Erase (Clear Code) | Valid for 24 hours. When entered at the keypad, deletes ALL passcodes from the lock simultaneously. | Clearing a lock before property handover or after a security incident. Never share. |
An eKey is a digital access invitation sent from one TTLock account to another. The recipient receives access to the lock via their own TTLock account without ever seeing your passcode or having administrative control. eKeys can be revoked at any time.
There are four eKey types: Permanent (unlimited until revoked), Timed (valid between two timestamps), One-Time (auto-deletes after first use), and Cyclic (repeats on a schedule). The scheduling flexibility mirrors the passcode types.
The app provides a deadline warning system: the key indicator turns yellow as expiry approaches and red once it has passed. This gives administrators a visual overview of which access grants are nearing expiry across a property or portfolio.
For property handovers, eKey management requires attention. Once a lock is paired to an account, it cannot be transferred to a new account until the current administrator deletes it via Bluetooth while physically at the lock. See our lock transfer guide for the procedure and common pitfalls. Note also that deleted eKeys may persist on the lock hardware itself — this is addressed in the Security Considerations section below.
A TTLock-platform lock works without a gateway. Passcodes work, IC cards work, fingerprints work, and Bluetooth access from the app works — all locally, without any WiFi or internet connection. For an explanation of what a gateway actually does and when you genuinely need one, see Chapter 08 — What a Gateway Does. Many residential installs run in Bluetooth-only mode without issues. The table below summarises exactly what changes when a gateway is added.
| Capability | Bluetooth only | With gateway |
|---|---|---|
| Keypad PIN entry | ✓ | ✓ |
| IC card / fingerprint | ✓ | ✓ |
| Bluetooth unlock (must be nearby) | ✓ | ✓ |
| Remote lock / unlock from anywhere | ✗ | ✓ |
| Real-time push notifications | ✗ | ✓ |
| Remote passcode creation / deletion | ✗ | ✓ |
| Automatic clock calibration | ✗ (manual required) | ✓ (continuous) |
| Remote IC card issuance | ✗ | ✓ |
| Alexa / Google Home voice control | ✗ | ✓ |
| PMS integration via API | ✗ | ✓ |
| Event data sent to cloud | ✗ (stays local) | ✓ (Sciener servers, China) |
For Airbnb and short-stay rental operators, a gateway is effectively required — remote passcode creation and real-time notifications are not optional at that operational scale. For context on what happens to your lock when the internet goes down, see Chapter 08 — What Happens When the Internet Goes Down. Local access methods remain completely unaffected.
Four gateway models are available for TTLock-platform locks in Australia. The right choice depends on your network environment and the number of locks you are managing. For full technical specifications and a detailed comparison including the Yale Connect Hub and Igloohome Bridge, see Chapter 08 — Smart Lock Gateway Comparison.
| Model | Connectivity | Best for | Key note |
|---|---|---|---|
| G2 | 2.4 GHz WiFi only | Residential, Airbnb, small office | Fails on band-steering routers. Split SSID or upgrade to G5. |
| G3 | Ethernet / PoE only | IT-managed commercial environments | No WiFi. Mesh-capable. Uses port 2999 to gateway.ttlock.com — confirm firewall allows this on managed networks. |
| G4 | 2.4 GHz WiFi + 4G SIM fallback | Remote or holiday homes with unreliable NBN | Up to 100 locks. Falls back to 4G if WiFi drops. |
| G5 | Dual-band 2.4 + 5 GHz | Any new install; 3+ lock deployments; modern routers | Eliminates band-steering problem. Up to 100 locks. USB-C. Recommended default for new installs. |
For the operational perspective on gateway choice and the impact of the G2 vs G5 decision on day-to-day reliability, see the gateway choice section of our TTLock tips guide.
Beyond PIN codes and app-based access, TTLock-platform locks support several additional credential types. Availability varies by hardware model. For a broader overview of all access methods and how they compare, see Chapter 03 — Access Methods Comparison.
IC Cards (RFID): IC cards must be enrolled via the app while physically at the lock. Permanent or time-limited card access can be set. With a gateway connected, remote card issuance is possible. Without a gateway, cards must be enrolled in person. See Chapter 03 — RFID Card Access for how RFID credentials work and their advantages over PIN for multi-user environments.
Fingerprints: Enrolled via the app at the lock. Multiple fingerprint entries per user are supported. The recommended technique is to enrol the same finger at three slightly different angles, plus a backup finger from the non-dominant hand — this significantly improves recognition reliability across different conditions. See the fingerprint enrolment technique in our tips guide for the full method. See also Chapter 03 — Fingerprint Access for failure modes and when biometric access suits your application.
Touch-to-Unlock (Bluetooth): When Touch-to-Unlock is enabled, touching the keypad while the TTLock app is open and the phone is within Bluetooth range unlocks the door without entering a PIN. It is enabled by default and can be disabled in app settings. See the Touch-to-Unlock guide for when to disable it and how. For the broader context of Bluetooth-based access, see Chapter 03 — Bluetooth Access.
Two-Factor Unlock: TTLock supports requiring two credentials simultaneously — fingerprint plus PIN, or IC card plus PIN. Appropriate for NDIS housing staff access, secure commercial doors, or safe rooms. See the two-factor unlock guide for which situations warrant it and which do not.
TTLock's open SDK and API is the primary reason the platform is popular among multi-property Airbnb and short-stay operators. Property Management System (PMS) platforms can connect to the TTLock API and automatically create, modify, and delete time-limited passcodes based on booking data — without any manual intervention from the host.
PMS platforms that integrate with TTLock in Australia include Hostaway, Guesty, Lodgify, and RemoteLock. API-level access is also available through Seam, which connects TTLock to a wider range of downstream tools. See PMS platforms that integrate with TTLock for the full list and how each works. For how multi-property operators scale this, see Chapter 07 — Property Management Systems and Chapter 07 — Multi-Property Management.
For a detailed guide to setting up TTLock with a PMS for Airbnb, see what changes with a gateway and PMS. For the Airbnb use-case comparison between TTLock and Igloohome, see Chapter 07 — Igloohome vs TTLock/McGrath.
Built into every TTLock account at no additional cost, Attendance Management turns the lock into a staff check-in system. It is designed for commercial use cases: offices, retail tenancies, NDIS group homes with paid staff, and any environment where arrival and departure times need to be logged.
When enabled on a lock, the system records the time of each access event by credential. The app generates monthly statistics showing arrival times, departure times, late arrivals, and early departures against a configurable schedule. A holiday calendar can be set to exclude public holidays. Three check-in methods are supported: app unlock, passcode entry, and IC card.
The feature is toggled on or off per lock in the lock settings. It does not affect normal access operation — the lock works identically with Attendance Management on or off. The difference is whether the platform is actively building a timesheet from the access log.
TTLock is a capable platform. It is also missing features that some buyers will care about. The table below compares TTLock against the platforms most likely to come up in an Australian buying decision.
| Feature | TTLock | Yale Home | Igloohome | KAS Access | Carbine Connect |
|---|---|---|---|---|---|
| Apple HomeKit | ✗ | ✓ Native | ✗ | ✗ | ✗ |
| Auto-Unlock (geofence) | ✗ | ✓ Home/Away | ✗ | Partial | ✓ BT proximity |
| Door-state sensor (DoorSense) | ✗ | ✓ | ✗ | ✗ | ✗ |
| Offline algoPIN (no internet needed) | ✗ | ✗ | ✓ Key differentiator | ✗ | ✗ |
| Native Airbnb Connect (AU) | ✗ | ✗ | ✓ | ✗ | ✗ |
| Remote access (away from property) | ✓ Via gateway | ✓ | ✓ Via bridge | ✓ | ✗ Bluetooth only |
| Third-party PMS ecosystem (AU) | ✓ Broad | Limited | Growing | ✓ Via integrations | ✗ |
| Attendance management | ✓ Built-in | ✗ | ✗ | ✓ | ✗ |
| Web-based management console | Basic (TT Renting) | ✗ | Limited | ✓ Comprehensive | ✗ |
| Six distinct passcode types | ✓ | ✗ | ✗ | ✗ | ✗ |
| No-cloud privacy architecture | ✗ (cloud for remote) | ✗ | ✗ | ✗ | ✓ Fully offline |
| Hardware variety (AU market) | Very broad | Moderate | Focused | Commercial-focused | CEL2-BT range only |
| Hardware price | Lowest | Mid-high | Mid | High | Mid |
For Australian Airbnb and short-stay operators, TTLock and Igloohome are the two platforms that matter most. They take fundamentally different approaches. See Chapter 07 — The Two Main Approaches for the foundational framing of this decision.
| Factor | TTLock | Igloohome |
|---|---|---|
| Offline passcode validation | No — gateway + internet required for remote management | Yes — algoPIN codes validated locally on lock |
| Airbnb Connect (AU) | Not available in Australia | Available |
| Passcode scheduling types | Six (Permanent, Time-Limited, One-Time, Cyclic, Customised, Erase) | Three (Permanent, Time-Limited, One-Time) |
| Hardware variety (AU) | High — McGrath, Lockton, Austyle across many form factors | Focused range — strong on deadbolt, mortice, and keybox. See Igloohome products for Airbnb. |
| PMS ecosystem (AU) | Broad — Hostaway, Guesty, Lodgify, RemoteLock, Seam | Growing but narrower |
| Price | Lower on hardware | Mid-range |
| Setup complexity | Moderate — gateway and network config needed for full features | Simpler — no gateway required for algoPIN to work |
Use this decision framework:
For the Airbnb-specific WiFi decision in full detail, see Igloohome vs TTLock/McGrath at a glance and when TTLock is the right answer and when Igloohome will serve you better. For a platform-to-scenario decision table, see Chapter 15 — Choosing the Right Platform →
In March 2024, CERT/CC (the US Computer Emergency Readiness Team Coordination Centre) published advisory VU#949046 documenting multiple unpatched vulnerabilities in Sciener firmware — the same firmware that powers TTLock-platform locks including McGrath, Lockton, and Austyle. Sciener was notified in November 2023 and had not responded publicly as of the March 2024 disclosure.
We document these in full because trade-grade honesty serves buyers better than omission. The critical context is at the bottom of this section.
| CVE Number | Vulnerability | What it means in plain English |
|---|---|---|
| CVE-2023-7006 | Unlock key brute-forceable | The lock accepts repeated unlock challenge requests with no rate limiting. A technically sophisticated attacker nearby could, in theory, determine the unlock key through repeated trials. In practice this requires specialised equipment and physical presence at your door. |
| CVE-2023-7005 | Encryption protocol downgrade to plaintext | An attacker can manipulate the communication between a TTLock lock and an authorised device to force both parties to drop encryption and communicate in plaintext. The Bluetooth traffic between lock and phone becomes readable to anyone intercepting it within Bluetooth range. |
| CVE-2023-7003 | AES key reuse across all wireless keypad locks | All TTLock-compatible locks that include a wireless keypad share the same AES encryption key. If that key were extracted from one lock, it would theoretically apply to other locks using wireless keypads on the same platform. |
| CVE-2023-6960 | Deleted virtual keys persist on the lock | When you delete an eKey through the TTLock app, the lock itself may not actually remove it. The app shows the key as deleted, but the lock retains it. An attacker who captured that key before deletion could potentially still use it to unlock the door. This is the most practically significant CVE for property operators — treat deleted eKeys as potentially still active on the lock hardware. |
| CVE-2023-7004 & CVE-2023-7007 | Device spoofing via MAC address cloning | An attacker could clone the MAC address of an authorised device — a phone or gateway — and use that spoofed identity when communicating with the lock, allowing an unauthorised device to be treated as trusted. |
Data sovereignty
All lock event logs and remote commands sent through a connected TTLock gateway transit Sciener's servers, which are hosted in China. Bluetooth-only operation stores nothing in the cloud — event logs remain on the lock and are retrieved locally when the app connects via Bluetooth. For most residential and Airbnb use cases, data transiting through Chinese servers is an accepted consideration. For NDIS providers, body corporate managers, commercial property operators, or any environment where data sensitivity or regulatory compliance is a factor, this warrants explicit consideration before selecting TTLock as the platform. There is no Australian-hosted alternative on this platform. See the cross-platform security and data sovereignty table in Chapter 15, and the TTLock-specific CVE security assessment →, for a comparative view.
Mitigations
By comparison, Carbine Connect's Bluetooth-only architecture means no event data ever transits any server — cloud or otherwise. An independent penetration test by SilentGrid (an Australian cybersecurity firm) confirmed the CEL2-BT platform as low-risk with one-time-use encryption keys eliminating replay attacks. For the full comparison, see Carbine Connect in Chapter 15 and our Carbine Connect platform guide.
Whether you need a single residential lock or a multi-property Airbnb system, our team can help you choose the right hardware and configuration before you commit.
Disclaimer: Platform features, third-party PMS integrations, and app functionality change over time with firmware and platform updates. CVE information reflects the CERT/CC advisory VU#949046 published March 2024. Verify current security status and capabilities with your supplier before purchasing. Security vulnerability disclosures should be checked against the most current CERT/CC advisories at kb.cert.org.