The short answer
Three causes account for nearly all of it: weak 2.4GHz signal at the hallway where the thermostat lives, a router that has band steering or a captive portal confusing the device, and insufficient power on systems without a common wire, where the thermostat browns out when the Wi-Fi radio draws current. Check signal first, power second.
A thermostat that drops off Wi-Fi is annoying rather than dangerous, because almost all of them keep controlling the heating locally when offline. What you lose is remote control, schedules that depend on the cloud, and the ability to check anything from your phone. The causes are consistent enough that you can usually identify yours in ten minutes.
Cause 1: the thermostat is at the edge of coverage
Thermostats are installed where the wiring is, which is typically a hallway, a stairwell, or a spot near the front door. That is often the furthest point from the router, behind at least one masonry wall. Add to this that thermostats have small internal antennas designed for cost rather than sensitivity, and you have a device that reports a connection while barely holding one.
Check the signal the thermostat itself reports
Most units show Wi-Fi signal strength in their settings or in the app’s device information. Nest shows it under Technical Info, Hive and Tado show a strength indicator in the app. Anything below about -70 dBm, or one bar, is the likely cause.
Measure with a phone at the thermostat
Hold a phone flat against the wall beside the thermostat and check the signal with a Wi-Fi analyser app. Phones have better antennas than thermostats, so if the phone is marginal there, the thermostat has no chance.
Try moving the router, not the thermostat
The thermostat cannot move. Raising the router off the floor, getting it out of a cupboard by the front door, or moving it a couple of metres towards the centre of the house often changes the hallway reading substantially.
Add a mesh node or access point in the hallway
This is the reliable fix. A single node roughly halfway, on mains power, usually lifts the thermostat from marginal to solid.
Thermostats are 2.4GHz only, almost without exception. That is a deliberate choice for range, and it means the 5GHz coverage you can see on your phone tells you nothing about what the thermostat experiences.
Cause 2: the router setup confuses it
- Band steering. If your router broadcasts one name for both bands, the thermostat may attempt to associate with 5GHz and fail, or get steered mid-session. Splitting the bands into separate names, or temporarily disabling 5GHz during setup, solves a surprising number of these.
- WPA3 only mode. Older thermostats support WPA2 and fail on WPA3-only networks. Set the router to WPA2/WPA3 mixed mode.
- Channel width. Set 2.4GHz to 20MHz. Many simple devices handle 40MHz channels poorly.
- Guest network isolation. If the thermostat is on a guest network with client isolation enabled, the app on your phone may not reach it locally, giving the appearance of a dropout.
- DHCP lease exhaustion. A small address pool with many devices can leave the thermostat without an address after a reboot. Reserve a static address for it in the router.
Cause 3: not enough power
This one is specific and worth understanding. Many thermostats in older installations have no dedicated power wire, known in the United States as a C wire. Instead they harvest small amounts of power by leaking current through the heating control circuit while it is idle. That works for a display and a relay, and it is marginal for a Wi-Fi radio, which draws current in bursts when it transmits.
The symptom is distinctive: the thermostat drops offline repeatedly, often more in mild weather when the heating runs less, and it may also reboot or show a low battery warning. Nest units in particular log this as a battery voltage issue.
The fixes are, in order of preference: run a proper C wire from the boiler or air handler, fit a C wire adapter kit which uses the existing wires to deliver power, or use a plug-in transformer. Any of those is a permanent fix. Turning the display brightness down and disabling features to reduce draw is a workaround, not a solution.
Heating wiring carries mains voltage in many systems, and boiler wiring in particular should be treated as such. If you are not confident identifying which terminals are live, this is work for a heating engineer or electrician rather than a weekend job.
Cause 4: the cloud, not your house
Before rebuilding your network, check whether the manufacturer is having an outage. If the thermostat shows as connected to Wi-Fi but the app says it is offline, that is a cloud problem, not a local one. Manufacturer status pages and outage trackers will tell you within a minute. These happen more often than most people realise, and nothing you do at home will help.
A sensible order of work
Check the manufacturer status page
Rule out an outage before touching anything.
Read the signal strength on the thermostat
This single number tells you whether to work on coverage or on power.
Reserve a fixed IP address for it in the router
Eliminates address conflicts and lease problems permanently, and takes two minutes.
Set 2.4GHz to 20MHz width and WPA2/WPA3 mixed
Removes two common compatibility problems at once.
Add coverage if signal is weak
A mesh node or access point in the hallway, on mains power.
Address power if the unit reboots or warns about battery
C wire, adapter kit, or transformer. This is the fix that ends the problem for good on power-starved installs.
Will my heating still work if the thermostat is offline?
Yes, on essentially every system. The thermostat keeps its schedule and controls the boiler locally. You lose remote control and app features until it reconnects.
Why does it drop off more in spring and autumn?
On systems without a dedicated power wire, the thermostat harvests power while the heating circuit is idle and tops up when it runs. In mild weather the heating runs rarely, so there is less opportunity to charge, and the Wi-Fi radio is the first thing to suffer.
Is a Wi-Fi extender enough, or do I need mesh?
An extender in a good position often works, since a thermostat needs very little bandwidth. A mesh node is more reliable because it handles roaming and backhaul better, but for a single fixed device an extender is usually adequate.
Should I put the thermostat on a guest network?
Only if the guest network allows local access from your phone. Client isolation, which most guest networks enable by default, will break the app’s local control. A separate IoT network without isolation is a better approach.
Does the thermostat need to be reset after router changes?
If you change the network name or password, yes, it will need reconnecting. If you only change channel or width settings, it should reconnect on its own within a few minutes.
In summary
Read the signal strength the thermostat reports. Weak signal means adding coverage in the hallway, which is the most common fix. Reboots and battery warnings mean a power problem that only a C wire or adapter will solve. Along the way, reserve a fixed address, use 20MHz channel width, and allow WPA2. Those changes cost nothing and remove most of the remaining causes.
