|

How to Fix Smart Lock Shows Offline in Home Assistant: Troubleshooting Guide

ByAlex Turner

Your smart lock shows offline in Home Assistant, but the lock itself is probably fine. In most cases, the problem is a temporary wireless handoff failure between the lock and its hub or coordinator — not a broken device or a Home Assistant bug. Start by checking the lock in its own app. If it responds there, you’ll likely fix the issue within the protocol integration (ZHA, Zigbee2MQTT, Matter, or direct Wi‑Fi). If the lock is unreachable everywhere, the quick checks below will point you to the right cause.

First, Check These Five Things

Run through these five checks before touching any Home Assistant settings. Mark each as pass or fail.

  • Lock battery level – Open the manufacturer’s app (Ultraloq, Aqara, Schlage, etc.) and read the battery percentage. Below 20% can cause intermittent dropouts. Replace batteries now if low.
  • Lock responds in its own app – Try locking/unlocking from the native app. If it works, the lock is on the network and the issue is only in Home Assistant’s integration.
  • Physical lock operation – Use the keypad, fingerprint, or physical key. If the lock won’t operate at all, it’s a hardware problem — not a Home Assistant one.
  • Home Assistant logs – Navigate to Settings → System → Logs and filter for your lock’s integration (e.g., `zha`, `z2m`, `matter`). Look for repeated “device unavailable” or “timeout” errors.
  • Router or coordinator reboot – Restart your Wi‑Fi router, Zigbee coordinator (Conbee II, Sonoff ZBDongle-E, or similar), or Thread border router. Do this last if everything else passes.

