WiFi Mesh technician helping fix casting problems from phone to TV

Steve H.

Expert ★★★★★ 27,853 satisfied customers

Specialities: Mesh Wi-Fi systems, Chromecast & Google TV, AirPlay, smart TVs, router & bridge mode, DHCP/subnets, AP/client isolation

WiFi Mesh not casting from phone — Chromecast, AirPlay, smart TV and guest network issues

Technician avatar Technician
Hey! We’ll track down why your WiFi mesh won’t cast from your phone and get the Cast/AirPlay icon back. A few quick details so we don’t guess:
• Brand/model of your mesh Wi-Fi system (Deco, Orbi, Eero, Google Nest WiFi, ASUS, etc.)?
• What are you casting to — Chromecast / Google TV, built-in TV casting (Samsung, LG, Vizio, Roku TV), Fire TV, or Apple TV / AirPlay?
• Is the phone Android or iPhone, and are you using the Google Home app, a streaming app (YouTube/Netflix), or screen mirroring?
• Symptoms: cast icon missing, TV or Chromecast not showing up, “something went wrong” when you try to cast, or casting only works when you’re next to the main router?
The more we know about the mesh, phone, and TV, the easier it is to fix casting not working on a WiFi mesh network instead of randomly rebooting everything.
Customer
I recently switched to a WiFi mesh system (TP-Link Deco) and since then my phone won’t cast properly. The Chromecast and built-in TV cast barely show up. Sometimes the cast icon disappears completely, other times it connects and then drops after a few seconds. Streaming otherwise works fine on the TV and the phone.
Technician avatar Technician
Got it — classic case of casting breaking after installing a mesh WiFi.
When you add a WiFi mesh, a few things usually change:
• Phone and TV can end up on different bands, nodes or subnets (2.4/5 GHz, main router vs mesh, double NAT). If they’re not on the same network, casting fails or the device never appears.
• Mesh systems sometimes enable AP isolation / client isolation / guest network that blocks devices from talking to each other — exactly what Chromecast and AirPlay need.
• Multicast/UPnP/IGMP settings change, so discovery traffic that makes devices visible (“cast targets”) is filtered or stuck on one node.

We’ll:
1) Make sure your phone and cast device are really on the same WiFi mesh network and subnet.
2) Turn off any guest/client isolation and let multicast & UPnP through the mesh.
3) Re-sync the Google Home / AirPlay setup so casting works reliably again.
If one TV or Chromecast still won’t show up, we’ll then look at that device’s WiFi and power settings.
Customer
The ISP modem/router is still there but WiFi is turned off and the Deco mesh is in router mode. My phone and TV both show the same SSID. Still, half the time I don’t see the cast icon, especially when the phone is on 5 GHz and the TV is on 2.4 GHz or connected to another mesh node.
Technician avatar Technician
Good detail — this is where most WiFi mesh casting issues come from.
Step 1 — Confirm one router and one subnet
• In the Deco (or other mesh) app, check that the mesh is the only router doing DHCP and that the ISP modem is in bridge mode or has its DHCP disabled. If you have “double NAT”, phones and cast devices can land on different internal networks, so Chromecast and AirPlay don’t see each other.
• In the mesh app, look at the IP addresses: make sure both the phone and TV/Chromecast are in the same range (for example 192.168.68.x).

Step 2 — Turn off client isolation/guest mode
• In WiFi settings, verify that your main SSID is not a guest network and that “AP isolation” or “client isolation” is disabled. Those features deliberately stop devices from communicating, which breaks casting.
• If you have a separate guest SSID, make sure the phone and cast device are both on the main network, not split between main and guest.

Once we know everything is on one subnet with no isolation, we’ll fine-tune band/mesh behavior so casting works even when the phone roams between nodes.
Customer
Guest network is off and both devices are on the main SSID. Double NAT might be happening though — the ISP router still shows its own 192.168.0.x network. Also, sometimes when I move to another room, the Cast icon disappears on my phone until I toggle WiFi off and on.
Technician avatar Technician
Yep, that combo (mesh + double NAT + roaming) is a textbook reason why a WiFi mesh won’t cast from a phone reliably.
Step 3 — Put the modem in bridge mode or the mesh in access point mode
1) Log into the ISP modem/router and either set it to bridge/”modem only” mode or turn off its DHCP so the mesh hands out the only IP addresses.
2) Alternatively, switch the mesh to Access Point (AP) mode so your ISP router handles routing, but all WiFi still comes from the mesh. Either way, you want a single layer of NAT, not two.
3) After changing modes, reboot modem, mesh, TV, Chromecast and phone.

