Short answer
Aqara U200 is a Matter over Thread lock, so Home Assistant setup can fail if you do not have a usable Thread Border Router, Matter Server, compatible commissioning phone path, and a valid Matter setup code from the ecosystem that currently owns the lock.
Next step
Symptoms this page covers
- Pairing code spins
- Commissioning times out
- Works in Aqara app but not Home Assistant
- Works in Apple Home but not Home Assistant
Likely causes
- Home Assistant Matter Server is missing or not reachable.
- The selected hub is not acting as a Thread Border Router for the lock.
- The U200 is already commissioned into another ecosystem and needs a fresh multi-admin code.
- Android or iOS commissioning is selecting the wrong Thread network or controller path.
Fix checklist
- Run the Matter/Thread Troubleshooter with Aqara U200, Home Assistant, and pairing failed selected.
- Confirm a Thread Border Router is online before commissioning the lock.
- Confirm Home Assistant Matter Server is installed and running.
- Generate a fresh Matter sharing code from the ecosystem where U200 is already working.
- Keep the phone near both the lock and Thread Border Router during commissioning.
Capability matrix
Feature-level support can differ from basic compatibility. Treat low-confidence rows as buying or setup questions to verify before relying on automations.
| Feature | Aqara app | Apple Home | Home Assistant Matter | Google Home | Alexa | Notes |
|---|---|---|---|---|---|---|
| Lock / unlock | works | works | works | works | partial | Basic lock control is the main Matter lock capability users should expect first.Confidence: medium |
| Battery status | works | works | partial | partial | unknown | Battery exposure can vary by ecosystem and Matter integration behavior.Confidence: medium |
| Door / latch state | works | partial | partial | unknown | unknown | Some state details may appear differently from lock/unlock state.Confidence: low |
| Jammed state | works | unknown | partial | unknown | unknown | Users explicitly ask for full lock status; verify in the target integration before relying on automations.Confidence: low |
| PIN code management | works | partial | not-supported | unknown | unknown | Matter pairing may expose lock control without Home Assistant lock code management.Confidence: medium |
| Temporary passcodes | works | unknown | not-supported | unknown | unknown | Treat temporary passcodes as Aqara-app-managed unless your target ecosystem proves otherwise.Confidence: medium |
| Unlock logs / user logs | works | unknown | not-supported | unknown | unknown | Audit-style logs are usually vendor-app territory, not a safe Matter assumption.Confidence: medium |
| NFC / Apple Home Key | partial | works | not-supported | not-supported | not-supported | Home Key is an Apple Home feature path, not a Home Assistant Matter feature.Confidence: medium |
| Firmware updates | works | not-supported | not-supported | not-supported | not-supported | Keep the Aqara app available for firmware and advanced settings.Confidence: high |
| Matter multi-admin sharing | works | works | partial | partial | partial | Sharing between ecosystems can fail when Thread credentials, fabric ownership, or setup codes are misaligned.Confidence: medium |
Avoid these mistakes
- Do not assume the Aqara Hub M3, Apple Home, Google Home, and Home Assistant are all on the same Thread network.
- Do not reuse an expired or already consumed Matter setup code.
- Do not reset the lock repeatedly until you have confirmed the Thread and Matter controller path.
Need a final setup and reliability path?
$1.99 setup + reliability report
Send your scene, devices, hubs, and target ecosystem. We will return what to connect, what hub is missing, which features may not work, reliability risks, fallback checks, and what to buy or avoid.
FAQ
Should I factory reset Aqara Smart Lock U200 first?
Usually no. First confirm the controller, hub, network, and integration path. Resetting too early can remove useful evidence about which ecosystem or Thread network currently owns the device.
Do I need a Thread Border Router?
You need a Thread Border Router when the device is Matter over Thread or otherwise uses Thread. A Matter Controller is not always a Thread Border Router, so verify the exact hub role before pairing.
Does Matter expose every feature and entity?
Not always. Matter often exposes standard controls, while advanced settings, vendor-specific features, and some bridged child entities may remain available only through the vendor app or another integration path.
What should I check before buying another hub?
Check whether you already have the required Matter Controller, Thread Border Router, vendor hub, Zigbee coordinator, and Home Assistant service. Use the linked calculator or diagnostic tool before purchasing extra hardware.
Can SmartHomeCompat guarantee this fix for Home Assistant?
No. These pages are based on official docs, product information, public compatibility data, and community issue patterns. They are designed to narrow the likely setup path and reveal missing pieces.
Feedback
Help improve this compatibility data
Smart home compatibility changes quickly. Send a report, request a missing device, flag information that needs another review, or tell us if a paid setup diagnosis would save you time.
Describe your devices, hubs, blocker, reliability risk, and the report output that would save you time.
Tell us which device, hub, bridge, protocol, or ecosystem should be added next.
Flag outdated, incomplete, or unclear setup guidance so it can be reviewed.
Choose a gateway, bridge, interface, or conversion path for KNX, BACnet, Modbus, DALI, Matter, Zigbee, Z-Wave, MQTT, or Home Assistant.