How to Fix Matter Smart Home Devices Not Responding?

Are your Matter smart home devices suddenly showing “Not Responding” in your app? You are not alone. Thousands of homeowners deal with this frustrating issue every day, and the good news is that most of these problems have simple, fixable causes.

Whether your lights stopped working after a firmware update, your smart plugs went silent after a power outage, or your Thread devices dropped off the network for no clear reason, this guide has you covered.

This post walks you through every known fix, step by step, in plain language. You will learn exactly why Matter devices stop responding and what to do about it, right now.

Key Takeaways

• Matter devices rely on a healthy local network. If your Wi-Fi, router, or Thread border router has any issue, your devices will show “Not Responding” even though nothing is wrong with the device itself. Always start troubleshooting at the network level.
• IPv6 and mDNS must be enabled on your home network for Matter to function correctly. Many router brands disable these by default, and that single setting can make all your Matter devices go offline at once.
• A 2.4GHz Wi-Fi connection is strongly recommended for Matter device setup and stable operation. Connecting your phone to a 5GHz band during setup is one of the most common causes of pairing failure and unresponsive behavior.
• Factory resetting and re-pairing a device is often the fastest fix for a device that has been unresponsive for a long time, especially after power outages or firmware updates that went wrong.
• Thread-based Matter devices need a working Thread Border Router. If your border router lost power, rebooted, or has outdated firmware, every Thread device in your home will stop responding until the Thread network rebuilds itself.
• Firmware updates on both your hub and your devices are critical. Outdated firmware is a top cause of Matter devices becoming unresponsive, and manufacturers release patches regularly to fix these exact issues.

Understanding Why Matter Devices Stop Responding

Before jumping into fixes, it helps to understand what is actually happening when a Matter device stops responding. Matter is a local, IP-based smart home standard that works over your home Wi-Fi or Thread mesh network. Unlike older cloud-based smart home systems, Matter sends commands directly over your local network without needing the internet. That means any disruption at the local network level, whether it is your router, your Wi-Fi signal, or your Thread mesh, will cause devices to go silent.

Matter devices communicate using IPv6 addresses and rely on a protocol called mDNS (Multicast DNS) to find each other on your network. When mDNS traffic is blocked, or when IPv6 is disabled on your router, your controller apps like Apple Home, Google Home, or Amazon Alexa simply cannot locate the device anymore, even if the device is still powered on and working fine internally.

The most common reasons Matter devices stop responding include: Wi-Fi network problems, an outdated Thread border router, router settings blocking mDNS or IPv6, outdated firmware on the device or hub, AP isolation being enabled on the router, power outages resetting the Thread mesh, and too many devices overloading the controller.

Understanding the root cause helps you pick the right fix the first time and avoid wasting an hour restarting things that were never the problem to begin with.

Check Your Wi-Fi Network Connection First

The very first thing you should do is check your home Wi-Fi network. A surprising number of “not responding” issues are simply Wi-Fi problems in disguise. Matter devices use your local network constantly, and even minor Wi-Fi instability can cause devices to appear offline in your app.

Start by opening your router’s admin page or app and checking whether the device is still visible on the network. Most routers list connected devices under a section called “Connected Devices” or “DHCP Clients.” If your Matter device does not appear there, it has dropped off the network entirely, and a network fix is what you need.

Next, check your Wi-Fi signal strength at the location of the device. Matter devices, especially Wi-Fi-based ones, need a strong and stable signal. If the device is far from your router or access point, signal loss is likely your problem. Move the device closer temporarily to test this theory. If it responds when nearby but not when far away, you need to improve Wi-Fi coverage in that area using a mesh network node or a Wi-Fi range extender.

Also, make sure your home network is not set to “isolated” mode. Some routers have a feature called “AP isolation” or “client isolation” that prevents devices on the same network from talking to each other. This feature will silently block all Matter communication even though every device appears connected to Wi-Fi. Log into your router admin panel, go to wireless settings, and turn off any AP isolation or client isolation option you find.

Fix Your Router’s IPv6 and mDNS Settings

This is one of the most overlooked fixes for Matter devices, and it solves a huge number of cases where devices appear completely offline. Matter is built on IPv6 addressing, and it requires mDNS (Multicast DNS) to work properly. If either of these is disabled or blocked on your router, your devices will show as “Not Responding” even when they are physically powered and connected.

To check IPv6 status, log into your router admin interface. The address is usually 192.168.1.1 or 192.168.0.1. Look for IPv6 settings under “Advanced,” “LAN Settings,” or “Network Settings.” Make sure IPv6 is enabled. You do not need a public IPv6 address from your internet provider. IPv6 just needs to be active on your local network (LAN) for Matter to function.

