If an app cannot find your Chromecast, Nest or Sonos speakers, your phone and the speakers almost certainly cannot see each other on the network, even though both are online. The usual causes are a guest network, a router setting called AP isolation or client isolation, a mesh system that created a second network, a separate VLAN for smart home devices, or the app's Local Network permission being off. Put the phone and speakers on the same main Wi-Fi, turn isolation off, and allow Local Network access.
Why "same Wi-Fi" matters more than "connected to Wi-Fi"
When an app looks for speakers, it does not ask the internet. It shouts a question onto your home network and waits for the speakers to answer. Chromecast and Nest speakers answer through mDNS (also called Bonjour, the same system printers use), advertising themselves as _googlecast._tcp. Sonos uses SSDP and UPnP, a similar "who's out there?" system.
Think of it like calling out in a house. If your phone and the speaker are in the same room, the speaker hears the question and answers. If the router has put them in separate rooms with the door shut, the speaker never hears it, and the app says it found nothing. Both devices still have internet, which is why this is so confusing.
So the fix is never "restart the internet". It is getting the phone and the speakers into the same room again.
Check these first (five minutes)
- Is the phone on the home Wi-Fi, not cellular? Look at the Wi-Fi name in Settings, not just the icon.
- Is it the same Wi-Fi name as the speakers? Many homes have two: "Smith Home" and "Smith Guest". Check which one the speakers joined in the Google Home or Sonos app.
- Is Local Network access on for the app? On iPhone or iPad: Settings > Privacy & Security > Local Network. On Mac: System Settings > Privacy & Security > Local Network. Google's casting help says this switch is required for casting apps on iPhone.
- Is a VPN running? Sonos lists VPNs that block local network access as unsupported. Turn the VPN off and try again.
- Restart the app. After you change a permission, close the app fully and reopen it.
If that did not do it, the cause is in the router. The next sections cover the three big ones.
Guest networks and client isolation
Guest networks are designed to let visitors reach the internet without seeing anything else in your house. That is exactly what breaks speaker discovery. Sonos says plainly that guest networks are not compatible with Sonos, and Google says you need to disable AP isolation, which routers may also label "Client Isolation" or "Guest Mode".
Isolation is not always on a guest network. Some routers apply it to the main network too, especially when they have a "security" or "privacy" mode switched on.
- Move your phone and every speaker to the main Wi-Fi network, not the guest one.
- Open your router's settings (usually its own app, or a web page printed on the router).
- Look for "AP isolation", "Client isolation", "Wireless isolation" or "Allow guests to see each other".
- Turn isolation off for the network your speakers use. Google's advice is to check your router's manual for the exact menu.
- Reopen the app and let it search again.
If you want to keep a guest network for visitors, keep it. Just do not put the speakers or the family's phones on it.
Mesh Wi-Fi and the hidden second network
A single mesh system (several units that create one Wi-Fi name) is usually fine for speakers. The trouble starts when the mesh is plugged in behind the router your internet provider gave you, and both of them act as routers. Now you have two networks with two Wi-Fi names, or worse, two networks that look like one.
A phone on the provider's Wi-Fi and a speaker on the mesh Wi-Fi are in separate rooms with the door shut. Sonos's recommendation for this setup is to put the provider's gateway in bridge mode, so its own Wi-Fi and routing turn off and the mesh does all the work.
Two more mesh details worth knowing:
- 2.4 GHz and 5 GHz. Google says most routers let devices on the two bands talk to each other (this is called bridging), but if they do not, you may need to change router settings or use the 2.4 GHz band for setup.
- Extenders. An old plug-in extender often creates its own Wi-Fi name like "Home_EXT". Speakers on the extender and a phone on the main network can lose sight of each other. Use one network name for the whole house if your equipment allows it.
VLANs and separate smart home networks
A VLAN is a way of splitting one physical network into several virtual ones. People who care about security often put smart devices on their own "IoT" VLAN so a hacked light bulb cannot reach a laptop. That is a reasonable idea, and it blocks speaker discovery by design, because mDNS and SSDP messages do not cross from one VLAN to another on their own.
You have two choices:
| Approach | What you do | Good for |
|---|---|---|
| Put speakers back on the main network | Move the speakers to the same network as your phones | Most homes; nothing to maintain |
| Keep the VLAN and forward discovery | Turn on an mDNS reflector (sometimes called mDNS repeater or Bonjour gateway) for Chromecast, and SSDP or UPnP forwarding for Sonos, plus firewall rules that let the app reach the speakers | People already running a prosumer router or firewall who are comfortable with its settings |
Even with forwarding, Sonos lists "same subnet" as a requirement for the Sonos app and its speakers, so a split network with Sonos is unsupported territory. If you are not sure what a VLAN is, you almost certainly do not have one, and the guest network section above is the one that applies to you.
What each part of your setup needs
| Setting | Chromecast and Nest | Sonos |
|---|---|---|
| Discovery method | mDNS / Bonjour (_googlecast._tcp) | SSDP / UPnP |
| Guest network | Blocked by isolation | Not supported, per Sonos |
| AP or client isolation | Must be off, per Google | Must be off |
| Separate VLAN | Needs an mDNS reflector | Same subnet required, per Sonos |
| VPN on the phone or Mac | Turn off to test | Unsupported if it blocks local access |
Why this affects every speaker app, not just one
These rules apply to the Google Home app, the Sonos app, and any third-party app that plays to your speakers. Holler, for example, sends your voice straight from your device to the speakers over your own Wi-Fi, with no servers in the middle. That is good for privacy, and it also means Holler can only reach speakers it can see on the local network. If the Google Home app can find a speaker but another app cannot, compare the two apps' Local Network permission first.
Once your speakers show up, you can put them to work. How to use your Nest and Chromecast speakers as a home intercom covers the options for Google speakers, and How to make voice announcements on Sonos speakers from a Mac covers Sonos. If you are still stuck with Holler, the Support page has the contact details, and the FAQ covers the common questions.