Smart lock won’t connect to Wi-Fi: what to check, in order

A lock that has behaved itself for three weeks starts showing as offline on a Tuesday evening. The keypad still lights up. The bolt still throws. Nothing at the door has changed, and nothing at the door is the problem. Almost every time, the thing that changed is at the other end of the house, sitting on a shelf with its little lights on.

Working through this in a fixed order matters, because the two moves people reach for first are the two that cost the most: pulling the batteries out, and factory resetting a lock that was never faulty.

Start by working out what actually went offline

Smart locks reach the internet in four different ways, and offline means something different in each.

• A lock with its own Wi-Fi radio talks to the router directly. Offline means it lost the router, or the router lost the internet.
• A Bluetooth lock paired to a plug-in bridge goes offline when the bridge is unplugged, out of Bluetooth range of the lock, or off the network. The lock itself may be in perfect health.
• A Matter over Thread lock reaches the network through a border router hidden inside some other device you own. If that device is down or was replaced, the lock goes quiet.
• A Z-Wave or Zigbee lock never touches Wi-Fi. If it has gone offline, the hub is the place to look, and no amount of router fiddling will help.

The most useful test takes ten seconds. Stand at the door and try to operate the lock from the app. If it answers at arm’s length but not from the sofa, the lock is alive on Bluetooth and what is broken is the path out to the internet. If it answers from nowhere, treat it as a power fault and start with fresh batteries. Which of the four you own comes down to the radio the lock was built around.

The 2.4 GHz problem, which is most of them

Nearly every smart lock radio is 2.4 GHz only. No 5 GHz, no dual band, no negotiation. That band is slower and more crowded, and it travels through walls, which is precisely why lock makers use it.

Modern routers publish both bands under a single network name and steer each device to one of them. Convenient for laptops, hostile to a setup flow that expects your phone and the lock on the same band at the same moment. The symptom is recognisable: the app finds the lock over Bluetooth, accepts the Wi-Fi password without complaint, then fails at the last step with a vague error.

The fix is to give the 2.4 GHz band a name of its own for the length of the setup.

1. In the router or ISP app, split the bands and give the 2.4 GHz network a distinct name, or switch band steering off temporarily.
2. Join your phone to that 2.4 GHz network before you open the lock’s app.
3. Run setup through to the end, then put the router back the way it was if you prefer one name. The lock keeps the credentials it was handed.

Other settings break setup quietly. WPA3-only security is not universally supported by lock radios, so a mixed WPA2 and WPA3 mode is safer. A hidden network name makes provisioning harder than it needs to be, and guest networks with client isolation stop a bridge and a phone seeing each other. Any network with a sign-in page in front of it will never work.

When setup never finishes in the first place

Setup failures sort themselves by where they stall. If the app never sees the lock, the problem is on the phone: Bluetooth switched off, Bluetooth permission never granted to the app, or on Android the location permission, which the system demands before an app may scan for nearby networks. Locks are also discoverable only for a short window after being put into pairing mode, and it closes faster than most people read.

If the credentials come back rejected, type the password by hand rather than pasting it and check the network name for capitals and stray spaces. If the app swallows the credentials and then stalls at the very end, the lock has usually reached the router and failed to hold an association, which points at the band or the signal. Weak cells produce the same stall: bringing up a radio draws harder than a keypad entry, so batteries with enough left to drive the motor can still fail to hold a connection.

The signal at the door is worse than you think

An exterior door is close to the worst address in the house for 2.4 GHz. It sits on an outside wall, often behind brick or stucco over metal lath, sometimes inside a steel door skin, and usually as far from the router as the floor plan allows. Full bars on a phone in the hallway prove nothing about conditions inside the lock body eight feet away.

Checking it without any tools

Join a phone to the 2.4 GHz network, start a video call and walk to the closed door. If the call falls apart over the last few feet, that is the environment the lock lives in. Better still, leave a laptop on a chair by the door for ten minutes and watch whether it holds, because one instantaneous reading proves very little.

Where a bridge belongs

A plug-in bridge wants to sit between the router and the door, on the same floor, in open air. Behind a sofa, inside a metal utility cupboard or at the far end of a basement are all common and all bad. Higher up a wall beats down at skirting level. If you run a mesh system, a node near the entry does more than a stronger router, because the obstacle is the wall rather than the transmit power.

It connects, then drops every night

