Hey! We’ll fix why your Chromecast is not discovering devices (or why your phone/laptop can’t discover Chromecast). Quick questions so we target the real cause:
• Which model: Chromecast (3rd gen), Chromecast Ultra, or Chromecast with Google TV?
• What are you casting from: Android, iPhone/iPad, or Chrome browser on Windows/Mac?
• What exactly happens: Cast icon missing, “No devices found”, “Cast device not found”, or Chromecast appears but fails to connect?
• Are your phone and Chromecast on the same Wi-Fi network (same SSID), and is it 2.4 GHz or 5 GHz? Any guest network, extender, or mesh Wi-Fi in between?
Share those details and we’ll walk through a complete Chromecast discovery fix step by step.

That combination (Chromecast shows Wi-Fi connected, but your phone says Chromecast not showing up) usually points to discovery traffic being blocked, not “internet is down.” Chromecast discovery relies on local network broadcasts like mDNS / multicast. A few common triggers:
• Phone is on a different SSID (even if the name looks similar) or a guest network.
• Router/mesh feature like AP isolation / client isolation is enabled, so devices can’t see each other.
• 2.4 GHz and 5 GHz are split or band-steering is moving the phone around (so it can’t reliably see the cast device).
• VPN/ad-blocking DNS/firewall app on the phone blocks local discovery.
• After a router update, multicast settings (sometimes called IGMP snooping / “multicast enhancement”) change and casting breaks.

We’ll fix this in a clean order: verify same network → remove isolation blocks → refresh Chromecast network → update/reboot → only then reset if needed.

Great — let’s do the fastest checks that fix a lot of “Chromecast not discovering devices” cases in under 5 minutes.

Step 1 — Turn off anything that blocks local discovery
1) Disable your VPN temporarily on the phone (VPNs often break local casting and make the cast icon disappear).
2) If you use any firewall/“internet security” app, pause it for a moment too.

Step 2 — Confirm the phone and Chromecast are truly on the same network
1) On the TV: Settings → Network & Internet → confirm the exact Wi-Fi name (SSID).
2) On your phone: connect to the exact same SSID (not Guest, not “IoT”, not an extender SSID).
3) If your mesh has multiple nodes, keep your phone in the same room as the Chromecast during testing so it attaches to the same node.

After that, open YouTube and check if the Cast icon reappears. If it’s still “No devices found,” we’ll adjust the mesh/router settings next (client isolation + multicast).

Perfect — now we treat it like a network discovery block. On mesh systems, this is super common when Chromecast is not showing up on Wi-Fi.

Step 3 — Check mesh settings that break Chromecast discovery
In your mesh app / router admin panel, look for these and adjust as follows:
• Guest network: keep Chromecast and phone off Guest (you already did). Also confirm Guest is not “isolating” the main network.
• AP isolation / Client isolation / Device isolation: must be OFF on the main network. This single switch can cause “Cast device not found.”
• Multicast / mDNS / Bonjour settings (names vary): if there’s an option like “Multicast enhancement”, “mDNS repeater”, or “IGMP proxy/snooping”, set it to allow multicast on the LAN. Some meshes hide this under “Advanced” or “LAN.”
• Parental controls or “Block local network” rules: temporarily disable for the phone and Chromecast.

Quick test: after saving changes, reboot the mesh (main node first), then power-cycle Chromecast (unplug 20 seconds). This often restores the Chromecast discovery instantly.

Nice find — that explains the “No devices found” problem. The inconsistency now usually comes from band steering / node roaming or a stale network state.

Step 4 — Make discovery stable (same band + clean network session)
1) If your mesh allows it, temporarily create separate SSIDs for testing (even just for 10 minutes):
  • Home_2G (2.4 GHz) and Home_5G (5 GHz).
2) Connect Chromecast and your phone to the same SSID (start with Home_5G if signal is strong; if walls are thick, test Home_2G). Mixed-band setups can cause Chromecast to “appear then vanish.”
3) Reboot order matters for casting: reboot mesh/router → wait until Wi-Fi is fully back → then power up Chromecast → then reconnect phone to Wi-Fi.

Step 5 — Prevent “drops” with a stable IP
In the router/mesh “connected devices” list, set a DHCP reservation for Chromecast (so it keeps the same local IP). This helps Google Home and apps keep finding it reliably, especially on some mesh systems.

Good — that means your Chromecast discovery is mostly fixed on the LAN, so now we tune the laptop side. When Chrome can’t find Chromecast, it’s usually one of these:

Step 6 — Fix “Chrome cast not finding devices”
1) Confirm the laptop is on the same SSID as Chromecast (Home_5G). If it’s on Guest or a different node/SSID, the cast list may be empty.
2) In Chrome, go to Settings → Privacy & security → ensure you’re not blocking local network discovery via aggressive extensions. Temporarily disable ad-blockers or “privacy” extensions that interfere with multicast/mDNS.
3) If you have a VPN on the laptop, turn it off (same reason as phone).
4) Restart Chrome completely (close all Chrome windows) and try Cast again.
5) On Windows: allow Chrome through the firewall for private networks. On macOS: check that firewall isn’t blocking incoming connections.

This is the classic “phone can cast but laptop can’t see Chromecast” scenario — once both are on the same SSID and no VPN/firewall blocks it, Chrome casting becomes consistent.

Totally fair — casting issues often pop up after router/mesh firmware changes. Here’s how to “future-proof” Chromecast not discovering devices so you don’t keep repeating the same fixes.

Prevent Chromecast discovery problems
• Keep Chromecast and your main devices on the same primary SSID (avoid Guest/IoT networks for Chromecast unless your router supports cross-network casting).
• Leave client isolation OFF on the main LAN. If you want isolation, use it only on Guest Wi-Fi.
• If your mesh supports it, keep a stable configuration for multicast/mDNS (some brands call it Bonjour/mDNS/Multicast). Casting is very sensitive to these settings.
• Avoid always-on VPN while casting; use split tunneling if available so local network traffic stays local.
• After any router firmware update, do a quick reboot order: router/mesh → Chromecast → phone/laptop. That refreshes discovery tables and prevents “cast device not found.”

If you ever see “No devices found” again, the fastest check is still: same SSID + no VPN + isolation OFF.

Great question — factory reset is the “last mile” fix, not step one.

When to factory reset Chromecast
Do it if:
• Chromecast connects to Wi-Fi but Google Home can’t find Chromecast for setup even after disabling VPN and turning off client isolation.
• The device keeps jumping between networks, or it’s stuck with a wrong/old Wi-Fi profile (common after changing SSID/password).
• You see persistent errors like “Cast device not found” across multiple phones on the same SSID and you’ve already rebooted router/mesh + Chromecast.

Before resetting: try forgetting the Wi-Fi on Chromecast (if available in settings), then reconnect to the correct SSID. If that fails, factory reset usually clears the corrupted network state and brings discovery back immediately.

Summary: when Chromecast is not discovering devices, it’s almost always (1) different SSID/Guest Wi-Fi, (2) VPN/firewall blocking local discovery, or (3) router/mesh settings like client isolation or blocked multicast/mDNS. Once your phone/laptop and Chromecast are on the same network with isolation OFF, casting becomes stable. If you’re stuck on a specific mesh brand setting, open the chat and an expert will guide you step by step.