Hey! We’ll fix why your Samsung TV is not discovering devices — whether your phone can’t find the TV in SmartThings, your TV can’t see a Bluetooth device (headphones/soundbar), screen mirroring / casting doesn’t show the TV, or HDMI devices don’t appear / keep switching inputs.

“Not discovering devices” can mean a few different discovery systems, so we’ll diagnose fast and avoid random resets:
• SmartThings pairing (phone ↔ TV) — requires same network + Samsung Account + permissions.
• Bluetooth pairing (TV ↔ headphones/soundbar) — depends on TV model support + pairing mode + distance/interference.
• Casting / screen mirroring (Smart View / AirPlay / Wi-Fi Direct) — depends on network discovery (multicast/UPnP), privacy settings, and both devices on the same Wi-Fi.
• HDMI device detection / Anynet+ (HDMI-CEC) — depends on cable, correct port, and CEC enabled on both ends.

Quick questions so we don’t guess:
1) What device isn’t being discovered: phone, soundbar/headphones, PC, game console, or other smart device?
2) What’s the exact symptom: “TV not found” in SmartThings, “Bluetooth device not found”, AirPlay/Smart View missing, or HDMI input not showing?
3) TV model/year (approx) and current connection: Wi-Fi or Ethernet?
4) Any recent changes: router swap, Wi-Fi name/password change, firmware update, VPN on phone, new mesh system?

Reply with those and we’ll start with the first checks that fix most Samsung discovery issues.

That “apps work but discovery fails” detail is huge. It means the TV has internet, but your phone and TV aren’t seeing each other on the local network — that’s exactly what SmartThings pairing, Smart View, and many “discover devices” flows depend on.

After a router change, the most common reasons a Samsung TV is not discovered are:
• Phone and TV are on different networks (2.4 vs 5 GHz on separate SSIDs, guest Wi-Fi, or a mesh “isolated” band).
• Router features blocking discovery: AP isolation / client isolation, “block LAN access”, multicast filtering, or UPnP disabled.
• The TV’s network profile is “stuck” (kept old gateway/DNS), so it has internet but local discovery is flaky.
• SmartThings permissions/account mismatch (Samsung Account, local network permission on iPhone/Android).

We’ll do a safe ladder: same Wi-Fi + permissions → TV network refresh → router discovery settings → SmartThings add TV.

Yes — guest networks are a top reason a Samsung TV won’t be discovered. Guest Wi-Fi typically blocks device-to-device traffic, so your phone can’t “see” the TV for SmartThings, Smart View, AirPlay, or DLNA — even though both have internet.

Step 1 — Confirm phone + TV are on the same real LAN (not guest)
1) On the TV: go to Settings → General → Network → Network Status (or Network Settings) and note the Wi-Fi name (SSID).
2) On your phone: confirm you’re on the same SSID (and not “Guest”).
3) If your mesh has “guest isolation” or “IoT network”: make sure the TV is on the main network while testing discovery.

Step 2 — Fast discovery reset without deleting anything
• Restart the TV fully (hold the remote power button ~5 seconds until the Samsung logo appears).
• Toggle Wi-Fi off/on on your phone, then reopen SmartThings and try “Add device”.

After this, tell me: does SmartThings still say TV not found, or does it see the TV but fails during pairing?

Inconsistent discovery usually means the router is allowing internet traffic but interfering with local discovery protocols (multicast/Bonjour/SSDP/UPnP). That affects SmartThings and casting differently, but the root cause is often the same: the phone can’t reliably find the TV on the local network.

Step 3 — Check the 4 “router settings” that break Samsung TV discovery
On your router/mesh app, look for these (names vary):
1) AP / Client Isolation or “Block LAN access” → turn OFF for the main Wi-Fi.
2) Multicast filtering / “IGMP snooping” / “mDNS” options → allow multicast (or disable filtering). Discovery relies on multicast packets.
3) UPnP → enable (helps with discovery for some casting flows and device announcements).
4) Security / firewall set to “High” that blocks local traffic → set to “Normal” while testing.

Step 4 — Refresh the TV’s network profile (this fixes “TV online but not discoverable” a lot):
• TV: Settings → General → Network → Reset Network (this does NOT factory reset the TV).
• Reconnect the TV to Wi-Fi again and re-test SmartThings + screen mirroring.

Tell me what mesh brand you use (Eero/Deco/Orbi/Asus/etc.) and I’ll translate the settings names precisely — but you can already test with the steps above.

Great progress: if mirroring got better, the local discovery layer is healthier. Now SmartThings failing to add often comes down to account + permissions + pairing mode rather than pure network discovery.

Step 5 — SmartThings pairing checklist (what to check first)
1) On the TV: confirm you’re signed into the same Samsung Account you use on your phone (TV: Settings → General → System Manager → Samsung Account). Account mismatch can look like “TV not found” or “couldn’t add device.”
2) On your phone: open SmartThings and ensure these are allowed:
• Local Network permission (iPhone) or Nearby devices (Android) — required for discovery.
• Bluetooth permission (SmartThings may use BLE during pairing).
3) Make sure the TV is not in a restricted mode that blocks pairing prompts (some privacy / “autorun” options can interfere).
4) Update both ends:
• TV software update: Settings → Support → Software Update.
• SmartThings app update from the app store.

