I have setup a U400 lock with an admin access code, and the connected it to my Nest Hub via Thread/Matter. I note that in the Home app, my entire family is listed as admins (is that right?!) and I can set access codes for each of them. The Aqara app also lets me create users and add access codes for them. I verified that codes from Aqara and codes from Home both work. Google Home seems to let me add users remotely, but I seem to need bluetooth connection to use Aqara to add users.
It seems that Home cannot list that Aqara codes (or users) exist, and Aqara does not list that the Home access codes (or users) exist. So I cannot associate a fingerprint with a Google Home created user. I take it that this is by design or constraint, and would be interested to know the rationale.
To test, I also installed Apple Home and connected the lock to it. I can see some users with passcodes there, but the users have unknown names.
What is the right mental model about how this all works, and how do people manage users & passcodes across these different ecosystems?
@wang_roat Great question — this is one of the more nuanced aspects of Matter-enabled locks, and your observations are spot on.
The mental model: Think of the U400 as having two independent user databases that don’t sync with each other. One lives in Aqara Home (local Bluetooth), the other in each Matter ecosystem you bind to (Google Home, Apple Home, etc.). They’re parallel tracks, not intersecting ones.
Why this separation? Matter’s architecture treats each ecosystem as its own “fabric” with isolated credential storage — a security design choice, not a bug. Your Aqara fingerprints, PINs, and admin codes stay in Aqara’s sphere; Matter passcodes live in whatever hub/controller manages that fabric. The lock stores both sets but doesn’t cross-reference them.
The practical workflow most users settle on:
| Use Case |
Best Approach |
| Fingerprints, UWB, detailed access logs |
Aqara Home (requires Bluetooth proximity for setup) |
| Remote passcode management, family sharing |
Google Home / Apple Home via Thread |
| Mixed households |
Pick one “source of truth” per credential type — e.g., fingerprints in Aqara, guest codes in Google Home |
On your specific observations:
- Family showing as “admins” in Google Home is typical — it inherits your Google Home structure, not the lock’s native hierarchy.
- Apple Home showing “unknown” names likely reflects Matter passcodes created elsewhere without iOS Wallet pairing; Apple Home keys with proper setup should display clearly[“content_id”:3"].
The fingerprint-to-Matter-user gap you identified is indeed a current limitation. No ecosystem currently bridges Aqara’s biometric enrollments to Matter identity profiles — you’d need to manually correlate them via logs or naming conventions.
For deeper ecosystem-specific behaviors or if you’re hitting edge cases, the Aqara Home App Customer Service Team can clarify your exact setup: Profile > Help & Feedback > Customer Service, or scan the QR code below. If you don’t have an Aqara Home account, click here to create a ticket.
Curious how others here handle multi-ecosystem credential management — any creative workarounds?
