Google Home Matter Device Shows Offline in App
- Google Nest hub is offline or in a degraded state
- Device lost its Thread or WiFi connection
- Google Home firmware update changed Matter fabric state
Problem Description
Your Matter device appears in the Google Home app but shows as Offline or Unavailable. Google Assistant responds with the device is unavailable when commanded. Google Home offline errors on Matter devices indicate a broken communication path between the Google Home hub and the device — caused by hub state, Thread mesh gaps, or local network issues rather than a device hardware fault.
Symptoms
- Device shows Offline in Google Home and cannot be controlled
- Google Assistant says device is unavailable when commanded
- Device goes offline intermittently, recovering then dropping again
- Device appears offline in Google Home but works in another Matter controller
- Multiple Matter devices show offline simultaneously after a Nest hub reboot
Recognize these? Here's what usually causes it.
Common Causes
- Google Nest hub is offline or in a degraded state
- Device lost its Thread or WiFi connection
- Google Home firmware update changed Matter fabric state
- Thread border router coverage insufficient for device location
- IP address change causing hub to lose device
Most fixes happen in the first 3 steps.
Removing a device from Google Home only removes it from the Google fabric. Other platforms are unaffected.
Tools & Requirements
Step-by-Step Solution
Restart the Google Nest Hub
Open the Google Home app, tap the hub device, tap settings, and use the Reboot option — or unplug the Nest Hub for 30 seconds and reconnect. Wait 3 full minutes for the hub to rejoin the Matter fabric before checking device status. A hub that shows as Not Connected cannot route Matter commands regardless of the device connection state.
Check Thread Network Status
In Google Home go to Settings then Matter and Thread to view the Thread network and border router list. If your Nest Hub 2nd gen shows as offline under Thread, the Thread mesh is not active. Thread-based devices — sensors, locks, bulbs — all require a functioning Thread border router to communicate. Ensure at least one Nest Hub 2nd gen is within 30 feet of the affected device and shows Connected.
Power Cycle the Offline Device
Unplug the device or remove its batteries for 30 seconds. Restore power and wait 90 seconds for the device to rejoin WiFi or Thread and re-register with the Google Home hub. The Google Home app should update status within 2 minutes of reconnection. If the device goes offline again within hours, the issue is an ongoing connectivity problem at the device location — investigate WiFi signal or Thread path coverage.
Verify Device and Hub Are on the Same Network
Matter devices communicate with the hub over the local network. If your router has separate network segments — a guest network, IoT VLAN, or multiple subnets — the device and hub must be on the same segment. Confirm both the Nest Hub and the Matter device appear on the same SSID and subnet in your router admin panel. A device on a guest network and a hub on the main network cannot communicate, causing a permanent offline state.
Remove and Re-Commission if Offline Persists
If one device is consistently offline while all others work, remove it from Google Home under device settings then Remove device. Factory reset the device to clear its fabric state. Re-add it by tapping Add then Set up device then Have something already set up and scan the Matter QR code. After re-commissioning, issue a voice command immediately to confirm the device responds before creating any automations.
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 a Matter device is offline in Google Home but works in Apple Home, the issue is specific to Google Home's connection — not the device. Remove and re-add it to Google Home specifically.
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.
- Google Nest hub is offline or in a degraded
- Device lost its Thread or WiFi connection
- Google Home firmware update changed Matter fabric state
- Thread border router coverage insufficient for device location
- IP address change causing hub to lose device