What to do next based on your results:

  • If the lock fails only in its own app (check #2 fails), skip ahead to the hardware and network checks — it’s not an integration problem.
  • If the lock passes in its own app but fails in Home Assistant, move straight to the protocol‑specific fixes below.

The Real Cause Isn’t What You Think

Most guides jump straight to “restart Home Assistant” or “re‑add the device.” The counter‑intuitive truth: a smart lock showing offline in Home Assistant is almost never a Home Assistant bug. It’s a wireless interface conflict or a coordinator that has lost the device’s pairing state.

Two scenarios cause roughly 80% of all offline lock problems:

1. Zigbee channel overlap with Wi‑Fi – Zigbee channels 11–26 sit directly next to common Wi‑Fi channels 1, 6, and 11. If your lock uses a channel that overlaps with a busy Wi‑Fi network (common in apartments or dense neighborhoods), it will drop packets and appear offline.

2. Matter/Thread locks depend on a live border router – A Matter lock like the Aqara Smart Lock U100 needs a 24/7 Thread border router (Apple TV 4K, HomePod mini, or Echo 4th Gen). If that device restarts or loses power, the lock goes offline until the border router reconnects.

For Wi‑Fi direct locks, the same channel congestion applies — the lock’s own Wi‑Fi radio may be fighting for airtime. All three protocols share the same fix: move the hub closer, change the channel, or add a signal repeater.

Fixes That Match Your Lock’s Protocol

Jump to the section that matches how your lock connects. Each set of steps assumes you’ve already done the quick checks above.

Zigbee2MQTT (Z2M)

1. Open the Z2M frontend – Go to `http://:8080` or use the add‑on web UI.

2. Check the device state – Find your lock. If it shows “offline,” click it and select Interview. This forces a fresh device information exchange with the coordinator.

3. Change the Zigbee channel – Edit `configuration.yaml` (in the Z2M add‑on folder) to `channel: 15` or `channel: 20`. These are least likely to overlap with common Wi‑Fi channels. Restart the add‑on after saving.

4. Repair the lock – If the lock still won’t appear, press the pair button on the lock (often a pinhole or long keypad press). In Z2M, click Permit join (all) for 60 seconds and wait for the lock to rejoin.

5. Move the coordinator – If the lock is more than 30 feet from the coordinator with walls in between, extend the coordinator with a USB extension cable. Zigbee drops quickly through concrete and metal. A cheap Zigbee router (like an IKEA TRÅDFRI outlet) can also fill coverage gaps.

ZHA (Home Assistant’s Built‑in Zigbee)

1. Go to Settings → Devices & Services → ZHA – Click Configure.

2. Reconfigure the lock – Open the lock device. If it says “Unavailable,” click Reconfigure. This resets bindings and often brings the device back online.

3. Verify coordinator placement – For USB coordinators (Conbee II, Sonoff), plug directly into your HA server — avoid USB hubs. Keep the cable under 6 feet.

4. Change Zigbee channel (last resort) – ZHA uses your coordinator’s default channel (usually 11 or 15). Changing it requires re‑flashing the coordinator firmware with tools like `zigpy‑flash`. Only attempt this if you see consistent packet loss. After flashing, you must re‑pair all devices.

5. Add a Zigbee router – Pair a router (smart plug or repeater) near the lock. Then the lock will connect through it, improving range and stability.

Wi‑Fi Direct Smart Locks

Some Wi‑Fi locks (e.g., ULTRALOQ U-Bolt Pro WiFi Smart Lock with Door Sensor) connect directly to your home Wi‑Fi without a hub.

1. Confirm 2.4 GHz only – In the lock’s own app, verify it’s connected to a 2.4 GHz network. Dual‑band routers can steer the lock to 5 GHz, which locks often don’t support. Create a dedicated 2.4 GHz SSID if needed.

2. Power‑cycle the lock – Remove one battery for 10 seconds, then reinsert. This forces the Wi‑Fi radio to reassociate with your router.

3. Ping the lock from HA – In Home Assistant’s terminal (or via SSH), run `ping 192.168.x.x` (use the lock’s IP from your router’s DHCP list). No reply means it lost Wi‑Fi. Re‑enter Wi‑Fi credentials in the lock’s app.

4. Reserve a static IP – In your router, assign a DHCP reservation for the lock’s MAC address. This prevents IP changes that confuse Home Assistant.

Matter / Thread Locks

Matter locks like the Aqara U100 rely on a Thread border router.

1. Is the border router online? – Check the device acting as your Thread border router (Apple TV 4K, HomePod mini, Echo 4th Gen). If it rebooted recently, wait 5 minutes for the Thread network to stabilize.

2. Re‑pair the lock – Remove the lock from Home Assistant’s Matter integration. Factory reset the lock (see its manual). Pair it again using the Matter pairing code — this forces a fresh credential exchange.

3. Check Thread diagnostics – In HA, go to Settings → Devices & Services → Matter and view the lock’s details. Look for “Thread network: healthy.” If you see “operational dataset missing,” restart the border router, then re‑provision the lock.

How to Confirm the Fix Worked

After trying the steps above, verify the connection in Home Assistant:

  • Watch the lock entity – On the HA dashboard, the lock’s status should change from “Unavailable” to “Locked” or “Unlocked” within 2–5 minutes.
  • Test a command – Lock and unlock the door from Home Assistant. If the lock responds and the status updates in both HA and the manufacturer’s app, the connection is restored.
  • Check logs again – Filter for the lock’s integration. If you no longer see “timeout” or “device unavailable” errors, the issue is resolved.

If the lock still shows offline after applying the correct protocol fixes, move to the next section.

When to Stop Troubleshooting

Stop DIY efforts and contact support if:

  • The lock’s own app shows it offline after fresh batteries and a router/coordinator reboot.
  • The lock behaves erratically (unlocking by itself, ignoring physical touch).
  • You see repeated “low voltage” or “brownout” warnings in logs even with brand‑new batteries.

In these cases, the lock’s internal radio or control board is failing. A persistently offline smart lock is a security risk — don’t leave it unreliably connected. Contact the manufacturer for a warranty replacement or install a new unit.

FAQ

Why does my smart lock go offline after a power outage?

A power outage often resets your router, Zigbee coordinator, or Thread border router. When they come back online, the lock may take several minutes to rejoin the network. If it doesn’t come back after 10 minutes, follow the protocol‑specific steps above to re‑pair or reconfigure the lock.

Can a firmware update cause the lock to appear offline?

Yes. Some manufacturers ship firmware updates that change the lock’s radio behavior or pairing keys. Check the manufacturer’s app for recent firmware changes, and if the offline issue started after an update, try a factory reset and re‑pair.

Do I need a dedicated Zigbee coordinator for my lock?

If you use ZHA or Zigbee2MQTT, yes — the coordinator is the radio that talks to the lock. Make sure your coordinator is on the latest firmware and not overloaded with too many devices (keep under 40–50 for most USB coordinators).

Explore This Topic

Related guides in this cluster:

Similar Posts