Matter Device Goes Offline After Router Reboot or Network Change
- Device received a different IP address after the router reboot and the hub cached the old one
- Router took longer to boot than the device's reconnect retry window
- WiFi password or network name was changed during the router update
Problem Description
Your Matter device goes offline and does not automatically recover after your router reboots, your WiFi network is changed, or your internet connection drops. The device remains offline until you manually power cycle it or re-add it to the controller app. Matter devices should reconnect automatically after a network interruption — persistent offline status after router events means the device is failing the reconnection handshake rather than being fundamentally broken.
Symptoms
- Device shows offline immediately after a router reboot or firmware update
- Device does not reconnect on its own after a brief internet outage
- Device comes back online after manual power cycle but drops again at the next router event
- All Matter devices go offline at once after a network change
- Device reconnects on some router reboots but not others
Recognize these? Here's what usually causes it.
Common Causes
- Device received a different IP address after the router reboot and the hub cached the old one
- Router took longer to boot than the device's reconnect retry window
- WiFi password or network name was changed during the router update
- DHCP lease table was cleared by the router reboot, forcing all devices to re-negotiate
- Thread border router rebooted first and the Thread mesh was not fully reconstructed when devices attempted to reconnect
Most fixes happen in the first 3 steps.
Changing your WiFi network name or password requires re-commissioning all WiFi-based Matter devices. There is no over-the-air credential update mechanism in the Matter protocol.
Tools & Requirements
Step-by-Step Solution
Power Cycle All Offline Matter Devices After the Router Finishes Booting
After a router reboot, wait until the router is fully online — all indicator lights stable, internet connection confirmed — before attempting any device recovery. Then power cycle each offline Matter device by unplugging it for 10 seconds and plugging it back in. Do not attempt reconnection while the router is still booting, as devices that try to reconnect before the DHCP server is ready will fail and may not retry for several minutes. Allowing the router to fully stabilize first reduces the reconnect window from minutes to seconds.
Assign Static DHCP Reservations to All Matter Devices
The most reliable long-term fix for post-reboot offline issues is to assign every Matter device a reserved IP address in your router. Log into your router admin panel and navigate to the DHCP reservation or static IP section. Find each Matter device by its MAC address in the connected devices list and assign it a permanent IP address outside the dynamic DHCP pool. This ensures the device always gets the same IP address after any reboot, so the Matter hub never loses track of it due to an address change.
Check If the WiFi Network Name or Password Changed During the Router Update
Some router firmware updates reset WiFi settings, including the network name (SSID) or password. If your network credentials changed, Matter WiFi devices cannot reconnect because they still hold the old credentials. Check your current WiFi SSID and password and compare against what was set before the update. If the credentials changed, each affected Matter device must be factory reset and re-commissioned with the new network credentials — there is no way to update WiFi credentials on a Matter device without re-commissioning.
For Thread Devices: Allow the Thread Mesh to Fully Rebuild
Matter over Thread devices — sensors, locks, and some bulbs — connect through a Thread mesh network anchored by border routers. After a router reboot, Thread border routers (Apple TV, HomePod, Echo 4th gen, Google Nest Hub) need several minutes to rebuild the Thread mesh before Thread end devices can reconnect. If Thread devices show offline after a reboot, wait 5 minutes without taking any action. In most cases the Thread mesh rebuilds on its own and all Thread devices come back online without manual intervention.
Increase the DHCP Lease Time in Router Settings
Short DHCP lease times — some routers default to 1 hour — cause devices to frequently renegotiate their IP addresses. If a device's DHCP lease expires at the same time the router reboots, the device loses both its IP address and its router connection simultaneously, making recovery take longer. Log into your router admin panel and increase the DHCP lease duration to 24 hours or 48 hours. This reduces how often devices need to renegotiate addresses and dramatically decreases the frequency of post-reboot offline events.
Quick Solutions
Still having issues? This is usually the deeper cause below.
This usually happens right after a router reboot or ISP change — the device rejoins the network but drops its cloud session silently.
If only Thread-based devices go offline while WiFi Matter devices stay online after a reboot, the issue is Thread mesh rebuilding time — not a WiFi problem. Thread devices reconnect automatically once the border router fully restarts.
Most WiFi drop-offs happen right after a router reboot or ISP swap — the device reconnects to the network but silently loses its cloud registration.
- Device received a different IP address
- Router took longer to boot than the device's reconnect
- WiFi password or network name was changed during the
- DHCP lease table was cleared by the router reboot,
- Thread border router rebooted first and the Thread mesh
