Hey! We’ll fix why Honeywell isn’t discovering devices and get your thermostat/sensors to show up in the app. A few quick details so we choose the right path (Honeywell has multiple apps and setup modes):
• Which app are you using: Honeywell Home, Resideo, or Total Connect Comfort?
• What device are you adding: Wi-Fi thermostat (T5/T6/T9/T10, VisionPRO, etc.), Room Sensor, leak detector, or another accessory?
• Where does it fail: “searching”, “no devices found”, QR scan won’t work, or it never creates the device Wi-Fi (like NewThermostat_…)?
• Phone type (iPhone/Android) and network setup: 2.4 GHz vs 5 GHz, mesh Wi-Fi, guest network, VPN, or extender?
Once we know that, we’ll fix the Honeywell Home app not finding device issue without random resets.

Perfect — that symptom usually means one of three things:
1) App permissions block discovery (especially on iOS/Android): the Honeywell Home app may need Bluetooth and Location enabled to detect the thermostat during setup.
2) Network mismatch: many Honeywell thermostats require a stable 2.4 GHz Wi-Fi (not 5 GHz). If your router uses one combined SSID with band steering, the setup can fail and look like “not discovering devices.”
3) Thermostat isn’t in pairing / Wi-Fi setup mode: if it’s not actively broadcasting setup (or ready to be found), the app keeps “searching” forever.

We’ll fix it in a clean order: permissions → pairing mode → Wi-Fi (2.4 GHz + security) → router options like AP isolation.

Great clues. Let’s do the two biggest “hidden” blockers first — this fixes a lot of Honeywell not discovering devices cases on iPhone.

Step 1 — Give Honeywell Home the right iPhone permissions
1) iPhone: Settings → Privacy & Security → Location Services → ON.
2) Scroll to Honeywell Home → set to While Using the App (and enable “Precise Location” if you see it).
3) iPhone: Settings → Bluetooth → ON, then confirm Honeywell Home is allowed (some iOS versions show app-level toggles).
4) Temporarily disable any VPN or “Private Relay” style filtering while pairing (it can break cloud registration and look like a discovery problem).

Step 2 — Put the thermostat into setup mode
Since you don’t see a setup Wi-Fi name, the thermostat may not be in Wi-Fi setup / pairing mode. On many Honeywell Wi-Fi thermostats you’ll see a prompt like “Wi-Fi Setup” or a setup icon. If it’s already configured to an old network, we may need to “reset Wi-Fi” (not a full factory reset yet).

After you check permissions, tell me what the thermostat screen shows (any Wi-Fi symbol, “SETUP”, or a code/QR).

Nice — fixing Location permissions was necessary. Now we’ll make the thermostat “advertise” itself properly and make sure your network won’t reject it.

Step 3 — Force Honeywell Wi-Fi setup mode
In the thermostat’s Wi-Fi menu, look for one of these options (wording varies by model):
• Wi-Fi Setup / Set up Wi-Fi
• Reset Wi-Fi / Disconnect Wi-Fi
• Change Network
After you trigger setup, the thermostat should either:
• show a setup screen/code, or
• briefly broadcast a temporary Wi-Fi network (often something like NewThermostat_XXXXXX).

Step 4 — Make 2.4 GHz “easy mode” for discovery
Mesh networks with one SSID can cause the Honeywell Home app not finding thermostat problem. Do one of these for setup:
• If your mesh has an IoT network or a dedicated 2.4 GHz SSID, use it for pairing.
• If you can’t split bands, move your phone farther from the main node so it drops to 2.4 GHz during setup.
Router security should be WPA2 (AES) (avoid WPA3-only during pairing).

Once you see a setup screen or the temporary thermostat Wi-Fi, we’ll connect it to your home network and finish registration.

That’s progress: discovery is working intermittently, but Wi-Fi join is failing — very common with mesh defaults.