Step 4 — Re-discover devices in Google Home / AirPlay
• On Android, open the Google Home app and let it rediscover the Chromecast/TV on the new network; on iPhone, check that AirPlay sees the TV/Apple TV.
• Test from the room where casting fails most often. If the Cast icon still disappears when you roam to another mesh node, we’ll tweak mesh “fast roaming” and multicast options next so casting survives node changes.
Customer
After setting the ISP router to bridge mode, everything is on the mesh subnet now. Casting is better, but one Chromecast with Google TV still doesn’t show up consistently. It’s on a satellite node in the living room. Sometimes YouTube sees it, sometimes it just says “no devices found on this network”.
Technician avatar Technician
When casting only fails on one Chromecast or one mesh node, it’s usually multicast/mesh settings or signal quality on that node.
Step 5 — Check signal and multicast settings for the “problem node”
• In the mesh app, check the link between the main router and that satellite node. If it’s weak, move the node closer or add another node so the Chromecast has a solid backhaul.
• Look for advanced options like IGMP snooping, multicast enhancement, mDNS/Bonjour or “optimize for streaming”. For casting, you usually want multicast allowed between nodes, not blocked.
• If there’s an option called “client steering” or “fast roaming”, try toggling it — some devices behave better with it off, others with it on.

Step 6 — Reboot and re-add just that Chromecast
• Power the Chromecast fully off (unplug for 30 seconds), then back on.
• In Google Home, remove the old “ghost” device entry if it exists, then set the Chromecast up again on the main SSID.
• Test casting from multiple apps. If YouTube finds it but Netflix or Spotify don’t, clearing app cache or reinstalling the app on the phone often fixes that part.
Customer
That Chromecast is better now. But I also use AirPlay from my iPhone to a smart TV, and that still fails randomly. The TV shows up, but when I start mirroring it just hangs or disconnects, especially when I’m connected to a different mesh node than the TV.
Technician avatar Technician
AirPlay is picky about latency, multicast and being truly on the same WiFi network, so mesh behavior matters a lot.
Try this:
• Make sure Bluetooth is enabled on the iPhone — AirPlay often uses it for discovery along with WiFi.
• In the mesh app, confirm that the TV isn’t accidentally connected to a guest SSID while the phone is on the main one.
• If your mesh has separate 2.4 and 5 GHz SSIDs, connect both iPhone and TV to the same SSID. If it’s a single SSID with band steering, that’s fine as long as there isn’t client isolation between bands.
• Power-cycle the TV and iPhone, then test shorter AirPlay sessions (start with mirroring for 1–2 minutes). If AirPlay only fails when you move around the house, we may want to reduce roaming aggressiveness for Apple devices or lock the TV to a closer node if the mesh allows it.
After a big mesh firmware update, re-pairing the TV in the Home/Apple TV settings can also help stabilise AirPlay over mesh WiFi.
Customer
Is there anything I can change now so I don’t have to fight this every time I upgrade the mesh, move nodes, or change SSIDs? I just want casting from phone to TV over WiFi mesh to be reliable.
Technician avatar Technician
For sure. Once you know the rules, it’s easy to avoid “why won’t my WiFi mesh cast from my phone?” every time there’s a tweak.
Preventive setup for casting on mesh WiFi
• Keep one main SSID for phones, TVs, Chromecasts, consoles and speakers, and don’t rename it or change the password unless you have to.
• Avoid running two routers (no long-term double NAT). Either the ISP box is just a modem, or the mesh runs in AP mode.
• Make sure AP/client isolation is off on the main network so devices can see each other for casting and local streaming.
• Enable features like UPnP, mDNS/Bonjour and multicast if your mesh offers controls for them — casting protocols rely on these.
• After mesh firmware updates, quickly open Google Home and your main streaming apps to let them rediscover the TVs/Chromecasts on the network.
These steps make a mesh WiFi casting setup a lot less fragile and save you from random “no devices found” messages.
Customer
What if a particular app won’t cast, but others on the same phone do? For example, YouTube casts fine but a sports streaming app says it can’t find any devices on this WiFi mesh.
Technician avatar Technician
Great question — that’s the “worst-case” version of a WiFi mesh casting problem, but there are still options:
• First, check the app’s own settings: some require you to enable casting or use an in-app device picker instead of the system Cast icon.
• Sign out and back in, or reinstall that specific app on the phone. A bad update can break how it talks to Google Play Services or AirPlay.
• Make sure the app isn’t restricted by a VPN, ad-blocker, or private DNS on the phone — these can block the local discovery traffic required for casting on a mesh network.
• Try casting the same app from another phone or tablet on the same mesh. If it only fails on one device, we focus on that phone; if it fails on every device, we revisit mesh firewall/multicast rules.
Worst case, we can still use AirPlay or Chromecast from another supported app (YouTube, Chrome tab casting, etc.) while we track down why that one app is stubborn. We can go through your exact app and mesh brand live in chat if you’d like.
Customer
After fixing the double NAT, turning off client isolation and tweaking multicast, everything’s stable. My WiFi mesh now casts from phone to all TVs without the icon disappearing. Even AirPlay is working again. Thanks a lot!
Technician avatar Technician
Summary: when a WiFi mesh won’t cast from your phone, start by removing double NAT, keeping everything on one main SSID/subnet, and disabling client/AP isolation. Then make sure multicast, UPnP and discovery traffic can flow between mesh nodes, and re-add any stubborn Chromecast, smart TV or AirPlay device. If one app or device still won’t cast, a reset or app reinstall usually finishes the job. Not sure which setting your mesh uses for this? Open the chat and an expert will walk through it step by step.