mDNS issues are more common in advanced router setups, especially with brands like UniFi, pfSense, or OPNsense. On these platforms, mDNS traffic does not automatically pass between VLANs or between the router and IoT devices. You need to enable an mDNS repeater or “Avahi” service to allow Matter discovery traffic to flow freely across your network.

For standard home routers from brands like TP-Link, ASUS, Netgear, and Eero, simply enabling IPv6 in the LAN settings is usually enough. If you made any recent changes to your router’s firewall rules or network segmentation, roll those changes back and test again. A single firewall rule accidentally blocking multicast traffic is enough to take down every Matter device in your home.

Restart Everything in the Right Order

Sometimes the fix really is as simple as restarting your devices. But the order in which you restart things matters a lot with Matter. Restarting in the wrong order can leave your network in a partially connected state that is just as broken as before.

Here is the correct restart sequence to follow. First, unplug your modem and router from the wall. Wait at least 60 seconds. Do not just use the restart button if your router has one. A full power cycle clears cached network states that a soft reboot will not fix.

Second, while your router is still off, unplug your Thread Border Router if you have one. This could be a Google Nest Hub, Apple HomePod mini, Apple TV 4K, Amazon Echo, or any other hub that acts as a Thread Border Router. Unplug any smart home hubs or bridges from other brands too.

Third, power your modem back on first, then your router. Wait for a full 2 minutes until the router has fully connected to the internet and all its radios are active.

Fourth, plug your Thread Border Router and any hubs back in. Wait another 5 to 10 minutes before testing your devices. Thread networks take time to rebuild after a power cycle. Testing too soon will make it look like the fix did not work, when in reality the Thread mesh just has not finished forming yet.

Finally, restart the app on your phone and check whether devices are now responding.

Switch to the Correct Wi-Fi Band During Setup

This tip applies specifically if your Matter devices are not responding right after you tried to set them up, or if a re-pairing attempt keeps failing. One of the most common setup mistakes is having your phone connected to a 5GHz Wi-Fi band when adding a Matter device.

Almost all Matter Wi-Fi devices require the initial connection to happen over a 2.4GHz network. The 5GHz band uses a different radio frequency that many Matter devices simply cannot use. When your phone is on 5GHz and the device is trying to connect on 2.4GHz, the pairing process fails or the device ends up stuck in a half-configured state and shows as “Not Responding.”

To fix this, go to your phone’s Wi-Fi settings and manually connect to your 2.4GHz network. Most routers broadcast both bands under the same name automatically, which makes it hard to know which you are on. The easiest solution is to temporarily create a separate 2.4GHz-only SSID on your router just for the setup process.

On iPhone, go to Settings, then Wi-Fi, and tap the (i) icon next to your network name to see if the frequency is shown. On Android, Wi-Fi frequency is often visible under “Network Details” or in your router’s device list. Once your phone is confirmed on 2.4GHz and Bluetooth is also turned on, try adding the device again. Most pairing failures resolve immediately after making this change.

Check and Update Your Device Firmware

Outdated firmware is a leading cause of Matter devices becoming unresponsive, and this applies to both your smart home hub and the devices themselves. Manufacturers release firmware updates specifically to fix Matter bugs, improve connectivity stability, and patch issues that cause “Not Responding” errors.

Start by checking the firmware on your Matter hub or controller. For Google Home users, make sure your Nest Hub, Nest Mini, or Google Home speaker is on the latest software. For Apple Home users, your HomePod, HomePod mini, or Apple TV 4K should be updated to the latest tvOS or HomePod software version. For Amazon Alexa users, Echo devices update automatically, but you can check the version in Device Settings within the Alexa app.

Next, check firmware on the devices themselves. Open the manufacturer’s native app (for example, TP-Link Tapo, Aqara, Eve, IKEA Home Smart) and navigate to device settings. Look for a firmware update option. Even if the app says the device is “up to date,” visit the manufacturer’s website and compare the listed firmware version with what your device is running.

If a firmware update itself caused the issue, the recovery process is to factory reset the device and re-add it. Some devices can be soft-reset and will auto-pull the corrected firmware during re-setup. If the device is completely bricked after an update, check the manufacturer’s support page for a hard recovery procedure, which usually involves holding the reset button in a specific pattern while powering the device on.

Power Cycle Your Matter Devices

A simple power cycle can clear internal errors that cause a Matter device to stop responding, even if the device appears powered on. This is different from a factory reset. A power cycle just reboots the device’s software without erasing any configuration or removing it from your smart home platform.

