Aqara Smart Lock U100: Home Assistant Local Setup Guide

The Aqara U100 is a deadbolt lock with a fingerprint reader, keypad, mechanical-key backup, and native Apple Home support. For Home Assistant, this guide uses a compatible Aqara hub as a Matter bridge. The lock talks to the hub over Zigbee; Home Assistant talks to the bridge over the local network.

The hub route is separate from the U100’s Bluetooth setup and Apple Home pairing. An Aqara hub is not required for every way of using the lock, and a Home Assistant Matter entity does not supply Apple Home Key by itself.

Direct Zigbee is a different integration path

The U100’s Zigbee support is intended for its Aqara hub connection. Do not assume that a Zigbee radio means full support in ZHA or Zigbee2MQTT. Before attempting a direct route, look for a current definition or quirk for the exact lock model and the functions it actually exposes.

This walkthrough uses the documented hub bridge route rather than claiming that all Aqara locks share the same restrictions. Resetting a working lock to try an unsupported route can also clear configuration you need to restore.

Matter bridge through an Aqara hub

Set up the U100 in Aqara Home, bind it to a compatible hub, and share that hub’s Matter bridge with Home Assistant. The available lock entity and attributes depend on the lock, hub firmware, and Matter mapping.

Native Apple Home pairing is separate. Aqara’s U100 FAQ describes Bluetooth setup and Apple Home Key. Home Assistant’s HomeKit Device integration supports compatible Bluetooth accessories, but that general capability is not proof of a complete U100 workflow or preservation of Home Key. Check those requirements before changing an existing Apple pairing.

What you need

• A U100 suitable for the door, correctly installed and mechanically calibrated according to its manual.
• A compatible Aqara hub with the required Matter bridge firmware and a supported app region.
• Home Assistant’s Matter integration connected to a working Matter Server.
• A phone with Aqara Home and the Home Assistant Companion app for the applicable setup steps.
• Access to the lock’s setup details and mechanical backup key.

For one hub option, see the Aqara E1 integration guide. Confirm U100 support on the exact regional hub before choosing it.

Setup walkthrough

1. Install and calibrate the lock using its manual. Test mechanical operation with the door open before any automation.
2. Add the lock in Aqara Home over Bluetooth and configure the users and access methods you need. Keep backup access available.
3. Bind the lock to the compatible Aqara hub and confirm that the app shows that relationship.
4. In the hub’s Matter settings, obtain a pairing or sharing code for Home Assistant.
5. Use the Home Assistant Companion app’s Matter workflow to add or share the hub. A code for an existing ecosystem may need to be generated through its sharing workflow.
6. Inspect the discovered lock entity. Test a command and compare its reported state with the actual bolt, first with the door open and then under the normal installed conditions.

For the initial pairing, keep the hub and Home Assistant on the same LAN. The IoT VLAN guide covers the additional discovery and IPv6 issues introduced by separating networks.

Check the discovered lock controls

Start with the lock entity, its lock/unlock commands, and state feedback. Check any battery, door, or diagnostic attributes that actually appear. Do not assume a latched bolt, closed door, jam condition, or user identity is represented simply because the app can show it.

Fingerprint enrollment, user credentials, and detailed access management remain separate from the basic Matter lock control. Test each event you intend to use before building an automation around it. A generic “unlocked” report is not necessarily a named person’s arrival.

Local control and account functions

Aqara states that fingerprints are stored locally on the U100 and that one-time passwords are generated locally. Those are manufacturer claims about credential handling, rather than an independent audit of the lock or app. They also do not establish what information a connected hub or remote service retains. Keep physical credential operation, local Home Assistant commands and remote account services separate when assessing privacy.

Aqara says the U100 can be set up and controlled at short range through Bluetooth without an Aqara hub. The app can manage some functions locally; it is inaccurate to label all PIN or fingerprint administration as cloud-only. Remote app control has different hub and network requirements.

For the Matter bridge, Home Assistant sends local commands to the hub. Account services, firmware downloads, remote app access, and phone notifications should be assessed separately. After setup, test the controls you use during a controlled WAN outage, while keeping backup door access available. See Aqara’s internet dependencies for the broader distinction.

Things to test before relying on an automation

• Apple Home Key: it belongs to the native Apple Home setup. A Matter bridge in Home Assistant does not create the Wallet credential. Check this before removing an Apple pairing.
• State feedback: compare the reported state with the physical door and bolt. Treat missing or stale feedback as a problem to investigate.
• Hub or server restart: confirm that the entity returns and that you can still use the lock’s independent access methods.
• Cards and fingerprints: use the enrollment and supported credentials documented for this model; an arbitrary NFC card is not automatically compatible.
• Remote unlocking: explicitly test the permissions and route you intend to use. Begin with state monitoring and notifications before adding unlocking automations.

An isolated report of delayed updates does not establish a fault affecting every U100. Record the lock and hub firmware, Home Assistant version, and observed behaviour when investigating an issue.

U100 and other Aqara lock formats

Door fit is the first comparison. A deadbolt and a mortise lock have different installation requirements, and regional model names do not guarantee the same bridge features.

Aqara’s U50 page and D100/N100 comparison describe those differences. Choose the exact lock first, then check which functions its supported hub exposes to Home Assistant.

Dependencies by function

Keep those functions distinct when testing an outage. A failed remote app session and a working local Matter command can both be valid results; neither alone describes the behaviour of the whole lock.