You tap the cast button in YouTube or another app on your phone. The list of cast targets appears. You select your Nest Hub. The cast button shows the connecting animation. Nothing happens on the Nest Hub. The cast eventually times out. You try again, same result. Casting that worked yesterday no longer works today.
How casting works
Cast uses local network discovery (mDNS) to find devices. The phone app sees the cast targets, sends a request to the chosen target, and the target streams the content.
Failure points:
- Phone cannot discover the cast target (mDNS issue)
- Phone discovers the target but cannot reach it (firewall, subnet)
- Target receives the request but cannot stream (codec issue, network)
Verify both devices are on the same network
The most common cause: phone on cellular or guest Wi-Fi, target on home Wi-Fi.
Verify both are on the same SSID. If you have an IoT VLAN with the target on it and your phone on main, cast may not work across the VLAN boundary without explicit configuration.
Restart the cast target
Cast services on smart displays sometimes hang. Unplug the display for 30 seconds, plug back in. After boot, retry casting.
Restart your router
If multiple cast targets are missing or unreachable, the router’s mDNS or multicast may be broken. Restart the router.
The cast app version
If you updated the source app (YouTube, Spotify, Netflix) and casting stopped, the app version may have a regression. Check for further updates.
The target firmware
Cast targets need updated firmware to support new cast features. Check for firmware updates on the target.
Most cast targets update automatically. Verify in their settings.
The Wi-Fi band
Cast targets and casting clients should ideally be on the same band. If your phone is on 5 GHz and the cast target is on 2.4 GHz only, performance is reduced and discovery can be unreliable in some routers.
The Google Home app linking
For Cast to work, the target must be properly linked in the Google Home app. If the link is broken, the device shows but cannot accept casts.
Open Google Home app, verify the device is listed and shows as online. Tap to interact; if it responds, the link is healthy.
The Cast permissions
Some apps need explicit permission to cast. iOS apps need local network access permission (Settings, Privacy & Security, Local Network).
Android apps usually have cast permission by default.
The voice command alternative
If you cannot tap-to-cast, try voice casting: “Hey Google, play [content] on [display name]”. Voice casting goes through Google’s cloud rather than local discovery, bypassing some discovery issues.
If voice casting works but tap-to-cast does not, you have a local network discovery issue.
The Bluetooth interference
Some Cast targets occasionally enter a Bluetooth pairing mode that interferes with Cast service. Force the device out of pairing mode by power-cycling.
The mesh roaming issue
If your phone roams to a different mesh node from the cast target, cast may briefly drop. Stay on the same mesh node for testing.
The cast group issue
If your cast target is part of a group and the group is in a weird state, casts to the individual device may fail. Disband the group, retry the individual cast.
Recreate the group if you still want it.
The IPv6 issue
Some Cast implementations prefer IPv6 for discovery. If your network has partial IPv6 support, Cast may discover devices but fail to connect.
Disable IPv6 on your router temporarily. If cast works after that, IPv6 was the cause.
The content licensing issue
Some content (live TV, specific streaming services) does not support casting. The cast button may not appear, or appears but fails. This is by design.
For licensed content, use the manufacturer’s app on the cast target directly rather than casting from your phone.
The cast service restart
On Android, the Google Play Services Cast component sometimes hangs. Restart the phone to refresh.
On iOS, the equivalent is to force-quit Settings and the app you are casting from.
The cast target’s storage
If the cast target’s storage is full (often a Chromecast), it cannot buffer the stream. Casting fails or stutters.
Storage issues are typically only on streaming-focused devices with limited memory. Restart usually clears.
The two-step cast
For some apps, the cast involves two steps: the phone opens the app on the display, then the display loads the content. If the first step succeeds but the second fails, the display shows a blank loaded app.
Manually navigate on the display to the desired content if the cast handoff partially failed.
The router QoS
If QoS in your router prioritizes other traffic over cast, cast streams can drop. Set QoS to give cast traffic high priority, or disable QoS for testing.
The casting failure that traces to nothing obvious
If everything in this guide checks out and casting still fails intermittently, the culprit is often the mesh node your phone is on at the moment of the cast. Phones roam between mesh nodes invisibly. When the cast request goes out from a node that the cast target cannot see well, the request quietly fails. Move physically next to the cast target and try again. If it works, your mesh roaming is the issue and you need to either lock your phone to a single node or improve mesh node placement so every common location has at least one strong-signal node within reach.
The other invisible failure is sleep mode on the cast target. Newer smart displays sleep their display radio when not in use to save power. The Cast service should wake them, but the wake handshake sometimes takes longer than the cast app is willing to wait. A brief touch interaction on the display before triggering the cast can warm it up and prevent the timeout.
The cast-via-voice fallback
When tap-to-cast fails, voice casting often works because it routes through the cloud rather than local discovery. “Hey Google, play X on display Y” bypasses the network issue that broke tap-to-cast. Use this while you diagnose the underlying discovery problem.
It is not a permanent fix but it confirms whether the issue is local discovery (likely) versus the cast target itself (less likely). The wider topic of cross-ecosystem voice is in our cross-ecosystem voice guide.
