Remote App Cannot Find Your TV? The Network Checklist That Fixes It
Every TV remote app — ours, the official brand apps, all of them — depends on the phone and the TV genuinely sharing a network and being allowed to see each other. When the device list comes up empty, the cause is almost always in this list. Work it top to bottom; each check takes seconds.
The checklist, in order of likelihood
1. iOS Local Network permission. The #1 cause by a wide margin. iOS asks exactly once, and a denied or dismissed prompt silently blanks every discovery scan afterward. Fix: Settings → Privacy & Security → Local Network → toggle the remote app on. If the toggle isn’t listed, delete and reinstall the app to re-trigger the prompt.
2. VPN on the phone. A VPN reroutes exactly the traffic discovery depends on. Toggle it off (including “private relay”-style services if discovery still fails) and rescan.
3. Actually the same network? Phones hop to cellular silently when Wi-Fi is weak, and houses with an extender or a second SSID make it easy to be one network apart. Confirm the phone’s Wi-Fi name matches the network the TV was set up on.
4. Guest network / AP isolation. Guest SSIDs isolate clients from each other by design — that’s their job. Hotel and dorm Wi-Fi nearly always isolates. Put phone and TV on the main network; in hotels, the hotspot trick (covered in the no-Wi-Fi article) sidesteps the hotel network entirely.
5. Mesh system isolation settings. Some mesh kits ship with “device isolation” or “IoT network” features enabled, which quietly wall the TV off. Check the mesh app’s security settings.
6. Multicast filtering on the router. Discovery rides on multicast (SSDP/mDNS), and some routers offer “multicast filtering” or “IGMP snooping” toggles that break it when set aggressively. If devices only appear after a router reboot, look here.
7. The TV is fully asleep. A TV in deep eco-standby has its network radio off and cannot be discovered — this one masquerades as a network problem but isn’t. Turn the TV on physically once, let the app find it, and then read why the app can turn it on afterward.
If the list is still empty
Wired-vs-wireless splits (TV on Ethernet placed on a different subnet by a second router) and corporate-style VLAN setups will also do it — rarer, but if you know your network has two routers chained together, the TV and phone need to hang off the same one. Once discovery works, pairing is the easy part: see the brand guides for Roku, Samsung, LG, Fire TV, Vizio, Android TV and the rest.
Get A Decent Remote on the App Store One iPhone remote for Roku, Samsung, LG, Sony, Fire TV, Apple TV, Vizio, Hisense, Philips, Panasonic, Toshiba, Chromecast and Android/Google TVFrequently asked questions
What is the single most common cause on iPhone?
The Local Network permission. iOS asks once, and if it was dismissed or denied, every remote app shows an empty list forever after. Check Settings → Privacy & Security → Local Network and make sure the app is toggled on.
Phone and TV are on the same Wi-Fi but still nothing — why?
Usually a VPN on the phone (which routes discovery traffic away from the local network) or client/AP isolation on the router, common on guest networks, hotel Wi-Fi, and some mesh systems' default settings.
Does it matter if the phone is on 5 GHz and the TV on 2.4 GHz?
Normally no — both bands are the same local network on home routers. It only matters if the router treats them as separate networks, which is rare outside of deliberately segmented setups.
The TV shows up but won't connect — is that the same problem?
No, that's progress. Discovery works; the failure is in pairing or standby. See the brand guide for your TV, or the standby article if the TV was off when you tried.