Smart lock unlocks on its own: what’s actually happening

Your phone buzzes with a lock notification at ten at night and nobody touched the door. Or you walk into the hallway and the deadbolt is sitting open, though you distinctly remember locking it that morning. A smart lock that unlocks on its own is unsettling, and in nearly every case the cause is ordinary: a setting called passage mode left on by accident, a geofence drawn wider than the porch, or a hub automation somebody set up two years ago and forgot about. The hardware is rarely at fault. Working through what actually changed, in order, finds the cause faster than resetting anything.

The four things that actually do this

Strip away the alarm and a lock that unlocks itself almost always traces back to one of a short list of causes, roughly in order of how often each one turns up.

• A setting on the lock itself, usually called passage mode or an always-unlocked mode, switched on by a stray button press or a setup step nobody finished.
• Auto-unlock or geofencing firing because the perimeter it watches is bigger than the house, so the lock decides you have arrived while you are still at the end of the street.
• An automation in a hub or an app doing precisely what it was told, on a schedule or a trigger nobody remembers setting.
• A person with a working code or app access who is not you: a partner, a former housemate, or a contractor whose code was never revoked.

A fifth cause is mechanical rather than electronic and gets mistaken for the other four constantly: a bolt that never fully seated read back by the lock, or by you, as open. That one gets its own section further down, because the fix looks nothing like the others.

Passage mode, or an always-unlocked setting nobody meant to turn on

Most keypad and app-controlled deadbolts have a mode that holds the bolt retracted on purpose, meant for a party, a move, or a day when the door needs to stay open for deliveries. Manufacturers name it differently: Yale and Schlage locks generally call it passage mode, August’s retrofit units describe the same idea as an unlocked state set from the app, and Kwikset documentation uses similar language for its own keypad models. Whatever the name, the effect is identical: the lock stops locking, on command, until someone turns the mode back off.

It gets switched on by accident more often than people expect. A code sequence that also happens to be the passage-mode shortcut, a menu setting bumped during a battery change, or a well-meaning house sitter who wanted the door to stay open for a delivery and never reversed it afterward. Because the lock is doing exactly what it was told, there is no fault to diagnose. Check the mode setting in the lock’s own menu or app before anything else, since this single check clears a surprising share of “it keeps unlocking itself” reports.

Where to find it

On a keypad lock, the setting usually lives behind a programming code entered at the door itself, the same code used to add or remove user codes. On an app-connected lock it sits in the device settings screen, sometimes labeled clearly and sometimes tucked under a generic “modes” menu. If the manual is gone, searching the exact model number rather than the family name is what turns up the right page, since a sibling model in the same product line can hide the setting somewhere completely different.

Auto-unlock and geofencing firing at the wrong moment

Auto-unlock is the feature that opens the door as you walk up, and it is the single most common reason a lock unlocks with nobody touching it. The lock is not guessing. It is following a boundary drawn around the house, called a geofence, and reacting when your phone crosses it. The trouble starts when that boundary is bigger than intended.

August’s own documentation for its auto-unlock feature explains that the perimeter cannot be drawn too small, because doing so hurts location accuracy, and warns plainly that “it is not possible to have the perimeters too small as this could lead to the possibility of false auto-unlocks while you are at home.” In other words, the safety margin built into the feature is what produces the false trigger: a geofence wide enough to reliably notice you arriving is also wide enough to occasionally decide you have arrived when you are still in the kitchen or the yard. The system leans on Bluetooth, Wi-Fi and GPS together to judge where the phone actually is, and any one of those three drifting, especially GPS in a dense neighborhood or near tall buildings, can nudge the estimate across the line.

A second phone on the same account makes this worse. If a partner’s or a teenager’s phone is also enrolled in auto-unlock, the lock will open for whichever device crosses the boundary first, which can look exactly like the door unlocking itself if you were not watching for it. How the underlying radio decides what the lock can even sense is worth a look if auto-unlock has never behaved the way the box implied it would.

The fix that actually works is narrowing the geofence rather than fighting it. Most apps let you redraw the perimeter by hand or shrink a default radius; pulling it in until it sits close to the property line, then testing by walking the actual approach to the door a few times, settles most false triggers within a day. If the false unlocks keep happening after that, turning auto-unlock off entirely and relying on the keypad or a code is a legitimate outcome, not a failure to configure it correctly.

A hub or app automation doing exactly what it was told

Locks tied into a hub such as SmartThings or Hubitat, or into a general automation app, do whatever the rules say, and rules outlive the reasons they were written. A routine that unlocks the door when a specific person’s phone connects to the home Wi-Fi, a scene that runs at sunset and happens to include the lock alongside the porch light, or a voice-assistant routine triggered by a phrase that sounds like something said in passing: all of these unlock a door without anyone standing at it on purpose.

