Google Home Not Finding Your Devices? Fixes for Every Situation

Why Google Home Can't Find Your Devices

Few things in smart home life are more frustrating than telling Google to turn on a light and hearing "Sorry, I couldn't reach [device name]." I've troubleshot this issue dozens of times across my own setup and for friends and family, and the causes fall into a handful of categories that are almost always fixable. This guide walks through every scenario I've encountered, from the obvious to the obscure.

Before we dive in, a quick note: Google has been migrating its smart home infrastructure over the past year, moving devices from the old "Works with Google" architecture to the newer Google Home app with local control and Matter support. This transition has introduced its own set of issues, which I'll cover specifically.

The First Thing to Check: Your Wi-Fi Network

I'd estimate that 60% of "Google Home can't find my device" problems come down to networking. Smart home devices are picky about their Wi-Fi, and Google Home is pickier than most platforms about how devices connect.

Same Network Requirement

Your phone (running the Google Home app) and the device you're trying to add must be on the same Wi-Fi network during setup. This sounds obvious, but it catches people more often than you'd think — especially if you have a mesh network with separate SSIDs for 2.4GHz and 5GHz bands, or a guest network that's isolated from your main network.

Check your phone's Wi-Fi settings and confirm it's connected to your primary home network, not a guest network, VPN, or cellular data. Then verify the device you're adding is on the same network.

The 2.4GHz vs 5GHz Problem

This is the single most common networking issue with smart home devices, and it affects Google Home heavily. Most smart home devices — especially plugs, bulbs, and sensors — only support 2.4GHz Wi-Fi. If your phone is connected to the 5GHz band of your router, it may not be able to discover devices that are on the 2.4GHz band during setup.

The fix depends on your router setup:

• If you have separate SSIDs for each band (e.g., "HomeNetwork" and "HomeNetwork-5G"): Connect your phone to the 2.4GHz SSID before setting up the device. You can switch back to 5GHz afterward.
• If you use a single SSID for both bands (band steering): Temporarily disable band steering in your router settings, or move your phone far enough from the router that it drops to 2.4GHz. Some routers have a "smart connect" feature that can be disabled temporarily.
• If you use a mesh network (Google Wifi, Eero, etc.): Most mesh systems handle band steering automatically. Try moving the device closer to a mesh node during setup. For Google Wifi specifically, the Google Home app handles both the mesh network and device setup, which generally avoids band conflicts.

AP/Client Isolation

Some routers have a feature called AP isolation, client isolation, or device isolation that prevents devices on the network from communicating with each other. This is common on guest networks and some ISP-provided routers. If it's enabled on your main network, Google Home literally cannot discover devices because network discovery packets are blocked.

Log into your router admin panel and look for this setting under wireless settings or advanced settings. It should be disabled for your primary network.

Google Home App Troubleshooting

If your network is configured correctly and devices still aren't showing up, the Google Home app itself may be the issue.

Clear the App Cache

The Google Home app's cache can become corrupted, especially after app updates or OS updates. This manifests as devices not appearing, setup flows hanging, or the app crashing during discovery.

On Android:

• Go to Settings > Apps > Google Home > Storage
• Tap "Clear Cache" (not "Clear Data" — that will log you out)
• Force stop the app
• Reopen and try device discovery again

On iPhone:

• iOS doesn't have a cache clear option, so delete the Google Home app and reinstall it from the App Store
• Log back in with your Google account
• Wait for all your existing devices to sync (this can take a minute)

Location Permissions

Google Home requires location permissions to discover nearby devices. On both Android and iOS, make sure the app has "Allow all the time" or "While using the app" location access. On Android 12+, you also need "Nearby devices" permission enabled for the Google Home app. Without these, Bluetooth-based device discovery (used for initial setup of many devices) won't work.

Bluetooth Must Be On

Many smart home devices use Bluetooth Low Energy (BLE) for initial setup, then switch to Wi-Fi for ongoing communication. If Bluetooth is disabled on your phone, the Google Home app can't discover these devices. Make sure Bluetooth is enabled before starting the setup process.

Matter Pairing Issues

Matter is supposed to make device setup universal, but the reality in 2024 is that Matter pairing through Google Home has its own set of quirks.

QR Code Scanning Failures

If the Google Home app won't scan your Matter device's QR code, try these steps in order:

• Make sure you're scanning the Matter QR code, not a different QR code on the packaging (some devices have multiple codes)
• Ensure adequate lighting — the camera needs a clear view of the code
• Try entering the numeric setup code manually instead (the 11-digit number usually printed near the QR code)
• Check that the device is in pairing mode — most Matter devices need to be factory reset or put into pairing mode before they'll respond to setup

Matter Device Stuck on "Setting Up"

I've seen this with several Matter devices including TP-Link Kasa plugs and Nanoleaf bulbs. The device starts the pairing process, the app says "Setting up your device," and then it hangs or fails after a few minutes.

The fix that works most often:

• Factory reset the device (check the manufacturer's instructions — usually holding a button for 10+ seconds)
• Remove any existing pairing for that device in the Google Home app
• Restart your Google Home speaker or hub (the one that will be the Matter controller)
• Try pairing again with your phone within a few feet of both the device and your Google Home speaker/hub

Thread Device Pairing

Thread-based Matter devices (like some Eve and Nanoleaf products) require a Thread border router on your network. For Google Home, this means you need a Nest Hub (2nd gen), Nest Hub Max, or Nest Wifi Pro — the Nest Audio and Nest Mini do not have Thread radios. If you're trying to pair a Thread device and don't have a Thread border router, the device won't be discovered.

"Something Went Wrong" Errors

This is Google's catch-all error message, and it can mean almost anything. Here's how to narrow it down.

Check Google's Service Status

Google Home relies on cloud services for account management, device linking, and many control commands. If Google's services are experiencing an outage, device discovery and control will fail. Check the Google Home community forums or Downdetector before spending an hour troubleshooting your own setup.

Account Issues

If you've recently changed your Google password, enabled two-factor authentication, or switched Google accounts, your Google Home devices may lose their account link. Open the Google Home app, go to Settings > your account, and verify you're logged in with the correct account. Also check that you haven't hit the device limit for your Google account (there's a limit of around 50-60 devices per home structure).

