LG ThinQ Won’t Connect to Your TV: Pairing, Wi-Fi, Account and Local-Network Fixes

The short answer

If LG ThinQ cannot find or pair with your TV, start with the phone and TV on the same home network, the TV fully awake, and mobile data temporarily off. Then check that ThinQ has local-network access on iPhone or iPad, or the nearby-device and location permissions requested during Android setup. Remove guest-network isolation and VPNs from the test. Only after discovery works should you troubleshoot the LG account or standby wake-up.

That order matters. “TV not found,” “pairing code failed,” “TV is offline,” and “the remote works except for power-on” look similar in an app, but they occur at different stages.

Identify the stage that is failing

What you see	Most likely stage	First check
The TV never appears in Add Device	Local discovery	Same network, phone permission, no guest isolation
The TV appears but no code arrives	TV registration	TV awake, correct device selected, restart registration
The code appears but pairing fails	Registration/account	Code expiry, ThinQ sign-in, prior registration
The TV was paired but now shows offline	Network reachability	TV network status, router, changed SSID
Control works while on but not from standby	Wake configuration	TV On With Mobile, supported webOS/model

Do not factory-reset the TV merely because the first row fails. A denied local-network permission or isolated guest Wi-Fi cannot be fixed from the TV’s reset menu.

1. Prove that both devices are on the same network

LG’s registration guide tells you to connect the phone to the same Wi-Fi network as the TV and to disable cellular data during setup. Check the network name on both devices instead of relying on the Wi-Fi icon. A router may broadcast a main network, a guest network and one or more mesh names that look nearly identical.

The important property is not simply 2.4 GHz versus 5 GHz. The phone and TV must be able to reach one another on the local network. Some routers bridge their radio bands normally; a guest network often blocks device-to-device traffic by design. For a clean test:

Put the TV and phone on the router’s normal home SSID.

Turn off the phone’s VPN for the test.

Disable cellular data temporarily, as LG recommends for registration.

Keep the phone near the TV and router until setup completes.

Confirm the TV itself reports an active network connection.

If other local-control apps also cannot see the TV, stop retrying the ThinQ login. The fault is probably below the account layer. Continue with the broader LG OLED connection checklist.

2. Restore the phone permission ThinQ needs

On iOS and iPadOS 14 or later, an app must ask before browsing devices on the local network. If Local Network was denied when ThinQ first opened, internet-based parts of the app may still load while TV discovery fails.

Open Settings → Privacy & Security → Local Network and allow LG ThinQ. Apple lets you revoke the same permission later. Bluetooth and Location are separate permissions; grant only those ThinQ explains as necessary for the registration method you are using.

On Android, the exact labels depend on Android version and manufacturer. Review ThinQ under Settings → Apps → LG ThinQ → Permissions. During device registration, the app may request nearby-device/Bluetooth and location-related access used to discover or configure Wi-Fi devices. If you previously chose “Don’t allow,” restore the requested permission and reopen ThinQ.

Permissions are an operating-system boundary. Reinstalling the TV firmware does not change a permission denied on the phone.

3. Register the TV again without changing everything at once

With the TV on and displaying a normal screen, open ThinQ, sign in, choose Add a Device, select TV, and select the detected set. LG’s current guide shows a PIN on the TV that must be entered in the app. Treat that code as short-lived: if the flow was interrupted, cancel and start a fresh registration rather than repeatedly entering an old code.

If several LG TVs appear, compare the model or room name carefully. Do not approve a pairing prompt on a different set. If the TV is already listed in ThinQ but permanently offline, remove only that stale device entry and add it again before considering a TV reset.

Account linking is a later step. The same-network discovery and PIN exchange must work first. Voice-assistant linking can require additional account agreements, but it is not the right place to diagnose a TV that never appears in the device list.

4. Separate “paired” from “available after standby”

A successful ThinQ registration proves control while the TV is awake. Power-on from standby is another capability. LG documents TV On With Mobile for webOS 3.5 and later; older versions may support power-off without power-on. On webOS 6 examples, LG places the options under Devices/External Devices, with Wi-Fi and—on supported Android paths—Bluetooth wake choices. Menu names and availability vary by model and region.

If the remote screen works after you manually turn on the TV but the set appears offline after shutdown, read Wake-on-LAN, Quick Start+ and Simplink. Do not undo a healthy ThinQ pairing to solve only standby wake.

5. Use a controlled restart, not a ritual

If the network and permissions are correct but discovery remains stuck:

Close ThinQ completely.

Restart the phone.

Turn the TV off, disconnect its power briefly, then reconnect it.

Restart the router only if other local devices also show reachability trouble.

Retry registration once with the simplified network described above.

This sequence clears transient state while preserving picture settings and accounts. A factory reset removes far more state and should be a last resort after LG model-specific support has been checked.

Model, firmware and router boundaries

LG says ThinQ TV registration is for supported products and notes that some models remain exceptions even within broad release-year guidance. Menu paths also move between webOS generations. Use the full model suffix and current software version when comparing instructions.

Router behavior is equally important. Client isolation, enterprise Wi-Fi, captive portals and some managed apartment networks may deliberately prevent local discovery. If you do not control that network, test on a normal private router before declaring the TV incompatible.

A privacy-conscious alternative for local control

ThinQ is LG’s account-based ecosystem. OLED Control uses supported local-network communication for compatible LG webOS TVs. It still needs local-network permission and a reachable TV, but you can keep the diagnostic boundary clear: first prove local reachability, then choose the control app that fits your workflow. Start with first setup and verify your TV against supported LG models.