Short Answer: Buy the Boring Local Path First

For most Home Assistant homes in mid-2026, the safest local smart-lock path is still a Z-Wave lock paired directly to Home Assistant. It keeps the radio, user codes, and automations inside your own stack, and Home Assistant's June 3, 2026 release added first-party credential management for Z-Wave locks.

Matter over Thread is now a real option, especially if you want a lock model that also lives in Apple Home or Google Home, or you want features that only ship on newer Matter locks. But it is still the more network-sensitive path: Thread health, border routers, phone commissioning, and model-specific lock-management bugs matter more.

Tara's rule: never let phone presence or a cloud app be the only way in. Keep a physical key, a manual keypad or fallback code path, and a lock that behaves sensibly when Home Assistant is offline.

Why This Question Is Worth Publishing Right Now

The demand signal is clear and current. On the Home Assistant Community thread "2026 Smart lock recommendations" published on March 31, 2026, the opening question is exactly the homeowner version of this article: what smart locks work with Home Assistant, with auto-lock and some kind of PIN or biometric access.

The lock tag page on the Home Assistant Community, as visible on June 24, 2026, shows that this is not a one-thread topic. It lists Level Door Lock Pairing Guide with 14,614 views, Automatically unlock your door when getting in bluetooth range with 7,071 views, Zigbee Lock Manager with 4,224 views, Yale Assure lock code management with zigbee2mqtt with 3,209 views, and Locks which support Home Assistant and Apple Home Key with 1,505 views. The question is not just which brand to buy. It is which protocol path gives local control, sane code management, and fewer edge cases.

Reddit is asking the same thing in slightly different language. Recent r/homeassistant threads include Smart lock that is fully local, good HA integration, AA or AAA battery powered, Matter Over Thread or Z-Wave for Smart Locks?, and Locally Hosted Smart Lock Recommendations. That is enough overlap to treat this as an active Home Assistant question, not a generic smart-home shopping post.

What Changed in 2026

Home Assistant's answer changed this spring. On April 1, 2026, the official release notes added the Matter lock manager, which lets Home Assistant manage lock users and PIN codes directly on supported Matter locks. Then on June 3, 2026, Home Assistant added equivalent Z-Wave smart lock credential management, including the new Manage access flow and corresponding Home Assistant actions.

That means this is no longer a simple "Matter is too young, use Z-Wave" conversation. Both paths now have first-party lock management inside Home Assistant. The real question is which path gives you the right combination of local control, cross-platform behavior, and operational calm.

Path Best when Why it is strong What can still bite you
Z-Wave lock direct to Home Assistant You want the cleanest Home Assistant-first local setup. Direct local control, first-party code management, keypad events for automations, no vendor app or cloud requirement in the Home Assistant flow. You need a Z-Wave radio and the product selection is shaped by your region and door type.
Matter-over-Thread lock shared with Home Assistant You want Apple or Google coexistence, or a lock model whose best features ship on the Matter version. Standards-based local control, multi-admin sharing, first-party lock management inside Home Assistant on supported devices. Thread health, phone commissioning, border routers, and some model-specific lock-management bugs still matter.
Works with Home Assistant certified local lock You want a better shopping filter than vague marketing claims. Home Assistant certifies exact devices, not just brands, and requires local key functionality. Certification does not mean every secondary feature is identical across protocols.
Cloud or app-first Wi-Fi lock You care more about app features or selection than a local-first architecture. Wide availability and lots of consumer features. More vendor dependency, weaker handoff story, and a worse fit if your goal is a local Home Assistant home.

Why Z-Wave Is Still the Default Recommendation

The new Z-Wave lock flow in Home Assistant is unusually direct about the value proposition. The official June 3, 2026 release notes say "Everything happens directly between Home Assistant and your lock over Z-Wave; no cloud account, no vendor app, no internet connection required." That is almost exactly what local-control buyers keep asking for on Reddit.

The official Z-Wave integration docs also show why Z-Wave is still so attractive for front doors. Home Assistant exposes actions to get users, set a credential, set a lock user code, and delete credentials. It also exposes notification events such as "Keypad unlock operation" and "Keypad lock operation". That matters when you want a guest-code automation, a cleaner audit trail, or a sane "unlock once, then disarm lights and hallway scene" flow without depending on a vendor cloud.

If your goal is a house-owned lock path, Z-Wave remains the easiest one to explain on a whiteboard: your lock talks to your Z-Wave radio, Home Assistant manages users and codes locally, and the rest is just automations. If you need the radio architecture context, Tara's guide on Z-Wave JS vs Z-Wave JS UI covers when you should keep the topology simple and when you should not.

When Matter Is Worth It

Matter is now credible enough that the answer cannot be "never." Home Assistant's April 1, 2026 release added first-party Matter lock management, and the official Matter docs describe the multi-admin path for bringing a device that is already in Apple Home or Google Home into Home Assistant as well. For some households, that is the whole point: one lock, multiple local controllers.

