Why can't my phone find my TV? Fixing Wi-Fi remote discovery and pairing problems

You open a remote app, tap Add device, and the list stays empty. The TV is on, the Wi-Fi is working, and yet nothing shows up. This is by far the most common problem with any Wi-Fi remote, and in most cases it has nothing to do with the TV being incompatible.

A phone remote works in two steps: it discovers the TV on the local network, then it pairs with it. Both steps can fail quietly. This guide goes through the causes in the order they usually turn out to be the culprit, from the network to the TV itself, and shows what to do in Remotly at each point.

Start with the network, not the TV

Discovery only works when the phone and the TV are on the same local network. That sounds obvious, but it fails more often than people expect: a phone that silently dropped to cellular, a TV wired to the router while the phone hangs off a Wi-Fi extender with its own subnet, or two Wi-Fi names in the house that are not actually bridged.

Guest networks are the classic trap. Most routers isolate guest clients from each other, so a phone on the guest network can reach the internet but never the TV. The same thing happens with client isolation (sometimes called AP isolation) on the main network. Turn it off for the devices you want to control, or move the phone to the main network.

• Check that Wi-Fi is on and that the phone shows the same network name as the TV's network settings.
• If the TV uses Ethernet, make sure the phone's Wi-Fi comes from the same router, not from a separate access point with its own address range.
• Open the router's settings and look for guest network, client isolation or AP isolation. Disable it for the network your TV is on.
• On iPhone, confirm that Remotly is allowed to use the local network under Settings → Privacy & Security → Local Network. Without this permission iOS blocks discovery entirely, and the list stays empty with no error message.

Make the TV easy to find

A TV in standby, in a power-saving mode or still booting may not answer discovery requests. Bring it to its home screen before you search. Some TVs also have a setting that allows mobile remotes or network control; if yours has one, enable it.

Remotly never searches in the background. Discovery runs only while you are on the Add device screen and only when you ask for it, so if you left the screen and came back, start the search again rather than waiting for the TV to appear on its own.

Add the TV by its IP address

When discovery is blocked but the two devices can still reach each other, a direct address works. Address-based setup also helps on networks where multicast traffic is filtered, which is common in apartment buildings, offices and on mesh systems with strict settings. If the TV does not respond to its address either, the phone cannot reach it at all, and the problem is back on the network side.

1. On the TV, open the network settings and note the IP address (something like 192.168.1.42).
2. In Remotly, open My devices, tap Add device and choose Television.
3. Tap I can't find my TV, then Advanced connection, and enter the address.
4. Follow the TV's pairing prompt as usual. Shelly devices and Hue bridges have a manual address field on their own setup screens too.

When the pairing code does not appear

Finding the TV is half the job. Pairing is the TV's way of making sure the remote belongs to you, and it looks different from one platform to another. Android TV and Google TV devices running Android TV Remote Service v2 show a six-character code; other compatible TVs show a code or ask you to confirm on screen; and some TVs want you to press a button on the existing remote instead of showing any code at all.

• Make sure you selected the right TV in the list. Two TVs with similar names are easy to mix up.
• Bring the TV to its home screen and try again. A full-screen app can hide the pairing prompt.
• Look for a confirmation dialog on the TV that expects the original remote rather than a code.
• Restart the TV if nothing appears after a second attempt; pairing services on TVs occasionally stall.
• Once paired, Remotly remembers the TV. Saved TVs reconnect from their card, and a TV that allows it skips the code next time.

Still nothing? Check compatibility

A TV that is found is not always a TV that can be controlled. Finding a Chromecast or DLNA device on the network does not mean the TV exposes a remote control service. Remotly connects through the control service a device actually exposes, not by brand name: compatible TVs and Android TV or Google TV devices running Android TV Remote Service v2 connect directly, while older Android remote services are detected and shown as unsupported. Samsung Tizen and Roku have no supported direct connection in this release.

If your TV is one of those but your home runs Home Assistant, there is a second route: a TV the server exposes as a media player can be added through the Home Assistant integration, with the controls the server publishes. And if you write to support, include the TV model, its software version and the message Remotly showed, but never the pairing code.