TTLock IC Card Not Adding? How to Fix It

IC card readers built into smart locks are tuned to one radio frequency, and enrolment is a two-step process — the app tells the lock to expect a new card over Bluetooth, then the lock itself has to detect the card's signal. Either step can fail independently.

• Wrong card frequency. Most TTLock-compatible locks read 13.56MHz Mifare-type cards; some models instead use 125kHz proximity (EM) cards. A card built for the other frequency will never be detected, no matter how it's presented — it's a physical incompatibility, not a software issue.
• Wrong position on the reader. The reader coil sits in a specific spot behind the lock's faceplate, often marked with an icon. Holding the card even a centimetre off that zone can prevent detection, especially on metal doors that shield the signal.
• The phone lost Bluetooth connection during enrolment. The app has to stay connected to the lock while it waits for the card to be presented; if the connection drops mid-process, the enrolment step silently times out.
• The card is already registered. A card already added to this lock, or in some cases still bound from a previous lock's memory, can be rejected as a duplicate rather than added again.
• A validity window excludes the current time. If a validity period or schedule was set while adding the card, it can appear successfully added yet still be declined at the door outside that window.
• The lock has reached its card storage limit. Like passcodes and fingerprints, IC cards share a finite storage capacity that varies by lock model; once full, new cards fail to enrol until old ones are removed.

1. Confirm the card frequency matches the lock. Check the lock's specifications for 13.56MHz (Mifare) versus 125kHz support, and use a card or fob known to match — a card that works on an unrelated access system is not a reliable test.
2. Start the add-card process in the app first. Wait for the app to show it is actively waiting for a card before presenting one; presenting a card too early does nothing.
3. Hold the card flat against the marked reader area and keep it still.Give it a second or two rather than tapping quickly, and try slightly different positions around the icon if the first attempt fails.
4. Stay in Bluetooth range of the lock throughout enrolment. Keep the phone within about a metre so the connection doesn't drop while the lock waits for the card.
5. Try a different, known-unused card. This rules out both a duplicate-card rejection and a faulty or previously-registered card.
6. Check and clear old cards if the lock is near its storage limit. Remove cards for people who no longer need access before adding new ones.

Two card families are common on smart locks: 13.56MHz Mifare-family cards (also used in many transit and office access systems) and 125kHz EM/proximity cards (common in older access-control fobs). They are not interchangeable, and a lock's reader is built for one or the other — there is no software setting that switches a lock between them. If unsure which type a lock takes, use the blank cards or fobs supplied with it, or check the model's listed specifications before buying replacements.

Smart Lukko is an independent third-party app for TTLock-compatible smart locks and is not affiliated with TTLock or Sciener; card frequency support is a hardware property of each lock model, not something the app controls.

• Check the card isn't damaged. A cracked or bent card can have a broken internal antenna even though it looks fine.
• Remove any thick case, sleeve or other cards stacked against it. Metal or multiple RFID cards together can interfere with the reader picking up a clean signal.
• Reboot the lock's Bluetooth by moving out of range and back. A stale connection can occasionally block the card-waiting state from starting properly; closing and reopening the app can also help.
• Confirm the validity settings on any card that seems added but doesn't work. Check its schedule or expiry date in the app rather than assuming the enrolment itself failed.