For plug-in devices like smart plugs and smart light bulbs, simply pull the plug from the wall, wait 30 seconds, and plug it back in. For hardwired devices like smart switches and dimmers, turn the circuit breaker off for that circuit, wait 30 seconds, and turn it back on.

For battery-powered devices, remove the battery, wait 30 seconds, and reinsert it. After the device powers back on, wait about 60 to 90 seconds before testing it in your app. Many Matter devices, especially Thread-based ones, need time to rejoin the Thread mesh network after restarting.

A helpful tip: If you have many devices that went offline at once (for example, after a power outage), do not power cycle them all simultaneously. Power them back on one by one, starting with the devices closest to your Thread Border Router or Wi-Fi router. This staged approach helps each device find a strong network connection before the next one tries to join.

Fix Thread Border Router Issues

If you are using Matter over Thread devices (which include many smart sensors, buttons, and locks), your Thread Border Router is the most critical component in the chain. When the Thread Border Router has a problem, every single Thread device in your home will stop responding at the same time.

Your Thread Border Router is usually a Google Nest Hub (2nd gen), Google Nest Hub Max, Apple HomePod mini, Apple TV 4K (3rd gen), or Amazon Echo (4th gen). Some third-party hubs like Aqara M2 and Samsung SmartThings Station also serve as Thread Border Routers.

The first step is to identify which device in your home is acting as the Thread Border Router and confirm it is powered on and healthy. On Apple Home, go to the Home app, tap the three-dot menu, then Home Settings, and scroll down to “Thread Network” to see your border router status. On Google Home, the Thread network status is visible in the Google Home app under the hub device settings.

If your Thread Border Router appears offline or shows errors, unplug it from power, wait 60 seconds, and plug it back in. After it restarts, wait a full 10 minutes before testing your Thread devices. Thread networks self-heal and self-organize, but this process takes several minutes. Testing immediately after restarting the border router will show devices as offline even if everything is actually recovering correctly.

Also, make sure your Thread Border Router’s firmware is current. Thread Border Routers receive firmware updates that improve Thread mesh stability and fix routing bugs. An outdated border router running old Thread firmware is one of the most common causes of intermittent “Not Responding” errors.

Resolve AP Isolation and Network Segmentation Problems

AP Isolation (also called Client Isolation or Wireless Isolation) is a router feature that blocks devices on the same Wi-Fi network from communicating with each other directly. It is designed for public hotspots where you want to protect users from each other, but it completely breaks Matter if it is accidentally enabled on your home network.

When AP Isolation is active, your phone cannot talk to your Matter hub, and your Matter hub cannot reach your devices, even though every device appears connected to Wi-Fi. The result is that every device shows as “Not Responding” in your app, and nothing you do to the devices themselves will fix it.

To check this, log into your router admin panel. This is usually found at 192.168.1.1 or 192.168.0.1 in your web browser. Navigate to Wireless Settings or Advanced Wi-Fi Settings. Look for any option labeled AP Isolation, Client Isolation, or Wireless Isolation and make sure it is turned OFF.

On mesh systems with multiple access points or nodes, this setting sometimes exists on individual nodes rather than the main router. Check every node’s settings individually. This is especially common on TP-Link Deco, ASUS ZenWiFi, and Netgear Orbi systems when a node is set to “AP Mode” instead of router mode.

A related issue is network segmentation, where your smart devices are placed on a separate IoT VLAN or guest network that cannot communicate with your main network. Matter devices and your Matter controller must always be on the same local network. If they are on different VLANs or subnets, Matter will not work, period.

Handle Matter Devices After a Power Outage

Power outages are a major trigger for Matter devices becoming unresponsive, and the behavior can be confusing because devices may work fine individually but not respond through the app. This is because power outages interrupt the Thread mesh network and can corrupt the connection state between devices and their paired controllers.

After power is restored, the Thread network needs time to rebuild. Every Thread Border Router and Thread device must power up and negotiate their roles in the mesh before any commands can flow through. This process can take anywhere from 5 minutes to over an hour in larger homes with many Thread devices.

The best approach after a power outage is patience. Follow these steps in order. First, let your router and internet connection fully restore. Second, make sure your Thread Border Router (HomePod, Google Nest Hub, etc.) is powered back on. Third, power your Thread devices back on one by one, starting from those closest to the border router. Wait 10 to 15 minutes before testing.

If devices still do not respond after 30 minutes, try the restart sequence described earlier in this guide. If specific devices remain unresponsive after a full restart cycle, a factory reset and re-pairing for those individual devices is likely the solution. This is because power interruptions sometimes cause a device’s network credentials or pairing information to become corrupted, and only a clean re-pairing will fix it.