The Structure/Home Problem

Google Home organizes devices into "homes" (called structures). If you accidentally created multiple homes, devices in one home won't be visible or controllable from another. Go to Google Home app settings and check which home is selected. I've seen situations where a phone update reset the active home selection, making it look like all devices disappeared.

Chromecast Devices Not Showing Up

Chromecast and Chromecast-enabled TVs have their own discovery issues, separate from general smart home devices.

Chromecast Firmware Updates

Chromecast devices occasionally get firmware updates that break Google Home integration temporarily. If your Chromecast suddenly stops appearing in the Home app, check its firmware version (Settings > System > About on Chromecast with Google TV) and look for any pending updates.

HDMI-CEC Conflicts

If your Chromecast is connected to a TV or AVR with HDMI-CEC enabled, CEC commands can interfere with the Chromecast's network connection when the TV is off. Some TVs cut power to HDMI ports when in standby, effectively disconnecting the Chromecast. If your Chromecast intermittently disappears from Google Home, try a different HDMI port or use the USB power adapter plugged into a wall outlet instead of the TV's USB port.

Cast to TV Not Working

If you can see your Chromecast in the Google Home app but can't cast to it from other apps, the issue is likely mDNS (multicast DNS) being blocked on your network. Some routers block multicast traffic by default, and some have IGMP snooping settings that can interfere. Check your router's multicast/IGMP settings and ensure they're enabled for your main network.

Nest Device Migration Issues

Google has been migrating Nest devices (thermostats, cameras, doorbells) from the old Nest app to the Google Home app. This migration has been rocky for some users.

Devices Stuck in the Nest App

If your Nest devices appear in the Nest app but not in Google Home, you need to migrate your Nest account to a Google account (if you haven't already) and then migrate your devices to the Google Home app. This is a one-way process — once migrated, devices can't go back to the Nest app.

Go to the Google Home app > Settings > Works with Google > Nest, and follow the migration flow. Some older Nest devices (like the original Nest Cam Indoor) may have limited functionality after migration.

Nest Devices Show "Offline"

After migration, some users report Nest devices showing as offline even though they're working. Usually a factory reset of the Nest device and re-adding it through the Google Home app fixes this, but it's annoying.

Third-Party "Works with Google" Devices

Third-party devices (TP-Link Kasa, Meross, Wemo, Philips Hue, etc.) connect to Google Home through account linking — you log into the manufacturer's app/account through Google Home, and Google Home pulls in your devices.

Account Linking Failures

If a third-party device isn't appearing in Google Home:

• First, set up the device in its native app. You must configure the device through the manufacturer's app (Kasa app for TP-Link, Meross app for Meross, etc.) before it can appear in Google Home. Google Home doesn't set up third-party devices directly — it imports them from the manufacturer's cloud.
• Check the linked service. In Google Home, go to Settings > Works with Google and find the manufacturer's service. If it shows as linked, try unlinking and relinking it. This forces a fresh device sync.
• Sync devices. After linking, say "Hey Google, sync my devices" to force Google Home to refresh its device list from linked services. You can also tap the "+" button in the Google Home app and select "Works with Google" to trigger a sync.

Devices Disappeared After App Update

I've seen this happen with Philips Hue and TP-Link Kasa devices after manufacturer app updates. The manufacturer's cloud connection to Google drops, and devices vanish from Google Home. The fix is usually to unlink and relink the service in Google Home settings. You'll need to reassign devices to rooms, but your routines should survive the relink.

Factory Resetting Devices as a Last Resort

If nothing else works, a factory reset of both the Google Home speaker/hub and the problem device usually resolves the issue. The order matters:

• Remove the problem device from the Google Home app (if it appears at all)
• Factory reset the device per the manufacturer's instructions
• Restart (not factory reset) your Google Home speaker or hub
• Wait two minutes for the speaker to fully boot
• Add the device fresh through the Google Home app

For Google Home speakers and hubs themselves, a factory reset is a 15-second press of the physical button on the back or bottom. After reset, you'll need to set up the speaker again through the app, but it will rejoin your home and rooms quickly.

Ongoing Reliability Tips

Once you've resolved the immediate issue, these practices help prevent future discovery and connectivity problems:

• Keep your router firmware updated. Router bugs are a common source of smart home connectivity issues.
• Assign static IPs or DHCP reservations to smart home devices. This prevents IP conflicts that can cause devices to drop offline.
• Don't overload your router. Consumer routers typically handle 30-50 connected devices well. Beyond that, consider a mesh system or a router designed for high device counts.
• Restart your router monthly. This clears network tables and often resolves lingering connectivity issues.
• Keep the Google Home app updated. Google frequently pushes fixes for device discovery bugs through app updates.

Smart home device discovery issues are frustrating, but they're almost always solvable. Work through this list methodically — start with networking, then move to app issues, then device-specific problems — and you'll almost certainly find the cause. And if you've gone through everything here and still can't get a device to connect, the issue is most likely on the manufacturer's side. Check their support forums and app store reviews to see if other users are reporting the same problem.