Short answer
Most Matter/Thread unavailable issues in Home Assistant come from Thread network mismatch, a missing or offline Thread Border Router, stale Matter Server state, blocked IPv6 or mDNS discovery, or a controller fabric that still works in Apple Home or Google Home but no longer reaches Home Assistant.
Next step
Diagnosis table
Start with the symptom that matches your setup. This avoids unnecessary factory resets when the real issue is a controller, border router, network, or entity exposure path.
| Symptom | Likely cause | What to check | Fix | Tool |
|---|---|---|---|---|
| Matter over Thread device is unavailable only in Home Assistant | The device is still attached to a Thread network owned by Apple Home, Google Home, or another controller. | See whether the device still responds in the ecosystem that originally commissioned it. | Keep that controller online, then use a fresh Matter multi-admin share code instead of resetting first. | Open |
| No Thread network or border router is detected | The selected hub is a Matter controller but not an active Thread Border Router, or it is offline. | Confirm the exact hub role and whether it is online before pairing or re-pairing the device. | Bring a known Thread Border Router online, then retry diagnosis from the same local network. | Open |
| Device went unavailable after router, VLAN, or Wi-Fi changes | IPv6, multicast, or mDNS discovery is blocked between Home Assistant, Matter Server, and the controller path. | Review network isolation, guest Wi-Fi, VLAN firewall rules, IPv6 settings, and mDNS forwarding. | Restore local discovery between the Home Assistant host, controller, phone, and border router before resetting devices. | Open |
| Device appears but entities are missing or stale | Matter exposes fewer entities than the vendor app, or Home Assistant has stale entity state after a fabric or firmware change. | Compare vendor app features with Home Assistant entities and note which entities are actually exposed by Matter. | Reload Matter integration, restart Matter Server only after network checks, and avoid assuming every vendor feature is exposed. | Open |
Symptoms this page covers
- Device dropped offline
- No border router found
- Unavailable after router or hub change
- Works in one ecosystem but not another
Likely causes
- The active Thread Border Router is offline or changed.
- Multiple Thread networks exist and the device is on a different one.
- Network changes blocked IPv6, multicast, or mDNS discovery.
- Home Assistant Matter Server is running but cannot reach the controller path.
Fix checklist
- Identify which Thread Border Router the device was originally commissioned through.
- Confirm that hub is online before changing Home Assistant settings.
- Check Home Assistant Thread and Matter diagnostics before resetting the device.
- Restart Matter Server only after confirming the network path.
- If Google Home or Apple Home still controls the device, use that as a clue for the active Thread network.
Avoid these mistakes
- Do not reset all Thread devices when only the border router path changed.
- Do not delete a working ecosystem fabric before exporting or recreating a multi-admin path.
- Do not assume Wi-Fi router changes are unrelated; IPv6 and multicast changes can affect Matter.
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
Why is my Matter device unavailable in Home Assistant?
Common causes are a changed Thread Border Router, a device attached to a different Thread network, blocked IPv6 or mDNS discovery, stale Matter Server state, or a controller fabric that still works in Apple Home or Google Home but no longer reaches Home Assistant.
Do I need a Thread Border Router?
You need a Thread Border Router for Matter over Thread devices. A Matter Controller is not always a Thread Border Router, so confirm the exact role of HomePod mini, Apple TV 4K, Google Nest Hub, Aqara Hub M3, or your Home Assistant OTBR setup.
Why does the device work in Apple Home or Google Home but not Home Assistant?
That usually means the accessory is still reachable through the ecosystem that owns the active Thread network or Matter fabric. Use that working ecosystem as evidence, then generate a fresh Matter sharing code instead of resetting immediately.
Should I reset and re-pair the device?
Reset only after you check the border router, Matter Server, controller path, and network discovery. Resetting too early can remove the working fabric or Thread-network clue you need to recover the setup.
Can Matter expose fewer entities than the vendor app?
Yes. Matter can expose fewer entities or standard controls only. Vendor-specific features, advanced diagnostics, and some bridge child devices may remain limited or unavailable in Home Assistant.
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.