In practice, this often lines up with people who also care about Apple-side features such as HomeKey. That is an inference from current shopping threads and forum demand, not a Home Assistant statement. If that is your priority, Matter is often the shortlist you will end up exploring, because those features tend to cluster around newer Thread-capable locks rather than older Home Assistant-first Z-Wave models.

But the current caveats are real. On GitHub, issue #167096 is still open as of June 24, 2026 and reports Aqara Matter locks showing "No users configured" and failing to set credentials. Another Matter lock-management issue, #166671, was filed on March 27, 2026 for some Nuki locks not showing the Manage Lock option during the 2026.4 cycle and was later closed. The lesson is not "Matter locks are broken." The lesson is that model-specific rough edges still exist, and your front door is a poor place to pilot a shaky Thread or beta-controller experiment.

If your Thread network is already stable and you deliberately want cross-platform behavior, Matter is a reasonable path. If you are still deciding whether your house even has the right Thread border router, do not make the lock your first Matter lab project.

Use Works With Home Assistant as the Shopping Filter

Home Assistant's official Works with Home Assistant recap is useful here because it explains what the badge actually means. The foundation says certified devices work seamlessly and locally, that it now certifies exact devices rather than only brands, and that the key functionality for a door lock is straightforward: the lock should lock and unlock from within Home Assistant.

The same recap also makes an important point about younger standards like Matter: secondary features can still vary depending on what the standard supports. That means the badge is not magic, but it is still a far better filter than a random product page that says "works with" somewhere in the footer.

My practical recommendation is simple: if you are shopping fresh, start from the Works with Home Assistant certified-device mindset, then choose between Z-Wave and Matter based on the rest of your house. Do not let a generic Matter logo, or a generic app-store rating, outrank the boring question of how this lock behaves when your phone battery is dead and your internet is irrelevant.

What to Avoid if Local Control Is the Goal

Home Assistant's Matter docs warn that bridging devices through Matter can lose features compared with a native local integration. The docs use Philips Hue as the obvious example, but the logic applies to locks too. If a lock already has a good native local path, or a direct Z-Wave path, or a clean direct Matter path, do not route it through an extra vendor bridge just because the bridge exists.

The other path to avoid is making the lock the only thing that decides entry. Local automation can improve convenience, but your front door should still be understandable without a dashboard. If the setup requires three apps, a flaky geofence, and a Thread topology you cannot diagram, it is not a finished household system yet.

Guardrails for Lock Automations

Locks deserve stricter rules than lights. Tara's baseline guardrails are:

  • Do not auto-unlock solely on GPS arrival or a vague presence signal.
  • Keep at least one independent fallback path: physical key, keypad, or both.
  • Rotate temporary guest codes and treat them as access credentials, not convenience toggles.
  • Test the lock's behavior when Home Assistant is offline before you call the setup done.
  • Keep convenience automations separate from true security assumptions.

If that sounds conservative, good. The front door is where "mostly works" becomes an expensive design standard.

Tara's Take

If I were planning a local, handoff-friendly Home Assistant install for a real house today, I would default to Z-Wave for the lock unless there was a specific reason to prefer Matter. The specific reasons are valid: Apple coexistence, a lock model you genuinely prefer, or a deliberate standards-first stack. But absent those reasons, Z-Wave is still the calmer answer.

Tara's general bias is simple: keep the front door on the path that the next homeowner, partner, or future-you can still operate after a phone migration, a bad update, or a dead internet connection. That usually means fewer moving parts, not more.

If this pushes you into bigger protocol or architecture decisions, these guides cover the neighboring choices.

FAQ

Is Z-Wave still the safer Home Assistant lock path in 2026?

Usually yes. Home Assistant's June 3, 2026 release added first-party Z-Wave credential management, and the release notes say the Z-Wave flow works directly between Home Assistant and the lock with no cloud account, vendor app, or internet requirement. Matter is much better than it was earlier in 2026, but it still asks more of your network.

Can Home Assistant manage PIN codes on both Matter and Z-Wave locks?

Yes, on supported locks. Home Assistant's April 1, 2026 release added Matter lock management for users and PIN codes, and the Z-Wave integration plus the June 3, 2026 release provide equivalent user and credential management for Z-Wave locks.

Can I keep Apple Home and Home Assistant on the same Matter lock?

Usually yes. Home Assistant's Matter docs describe adding a device that is already in Apple Home or Google Home so both platforms can control it. In practice, that is the normal path when people want Apple-side lock features and Home Assistant automations together.

Should I use a Matter bridge for a lock if a native local path already exists?

Usually no. Home Assistant's Matter docs say Matter bridges can lose features compared with a native local integration. For locks, prefer the direct Z-Wave, direct Matter, or native local integration path when it is available.

Do all smart locks need a Thread border router for Home Assistant?

No. Only Matter locks that use Thread need a Thread border router. Z-Wave locks use a Z-Wave radio, and Wi-Fi locks follow their own integration path.