Hey! We’ll fix why your smart thermostat is not discovering devices (or the app can’t find the thermostat / sensors). To troubleshoot this properly, I need a few details:
• Thermostat brand/model (Nest Thermostat / Learning Thermostat, ecobee, Honeywell Home/Resideo, Tado, Emerson Sensi, etc.)?
• What are you trying to “discover”: the thermostat itself in the app, remote room sensors, a smart home hub, or adding it to Apple Home / Google Home / Alexa?
• Which setup path fails: “device not found”, “pairing failed”, “unable to add accessory”, or it finds it but won’t finish setup?
• Phone details: iPhone/Android, and are Bluetooth, Location permissions, and local network (iOS) enabled for the app?
Once we know where discovery breaks (Bluetooth onboarding vs Wi‑Fi vs HomeKit/Matter), we can fix it step by step without guessing.

That combination of symptoms usually means discovery is failing in one of three places:
1) Bluetooth / local onboarding — many smart thermostats and sensors use Bluetooth (or a temporary Wi‑Fi) during setup, so if Bluetooth is off, permissions are blocked, or a VPN is running, you’ll see “not found in app”.
2) Wi‑Fi + router settings — if the thermostat is on 2.4 GHz but your phone is on 5 GHz (or you have band steering / “Smart Connect”), the app can lose local discovery. Also, AP isolation or blocked multicast/mDNS can break HomeKit/Matter discovery.
3) Device state — the thermostat or sensors are not in pairing mode, are still linked to an old account/home, or the firmware got stuck and needs a restart or reset.

Good news: we can isolate this quickly and get the thermostat and sensors to show up consistently.

Perfect — let’s fix the most common cause of a smart thermostat not being discovered: mixed bands + blocked local discovery.
Step 1 — Do the “phone + permissions” checklist (takes 2 minutes)
1) Turn Bluetooth ON (required for many “add device” flows).
2) On iPhone: Settings → Privacy & Security → Location Services ON, then allow location for the thermostat app (many apps require it for discovery).
3) On iPhone: Settings → (thermostat app) → enable Local Network (this is huge for “device not found” problems).
4) Temporarily disable VPN / iCloud Private Relay (they can interfere with pairing and device discovery).

Step 2 — Put your iPhone on the same “path” as the thermostat
Because you have a combined SSID, we want to force a clean 2.4 GHz environment for setup:
• If your router allows it, create a dedicated 2.4 GHz SSID (example: Home_IoT_2G) just for smart home devices.
• Connect your iPhone to that 2.4 GHz SSID during setup and sensor pairing.
This reduces “not found in app” issues and helps HomeKit/Matter pairing succeed.

Great questions — this is where people get stuck.
Step 3 — Reconnect the thermostat to stable 2.4 GHz
If you change the network name/password (or split SSIDs), many thermostats won’t magically follow. Do this once and it usually becomes stable:
1) Connect your iPhone to Home_IoT_2G (2.4 GHz).
2) On the thermostat: go to Wi‑Fi settings and select Home_IoT_2G (enter password).
3) Confirm the thermostat shows “connected” and has an IP in your router’s device list.

Step 4 — Pair room sensors the right way
Most room sensors do not join your Wi‑Fi. They pair directly with the thermostat (or via the brand’s hub) using a low‑power link. That means sensor discovery fails if:
• The thermostat isn’t online in the app, or
• The sensors aren’t in pairing mode, or
• The thermostat is mid‑update / needs a restart.
Once the thermostat stays visible in the app, we’ll pair sensors from the thermostat menu or the app’s sensor section.

HomeKit/Matter pairing errors usually come from local network discovery getting blocked — even when Wi‑Fi “works.” Let’s fix the common culprits:
Step 5 — Router settings that break HomeKit/Matter discovery
In your router settings, check these (names vary by brand):
• Turn OFF AP Isolation / Client Isolation (devices must see each other locally).
• If you use a “Guest” or “IoT” network, make sure it’s not isolated from your phone (or pair everything on the main LAN first).
• Avoid WPA3‑only on 2.4 GHz; use WPA2 (AES) for compatibility.
• If available: enable mDNS / Bonjour / multicast support (HomeKit depends on it).

Step 6 — Put the thermostat in pairing mode again
HomeKit accessories often time out if pairing mode expires. Reset just the HomeKit/Matter pairing state (not necessarily a full factory reset), then try again with your iPhone connected to the same Wi‑Fi.

If it still fails, we’ll do a clean remove/re-add path that clears “stuck” pairings.

When discovery works “randomly,” it’s usually a network consistency problem, not the thermostat itself.
Step 7 — Make discovery reliable (DHCP + stability)
1) In your router’s client list, find the thermostat and create a DHCP reservation (static IP) so it doesn’t change after a lease renew.
2) Reboot the router once after saving (yes, really). Then reboot the thermostat from its settings menu (or power cycle if the model supports it).
3) Check for firmware updates on the thermostat and update the app. Some “not found” issues happen after partial updates or old app versions.

Step 8 — Avoid mesh roaming for the thermostat
If you have mesh Wi‑Fi, thermostats can “roam” between nodes and appear offline in the app. If possible, pin the thermostat to the closest node, or place a node closer so the signal is strong. A stable -60 dBm-ish signal is a sweet spot for IoT reliability.

Yep — sensor discovery is its own mini-problem. Here’s the clean approach:
Step 9 — Pair sensors close, then move them
1) Bring each sensor into the same room as the thermostat for the first pairing (distance matters).
2) Replace the battery (low battery = “pairing failed” / “device not found” behavior).
3) Remove the sensor from the app (if it’s a “ghost” entry), then start pairing again from the thermostat/app menu and wait until it confirms the link.
4) After it’s paired, move it to the target room. If it drops after moving, you’re hitting range or interference (thick walls, metal ducts, mirrors).

Related keyword note: if you see “sensor not responding” later, it’s usually range, battery, or the thermostat rebooting during an update.

Totally fair — and you can usually fix it without touching HVAC wiring.
Step 10 — “Nuclear option” (software reset, not wiring)
• First, do an “account / home / pairing reset” inside the thermostat settings (many models let you reset HomeKit/Matter pairing without wiping schedules).
• If pairing is still stuck, do a factory reset on the thermostat, then set it up again on your 2.4 GHz SSID with Bluetooth enabled on your phone.
• Add it to the manufacturer app first (ecobee/Nest/Honeywell), confirm it’s stable, then add to Apple Home / Google Home as the final step.

Safety note: if the thermostat won’t power on, reboots endlessly, or shows a low-power warning (often “C‑wire” related), that’s the point to stop and ask for in‑person help. But for discovery/pairing errors, the steps above solve most cases.

Awesome — that’s exactly the “stable stack” we want. Summary: when a smart thermostat is not discovering devices, fix it in this order: (1) enable Bluetooth + correct app permissions (Location/Local Network), (2) use a stable 2.4 GHz Wi‑Fi for setup, (3) disable isolation features and allow local discovery (mDNS/Bonjour), (4) lock the thermostat’s IP with a DHCP reservation, and (5) re-enter pairing mode or reset stuck HomeKit/Matter pairing. If you want, open the chat and we’ll tailor the exact steps to your thermostat model and app screen-by-screen.