TTLock
homebridge-ttlock · v1.1.0
Adds TTLock smart locks to HomeKit via the TTLock cloud, using WiFi locks or a gateway.
What it says it supports
Brands
- TTLock
Devices it names
- TTLock locks
- Gateways G1-G4
Shows up in Apple Home as from its README
What people report
Users struggle with locks not appearing or API error 10003; plugin appears poorly maintained. Shared locks are not visible unless owned by the developer account.
- Partly works2
- Not working1
| Device | Status | What they said | Source |
|---|---|---|---|
| E-Lok lock (NZ, TTLock platform) | Partly works | Lock appears in Homebridge accessories but not pulling into Apple Home.Saved copySorry, to follow up, I live in NZ, and E-Lok uses the same software and platform, and I was able to set up a new account and migrate it into the Homebridge environment, and I can see the Lock in the Accessories. However, I can't see it pulling through into my Apple HomeKit. Excerpt saved from GitHub on 2026-10-22. | Issue #15 · 2024-11 |
| TTLock smart locks (shared locks) | Partly works | Locks managed under another admin account do not show; use the developer-registered account.Saved copySo i updated my json config from: `"platform": "TTLock Platform"` To: `"platform": "ttlock"` and also updated my Node.js to version v18.14.0 But still no locks showing up in Homebridge Dashboard, the locks are currently managed by my Admin1 account, I logged into Admin1 and added my new account (generated via TTLock API) as an Authorized Admin to the locks. I'm thinking this may be the issue to why its not showing up in the Homebridge dashboard, I don't want to remove my locks from Admin1 account, is there any other way to get the locks to work without reseting them and provisioning to the … Excerpt saved from GitHub on 2026-10-22. | Issue #7 · 2023-02 |
| TTLock smart lock | Not working | Error 10003 despite correct API keys; user reports not working at all.Saved copyis this plugin still do not work, Im looking into getting one of those TTLOck locks only if I can get it to work with HomeKit Excerpt saved from GitHub on 2026-10-22. | Issue #14 · 2023-11 |
Gathered from the plugin’s GitHub issues, pull requests, discussions, wiki and docs, and from r/homebridge. These are individual reports, so check the linked thread and the date before you buy.
How it connects
Cloud
TTLock cloud API
You’ll need
- TTLock account
- Gateway for Bluetooth locks
- Remote Unlock on
Compatibility
| Verified by Homebridge | Yes |
|---|---|
| Homebridge versions | >=1.3.5 |
| Homebridge 2.0 | No |
| Node.js | >=14.18.1 |
| Settings in Homebridge UI | Yes |
| Matter | No |
| Platform name | ttlock |
| License | Apache-2.0 |
Community signals
| Downloads a week | 6 |
|---|---|
| Downloads a month | 46 |
| GitHub stars | 22 |
| Open issues | 9 |
| Closed issues | 7 |
| Last code push | 2022-08-29 |
| Latest version | 1.1.0 (2022-08-29) |
| First published | 2022-07-27 |
| Releases | 4 |
In ReReHome
Whatever this plugin publishes reaches Apple Home as a normal HomeKit accessory behind your Homebridge bridge, so ReReHome shows and controls it like any other.
Bridges get their own settings page listing the accessories behind them.
HomeKit services in its code
Found by scanning the published npm package. A plugin can register a service only for some devices.
- LockMechanism
Sources
- npm: https://www.npmjs.com/package/homebridge-ttlock
- Source code: https://github.com/bwitting/homebridge-ttlock
- Issues: https://github.com/bwitting/homebridge-ttlock/issues
- Verified plugins list: https://github.com/homebridge/verified