Quick test: with the TV on the home screen, try adding it again in SmartThings: + → Device → TV → Samsung. If it fails, tell me whether you see any pairing prompt on the TV at all.

Perfect — now we switch discovery “types.” Bluetooth issues are separate from SmartThings, and the fixes are different. Also, not every Samsung TV supports every Bluetooth profile (some TVs support Bluetooth audio but not keyboards/mice, etc.), so we’ll keep it practical.

Step 6 — Fix Samsung TV not discovering Bluetooth devices (headphones/soundbar)
1) Put the headphones/soundbar into pairing mode (not just “powered on”). Most require holding the Bluetooth button until the LED flashes rapidly.
2) On the TV, use the proper menu path (varies by model), usually:
Settings → Sound → Sound Output → Bluetooth Speaker List (or Settings → Connection → Bluetooth Device List).
3) Keep distance close during pairing: within 3–6 feet (1–2 meters). Pairing is most reliable when close, then you can move back.
4) Remove old pairings that confuse discovery:
• If the headphones are already paired to your phone/laptop, temporarily turn Bluetooth OFF on those devices so they don’t “steal” the connection.
• If the TV shows old devices, remove them from the list and re-scan.
5) Power cycle both devices: unplug TV power for 30 seconds, restart headphones/soundbar, then try again.

Tell me: are the headphones discoverable by your phone right now? And is your soundbar connected over Bluetooth, or HDMI (ARC/eARC), or optical?

Got it — you’re seeing BOTH:
• Bluetooth discovery (headphones list not showing / not finding), and
• HDMI detection + ARC/eARC + CEC (soundbar and console handshake problems).

Step 7 — Fix “soundbar not detected” and HDMI device discovery (ARC/eARC + Anynet+)
1) Confirm the soundbar is on the correct HDMI port: use the TV’s HDMI port labeled ARC or eARC (not a random HDMI).
2) Use a quality HDMI cable (older cables can cause “device not detected” and ARC dropouts). If in doubt, swap the cable first — it’s the fastest test.
3) Enable CEC on Samsung (it’s called Anynet+ (HDMI-CEC)):
• TV: Settings → Connection → External Device Manager → Anynet+ (HDMI-CEC) ON (menu names can vary slightly).
4) Set sound output correctly:
• TV: Settings → Sound → Sound Output → choose Receiver (HDMI) / your soundbar name.
• If you see eARC options: set eARC mode to Auto (if your bar supports it), or Off if you get unstable detection.
5) Do the “HDMI handshake reset” in the correct order (works shockingly often):
• Power OFF TV + soundbar + PS5.
• Unplug power to TV and soundbar for 30 seconds.
• Plug soundbar back in first, then TV, then PS5, then select the right HDMI input.

This solves many cases of Samsung TV not discovering HDMI devices, soundbar not detected, and “device disappears after sleep.”

Yes — the #1 “first check” for Bluetooth on Samsung TVs is whether your model supports the Bluetooth audio menu, and whether the headphones are truly in pairing mode (and not auto-connecting to your phone). Then we clean up conflicts.

What to check FIRST for Samsung TV not discovering Bluetooth devices
• Force pairing mode on the headphones (rapid flashing LED). If you’re unsure, delete pairing from the phone and re-enter pairing mode fresh.
• Disable Bluetooth on nearby devices (phone/laptop) for 2 minutes so the headphones don’t connect to them first.
• On the TV, go to the Bluetooth scan screen and stay there for 30–60 seconds — some models don’t refresh instantly.
• If the Bluetooth menu appears inconsistently, do a full TV restart (hold power until logo) and re-check the Sound Output list.

Quick workaround if the TV just won’t keep headphones paired:
If your soundbar supports it, pair headphones to the soundbar (or use a dedicated Bluetooth transmitter from the TV’s optical/3.5mm output). That bypasses TV Bluetooth limitations while keeping audio stable.

If you share your exact TV model code (like “QN90A” / “TU7000” / etc.), I can tell you the most reliable menu path and whether it supports Bluetooth audio output natively.

Summary (what to check first): When a Samsung TV is not discovering devices, don’t jump to factory reset. Start with the foundation, in this order:

1) Same network: phone + TV on the same main Wi-Fi (not Guest), then restart TV (hold power until logo).
2) Router discovery settings: disable client/AP isolation, allow multicast, and avoid overly strict firewall settings that block local discovery.
3) SmartThings pairing: make sure TV and phone are on the same Samsung Account and SmartThings has local network + Bluetooth permissions.
4) Bluetooth pairing: put the device in true pairing mode, turn off Bluetooth on nearby devices, then scan from the correct TV menu.
5) HDMI detection: for soundbars/consoles, confirm ARC/eARC port + enable Anynet+ (HDMI-CEC) + do the power order handshake reset.

Want help tuned to your exact Samsung model and router/mesh settings? Open the chat and we’ll walk through it live.