Hey! We’ll sort out why using your phone as a remote feels confusing. This problem usually falls into one of these buckets:

(A) Wrong control method — some devices need Wi-Fi cloud control (manufacturer app / Google Home / Alexa), others need Bluetooth, and some “remote apps” only work with IR blaster hardware (your phone may not have IR).
(B) Discovery / network mismatch — phone on 5 GHz but device on 2.4 GHz, guest network isolation, mesh band-steering, VPN, AP/client isolation, or the device is “paired” but not truly on the same LAN.
(C) Permissions & OS blocks — iOS Local Network permission, Bluetooth permission, Location services, background refresh, battery optimization, or Android “Nearby devices.”
(D) Account linking — Alexa Skill / Google Home linking, wrong region, multiple accounts, duplicate devices, or stale tokens after updates.

Quick questions so we pick the right fix without random resets:
• What are you controlling (TV, AC, fan, lights, LED strip, thermostat, smart plug, soundbar)? Brand/model if you know it.
• Which app are you using (manufacturer app, Google Home, Alexa, SmartThings, Home app, a “universal remote” app)?
• What happens exactly: not found, can’t pair, device offline, buttons do nothing, or lag/delays?

Answer those and I’ll map the safest next steps.

That symptom (“paired but not controllable”) is super common when the device is on 2.4 GHz and the phone is bouncing between networks, or when Local Network/Nearby devices permissions are blocked. Also, Google Home control can fail if the manufacturer link is stale even though the vendor app still works (or vice versa).

Before we do any factory reset, we’ll do a quick “reality check” to identify whether this is LAN control, cloud control, Bluetooth control, or an IR remote app situation. The exact path depends on the device category (TV/AC vs lights/plug vs hub-based devices).

One key detail: are you using a regular smartphone with no extra hardware, or do you have something like an IR blaster accessory / a smart IR hub (BroadLink-style) that turns your phone into a remote?

Perfect — that already narrows it down. If there’s no IR blaster, then any “universal remote” app that claims to control TVs/AC over IR won’t behave like a real remote unless your device supports control via Wi-Fi or Bluetooth through the official ecosystem.

Let’s do the safe, fast checks that don’t “break” anything:

Step 1 — Confirm which app is the “source of truth”
• If the device is added in the manufacturer app, Google Home is usually just a linked service. If linking is stale, Google Home shows it but can’t control it.
• If the device was added directly to Google Home (some Matter devices), control depends on the home structure, hub/thread border router, and network permissions.

Step 2 — Permission sanity check (most missed)
• iPhone: the app often needs Local Network (for discovery/control), plus Bluetooth if pairing is BLE-based.
• Android: “Nearby devices” / Bluetooth permission, sometimes Location (for BLE scanning), and battery optimization off for the control app.

Tell me: are you on iPhone (iOS) or Android, and is the device on a 2.4 GHz Wi-Fi network?

That combination (mesh + single SSID + iPhone + 2.4 GHz device + occasional VPN) is a classic recipe for device not responding and “phone remote not working.” Here’s why, at a high level (without forcing risky resets):

• Band steering / roaming can move your phone to a different node/band while the device stays anchored, and some devices hate that.
• A VPN can break local discovery/control (LAN broadcast/mDNS), so the app can’t find the device even though Wi-Fi is “on.”
• If iOS Local Network permission is off, the app can’t talk to devices on your home network reliably.

We’ll do a safe test sequence first (no factory reset):
1) Turn off VPN temporarily while testing control.
2) Check iOS Settings → the manufacturer app → make sure Local Network is allowed (and Bluetooth if pairing relies on it).
3) Confirm the phone and device are not on a guest network (guest networks often block device-to-device control).

If you tell me your mesh brand (eero, Deco, Orbi, Google/Nest Wi-Fi), I can point to the exact setting names — they’re different on each system.

Duplicate devices in Google Home usually means one of these situations:

• The device exists once in the manufacturer cloud and once as a “local/Matter” record (or a previous setup attempt left a ghost).
• The linked account was connected twice (two Google accounts, or the service was re-linked).
• The device was re-provisioned but the old entry didn’t clean up.

