Short answer
If U200 works in Google Home but will not share into Home Assistant, the failure is usually in Matter multi-admin sharing, Thread credential access, wrong Thread network selection, or Home Assistant Matter Server readiness.
Next step
Symptoms this page covers
- Google Home works but Home Assistant pairing fails
- Multi-admin code fails
- Thread network is not found
Likely causes
- Google Home owns the active Matter fabric and Home Assistant is using an invalid sharing code.
- The phone cannot access the Google-created Thread credentials during Home Assistant commissioning.
- Home Assistant Matter Server is not ready when the multi-admin code is used.
- There are multiple Thread networks and the lock is not on the network Home Assistant expects.
Fix checklist
- Confirm the lock is stable in Google Home before sharing.
- Create a new Matter sharing code from Google Home immediately before adding it to Home Assistant.
- Confirm Home Assistant Matter Server is running and reachable.
- Check whether Google Home and Home Assistant see the same Thread network.
- If pairing fails, document the active Thread Border Router before resetting the lock.
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 use an old multi-admin code after a failed commissioning attempt.
- Do not assume a Nest display and a Home Assistant Thread adapter automatically share Thread credentials.
- Do not remove U200 from Google Home until you have a fallback pairing 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 Google Home?
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.