Aqara Smart Lock U100: Home Assistant Local Setup Guide

The U100 is Aqara’s flagship lock for the North American and Australasian markets: Zigbee connectivity, fingerprint reader, Apple HomeKey, IP65 weatherproofing, and a deadbolt form factor that fits standard US prep holes. If you’re already running Home Assistant and want to add it, the integration path is workable but not obvious, and there are some genuine trade-offs worth understanding before you commit.

The short version: the U100 is not a standard Zigbee device. You cannot pair it directly with Zigbee2MQTT or ZHA. It requires an Aqara hub as an intermediary, and the cleanest path into HA is through that hub’s Matter bridge. Local operation after initial setup is substantially achieved, but “cloud-free” is not quite accurate given how the hub behaves.

Here’s what I found going through this setup.

Why direct Zigbee pairing does not work

The first thing people try is pairing the U100 directly to their Zigbee coordinator. It will not work, and this is worth understanding clearly so you don’t spend an afternoon debugging.

Aqara locks use a proprietary encryption layer on top of the standard Zigbee stack. The keys are not shared outside Aqara’s ecosystem. Zigbee2MQTT maintainers confirmed in a GitHub discussion (Z2M issue #22260) that support for Aqara locks will not be added without Aqara releasing those encryption keys, which they have not done. ZHA is in the same position.

This applies to all Aqara locks, not just the U100. The D100, N100, and U50 all have the same constraint. The hub-via-Matter path is the standard for this entire product line.

Integration path: Matter bridge via Aqara hub

The correct path is:

1. Pair the U100 to an Aqara hub (via the Aqara Home app)
2. Enable the hub’s Matter bridge feature and get its pairing code
3. Add the hub to HA as a Matter device
4. The lock appears as a device under the hub in HA

The hub acts as a Matter bridge, translating between the U100’s proprietary Zigbee protocol and Matter’s standard device types. HA then talks to the hub over your LAN via Matter, and the hub relays commands to the lock.

Compatible hubs: M2 (firmware 4.0.0 or later), M3, E1, and M100. If you have an older M2 on firmware below 4.0.0, it will only offer HomeKit bridging, not Matter. Check your hub’s firmware version in the Aqara app before attempting Matter commissioning.

There is also an Option B: adding the lock via HomeKit Controller instead of Matter. The hub exposes the lock through its HomeKit bridge, and HA’s HomeKit Controller integration picks it up. This path typically exposes fewer entities than the Matter path and historically has been more stable for some users. I’ll note where it differs, but the article focuses on Matter as the primary recommendation since it exposes more controls.

What you need

• Aqara Smart Lock U100 (US-market deadbolt SKU)
• A compatible Aqara hub: M2 (fw 4.0.0+), M3, E1, or M100
• Aqara Home app, active account (cloud access required for initial setup)
• Home Assistant with the Matter integration enabled
• A phone or tablet for Matter commissioning (required by the Matter spec; the QR code scan happens on mobile)

The hub is a hard requirement. There’s no documented way to use the U100 with HA without one.

Setup walkthrough

Step 1: Add the lock to your hub via Aqara Home app

Open the Aqara Home app, select your hub, and follow the lock’s pairing sequence (typically holding the reset button inside the battery compartment). The lock pairs to the hub over Zigbee. Run through access method setup in the app. Fingerprints, PIN codes, and NFC tags are all configured here, not in HA.

Step 2: Enable Matter bridging on the hub

In the Aqara app, go to your hub’s settings and find the Matter option (labelled “Matter” or “Expose to HomeKit/Matter” depending on hub model and firmware). Enable it and note the pairing code or QR code shown.

Our M3 Matter bridge guide covers this step in detail for the M3, and the Aqara Hub E1 local integration walkthrough covers the E1 path.

Step 3: Commission the Matter bridge in HA

On the Home Assistant side, go to Settings > Devices & Services > Add Integration > Matter. When prompted to scan or enter the pairing code, use your mobile device, since the commissioning flow requires Bluetooth or the phone to be on the same network. Enter the code from step 2.

The hub appears in HA as a Matter bridge device.

Step 4: Verify the lock appears

Under the hub’s device entry in HA, the U100 should appear as a child device. If you have other Aqara devices paired to the same hub, they’ll appear here too, depending on whether the hub exposes them via Matter.

Step 5: Check entities

Once the lock device is visible, confirm the entities are present. See the next section for what to expect.

Entities in Home Assistant

Via the Matter bridge, the U100 exposes:

• lock entity: lock and unlock state, plus the lock/unlock action. This is the core entity for automations.
• battery: battery percentage. The reporting cadence is not fixed and updates on the lock’s own schedule rather than on demand, so don’t expect second-by-second figures.
• Lock event attributes: whether HA receives the unlock method (fingerprint, PIN, NFC, physical key) as a distinct attribute, or only binary lock/unlock state, depends on the HA Matter implementation in your release. Treat granular per-method reporting as unreliable and confirm it on your own version before building automations around it.

What is not available from HA, regardless of integration path:

• PIN code management. Add, delete, or modify PINs from the Aqara app only. HA exposes no code management entities via Matter.
• Fingerprint enrollment. Done via the lock’s keypad or the Aqara app.
• User-labelled access log. HA may receive raw lock/unlock events, but there’s no user identity attached. You can’t tell from HA whether it was the master PIN or a guest code.

If granular access management via HA is important to your use case, the U100 does not offer it through any current integration path. That functionality stays in the Aqara app.

Cloud dependencies and privacy trade-offs

The honest breakdown:

Initial setup requires cloud. You need an Aqara account to pair the lock to the hub via the app. This is a one-time step, not an ongoing requirement for lock/unlock automation in HA. But there’s no documented offline-first pairing flow.

Ongoing lock/unlock automation is local. After Matter commissioning, HA communicates with the hub over your LAN. Lock and unlock commands go: HA → Matter (LAN) → hub → Zigbee → lock. No cloud hop for that specific path.

The hub continues to phone home. This is the main nuance. The hub maintains cloud connectivity for: Aqara app remote access, OTA firmware updates, and time synchronization. This is hub-level behavior that applies whether or not you have a lock on it. For guidance on limiting that traffic, see our Aqara/Xiaomi IoT VLAN setup guide. One note: blocking the hub’s cloud access will likely break remote access via the Aqara app and may affect OTA delivery.

Fingerprints are stored locally on the lock. Aqara’s FAQ states that fingerprint templates are stored on the lock’s local processor, not uploaded to their servers. I can’t independently verify this, so treat it as vendor-claimed rather than confirmed. The lock does not need internet access to perform fingerprint matching.

One-time codes are generated locally. Aqara describes one-time and offline passwords as being generated on the lock rather than fetched from the cloud. As with the fingerprint claim, treat this as vendor-stated.

Matter fabric and certificate concerns. There’s a community observation that Aqara may store Matter fabric certificates server-side rather than strictly on-device. The practical concern: if Aqara’s Matter infrastructure were to shut down, locally-paired devices might require re-commissioning. This is unconfirmed speculation from the HA Community forums, not a documented behavior. I’m noting it because it keeps coming up, not because I have evidence it’s a real risk.

Verdict. For the specific use case of automating lock/unlock in HA, local operation after initial setup is largely achieved. Full cloud independence is limited by hub behavior, which is a broader constraint of the Aqara ecosystem, not unique to the lock. If you want to understand where the cloud boundaries sit more generally, our explainer on whether Aqara works without internet covers this.

Known issues and gotchas

Matter connection drops approximately once a week. Multiple users on the Aqara Forum report that the Matter connection between the hub and HA stops receiving state updates after several days. The lock stops reflecting its true state in HA, and automations triggered by lock state may not fire. The workaround is to go into the Aqara app and refresh or re-expose the Matter connection. No automated fix has been confirmed as of early 2026. This is the biggest operational issue with this setup. Source: Aqara Forum thread “Matter appears to stop working (U100 Lock & M2 Hub)”.

Latch fault alerts don’t pass through the M3 Matter bridge. If the latch doesn’t fully extend or retract, the Aqara app shows a fault notification. That alert does not forward to HA via the Matter bridge on M3 hubs. Aqara Forum confirmed this is a known gap as of 2026, with no fix shipped. If latch monitoring matters for your setup (and for a front door it probably does), this is a meaningful limitation.

NFC compatibility is narrower than you’d expect. The U100 only works with MIFARE Classic 1k cards. NTAG215 tags, common in hobby NFC circles, do not work. If you’re planning to issue NFC keycards to family members, verify your card stock before buying in bulk.

M2 firmware requirement. If you’re using an M2 hub, you need firmware 4.0.0 or later for Matter bridge support. Older M2 firmware only offers HomeKit bridging. The update is available via the Aqara app, but it requires the hub to be online.

Initial cloud setup is unavoidable. There is no way to pair the lock and enable the Matter bridge without an Aqara account and internet access. This is a one-time dependency, but it is real. If you’re setting this up at a location with no reliable internet during install, plan accordingly.

HomeKit and HA coexist. The U100 can be simultaneously accessible via HomeKit (through the hub’s HomeKit bridge) and HA (via the hub’s Matter bridge). Both can control the lock. Comands sent from HA should update the state visible in Apple Home via the hub, though there may be a brief lag. I haven’t tested this extensively myself, so if you’re relying on tight synchronization between Apple Home and HA, verify it in your setup before deploying in production.

U100 vs other Aqara locks

If you’re still deciding which Aqara lock to get, here’s where the U100 fits:

The Z2M/ZHA limitation applies to all of these. The hub-via-Matter path is standard across the line. Choose based on form factor, HomeKey requirement, and your target market’s availability.

Cloud and privacy at a glance

The U100 paired with an Aqara hub and HA’s Matter integration gives you solid local control for what matters in daily use: automating the lock based on presence, time, or other HA triggers. What it doesn’t give you is full cloud independence — both the initial setup and the hub’s ongoing background connections remain cloud-dependent. That’s the honest trade-off, and for most people who weigh it, the local automation capability is worth accepting the hub’s residual cloud behavior.

If you’re at the buying stage, the bundled kits (U100 + M2 or U100 + M100) are worth considering since the lock genuinely requires a hub to work with HA. Buying separately and then discovering you need the hub anyway is a common experience.