TTLock Gateway Offline: How to Get It Back Online

A TTLock gateway is a small bridge: it talks to the lock over Bluetooth and to your router over Wi-Fi, then relays remote-unlock commands and status updates through the cloud. When it shows offline in the app, the break is almost always on the Wi-Fi side or in the Bluetooth link to the lock, not the gateway hardware itself.

• The router broadcasts 5GHz only, or a merged SSID picked 5GHz. Most TTLock gateways are 2.4GHz-only devices. If your router uses band steering to combine both bands under one network name, the gateway can silently fail to associate.
• The router password changed. The gateway keeps using its old saved credentials and will never reconnect until it is re-paired with the new password.
• The gateway lost power or was moved. A tripped outlet, a power strip switched off, or the gateway being unplugged and moved to a new spot all take it offline.
• The gateway is out of Bluetooth range of the lock. Even with a solid Wi-Fi connection, the gateway shows the lock as unreachable if it is more than a few metres away, especially through thick doors or metal frames.
• Router reboot changed the channel or DHCP lease. Some routers reassign channels or IPs after a firmware update, which can drop long-idle IoT devices like gateways.

1. Confirm the Wi-Fi band. On most routers you can create a separate 2.4GHz-only SSID temporarily, or disable band steering, so the gateway has an unambiguous 2.4GHz network to join.
2. Power-cycle the gateway. Unplug it for 10 seconds and plug it back in. Wait a minute or two for the status LED to settle — most gateways show a steady or slow-blinking light when connected.
3. Re-pair the gateway if the router password changed. In the app, open the gateway's settings, remove it, and add it again, entering the current Wi-Fi password when prompted.
4. Move the gateway closer to the lock. Keep it within a few metres, on the same side of the door as the lock's keypad, with as few walls in between as possible.
5. Check the router for the gateway's connection. If your router admin page lists connected devices, confirm the gateway appears with a stable IP.
6. Refresh the lock list in the app. Pull to refresh on the lock's page; gateway status can lag by a minute after reconnecting.

Many modern mesh routers merge 2.4GHz and 5GHz into a single network name and decide which band each device joins. That is convenient for phones and laptops but frequently breaks 2.4GHz-only IoT hardware like TTLock gateways, since the router may push the gateway toward 5GHz, which it cannot use, or the gateway may connect and then get moved during a later optimization pass.

The reliable fix is to give the gateway its own 2.4GHz network name, separate from the 5GHz one, at least during setup. Most router admin panels have this under wireless settings as "Smart Connect" or "Band Steering" — disable it, pair the gateway to the 2.4GHz SSID, then re-enable band steering afterward if you prefer a single network name. Once paired, the gateway generally reconnects automatically to the same band on future reboots.

• Factory reset the gateway. Look for a small reset button on the gateway itself (often a pinhole), hold it for several seconds until the LED flashes, then set it up again from scratch in the app.
• Test with a phone hotspot. Temporarily connect the gateway to a phone's 2.4GHz hotspot to confirm whether the problem is the gateway or your home router.
• Check for IP or DHCP conflicts. If your router assigns static leases, make sure nothing else on the network claimed the gateway's address.
• Verify the lock still works locally. If Bluetooth unlocking from right next to the door works fine, the lock is healthy and the issue is isolated to the gateway's network connection.
• Smart Lukko is an independent third-party app for TTLock-compatible locks and is not affiliated with TTLock or Sciener; gateway firmware behaviour can vary by manufacturer.