These are the hardest cause to spot because the trigger can sit several steps removed from the lock itself, buried in an automation list nobody has opened in a year. Working through the hub or app’s own automation or routines screen, and specifically searching for the lock’s name rather than scrolling the whole list, is faster than guessing. Disabling automations one at a time, rather than all together, is what actually identifies the culprit, since re-enabling them together just reproduces the mystery.

Someone else still has a code or the app

Before assuming anything technical, rule out the mundane explanation: a person with legitimate access used it. A partner who came home early, a code given to a dog walker or a cleaner months ago and never revoked, or a family member’s phone still logged into the shared account can each produce an unlock that looks unexplained until you check the lock’s own activity log, which most apps keep and most owners never open.

Reading that log first, before touching any setting, tells you whether you are chasing software or just chasing a person who forgot to mention they stopped by. If the log shows a code or a named user you do not recognize, removing that access and, if needed, resetting the lock is the direct fix, separate from anything covered above.

When it’s mechanical, not digital

Not every “it unlocked itself” is electronic at all. A bolt that never fully seats against the strike, because the door has swollen, the strike plate has drifted, or the calibration that tells the motor which way is locked has slipped, can leave the lock reporting a state that does not match what the door is actually doing. The lock believes it locked; the bolt is sitting a few millimeters short and pushes back open under its own spring tension or a firm pull on the handle. From the outside this looks identical to an unwanted unlock, and no setting change will fix it, because nothing digital is wrong.

The tell is consistency with the door, not the schedule. A lock that fails at the same door position, in the same weather, or only when the door was pulled shut rather than pushed firmly, points at alignment rather than software. Running the lock’s calibration routine again, after confirming the strike plate and bolt line up with the door closed, resolves this far more often than any app setting does.

The rare case: is this an attack?

It is worth naming so it can be set aside. A relay attack, where one device near the lock and another near your phone stretch an auto-unlock handshake across a distance neither radio could reach alone, is real but needs someone standing at your door with equipment for a stretch of time, not a stranger acting from another city. It is also the easiest cause to rule out: the risks that are actually real for a smart lock are overwhelmingly software and administration, not a remote hack, and turning auto-unlock off removes the relay scenario outright. If the unlocks stopped the moment you disabled auto-unlock, that alone tells you it was never an attack.

What to check right now, in order

Work down this list rather than jumping to a factory reset, which erases the very evidence that would have told you what happened.

1. Open the lock’s activity log and read the last unlock event: which method, which user, what time.
2. Check the mode setting on the lock or in the app for passage mode or an always-unlocked state.
3. If auto-unlock is on, narrow the geofence and test by walking the actual approach to the door.
4. Open the hub or automation app and search specifically for routines that name the lock.
5. Review the user and code list for anyone who should have been removed.
6. If none of the above explains it and the bolt is not seating cleanly by hand, treat it as a mechanical alignment problem rather than a software one.

A factory reset belongs at the very end of that list, if it belongs at all, since most of what causes a lock to unlock on its own lives in a setting or an account rather than in the firmware.

Common questions

Can a low battery make a smart lock unlock by itself?

Low batteries produce sluggish motors, false low-battery chirps and setup failures far more often than an unwanted unlock. A weak battery is still worth ruling out early because it is a two-minute check, and what actually drains a lock fastest is a shorter read than most of the other causes here.

Why does my lock only unlock itself at certain times of day?

A fixed schedule points almost certainly at an automation rather than at auto-unlock, since geofencing depends on where a phone happens to be, not the clock. Check any scene or routine that runs at sunset, sunrise or a set hour before looking anywhere else.

Should I turn off auto-unlock entirely?

If narrowing the geofence does not stop the false triggers within a few days of testing, yes. The feature saves reaching for a phone at the door, and for a lot of households that convenience is not worth chasing down a boundary that never quite settles.

Is it normal for a smart lock to unlock during a firmware update?

Some models do briefly change state during an update, and it is worth checking the manufacturer’s release notes or support pages for the specific model before assuming anything else is wrong, rather than guessing at the cause.

The short version

A smart lock that unlocks on its own is almost never broken. Start with the lock’s own activity log to see which method and which user actually triggered it, then check for a passage mode or always-unlocked setting switched on by accident, a geofence drawn wider than the porch, or an automation in a hub or app running on a schedule nobody remembers writing. Rule out a person with legitimate access before assuming anything technical, and treat a bolt that will not seat cleanly by hand as a mechanical alignment problem rather than a software one. Save the factory reset for last, since it erases the log that would have told you what actually happened.