Remove and Re-Pair Unresponsive Devices

When all other fixes fail, removing the device from your smart home platform and pairing it fresh is almost always the solution. This clears any corrupted configuration data, stale network credentials, or broken pairing information that is causing the device to refuse commands.

Before you do this, make sure you have the device’s Matter pairing code handy. This is usually a QR code or an 11-digit numeric code printed on the device or on a card in the box. For devices already set up in a manufacturer app (like TP-Link Tapo, Aqara, or IKEA), you can generate a new pairing code from inside the app under device settings.

Step one is to remove the device from your platform. In Apple Home, long press the device tile and select “Remove Accessory.” In Google Home, open the device, tap Settings, and select “Remove Device.” In Alexa, go to Devices, select the device, and tap Delete.

Step two is to factory reset the device itself. The method varies by brand. Most devices involve holding the reset button for 5 to 10 seconds until the indicator light flashes in a specific pattern. Check your device’s manual or the manufacturer’s website for the exact reset procedure. Do not skip this step. Removing a device from an app does not automatically reset the device, and re-adding without resetting can cause the same issues to reappear.

Step three is to add the device fresh using the QR code or setup code. Follow the platform’s standard setup process and wait for the device to fully commission before testing it.

Fix Multi-Admin Sharing Issues Across Platforms

One common and often misunderstood cause of Matter devices showing “Not Responding” is a problem with Multi-Admin sharing, where the same device has been added to more than one smart home platform (for example, both Apple Home and Google Home). Matter supports this feature, but it must be set up in the correct order with proper timing.

Each smart home platform that controls a Matter device consumes something called a “fabric.” Most Matter devices support up to 5 fabrics total. Apple Home uses 2 fabrics by itself, which means an Apple Home user only has 3 remaining fabrics for other platforms. If a device runs out of available fabrics, additional pairing attempts will fail and can leave the device in a broken state.

Pairing codes used for Multi-Admin sharing expire quickly. Google Home codes expire after 5 minutes, Alexa codes expire after 15 minutes, and Apple Home codes expire after just 3 minutes. If you try to use an expired code, the pairing will fail silently and the device may end up in an inconsistent state where it shows as “Not Responding” in one platform.

The fix is to remove the device from all platforms, factory reset it, and then re-add it to each platform one at a time. Always add to your primary platform first, then generate a sharing code from that platform to add it to the secondary platform. Do not generate multiple sharing codes at the same time. After creating a code for one platform, complete that setup fully before generating a code for the next platform.

Reduce Network Congestion and Interference

As you add more Matter devices to your home, the network load increases. Too many devices competing for bandwidth or Thread mesh time slots can cause slower responses or “Not Responding” errors, especially during peak usage times. This is more common in homes with 20 or more smart devices running on a single Wi-Fi access point.

For Wi-Fi-based Matter devices, the 2.4GHz band is particularly vulnerable to congestion because it is shared with many other household devices including microwaves, baby monitors, and neighboring networks. Use your router’s admin panel to check which Wi-Fi channel the 2.4GHz band is using and switch to a less crowded channel (1, 6, or 11 are the non-overlapping channels in the 2.4GHz band).

For Thread networks, adding more Thread-capable devices actually improves the mesh because Thread is designed as a self-healing mesh network. However, placing too many Thread devices too far apart can cause routing gaps. Make sure Thread devices are placed within 30 to 40 feet of each other to maintain strong mesh connections.

Consider upgrading to a Wi-Fi 6 or Wi-Fi 6E router if you have more than 15 smart devices. Wi-Fi 6 handles device congestion much more efficiently than older Wi-Fi standards. Also, if your internet service provider supplied router is over 4 years old, it may lack the processing power to handle the mDNS and IPv6 demands of a modern Matter smart home.

Check App Permissions and Platform-Specific Settings

Sometimes the Matter device is working perfectly but the app simply cannot see it due to missing permissions on your phone. This is one of the easiest fixes and one of the most overlooked. Both iOS and Android require specific permissions for smart home apps to discover and communicate with local network devices.

On iPhone and iPad, go to Settings, scroll down to your smart home app (for example, Google Home, Amazon Alexa, eWeLink), and tap on it. Make sure the following permissions are enabled: Local Network access, Bluetooth access, and Location access. Without Local Network permission, the app literally cannot communicate with Matter devices on your Wi-Fi. Without Bluetooth, the app cannot complete the initial pairing handshake.