Step 5 — Use the IoT network (2.4 GHz) and remove common blockers
1) Enable the mesh IoT network and confirm it’s 2.4 GHz.
2) Set IoT security to WPA2-AES (not WPA3-only).
3) Temporarily disable features that break setup:
  • Client isolation / AP isolation (prevents device discovery and handoff)
  • Overly strict firewall rules for new devices
  • Any “block LAN to WLAN” toggle on the IoT network during onboarding
4) On your iPhone, connect to that IoT SSID before you tap Add Device in Honeywell Home.

Step 6 — Finish registration cleanly
When the app asks for Wi-Fi, choose the IoT SSID, enter the password carefully, and wait 2–3 minutes. If it errors quickly, it’s usually a wrong band/security mismatch, not the thermostat itself.

This is the #1 fix for Honeywell not discovering devices on mesh Wi-Fi: use a stable 2.4 GHz IoT SSID + remove isolation.

Totally different discovery channel — sensors are usually found via Bluetooth / proximity scanning (and sometimes they “sleep” to save battery). Let’s do quick sensor-specific fixes that keep keywords natural: Honeywell sensor not discovered, room sensor pairing, and not finding accessory.

Step 7 — Wake the sensor and reset the pairing attempt
• Pull the battery tab (if it’s new) or remove the battery for 10 seconds, then reinsert.
• Watch for an LED blink (some models blink when awake / in pairing mode).
• Keep it within 1–2 feet of the phone for the first discovery pass.

Step 8 — Reduce iPhone Bluetooth “noise”
• Temporarily turn off other nearby Bluetooth devices (watch/earbuds) just for pairing.
• Fully close and reopen the Honeywell Home app (swipe away), then try Add Sensor again.
• If the app has a “Scan QR” option for the sensor, use that — it bypasses some discovery failures.

If it still won’t show, we’ll check whether your thermostat model supports that specific sensor type in Honeywell Home (some accessories are model-specific).

Yes — not “bad,” but it can interfere. When a device appears briefly and disappears, it’s usually scanning contention or permissions caching.

Step 9 — Make sensor discovery stable (the “no devices found” cure)
1) Temporarily disable the Apple Watch Bluetooth connection (or put the watch in Airplane Mode for 2 minutes).
2) iPhone: toggle Bluetooth OFF → wait 10 seconds → ON.
3) Open Honeywell Home and immediately start the Add Sensor flow again.
4) Keep the sensor awake: if it has a button, press once; if not, briefly remove/reinsert the battery right before scanning.

Step 10 — Prevention (so Honeywell keeps discovering devices)
• Keep Honeywell Home permissions set to Location: While Using and Bluetooth allowed.
• Keep your thermostat on a stable 2.4 GHz IoT SSID with WPA2 and avoid AP/client isolation during setup.
• If you change Wi-Fi name/password, use Reset Wi-Fi (not full factory reset) so the thermostat re-registers cleanly.

This combination stops the recurring Honeywell Home app not discovering devices loop.

Best question — router swaps are when people hit Honeywell not discovering devices again.

Fastest “new router” checklist
• Recreate the same 2.4 GHz SSID + password (especially on the IoT network). If the name/password stay the same, many Honeywell devices reconnect without re-adding.
• Keep security on WPA2-AES during onboarding (you can re-enable WPA3-mixed later if needed).
• Disable AP/client isolation until everything is added and visible in the app.
• If the thermostat won’t reconnect, use Reset Wi-Fi / Change Network on the thermostat (avoid factory reset unless it’s truly stuck).
• For sensors/accessories, do a quick “wake” + add flow and temporarily reduce Bluetooth clutter (watch/earbuds) if discovery gets flaky.

If you want, open the chat and tell me your router/mesh brand — I can give exact menu paths for IoT SSID and isolation settings.

Summary: when Honeywell isn’t discovering devices, fix app permissions first (Location + Bluetooth), then force the thermostat into Wi-Fi setup mode and join a stable 2.4 GHz network (IoT SSID is best). For sensors, wake the device and reduce Bluetooth interference (watch/earbuds) so the scan stays stable. If you’re stuck on “searching” or “no devices found,” open the chat and an expert can walk you through the exact steps for your Honeywell model and router.