Smart thermostats: wiring, heat pumps, and what Matter actually controls
A thermostat is the one smart device that can leave you cold at 3am, so the wiring question and the cloud question both matter more here than anywhere else in the house.
The C-wire question, answered properly#
A US low-voltage thermostat sits on a 24 VAC control circuit fed by a transformer in the furnace or air handler. The R terminal supplies power. W, Y, G and O/B are switched outputs that close a relay to call for heat, cooling, fan or reversing valve. The C terminal, the common, is the return leg that completes the circuit. Without it, a thermostat has a live wire and no path back, so it cannot draw continuous power.
A mercury or bimetal thermostat did not care. A device with a screen, a Wi-Fi radio and a processor does. That is the whole C-wire problem.
There are four ways out, in the order you should consider them:
- You already have one. Pull the old thermostat off the wall and look. A blue or black wire tucked unused behind the plate is extremely common in homes wired since the 1990s, because installers ran five-conductor cable and used four.
- An adapter at the furnace. ecobee's Power Extender Kit multiplexes the fan wire so the existing bundle can carry a common. It costs $24.99, ships in the box with every ecobee except the Essential and Lite, and works only on 24 VAC systems. ecobee's own figure is that the kit was needed in fewer than 15% of installations, which is a useful reality check against how much the internet worries about this.
- Power sharing. Google's Nest thermostats pulse tiny amounts of current through a switched leg and store it, so Google states a C-wire is not required in most homes and that the 4th generation Nest Learning Thermostat works with about 85% of systems. It works, and it is also the mechanism behind the classic failure below.
- Run a new cable. If the run is short and accessible, this is the permanent answer and costs an afternoon.
Four systems genuinely cannot take a standard smart thermostat, and no adapter fixes them: millivolt systems (a self-powered gas valve on a floor or wall heater), line-voltage 120 or 240 V electric baseboard, proprietary communicating equipment where the thermostat speaks a manufacturer bus rather than switching relays, and dual-transformer installs. ecobee names all four as incompatible on its compatibility checker, and other brands draw the same lines. Mini-splits are a fifth case: they take infrared, and Matter has no infrared abstraction at all, so they need a bridge. The radio decision table covers where infrared fits.
What Matter exposes, and what it does not#
The Matter thermostat cluster is one of the original 1.0 device types, and both Google and Amazon document it as a single cluster mapped onto a thermostat control interface. It is deliberately small.
| Carried over Matter | Stays in the vendor app |
|---|---|
| Local (current) temperature | Learning and auto-schedule |
| System mode: off, heat, cool, auto | Geofencing and presence |
| Occupied heating and cooling setpoints | Multi-stage and auxiliary heat status |
| Setback, setpoint hold, basic and enhanced schedules | Dual-fuel changeover |
| Presets, and thermostat suggestions added in 1.6 | Humidifier and dehumidifier control |
| Running state (is it calling for heat) | Remote room sensor values, HRV, filter reminders |
Two caveats on that left column. Schedules and presets exist in the specification, but the ecosystems mostly ignore them and keep scheduling in their own automation engine, so in practice you write the schedule in Google Home, Apple Home or Home Assistant rather than pushing it to the device. And thermostat suggestions, added in Matter 1.6 in June 2026, has no known controller implementation yet.
The right column is the important one, because it is not a controller lag problem. Multi-stage heating and cooling, auxiliary and emergency heat, and dual-fuel changeover are not modeled in Matter at all. No firmware update exposes them. That is a specification gap in the sense described in what Matter still cannot do.
Heat pumps and multi-stage systems#
This is where the gap bites. A modern US heat pump install is rarely a single relay.
- Two-stage or variable capacity. The thermostat picks a stage based on how far the room is from setpoint and how long the call has run. Matter gives you a setpoint and a mode. Which stage is running, and the minimum runtime logic that protects the compressor, are firmware.
- Auxiliary and emergency heat. Electric resistance strips or a gas furnace back up the heat pump below a balance point. The lockout temperature, the staging delay and the "aux heat is running" status are the numbers that decide your December bill, and none of them cross Matter.
- Dual fuel. Switching between heat pump and furnace by outdoor temperature or by cost per BTU is entirely vendor logic.
- Reversing valve orientation. O versus B is a wiring and configuration choice made once, in the vendor setup flow.
The practical consequence: on a heat pump, you should choose the thermostat by how good its native staging and aux-heat control is, then treat Matter or HomeKit as the layer that gives you a temperature reading in your dashboard and lets a voice assistant nudge the setpoint. ecobee's Smart Thermostat Premium, for example, publishes support for heat pumps at two heating and two cooling stages plus two stages of auxiliary heat. That is the specification that should drive the purchase, not the logo on the box.
The best available lesson: the October 2025 Nest cutoff#
On 25 October 2025, Google ended support for the 1st and 2nd generation Nest Learning Thermostats, including the 2014 European 2nd generation model. Google's own support article is blunt about what happened: the devices were unpaired and removed from both the Nest app and the Google Home app, which also removed third-party assistants, Home/Away Assist, multi-device Eco mode, and the link that let a Nest Protect trigger an emergency furnace shutoff. Remote control, notifications and status all stopped.
They still heat and cool a house. You can still turn the dial and the pre-set schedules keep running. But a product sold in 2011 and 2012 as a connected, learning thermostat became a manual thermostat with a nice display on a scheduled date, because the intelligence lived on a server.
Three things are worth taking from this, and none of them are "avoid Google".
A cloud-tied thermostat has a termination date you do not control. Fourteen years of support is genuinely long for consumer electronics. It is short for a device screwed to a wall next to a furnace that will outlive it. Price that in.
The failure was graceful, and that is the bar. The thermostat kept its schedule and kept controlling the HVAC. Compare that with what happened when Belkin shut Wemo down in January 2026. Ask, before buying, what the device does with no server: a thermostat that goes dumb but keeps running is acceptable, one that stops calling for heat is not.
Matter changes the risk, but only if the device implements it. The current Nest Learning Thermostat (4th generation) is Matter certified, so if Google discontinued the Nest cloud tomorrow, a Home Assistant or SmartThings controller on your own network could still hold setpoints and modes. That is a real improvement, and it is also a smaller safety net than it sounds, because everything in the right column of the table above dies with the app regardless.
How to buy one#
One more structural point. Matter 1.4 defined heat pump and water heater device types in November 2024, and as of September 2026 there are zero certified products for either. If you are looking at whole-home electrification and hoping the standard will unify it, read solar, batteries and EV charging first, because that page has the same shape and the same conclusion.
Do I need a C-wire for a smart thermostat?
Usually not. Many homes already have an unused common wire behind the plate. ecobee includes a Power Extender Kit that creates one at the furnace and says fewer than 15% of its installs need it, and Nest thermostats use power sharing so Google states a C-wire is not required in most homes. Millivolt, line-voltage and communicating systems are the real exclusions.
Does Matter work with heat pumps?
Only for the basics. Matter carries current temperature, mode and setpoints, and a heat pump accepts those fine. Staging, auxiliary and emergency heat, dual-fuel changeover and balance-point logic are not modeled in Matter at all, so they stay in the manufacturer's app no matter which platform you use.
Why did my Nest thermostat stop working in the app?
If it is a 1st or 2nd generation Nest Learning Thermostat, Google ended support on 25 October 2025 and removed it from both the Nest and Google Home apps. It still heats and cools from the dial and keeps its schedule, but remote control, notifications and third-party assistants are gone permanently.
Is ecobee Matter compatible?
No. As of September 2026 ecobee does not appear in the alliance's certified product database, and its own integration page lists Apple Home, Alexa, Google Assistant and SmartThings rather than Matter. The thermostats are good; they are tied to ecobee's cloud and those four ecosystem integrations.
Can Matter set my thermostat schedule?
The specification includes schedules and presets, but the mainstream ecosystems keep scheduling in their own automation engines instead of writing it to the device. In practice you build the schedule in the vendor app or in your platform's automations, not through Matter.
What happens to my smart thermostat during an internet outage?
It depends on the product. Good ones keep the current schedule and setpoint and keep switching the HVAC, losing only remote access and voice. Some lose scheduling entirely and hold the last setpoint. Test it before winter by pulling the router for ten minutes.
Should I buy a thermostat with a subscription?
For a thermostat, no subscription should be required for temperature control or scheduling. Paid tiers that add utility demand-response payments or HVAC health monitoring are fine as extras. If basic scheduling sits behind a fee, that is a signal about where the product is heading.
Primary sources
Specification and vendor documentation we checked while writing this page. Where a claim depends on firmware behaviour rather than a published spec, the page says so inline.