LG Smart TV cannot link device to smart home — easy checks for seniors (safe diagnosis)

Hi! When an LG Smart TV can’t link to a smart home, it’s usually not a “bad TV” problem — it’s almost always one of four things: the wrong account, the TV not fully registered in LG ThinQ, a network mismatch, or a permission/assistant setting that blocks discovery.

To keep this easy for seniors (and avoid stressful factory resets), I’ll ask a few quick questions. Answer whatever you know:
1) Which smart home app are you trying to link to — Google Home, Amazon Alexa, or something else?
2) Is the TV already added in the LG ThinQ app on the phone, or are you stuck before that step?
3) What does the error look like: “can’t link,” “no devices found,” “something went wrong,” or it keeps spinning?

“Linked but no devices found” is a classic pattern. It usually means Google Home successfully connected to the LG ThinQ account, but the TV isn’t visible inside that account (or it’s registered under a different LG login/region).

Let’s do the least disruptive checks first:

A) In the LG ThinQ app on the phone, do you see the TV listed as a device (even if you can’t control it yet)?
B) On the TV itself, is your dad signed in to an LG account (not just a streaming app account)?
C) When did this start — is it first-time setup, or did it work before and then stopped after a Wi-Fi change or update?

That’s actually good news, because it narrows it down: if the TV isn’t in ThinQ, Google Home can’t “discover” it through the LG integration yet.

For seniors, there are two easy-to-miss gates in first-time setup:
• The phone needs permission to find devices on the local network (iPhone privacy prompts).
• The TV needs to be paired/registered into the same LG ThinQ account you’re linking in Google Home.

Quick questions (so we don’t chase the wrong thing):
1) Is the phone using Wi-Fi (not cellular), and is it on the same Wi-Fi name as the TV?
2) Does your dad use any “VPN” or “security” app that might block local discovery?
3) Do you know the approximate TV model year (newer webOS vs older)? Some steps differ slightly.

Mesh + guest network is a common “invisible wall” for smart home linking, even when both devices are on the same Wi-Fi name. Some routers quietly isolate devices or move phones between nodes, and that can break pairing discovery.

But before we touch router settings, let’s confirm the simplest path for seniors:

Step 1 (TV-side): confirm the TV is logged into an LG account / has LG services enabled (this is separate from Netflix/YouTube).
Step 2 (Phone-side): confirm the LG ThinQ app has permission to access the local network on iPhone (this is what your dad calls a “privacy popup”).

When you try to add the TV in ThinQ, do you get an on-screen pairing code on the TV, or does it fail before that?

That combination explains a lot: if discovery never reaches the “code on TV” stage, it’s usually either phone permission or network stability (or both). Slow app loading is a hint the TV’s connection might be unstable, even if it says “connected.”

Here’s a senior-friendly way to think about it: streaming apps can sometimes “eventually work” on a weak connection, but pairing needs a clean, reliable local connection at the exact moment you try to link.

Two safe checks that don’t change accounts or delete anything:

1) TV network check: on the TV, verify the internet connection is stable (not just “Wi-Fi connected”). If the TV has a network test, it helps identify dropouts.

2) iPhone permission check: confirm the LG ThinQ app can use the Local Network on iPhone. If it’s blocked, the app can’t discover the TV even on the same Wi-Fi.

When your dad installed ThinQ, do you remember seeing a prompt like “Allow LG ThinQ to find and connect to devices on your local network” and did he tap “Don’t Allow”?

That’s a very normal concern, especially for seniors, and it’s smart to ask. In simple terms, Local Network permission allows the ThinQ app to talk to devices on your home Wi-Fi (like the TV) for setup and control. Without it, the app is basically “blind” to the TV on the network.

It doesn’t automatically mean “the company can see everything on your phone,” but it does allow the app to discover local devices — which is exactly what you need for linking the TV to the smart home.

Another low-risk guardrail: you can enable the permission, complete pairing, and then keep everything on your private home Wi-Fi (not guest). If your dad is worried, avoid doing setup on public Wi-Fi and keep the TV on the main network with a strong password.

After permission is enabled, the next common stumbling block is account mismatch: the TV and ThinQ app must use the same LG account sign-in for Google Home linking to show devices.

Yes — that matters a lot, and it’s one of the most common “why does it say no devices?” causes.

The smart home apps (Google Home or Alexa) don’t link to the TV directly — they link to the LG ThinQ account. So if the TV gets registered under your ThinQ login, but your dad links a different LG account in Google Home/Alexa, it can look like the TV “won’t link” when really it’s just in the wrong account bucket.

Senior-friendly approach: pick one “household LG account” that will own the TV in ThinQ (usually your dad’s email if he wants voice control himself), and make sure:
• The TV is signed into that LG account (where applicable)
• The ThinQ phone app is signed into that same LG account
• Google Home / Alexa links the same LG ThinQ account

For Alexa vs Google: the checks are similar (account, Wi-Fi, permissions, and whether the TV is actually visible in ThinQ). We can diagnose it without changing every integration at once.

That fear is totally understandable. The safest route is to avoid “big moves” first. We can do confirmation steps that don’t delete apps or reset the TV.

The least risky sequence is:
1) Verify the TV is consistently online (stable Wi-Fi, not bouncing).
2) Enable iPhone Local Network permission for ThinQ so it can discover the TV.
3) Confirm which email is used in ThinQ on the phone (so you know which account “owns” the TV once it’s added).

Only after that would you decide whether to standardize accounts for your dad’s smart home voice control. That’s a decision step, not something you have to do immediately.

If you tell me the exact wording of the error in ThinQ (or in Google Home when it says no devices), I can help you choose the lowest-disruption next check.