On Android, go to Settings, then Apps, find your smart home app, and check Permissions. Make sure Nearby Devices, Bluetooth, Wi-Fi, and Location are all allowed. Android sometimes revokes app permissions automatically after system updates, so this is especially worth checking if devices stopped responding after you updated your phone’s operating system.

For platform-specific issues, here are a few quick checks. For Apple Home, make sure at least one home hub (HomePod, HomePod mini, or Apple TV 4K) is connected and showing as “Connected” in Home Settings. For Google Home, sign out of the app and sign back in to refresh your authentication token. For Amazon Alexa, go to Skills and Games, find the Matter skill, and disable then re-enable it to force a resync.

When to Contact Manufacturer Support?

If you have tried every step in this guide and your Matter device is still not responding, it is time to reach out to the manufacturer directly. There are specific situations where support intervention is needed, and it is better to identify them early rather than spending more hours troubleshooting.

Contact the manufacturer when: the device does not enter factory reset mode no matter how long you hold the reset button; the device shows up in your router’s connected devices list but never appears in any smart home app; the device’s indicator light shows a pattern not described in any documentation; or the device went dead after a firmware update and no hard reset procedure resolves it.

Before contacting support, gather the following information to make the process faster: the device model number and serial number (usually found on a sticker on the device); the firmware version (from the manufacturer’s app or printed on the device); your home network setup (router brand and model, whether you use a mesh system); the smart home platform you are using; and a description of the exact symptoms and which steps you have already tried.

Most major Matter device manufacturers including TP-Link, Aqara, IKEA, Philips Hue, and Eve have active community forums where engineers and experienced users post solutions to known issues. Searching your exact device model plus “not responding Matter” in these forums often surfaces a fix that is not in any official documentation.

FAQs

Why do my Matter devices keep going offline every few hours?

This is usually caused by an unstable Thread Border Router or a Wi-Fi router that periodically drops mDNS or IPv6 traffic. Check whether your router’s firmware is up to date, make sure IPv6 is enabled on the local network, and verify that no AP isolation is active. Replacing an older Thread Border Router with a newer model running updated Thread firmware often resolves this persistent issue.

Do I need internet access for Matter devices to work locally?

No. Matter is designed to work entirely over your local home network without needing an internet connection for local control. However, remote access (controlling devices while you are away from home) does require an internet-connected hub. If your internet goes down but your router and local network are still running, your Matter devices should continue to respond to local commands from apps on your home network.

Why did all my Matter devices stop responding at the same time?

When all devices go offline at once, the problem is almost never with the devices themselves. The most likely cause is your Thread Border Router losing connection, your router blocking mDNS or IPv6 traffic, a firmware update on your hub, or AP isolation being accidentally enabled. Start your troubleshooting at the network and hub level rather than touching the individual devices.

Can I use Matter devices on a guest Wi-Fi network?

No. Matter devices must be on the same local network as your smartphone and your smart home hub. Most guest networks are isolated by design to protect guests from accessing local devices, and this isolation breaks Matter completely. Always connect your Matter devices and your phone to your primary home Wi-Fi network.

How do I know if my router supports Matter?

Your router does not need any special “Matter certification.” What it needs is: IPv6 enabled on the local network, mDNS traffic allowed (not blocked by a firewall), AP isolation turned off, and a stable 2.4GHz Wi-Fi band. Most home routers from major brands sold in the past 5 years meet these requirements with the right settings applied.

Why does my Matter device respond slowly with a 10 to 20 second delay?

Slow response is often caused by a device that has been idle for several hours entering a sleep or low-power state. Thread devices in particular can have a delayed “first response” after a long idle period. Updating firmware on both the device and the hub, reducing the number of devices sharing the same Thread router, and ensuring strong Thread mesh coverage by placing devices closer together are the most effective fixes for this issue.

Is a factory reset the same as removing a device from an app?

No, they are two different things. Removing a device from an app (like Apple Home or Google Home) only deletes the device from that platform’s configuration, but the device itself still holds its pairing and network data internally. A factory reset clears everything stored on the device and returns it to its original unboxed state. For a clean re-pairing, you should do both: remove it from the app and factory reset the device.

My Matter device works in the manufacturer’s app but not in Apple Home or Google Home. What is wrong?

This usually means the Multi-Admin fabric setup failed or was done in the wrong order. Remove the device from the secondary platform (Apple Home or Google Home), then go into the manufacturer’s app and generate a fresh Multi-Admin sharing code. Immediately switch to Apple Home or Google Home and complete the pairing before the code expires (3 to 5 minutes depending on the platform). Make sure Bluetooth and Local Network permissions are active on your phone during this process.