Short Answer: Find Which of Four Links Broke
If a Matter-over-Wi-Fi device worked and later went offline, do not delete it yet. Matter-over-Wi-Fi means the device uses ordinary Wi-Fi for its connection and Matter as its local control language. First decide whether it lost Wi-Fi, whether Home Assistant lost Matter's local IPv6 addresses and mDNS discovery, whether Matter Server—Home Assistant's local Matter controller app—is unhealthy, or whether that device's power or software failed. mDNS is the nearby-device announcement system that helps Matter find a device's current address. A device can still appear in the router and its vendor app while Home Assistant cannot reach it through Matter.
Update Home Assistant and the official Matter Server app, then compare the router's list of connected devices, sometimes called its client list, with Matter Server's WiFi map. If every Wi-Fi Matter device failed together, investigate Matter Server, IPv6, local discovery traffic, or a router and access-point change. An access point is the Wi-Fi unit the device joined. If one model or one room failed, check its power, Wi-Fi signal, access point, and device software (firmware). Keep Home Assistant and the device on the same simple local network while testing, and set Home Assistant IPv6 to Automatic if you are unsure.
Only after those checks should you turn one safely interruptible device off and back on, called a power cycle. Save factory reset and re-pairing for last. Home Assistant's Matter path is official: Home Assistant and the Open Home Foundation Matter Server were certified by the Connectivity Standards Alliance in 2025. That establishes a supported controller path, but it does not prove that every manufacturer's hardware, firmware, router combination, or installation is faultless.
The Four Links That Can Look Like the Same Offline Device
These devices do not use Thread, and they do not need a Thread border router. The Home Assistant screen shows one red unavailable state even though four different links may have failed.
| Possible failure | What it means in the house | Best first evidence | First move |
|---|---|---|---|
| Wi-Fi association | The device is no longer connected to an access point. | It is absent from the router or access-point client list. | Check power, coverage, the intended Wi-Fi network, and recent Wi-Fi changes. Do not touch Matter records yet. |
| Local IPv6 and mDNS | The device has Wi-Fi, but Home Assistant cannot discover or reach its local Matter address. | The router sees it, but Matter Server logs show discovery, timeout, subscription, or network errors. | Use the same home network while testing, enable Home Assistant IPv6, and allow nearby-device discovery traffic. |
| Matter Server or Home Assistant connection | The local controller service is starting, disconnected, migrating, or failing to recover sessions. | Many Matter devices fail together, Home Assistant's Matter connection is unavailable, or the app log repeats errors. | Use the current stable Matter Server app and Tara's server-recovery guide before touching devices. |
| Device power or firmware | One accessory is stuck even though the network and other Matter devices are healthy. | One model or one unit fails repeatedly while neighbors stay online. | Check vendor firmware and safely power-cycle that one device. Escalate with diagnostics if it returns. |
First Question: Is One Device Offline, or All of Them?
This is the fastest useful split. One failed device points toward its power, Wi-Fi link, access-point roaming, or device software. Several devices on one access point point toward that access point, mesh node, or network segment. Every Matter-over-Wi-Fi device points toward Matter Server, Home Assistant networking, IPv6, nearby-device discovery filtering, or a recent router change.
Do not let a working non-Matter Wi-Fi camera or speaker end the investigation. Ordinary Wi-Fi connectivity and Matter connectivity are not identical. Matter's operational discovery uses local IPv6 and DNS service discovery. Other products may use IPv4, a fixed local address, or an outbound cloud connection and therefore remain healthy during a Matter-specific local discovery failure.
The Five-Minute Check Before You Restart Anything
- Test the physical device. Use its normal button or load. Confirm it has power and the connected lamp or appliance itself is safe and working.
- Open the router or access-point client list. Look for the device name or address and note which access point it uses. If it is missing, solve Wi-Fi or power first.
- Open the Matter Server WiFi map. On Home Assistant OS, go to Settings > Apps > Matter Server > Open Web UI > WiFi. A red device node means Matter Server considers it offline. Signal and access-point data are clues, not a complete service history.
- Compare another Matter-over-Wi-Fi device. If another unit on the same access point works, the first device becomes the stronger suspect. If all nodes on that access point fail, inspect the shared path.
- Check Home Assistant and Matter Server logs. Look for the device or node number and plain clues such as
timeout,subscription,mDNS,IPv6, ornetwork is unreachable. Save the log before restarting.
Version note: This guide was checked on July 11, 2026 after the stable Matter Server 9 launch. Matter Server 9 added a Wi-Fi network view and faster reconnection. Labels can change in later releases, so use the current dashboard legend and keep the same one-device-versus-many-device reasoning.
If the Router Sees the Device but Home Assistant Does Not
This is where Matter's local network requirements matter. Home Assistant's official documentation says Matter relies on local IPv6 and mDNS discovery traffic moving freely. You do not need IPv6 service from your internet provider, but IPv6 must work inside the home. In Home Assistant, open Settings > System > Network. If you do not manage IPv6 deliberately, the official recommendation is Automatic.
Home Assistant also recommends keeping Wi-Fi Matter devices on the same local network segment as Home Assistant. In an advanced setup, that usually means the same VLAN, an intentionally separated network segment. A VLAN can be useful for security, but Matter needs correct IPv6 routing, multicast discovery—one message sent to nearby devices—and firewall rules across any boundary. If an IoT VLAN is failing, temporarily test one device and Home Assistant on the same trusted local segment. That controlled test is safer than randomly opening ports or disabling the firewall for the whole house.
Review guest-network isolation, wireless client isolation, multicast filtering, and router features marketed as multicast or IGMP optimization. IGMP is a router method for managing multicast traffic. Home Assistant warns that malfunctioning or over-aggressive settings can harm Matter discovery. Change only one setting at a time, record its original value, and restore it if the test does not help. Do not broadly disable Wi-Fi encryption, firewalling, or network segmentation simply because a forum post names the same router brand.
If the Device Has Actually Left Wi-Fi
Now the problem is below Matter. Many Matter Wi-Fi accessories use 2.4 GHz, which reaches farther than 5 GHz but can be crowded. During setup, Home Assistant's documentation tells Wi-Fi Matter users to keep the phone on the same 2.4 GHz network. For an already paired device, check the exact model's supported bands, the signal where it is installed, and whether a mesh system moved it to a distant access point.
In-wall switches and outlets are harder than a phone on a table: the radio may sit behind a wall plate, inside a metal box, or next to electrical wiring. A client list that shows frequent reconnects or a weak Matter Server Wi-Fi link supports a coverage investigation. Move or tune the access point only after confirming a repeat pattern; do not buy a hub or factory-reset the device merely because another room has stronger signal.
Community reports also mention band steering, fast roaming, automatic channel changes, and multi-access-point meshes. Those are useful suspects, not universal diagnoses. Test the affected device on one stable access point or a simpler Wi-Fi network name if your setup permits it, then put the original settings back if behavior does not change.
Why the Vendor App Can Still Work
A working vendor app proves less than it appears to. Some apps send commands through the manufacturer's cloud: the device makes an outbound internet connection, and the phone talks to the service. Home Assistant's Matter connection instead uses a direct local path inside the house. The cloud path can work while local IPv6 or mDNS is broken.
Use the vendor app for two useful jobs: confirm the exact model and device software, and install a supported firmware update when necessary. Then turn off duplicate schedules or automatic rules, called automations, so the vendor app and Home Assistant do not both operate the same switch. Do not assume that signing out of the vendor account makes Matter less local; daily Matter control remains local, while maintenance and remote features may still use the cloud.
When Matter Server Is the Shared Failure
If Wi-Fi and Thread Matter devices both fail, or Home Assistant's Matter connection—called the Matter integration—is unavailable, inspect the controller before the network edge. Matter Server 9 is the current official app line and was designed as a drop-in migration with faster start-up and device recovery. Update to the current stable release offered by Home Assistant, keep a backup, and let any first-start migration finish.
Open the Matter Server app log and its Web UI. If the app says Running but Home Assistant still shows the integration offline, allow its device reconnection check, sometimes called an interview, to settle, then make one controlled restart. If the server is stuck on Starting, repeats its first log lines, or reports storage or memory errors, follow Tara's Matter Server 9 recovery guide. Uninstalling the server or integration is not a routine troubleshooting step because controller state matters.
Is Home Assistant's Matter Integration Official?
Yes. The Connectivity Standards Alliance certified Home Assistant as a Matter software component on February 27, 2025, and separately lists the Open Home Foundation Matter Server. Home Assistant's certification announcement explains that the server handles the controller communication while Home Assistant provides the certified user-interface component. Calling that path an “unofficial Matter version” is inaccurate.
Certification still has a boundary. It does not guarantee that every device firmware, Wi-Fi chipset, optional feature, router, or installation will behave perfectly. When escalating a repeat failure, send the retailer or manufacturer the exact model, firmware, Home Assistant and Matter Server versions, whether the router still sees the device, the Matter diagnostics, and the smallest reproducible sequence. Ask which Matter version and certification record apply to that product, and whether the maker has reproduced the failure with another certified controller.
Home Assistant lets you download redacted device diagnostics: open Settings > Devices & services > Matter, select the device, open its menu, and choose Download diagnostics. Review files before sharing them publicly even when the tool says sensitive values are redacted.
The Lowest-Risk Recovery Order
- Record the symptom. Note which devices failed, their access points, the time, and whether a router, Home Assistant, or firmware update happened first.
- Save evidence. Download Matter diagnostics and copy the relevant Matter Server and Home Assistant log lines.
- Update supported software. Use current stable Home Assistant, Matter Server, and vendor firmware. Make a Home Assistant backup before controller updates.
- Fix the shared local path. Confirm IPv6, nearby-device discovery, the same local network segment, and the intended access point without weakening unrelated security.
- Power-cycle one accessible device. Interrupt only a load that is safe to stop, then give the device time to rejoin Wi-Fi and for Matter Server to rediscover it.
- Restart one shared component only if evidence points there. Schedule router, access-point, or Matter Server work so the household knows other devices may briefly go offline.
- Reset and re-pair only the one confirmed bad device. Preserve its original setup code and controller records first, then follow the manufacturer's factory-reset procedure exactly.
What Not to Do
- Do not delete every unavailable Matter device. A shared network fault should not become a full-house commissioning job.
- Do not create a Thread network. Matter-over-Wi-Fi devices do not use Thread, so a border router cannot repair their Wi-Fi path.
- Do not assume the vendor app proves local control. It may be using an internet service while Matter's local path is down.
- Do not turn off IPv6 because the internet provider does not offer it. Matter needs IPv6 locally inside the home.
- Do not disable firewalls or isolation everywhere. Make a narrow, reversible test and restore anything that does not help.
- Do not open a wall switch or outlet. Use the product's documented external controls. Hire a qualified electrician for wiring, damaged devices, heat, arcing, or unusual odors.
What Stays Local, and What May Still Need Cloud
| Function | Normal path | Internet or account caveat |
|---|---|---|
| Home Assistant control of a paired Matter device | Local IPv6 over Wi-Fi inside the home. | No vendor cloud is required for normal commands. |
| Vendor app control | May be local, cloud-based, or both. | A working app may rely on the vendor's internet service. |
| Device-software maintenance | Matter over-the-air (OTA) updates when the product publishes them, or the vendor's own method. | The vendor app, account, or internet may still be required. |
| Remote control away from home | A secure Home Assistant remote-access path or another controller's service. | Remote access is separate from Matter's local daily control. |
| Apple Home, Google Home, Alexa, or SmartThings sharing | Matter sharing, called multi-admin, gives each platform its own secure controller relationship. | Each platform's app, account, voice, and remote features have their own cloud boundaries. |
Tara's Practical Recommendation
For recurring Matter-over-Wi-Fi outages, keep the diagnosis boring and measurable. Check the router client list, the Matter Server WiFi view, and the logs before restarting anything. Separate one device from one access point from the whole Matter controller. Keep IPv6 and local discovery working, and use the simplest network boundary your household can support reliably.
If one certified product repeatedly drops while neighboring Matter devices remain healthy, preserve the evidence and hold the manufacturer to a specific firmware or compatibility answer. If every device fails together, fix the shared Home Assistant or network path. Either way, re-pairing is the last step, not the first reflex.
Related Tara Reading
- How to read Matter Server's Thread and Wi-Fi network map
- Matter Server 9 stuck on Starting or Offline
- Why Home Assistant devices are unavailable after a restart
- Will Home Assistant and Matter work without internet?
- Should Home Assistant live on the main network or an IoT VLAN?
- Can Home Assistant update Matter device firmware?
FAQ
Why does the vendor app work while Home Assistant says the device is offline?
The vendor app may be using the manufacturer's cloud while Home Assistant uses Matter's local IPv6 and mDNS path. A working app proves the device has power and some network access, but not that Home Assistant can discover and reach it locally.
Does a Matter-over-Wi-Fi device need a Thread border router?
No. Matter-over-Wi-Fi uses the home's Wi-Fi network and local IPv6. A Thread border router is required only for Matter-over-Thread devices.
Is Home Assistant's Matter support unofficial?
No. Home Assistant and the Open Home Foundation Matter Server were officially certified by the Connectivity Standards Alliance in 2025. Certification does not guarantee that every device model or firmware release is bug-free.
Should I delete and re-pair an offline Matter-over-Wi-Fi device?
Not first. Check whether the device remains on Wi-Fi, inspect the Matter Server WiFi map and logs, verify local IPv6 and mDNS, update firmware, and safely power-cycle one device. Re-pair only after preserving the setup code and exhausting reversible checks.
Does Matter-over-Wi-Fi need the internet for normal Home Assistant control?
Normal Matter control is local and does not need the vendor cloud. Internet access can still be used for remote control, some firmware updates, certificate data, or vendor-specific app features.