Quick answer: the accepted fix

Accepted fix when WiFi Mesh won’t cast from a phone: remove double NAT by using a single router/subnet, connect both phone and TV/Chromecast to the same main SSID, and turn off client/AP isolation on that network. Enable multicast/UPnP if your mesh supports it, reboot all mesh nodes and cast devices, then re-add the Chromecast or TV in Google Home or AirPlay and test casting from several apps.

Why WiFi Mesh can suddenly stop casting from your phone

Most WiFi mesh casting problems come down to three things: multiple routers creating separate subnets, isolation features blocking device-to-device traffic, or multicast/UPnP being filtered. When you install or update a mesh system, it can introduce double NAT, move phones and TVs onto different internal networks, or enable guest/client isolation. Casting protocols like Chromecast, Google Cast and AirPlay rely on discovery traffic (mDNS/DNS-SD, SSDP) and multicast packets. If those are blocked between mesh nodes, your TV, Chromecast or smart speaker either never appears or drops as soon as you start casting.

How to test if casting over WiFi Mesh is really fixed

After making changes, leave your phone and TVs/Chromecasts connected for a while and test casting from multiple apps (YouTube, Netflix, Spotify, Chrome tab cast, AirPlay). Move around the house so your phone roams between mesh nodes and confirm the Cast icon doesn’t disappear. If casting only breaks when the phone is on a specific satellite node, revisit your mesh backhaul quality and multicast options. If every device on the mesh can see and control each other consistently, your WiFi mesh casting setup is in good shape.

WiFi Mesh won’t cast from phone — quick troubleshooting tips

Most cases are fixed by putting everything on one subnet, disabling isolation, and re-adding cast devices.

Quick path: make sure your modem is in bridge mode or your mesh is in AP mode so there’s only one router doing NAT. Keep one main SSID for phones and TVs, turn off AP/client isolation on that network, and allow multicast/UPnP if your mesh offers those settings. Then reboot the mesh, TV, Apple TV or Chromecast, and set them up again in Google Home or AirPlay. If the Cast/AirPlay icon still goes missing, resetting just the stubborn device or app usually restores stable casting on your mesh WiFi.

Disclaimer: This information is AI-generated and intended for general guidance only. For advice specific to your WiFi mesh brand, router mode, and casting devices, please consult a verified expert on Whizz-Tech before making decisions.

Understand what these prompts mean

Getting Started Is Easy

Ask for help, 24/7

Members enjoy round-the-clock access to 12,000+ verified Experts, including mesh Wi-Fi, smart TV, streaming, and home networking specialists.

Expert will respond in minutes

We match you with an Expert who specialises in WiFi mesh casting issues, Chromecast, AirPlay and smart TV problems. Talk, text, or chat — whichever you prefer.

Save time & money

No scheduling hassles or on-site technician visits. Fixing WiFi mesh that won’t cast from your phone online can save you time and money.

FAQ

Why did casting stop working right after I installed a WiFi mesh?

Installing a mesh often adds a second router, creating double NAT or a second subnet. Your phone and TV/Chromecast may no longer be on the same internal network. Some meshes also enable guest or client isolation by default, blocking the device-to-device traffic and multicast that Chromecast and AirPlay rely on, so the Cast icon disappears or devices never show up.

Do my phone and TV need to be on the same WiFi for casting over a mesh?

Yes. For Chromecast, Google Cast and AirPlay, your phone and the TV/streaming device must be on the same main WiFi network and subnet. Being on different bands (2.4 GHz vs 5 GHz) is usually fine on a mesh, but being on different SSIDs, guest networks, VLANs or behind separate routers breaks discovery and casting.

How do I stop my WiFi mesh from blocking casting between devices?

Use only one router (put the modem in bridge mode or the mesh in AP mode), connect all phones and TVs to the same main SSID, and make sure AP/client isolation is turned off. If your mesh has options for UPnP, multicast, mDNS or IGMP snooping, configure them to allow discovery traffic between nodes so casting works in every room.

When should I reset my Chromecast or TV when casting fails on mesh WiFi?

If you’ve fixed double NAT and isolation but a particular Chromecast or smart TV still won’t appear, or casting drops immediately, it’s time to reset. Remove it from Google Home or AirPlay, perform a factory reset following the brand’s instructions, then add it again on the main SSID of your WiFi mesh network.

Sources

Matt Verified Icon
Matt ● replies in < 1 min
Technician Expert
⭐⭐⭐⭐⭐ Trusted by 27,000+ customers
Avatar
Alex · Expert's Assistant
5 Tech Support Specialists are online right now.