# Why your Matter device will not show up in Google Home A troubleshooting guide for Matter devices that fail to appear in Google Home, covering hubs, Thread border routers, IPv6, sharing, reset state, and device type support. Canonical page: https://matterhome.io/guides/why-matter-device-will-not-show-up-google-home Markdown page: https://matterhome.io/guides/why-matter-device-will-not-show-up-google-home.md Published: 2026-06-09 Guide type: Ecosystem guide Ecosystem: Google Home ## Feature Image - Image: https://matterhome.io/content-assets/guides/why-matter-device-will-not-show-up-google-home/feature.png - Alt text: A phone showing an abstract failed smart home setup near unbranded Matter devices - Caption: AI-generated editorial image representing a failed Matter setup flow, not a product test. ## Sources - https://support.google.com/googlenest/answer/12391458 - https://support.google.com/googlenest/answer/13127223 - https://support.google.com/googlenest/answer/7029585 - https://developers.home.google.com/matter/supported-devices - https://www.home-assistant.io/integrations/matter/ When a Matter device refuses to appear in Google Home, the device is not always broken. The usual failure is a missing piece of setup infrastructure: no compatible hub, no Thread border router for a Thread device, IPv6 trouble, a device that is already owned by another Matter fabric, or a category Google Home does not expose the way you expected. The useful move is to debug the path in order. Do not factory reset the device five times before checking the hub and network. ## Confirm the Google Home hub first Google says Matter setup needs a Matter-enabled hub for Google Home. For Wi-Fi Matter devices, Google lists hub devices such as Google Home, Nest Mini, Nest Audio, Nest Hub, Nest Wifi Pro, Google TV Streamer, and select compatible TVs. For Thread devices, Google says you need a hub that also works as a Thread border router, such as Nest Hub (2nd gen), Nest Hub Max, Nest Wifi Pro, or Google TV Streamer (4K). If the device is Matter over Thread and your only Google hardware is a speaker without Thread, Google Home may not have the network path it needs. ::device-group{title="Matter devices to test against the right Google Home path" slugs="aqara-motion-and-light-sensor-p2,ikea-klippbok-water-leak-sensor,govee-matter-smart-bulbs,philips-hue-bridge-and-bridge-pro"} ## Check whether the device is Thread or Wi-Fi Matter over Wi-Fi and Matter over Thread fail differently. A Wi-Fi device may need the phone, router, and device on the right network, often 2.4 GHz for smart home hardware. A Thread device needs the Thread border router close enough to complete setup and maintain the connection. Look for the network path on the product page or packaging. If the box says Matter and Thread, do not treat it like a Wi-Fi device. If it says Matter over Wi-Fi, do not spend time trying to fix Thread. ## Make sure IPv6 is not the hidden problem Google's Matter preparation guide is unusually direct about IPv6: without IPv6 enabled on the home wireless network, setup may appear to succeed at times, but control and other functions can fail later. That does not mean you need to become a network engineer. It does mean you should check your router settings, mesh router app, or ISP router documentation before blaming the device. Matter uses IP networking, and mixed Wi-Fi plus Thread homes need the network to hand traffic around properly. ## If the device is already in another app, share it correctly Matter devices can be used in multiple Matter-certified apps, but the second app usually needs a sharing flow from the first controller. Google says that if you set up a third-party Matter device in the manufacturer's app, you may need to accept the share prompt or follow the manufacturer app's instructions to share it with Google Home. If the device was first added to Apple Home, Home Assistant, SmartThings, Alexa, or a brand app, open that app and look for a Matter pairing, share, or multi-admin option. Scanning the original QR code again may not work if the device is no longer in factory-new commissioning mode. ## Check device type support and feature expectations Matter support expands by device type over time, and platform support does not always arrive at the same pace. Google points buyers to its supported device type documentation because a Matter-certified product can still expose only the parts Google Home currently supports. This matters most for sensors, environmental readings, bridges, robot vacuums, appliances, and advanced settings. A device may appear but not show the value you expected. It may also appear under a generic name or in a less obvious room after setup. ## Reset only after the basic checks Factory reset is the last normal step, not the first. Before resetting, confirm the Google Home app is current, the phone has Bluetooth enabled, the device is powered and in pairing mode, the hub is online, the Thread border router exists if needed, and IPv6 is enabled. If setup freezes, Google recommends restarting the Matter device, closing the Google Home app, clearing the app cache on Android, restarting the phone, and trying again. If the device still fails, the manufacturer's setup instructions matter. Some devices need their own app for firmware, unlock state, or Matter pairing mode. ## When to stop fighting it Stop and reconsider the product if Google Home support is listed as limited, if the exact device type is not useful in Google Home yet, or if the device's best features live in a brand app you do not want to keep. A Matter logo is worth something. It is not a guarantee that every feature will land cleanly in Google Home on the first try.