A lock that pairs cleanly and then goes offline at roughly the same hour each day is almost never suffering a firmware bug. Something on the network is on a schedule.

• DHCP lease expiry. The lock asks to renew its address, the renewal fails or it is handed a different one, and the cloud connection breaks. A DHCP reservation in the router settings fixes this for good.
• An ISP router that reboots itself overnight to apply firmware, which several do by default and none advertise.
• Mesh systems moving the lock between nodes. A lock at the edge of two nodes’ coverage can bounce between them all night.
• Channel congestion. In apartment buildings the 2.4 GHz band fills up in the evening. Pinning the router to channel 1, 6 or 11 rather than automatic often settles it.
• Device isolation features on newer routers, which quarantine smart-home gear onto their own segment and cut it off from the app.

Notice which pattern you have before changing five settings at once. Drops at a fixed hour point at leases and reboots. Drops that follow the evening or the weather point at signal and congestion.

Telling a dead bridge from a dead lock

The router’s own client list is the honest witness. Open the router or ISP app and look at connected devices. If the bridge or the lock appears there holding an address, it is on the network and the fault lies further along: the maker’s cloud, your account, or the short Bluetooth hop between bridge and lock. If it does not appear at all, the Wi-Fi connection is the fault and everything above applies.

Before resetting anything, check whether the maker’s service is simply down. Lock apps report a cloud outage as a device being offline, which from where you are standing looks identical to a network fault. A brand status page, or app store reviews from the last day, settles it in a minute. The same goes for a lock that has vanished from a voice assistant while still working in its own app: that is a broken account link, worth checking against how the platform integration was set up. A status that’s wrong at the door itself, not just slow to arrive, usually points at a sensor problem instead, with its own fix.

Firmware, and the update that stalls halfway

Some connection faults are known bugs with published fixes, so look at the firmware version before rebuilding the network around a problem the maker already solved. Updates arrive over Bluetooth from a phone held at the door, or through the bridge, and take longer than anyone expects.

Three conditions make a stalled update likely: a battery level below whatever floor the manufacturer sets, the phone wandering out of range partway through, and the screen locking and suspending the app behind it. Stay at the door, keep the app in front, and fit fresh cells first. A lock stuck mid-update is usually recovered with new batteries and a second attempt rather than a reset.

When a reset is the right move

A factory reset belongs at the end of this list, not the start, because it costs everything the lock knows: user codes, the app and hub pairing, auto-lock settings, and on some models the door handing it calibrated at installation. People reach for it early because it feels decisive, then reprogram codes for an hour over a fault that was a DHCP lease.

The order is what saves you. Remove the lock from the app and from any hub or voice platform first, then reset the hardware, then add it back. Reset the hardware first and you leave an orphaned entry in the app that often refuses to accept the same lock again. Where each brand hides its reset control, and what the reset erases, is the thing to read before you press anything.

Do it from inside with the door standing open, and keep a mechanical key or a working code within reach. Standing outside a half-reset lock at ten at night is a specific and avoidable misery.

Common questions

Why does my smart lock keep disconnecting from Wi-Fi?

If it drops at the same time each day, suspect a DHCP lease or a scheduled router reboot and set a reservation for the lock. If it drops unpredictably, suspect the signal at the door and evening congestion on the 2.4 GHz band. A lock that has never once held a connection belongs back at the setup section instead.

Does the lock still work if the Wi-Fi is down?

Yes. The keypad, the mechanical key and the interior thumbturn are untouched by a network outage, and Bluetooth control from a phone at the door usually keeps working too. What you lose is remote locking, remote code management and the notifications.

How far can a smart lock be from the router?

There is no honest number, because what sits between them decides it. Two interior stud walls is usually fine; a brick chimney breast or foil-faced insulation may not be. Count walls rather than feet, and put a bridge or mesh node in the middle if the lock is more than a couple of walls out. Thread locks work differently, relaying through other mains-powered Thread devices and reaching the network through a border router.

The short version

Establish first whether the lock, the bridge or the network went offline, because all three look identical from inside the app. Most setup failures are the 2.4 GHz band hiding behind a single network name, and most nightly drops are a DHCP lease or a router rebooting itself on a schedule. Check the router’s client list before believing the app, and the brand’s status page before believing the router. Save the factory reset for last, remove the lock from the app before you reset the hardware, and do the whole thing with the door propped open.