We can clean duplicates, but we do it carefully because removing the wrong one can break automations, rooms, or routines. The safe approach is:
(1) Identify which entry actually responds and which one is stale.
(2) Verify account linking (Google Home “Works with Google” / linked services).
(3) Only then remove/re-add if needed.

For eero specifically, “advanced security” features and some isolation-like behaviors can interfere with local discovery and mDNS for smart home control — but the exact fix depends on whether the device needs local LAN control or just cloud control.

If you want the quickest route: tell me the exact device type (e.g., smart lights, smart plug, thermostat, TV, IR hub) and the manufacturer app name — that determines the right cleanup method.

That “works better away from home” clue is important — it often hints the app is falling back to cloud control when you’re remote, but struggling with local LAN control at home (usually permissions, VPN, or network isolation). For smart lights that support Matter, the setup can also create multiple control paths (manufacturer cloud + Matter controller), which is where duplicates and confusion come from.

Here’s what we can do safely without breaking your scenes:

Step 3 — Protect your automations before cleanup
• Don’t delete blindly. First, confirm which ecosystem owns the scenes (manufacturer scenes vs Google Home automations).
• Make note of room assignments and names. Duplicates often differ by a tiny suffix (“Light” vs “Light 2”).

Step 4 — Quick checks that often fix “phone remote lag”
• iPhone: verify Local Network permission is ON for both Google Home and the manufacturer app.
• Turn off VPN while testing.
• Ensure the lights/hub are on stable 2.4 GHz and not a guest SSID.

After those checks, we’ll decide whether your best next step is: re-linking the service, cleaning duplicates, or re-provisioning Matter properly (that last part depends heavily on the exact model and controller).

Status desync (wrong ON/OFF) usually comes from one of three places: network latency, two controllers fighting (manufacturer + Google/Matter), or a hub/bridge that’s losing connection briefly and then resyncing. Cache can contribute too, but it’s rarely the only cause.

We can narrow it down with two fast observations (no risky changes):
• Does the manufacturer app show the correct status instantly while Google Home is wrong? (points to linking/controller issues).
• Do both apps lag at the same time? (points to Wi-Fi/mesh/node placement, 2.4 GHz congestion, or hub placement).

The “right” fix depends on whether you have:
Wi-Fi lights (no hub), Zigbee/Thread lights (needs a hub/border router), or Bluetooth lights (phone proximity matters).

If you share the exact brand/model and whether there’s a hub/bridge, I can give you the correct next step without wiping scenes.

Totally fair — here’s the “least disruptive ladder” for a smart home device using phone as remote when control is inconsistent. We start with steps that don’t risk losing scenes, then escalate only if needed.

Level 1 — 3-minute sanity checks
• Keep VPN OFF while testing.
• Confirm iOS Local Network is ON for the control apps.
• Make sure you’re not on guest Wi-Fi and the device is on 2.4 GHz if required.

Level 2 — Fix the “two controllers” problem
• Identify which device entry responds and which is stale (duplicates). Don’t delete until we confirm which one is the ghost.
• Check linked services in Google Home; stale linking is a top cause of “device not responding.”

Level 3 — Network stability (safe)
• One clean reboot of the eero system (not repeated), then wait for everything to fully settle.
• Verify the smart device (or hub/bridge) has strong signal and isn’t tucked behind metal/TVs.

Level 4 — Re-provision (highest risk)
• Re-adding or resetting can fix it, but it can also nuke scenes if done wrong — especially with Matter or mixed ecosystems.

If you want the fastest “do this next” tailored to your setup, open the chat and tell the expert the exact brand/model + whether it says Matter/Thread anywhere. That detail decides Level 2 vs Level 4.

Yes — that’s the ideal way to do it safely. With the model + what Google Home shows (and whether it’s Matter/Thread/Wi-Fi), we can pinpoint the exact cause of the confusion and avoid wiping your scenes. Open the chat and an expert will walk you through the correct next step for your setup in real time.