Hi! When an Android TV device isn’t appearing in the app, it usually comes down to one of a few “invisible” blockers: the phone and TV aren’t truly on the same local network, the wrong Google account/home is selected, or discovery traffic is being filtered (guest network, VPN, isolation, or certain router settings).

I’ll keep this practical and safe: we’ll identify which bucket you’re in first, without jumping straight to factory resets or random toggles.

Quick starting point: which app can’t see the TV — Google Home, Google TV (virtual remote), a casting app, or a manufacturer app? And what’s the TV/box brand (Sony, TCL, Philips, Xiaomi, Chromecast with Google TV, etc.)?

Thanks — that helps. When the TV works normally but Google Home can’t detect Android TV, the issue is often discovery (the app can’t “see” the TV on the local network) rather than the TV being broken.

Let me ask in a slightly unusual order because it narrows things fast:

1) Did this ever work before (it disappeared after an update/router change), or has it never shown up in Google Home?
2) Are you using the same Google account on your phone and on the TV (the account shown in TV settings)?
3) Network type: normal home Wi-Fi, mesh Wi-Fi, or do you have a guest network enabled?

New TV + mesh + multiple accounts is a very common combo for “not appearing.” Here’s the logic (so it feels less like random advice):

Discovery usually requires the phone and TV to be on the same local network segment and able to talk locally. Mesh systems can sometimes separate clients more than expected (especially if a device ends up on a node behaving like “guest” isolation).

Account/home mismatch happens when your phone is in one Google Home “Home,” but the TV is signed into a different Google account or not linked in the way Google Home expects yet.

Two safe checks to start with (no settings explosions):

• Check A (Wi-Fi reality check): On the TV, open Network settings and confirm the Wi-Fi name (SSID). On your phone, confirm you’re on that exact same SSID (not a similarly named one, not guest).
• Check B (Google account focus): In the Google Home app, tap your profile and confirm which Google account is active. Then, on the TV, confirm the primary signed-in Google account in system settings (not just YouTube).

If you tell me: is your phone Android or iPhone?

Perfect — iPhone adds one more frequent blocker: Local Network permission. If Google Home doesn’t have permission to access the local network, it can fail to discover devices even when Wi-Fi looks right.

Safe question: do you remember seeing an iOS prompt like “Allow Google Home to find and connect to devices on your local network?” If that was denied, the TV may never appear.

You can check without changing anything else: iPhone Settings → Privacy & Security → Local Network → make sure Google Home is allowed.

Another “quiet” iPhone thing: are you using a VPN or “security” filtering app? Even if the VPN says “not connected,” some profiles can still route traffic differently during discovery.

Turning Local Network on was a good move (and it’s understandable you denied it at first). If it still doesn’t show up, we’re likely dealing with one of these:

• Discovery traffic blocked on the network (guest isolation, “AP isolation,” or mesh settings that prevent devices from seeing each other).
• The TV isn’t advertising itself the way Google Home expects (for example, Chromecast built-in not available/disabled, or the TV isn’t fully connected).
• Home/app context mismatch (you’re adding to one “Home,” but the TV is effectively in another context).

Let’s do a simple symptom-based check: can you cast YouTube from your phone to the TV (the cast icon shows the TV name)? If casting works, discovery is probably fine and we look more at Google Home/account/home setup. If casting doesn’t work, we focus on network visibility first.

Inconsistent casting is a strong clue: it points away from “wrong button” and toward network discovery reliability (especially with mesh). Devices can appear/disappear if the phone switches nodes, if multicast discovery is filtered, or if the TV’s connection is unstable.

Two safe checks that often explain “Android TV not showing in app” on mesh networks:

1) Guest vs main network (again, but deeper): Some mesh systems have a feature that isolates clients even on the main network, or have “IoT network” modes. I’m not asking you to change those now — just: do you see any setting like “Client isolation,” “Block LAN,” “AP isolation,” “Private network,” or “mDNS / multicast filtering” in the mesh app?

2) Band/roaming behavior: If your mesh uses one SSID for 2.4/5 GHz, phones can roam aggressively. For testing (not forever), try standing near the main mesh router/node with the phone while the TV is on, then check if the TV appears more consistently. That helps separate “roaming discovery” from “account mismatch.”

Yes — and that’s a smart question. Incorrect time/date can cause weird sign-in and service behavior (not always, but enough that it’s worth checking). It’s a low-risk diagnostic step because you’re not “resetting” anything.

If your TV has “Use network-provided time” or “Automatic date & time,” it’s usually best to keep it on. If it’s off and the clock is wrong, it can make Google services behave inconsistently.

About the IoT network: if the TV or phone is accidentally on an isolated network, the phone may not see the TV in Google Home or casting lists. Some people use IoT networks to keep devices separate (which is fine), but discovery needs both devices on the same segment during setup.

One more quick “risk-first” check: are you trying to add the TV while it’s connected to Wi-Fi, or is it sometimes on Ethernet? Mixing Ethernet/Wi-Fi is usually fine, but on some networks it exposes segmentation problems.

I get why you want “manual add,” but for Android TV / Chromecast built-in, Google Home usually depends on discovery rather than typing in an IP address. So if discovery is flaky, manual add often isn’t available in the way people expect.

The good news is your test (standing near the main node) suggests this is more about discovery reliability than “wrong account.” That points to mesh roaming, multicast filtering, or an isolation feature that affects device visibility intermittently.

At this stage, the safest next step is not “wipe the TV,” it’s to capture specifics so the next change is targeted:

• Note exactly where it fails: does Google Home never show the TV, or does it appear then fail to assign to a room?
• Note whether the TV name appears in casting consistently when the phone is near the main node (this tells us if local discovery is stable).
• Confirm you’re in the correct Home in Google Home (some people have “Home” and “Home 2,” and devices won’t appear where you expect).

If you can tell me the mesh brand (Eero, Deco, Orbi, Google/Nest Wi-Fi, etc.), I can help you identify which discovery-related setting is most likely involved — without telling you to flip a bunch of advanced switches blindly.