Nest Thermostat will not stay connected to Wi-Fi

Usually not — Google states it is designed to work without one. But Google also names the exceptions: a heating-only or cooling-only system, or one using a zone controller, may need a C wire or another power-supply accessory. So the honest answer is that it normally does not, and your specific system may.

Probably not. The display sits behind a mirrored glass lens and reads as a plain mirror when asleep — that is the intended appearance. The motion sensor is what wakes it, so a thermostat in a corridor nobody walks down will appear dead far more often than one in a living room.

Yes, and on this model that is a real first step. It uses 2 AAA 1.5V alkaline cells for backup, user-replaceable — unlike Nest's rechargeable thermostats where a low-power symptom means a wiring investigation rather than a trip to the shop.

No. Google states it works with multi-zone systems but requires one thermostat per zone. A single unit controlling several zones is not a configuration this model supports, and trying to make one do it is the source of a lot of unexplained behaviour.

It works with most 24V systems — furnaces, air conditioners, boilers and heat pumps, forced air or radiant. Specifically: conventional systems with one stage of heating and cooling plus a second stage of either, and heat pumps with one stage of heating and cooling plus aux or emergency heat. Systems outside that are where compatibility problems come from.

Yes — 802.11b/g/n at 2.4 GHz and 802.11a/n at 5 GHz, plus Bluetooth Low Energy. It is dual-band, unlike much smart-home hardware.

Less than 1 kWh per month, per Google's specification. The thermostat's own consumption is not a meaningful factor in a heating bill either way.

Yes — it is Matter certified, so it can be controlled from Google Home and other Matter platforms. Capabilities exposed through Matter are those the standard defines; anything beyond that stays in the Google Home app.

Because they are not comparable. A phone has a larger antenna, far more transmit power and a battery sized for it. A small smart-home device — particularly a battery one, which throttles its radio to save charge — routinely reports poor signal where a phone reports full. Use the figure the device reports for itself.

Regularity that precise is almost always the router's DHCP lease. The device loses its address, fails to renew it, and drops until something forces a rejoin. A reservation against its MAC address fixes it permanently; rebooting only restarts the clock.

Not usually. Splitting them is the fastest way to prove whether band steering is the cause, and once proved, most routers allow the device to be pinned to a band without keeping the names separate. Keep the split only if pinning is unavailable.

Only if the problem is genuinely range. An extender on a congested channel adds another talker to the same congested channel and can make throughput worse. Establish whether you have a range problem or an interference problem first — they look identical from the app and have opposite fixes.

It is probably associated with a different node. Mesh systems rarely force a client that has already joined to move, so a device can be inches from one node and talking to one across the house. Power-cycling it beside the intended node forces a fresh association.

Check the security mode first. WPA3-only, IoT client isolation and DNS filtering have all changed defaults across firmware generations, and a device that requires WPA2 will fail against a WPA3-only router with no message that says so.

Fewer than most people assume — consumer routers have finite client tables, and exceeding one produces drops with no error anywhere. The tell is that a device drops when a new device joins, and which one drops varies.

Considerably. Metal, masonry, foil-backed insulation, wire-reinforced glass and low-emissivity window coatings all attenuate 2.4 GHz far more than plain distance. A large change in reported signal over a short move identifies an obstruction rather than range.

Longer than the previous drop interval. A device that used to drop every two days and has now run for ten minutes has proved nothing. This is the single most common way an unfixed Wi-Fi fault gets declared solved.

A DHCP reservation at the router is better than a static address set on the device. The reservation keeps the router in charge of the address pool, so it cannot hand the same address to something else — which is the failure a manually set static address invites.

That is a genuinely useful result. The radio link, the credentials and the band are all fine, so everything in this page about signal and placement is ruled out. What remains is the path from the router onward — DNS filtering, a firewall rule, or the provider's own service.

No. It is scoped to GA01334. Google Nest/Home device; Matter/Thread role, wired/battery power, subscription and Google Home migration vary.

Record the complete model identifier, exact message or indicator, software/firmware where visible, the operating stage and what still works.

A reset can erase accounts, networks, maps, schedules or preferences without distinguishing Wi-Fi, disconnecting. The ordered checks preserve that evidence.

Do not weaken router security for a legacy device without isolation.