Thermostat Error Codes: Nest, Honeywell & Smart Thermostats Explained

A thermostat error code is not the heating or cooling equipment confessing — it is the wall control reporting on its own world: the power arriving on its wires, the wires it can detect, its sensors, its radio and its connection to your phone. The equipment keeps its own, separate fault codes on its own control board. This hub explains how the two reporting systems divide the work, decodes the two great thermostat dialects — Nest's letter families and Honeywell's numeric alert tables — and covers the shared power story (the C wire) that produces more thermostat codes than every equipment fault combined.

Two machines, one wall plate: thermostat codes are not furnace codes

A heating and cooling system has two brains, and they file separate reports. The equipment brain — the furnace or air-handler control board, the outdoor unit's control — watches combustion, refrigerant pressures, airflow and its own safety chain, and reports what it finds in its own code system: counted LED flashes or display digits inside a cabinet you may never open. The thermostat brain watches a different beat entirely. It knows what power is arriving on each of its wires, whether a wire it expects is electrically present, what its own temperature and humidity sensors read, whether its radio can reach your router, and whether the room temperature is responding when it calls for heating or cooling. A thermostat code is drawn from that list. It cannot see a cracked igniter, a low refrigerant charge or a failing pressure switch, because none of those things happen on its side of the wall.

That division explains the shape of almost every thermostat code you will ever meet. Nest's help codes are dominated by power and wiring reports — no power to this wire, that wire not detected, an overcurrent on another wire — because power and wiring are what a thermostat can measure. Honeywell's T-series table is dominated by the thermostat's own sensors, its memory, its Wi-Fi radio and its maintenance timers, for the same reason. When a thermostat does relay an equipment problem, it says so in equipment-agnostic language: Honeywell's 164 is literally 'heat pump needs service', with the diagnosis left to the heat pump, and Nest's Furnace Heads-Up notices report that the furnace shut down early or failed to move the temperature, without pretending to know why. The practical rule follows directly: a thermostat code tells you which system to interrogate next. If the code is about power, wires, sensors or radios, the answer is at the wall or in the wiring. If it points at the equipment, the equipment's own board — not the thermostat — holds the specific fault, and that is the code a technician will read first on arrival.

Two reporting styles: Nest's letter families vs Honeywell's numeric alerts

Nest and Honeywell looked at the same problem — a small computer on a wall that must explain itself — and chose opposite languages. Nest speaks in letter families, and the letter is the severity and the subject in one character. E codes are critical help codes: Google states that the thermostat will not let you control heating or cooling and the message will not go away until the cause is fixed — E is the family of dead power feeds (E73 no power to the Rc wire, E74 no power to Rh), undetected wires (E157, E158, E194) and overcurrents (the E52-E58 group). N codes are notices, one step down: N260 and N410 say a C wire or Nest Power Connector is recommended, N261 and N411 say the C wire that is fitted is delivering low power — the system runs, but Google is telling you its power supply is marginal. TD codes leave the HVAC system entirely: they report Wi-Fi, app and setup connection problems. M codes are a mixed drawer that includes Google's Furnace Heads-Up reports (M6: the furnace shuts down within minutes of heating — Google's own first suspect is a clogged air filter) alongside setup and power renderings of the same events other models show as E codes.

Honeywell (Resideo) speaks in numbers — three-digit alert codes on its T-series thermostats (T5, T6 Pro, Lyric T6 Pro Wi-Fi, T6 Pro Smart, T6 Pro Z-Wave) — and organises them by subject rather than severity. The 160s and 170s are the service family: 164 heat pump needs service, 168 Wi-Fi radio error, 170 internal memory error, 173 the thermostat's own temperature sensor, 177 and 178 the wired indoor and outdoor sensors. The 180s (181-189) are not faults at all but maintenance timers — replace filter, humidifier pad, UV bulb — that expire on schedule and reset when you dismiss them after doing the chore. Around them sit the notices (171 set the date and time, 175 AC power resumed — an event log, not a fault) and the connection reports (210/388 register online, 399 no internet, 400 no Wi-Fi signal, 508 Wi-Fi not configured). Two warnings keep Honeywell numbers honest. The same brand runs other dialects on other lines: the older VisionPRO IAQ communicating system uses its own short error codes (027, 035-040, 089-091 and friends) that must never be read with the T-series table, and the VisionPRO 8000 with RedLINK uses no numbers at all, only plain-text alert messages. And the 'E1 to E5' Honeywell tables pasted across the internet appear in no Resideo manual checked for this site — on Honeywell thermostats, E-prefixed codes are a rumour, not a dialect.

The C wire: one conductor behind half of all thermostat codes

Almost every smart-thermostat power code is the same sentence in different words: this device needs more steady power than the old wiring gives it. A traditional thermostat was a switch with a battery or a clock motor; a modern one is a Wi-Fi computer with a colour screen, and it eats continuously. The 24 VAC that runs the whole control system arrives on the R wire, but a circuit needs a return path, and that return is the C (common) wire. With a C wire fitted, the thermostat draws its power cleanly across R and C, twenty-four hours a day, whether the equipment runs or not. Without one, the thermostat must steal power in sips through the equipment's own control circuits — a trick that works until it doesn't: the sipping can chatter relays, starve the thermostat during long equipment runs, or vanish entirely when the equipment's safety controls open the circuit the thermostat was sipping from.

Each brand's documentation confesses the same dependency in its own dialect. Google maintains an entire code group for it — E1 and E297 (a C wire is required), N260/N410 (a C wire or Power Connector is recommended), N261/N411 (the fitted C wire delivers low power) — and sells the confession as hardware: the Nest Power Connector, a module fitted at the furnace or air handler that lets a system without a spare wire feed the thermostat properly. Google also documents the failure mode that proves the point: on a thermostat with no C wire, power arrives through the Y1 wire, so when the air conditioner stops sending it — its cold-weather safety cut-out, or a breakdown — a whole family of codes (E10, E30, E66, E80, E116, E160, E196, E296, and M13) reports 'no power to Y1'. Ecobee's answer to the identical physics is its Power Extender Kit, installed at the control board to manufacture a common connection from the wires already in the wall. The owner's translation is simple: if your thermostat's codes keep circling power — any brand, any code number — suspect the missing or marginal C wire before you suspect the thermostat, and treat 'fit a proper C wire or the maker's power kit' as the permanent fix that the temporary fixes (charging a Nest by USB, swapping batteries) are only bridging toward.

'Check system': when the thermostat is a messenger, not the patient

The most misread thermostat messages are the vague ones — 'check system', 'system needs service', an alert with no number at all — because they feel like the thermostat accusing the equipment while refusing to say of what. Read correctly, that vagueness is honesty. The thermostat genuinely does not know what is wrong with the equipment; it knows only the few equipment facts visible from the wall: a call for heating or cooling went out and the room did not respond as expected, or a fault input wired to the thermostat (the heat-pump fault terminal behind Honeywell's 164) was asserted by the outdoor unit, or power that the equipment normally sends simply stopped arriving — which is why a summer power code on a Nest is documented by Google as, most likely, the HVAC system having broken down and stopped powering the thermostat. The thermostat is a witness reporting behaviour, and behaviour is all it has.

So the correct response to a messenger message is not to reset the messenger. It is to walk the short list of things the witness can actually testify about, in order. Was the call real — mode set correctly, setpoint beyond room temperature, schedule or hold not overriding it? Did anything respond — indoor fan, outdoor unit, warm or cool air at a register, and for how long before it stopped? What does the thermostat itself report — a power code, a wiring code, or nothing but the vague alert? And what changed recently — a filter long overdue (the documented first suspect behind both Nest's Furnace Heads-Up and many equipment shutdowns), a condensate drain that may have lifted its float switch and cut the system, a cover left ajar on its safety switch after a service visit? If the equipment runs from its own test controls but ignores the thermostat, the wiring and the call path are the story. If the equipment will not run at all, its own board holds the specific code, and the thermostat's vague message has done its whole job: it got you to look. Quote both reports to the technician — the thermostat's words and the equipment's code — because each brain saw a different half of the same failure.

Ecobee: the brand that answers in sentences, not codes

Ecobee is included on this page under a deliberate honesty rule: ecobee's own support documentation describes a thermostat that reports in plain language, and publishes no numeric error-code table of the Nest or Honeywell kind — so this page invents none for it. What ecobee documents is a two-part system of Reminders and Alerts, configurable on the thermostat and in the app, and delivered on screen, in the app and by email. Reminders are the maintenance calendar: HVAC maintenance due, furnace filter, UV lamp, and the humidifier, dehumidifier and ventilator filter reminders for systems configured to control those accessories. Alerts are the performance watch: low- and high-temperature alerts that warn of freeze or heat damage risk, low- and high-humidity alerts, an auxiliary-heat runtime alert (ecobee's default threshold is aux heat running more than three hours in twenty-four), an alert if auxiliary heat is called while the outdoor temperature is above its setpoint — and, most relevant here, heating and cooling alerts proper: ecobee states that you can enable or disable 'alerts indicating that the system failed to heat or cool', which is its version of the messenger message above, delivered as a sentence a homeowner can act on rather than a number to look up.

Two practical consequences follow. First, an ecobee owner searching for 'ecobee error code E-something' is chasing a table that does not exist in the maker's documentation; the productive search is the alert's own words, read literally, plus the reminder list under the thermostat's Reminders and Alerts settings. Second, ecobee's power story is the same C-wire story told without codes: the thermostat needs a common connection, homes without a C wire use the Power Extender Kit fitted at the control board (ecobee's support walks that installation wire by wire, and notes the kit replaces even a Honeywell Wire Saver module where one is fitted), and a blank ecobee screen is therefore a power-path report in everything but format — breaker, equipment switch, control-board fuse, drain float switch and the C/PEK connection are the checks, in the same order as for any other brand's no-power code. The lesson generalises beyond ecobee: the newest thermostat language is sentences, and the skill this page teaches — separate the power report from the wiring report from the equipment report — works whether the thermostat expresses it as E74, as 175, or as a plain English sentence in your inbox.

Nest thermostat error codes

Nest (Google) reports 'help codes' in letter families: E codes are critical — Google states the thermostat won't let you control heating or cooling and the message won't go away until the cause is fixed — and they cover power losses by wire (E73 Rc, E74 Rh, E72 no power wires at all), undetected wires, and equipment overcurrents. N codes are notices, mostly about C-wire power (N260/N410 fit one, N261/N411 the fitted one is weak); TD codes are Wi-Fi/app/setup connection reports; M codes mix Furnace Heads-Up equipment warnings with setup and power renderings. Google documents many codes as groups sharing one meaning, so quote the exact code — the group it belongs to is the diagnosis.

Full list: Nest Thermostat Error Codes List — every verified Nest code with causes and first fixes.

Honeywell thermostat error codes

Honeywell Home thermostats (Resideo) report numeric alerts, but the table depends on the line. The current T-series (T5, T6 Pro, Lyric T6 Pro Wi-Fi, T6 Pro Smart, T6 Pro Z-Wave) uses three-digit codes: service faults in the 160s-170s, maintenance-timer reminders at 181-189, informational notices such as 175 (AC power resumed), and Wi-Fi/registration reports at 210/388/399/400/508. The older VisionPRO IAQ communicating system uses a different, shorter code set, and the VisionPRO 8000 with RedLINK shows plain-text messages instead of numbers — and no Resideo manual publishes the 'E1-E5' codes that third-party sites attribute to Honeywell.

Full list: Honeywell Thermostat Error Codes List — every verified Honeywell code with causes and first fixes.

The same event, three dialects: how one power loss is reported

Which list do you actually need? Model first, code second

Every thermostat code lookup fails the same way: the code is searched without the model, and the internet returns the wrong dialect's answer with total confidence. The thermostat world punishes that shortcut harder than most, because one brand can run three systems at once — a Honeywell number from the T-series table means nothing on a VisionPRO IAQ display and cannot even appear on a VisionPRO 8000 — and one event can wear three codes across a single brand's generations, as Nest's Rh power loss does (E4, E24, E74 by generation, E195 on single-R bases). The discipline that prevents all of it takes thirty seconds: name the exact model (printed on the thermostat, in its settings' technical info, or in the app), confirm which reporting system that model uses, and only then open a table. The brand hubs below are organised exactly that way, with each code scoped to the models whose manuals publish it.

Two corollaries are worth more than any single code definition. First, a code that cannot be found in your model's manual probably does not belong to your thermostat — it belongs to another brand's table that a content site has relabelled, which is precisely how 'Honeywell E3' and similar phantom codes are manufactured. Second, when you call for help, quote the pair — code and model — every time: 'E74 on a Learning Thermostat' and '173 on a T6 Pro Smart' are diagnoses a technician can prepare for, while 'an error code on my thermostat' starts the visit from zero. Photograph the screen before you dismiss or reset anything; on both major systems a dismissed reminder or a cleared fault takes its evidence with it.

Stop, schedule, or ignore: reading a thermostat code's urgency

Thermostat codes sort into three urgency classes, and the class — not the scariness of the wording — should set your pace. Class one is stop-and-fix: codes that mean control is lost or a safety-relevant supply has failed. Nest is explicit about its version — E codes block heating and cooling control until cured, and an unfixed power loss drains the thermostat's battery until it disconnects or shuts down, turning one fault into two. Honeywell's equivalent is behavioural rather than stated: the T-series fault alerts (164, 168, 170, 173, 177, 178) cannot be snoozed or dismissed the way reminders can, and an alert that refuses dismissal is the thermostat telling you a measured fault is still present. Class two is schedule-the-chore: the maintenance timers (Honeywell 181-189) and their equivalents, which ask for a filter, a pad or a bulb and then a timer reset — urgent only in the sense that dismissing them undone restarts a countdown that no longer tracks the equipment's real condition. Class three is read-and-note: the event logs and administrative prompts (175 power resumed, 171 set the clock, 210/388 register online, Nest's N notices) that ask for thirty seconds of administration or nothing at all.

The traps sit at the class boundaries. A class-three code that keeps returning graduates: Honeywell's 175 is trivia once and a power-chain diagnosis the fifth time, because the thermostat is logging real interruptions, each of which also restarts the equipment's compressor-protection delay. A class-two code dismissed repeatedly without the chore quietly becomes a class-one cause, as the clogged filter behind it starts shutting the equipment down — the documented first suspect in Nest's Furnace Heads-Up. And a class-one code 'fixed' by resetting alone is not fixed at all: on both systems a standing fault re-reports itself, and the reset has only cost you the history that would have shown its pattern. When in doubt, ask the class question in the manufacturer's own terms — can this be dismissed, and does control still work — before asking what the code 'means'.

Keep the evidence: the thermostat remembers less than you think

Thermostats are forgetful witnesses. Reminders restart their timers when dismissed, fault alerts clear when their cause clears, app notifications scroll away, and a thermostat that loses power long enough forgets it ever had a complaint. Intermittent problems — the power feed that drops only on the coldest night, the drain that backs up only in peak cooling — are therefore diagnosed from records the homeowner keeps, not from anything the device retains. The useful record is small: the code exactly as shown (letter, digits, and the model's name), a photograph of the screen, the date and time, what the system was doing, and what the house felt like. Three entries usually expose the pattern — power events that match storms, shutdowns that match long cooling runs, alerts that follow every filter change when a door switch gets disturbed.

Bring that log to any service visit, and mention it when you book: a technician who knows a thermostat logged repeated power losses arrives with a meter and a plan for the power chain, not with a replacement thermostat to try. The log also protects you at the two moments thermostat evidence usually evaporates — a warranty dispute, where 'it kept showing a code' is a claim and a dated photo log is proof, and a home sale, where a documented, serviced fault history reads as diligence rather than trouble. None of this requires opening the equipment: the thermostat's whole design purpose is to be the house's witness stand, and a phone camera is all it takes to keep its testimony.

How to diagnose any thermostat code

Work the problem in this order: (1) write the code down exactly, including its letter prefix — on a smart thermostat the prefix names the family (a power report, a wiring report, a connection report), and the family matters more than the number; (2) remember what the thermostat is: a witness, not the patient. Most thermostat codes report the heating/cooling equipment — a furnace that lost power, a float switch that tripped, a wire that is not seated — so the second stop is always the equipment itself: is its power switch on, its breaker untripped, its access panel fully closed (the panel switch kills power on many furnaces), its condensate drain clear; (3) check the wiring at the thermostat base with the equipment powered OFF — a wire pushed beside its terminal instead of into it is the classic cause of wire-not-detected codes; (4) restore power and let the thermostat re-read the system before judging the result, because power codes clear only when the equipment actually delivers power again; (5) if the equipment runs normally from its own test mode but the thermostat still reports the fault, the wiring run or the thermostat itself is the remaining suspect — and 24V wiring faults inside walls or at the equipment board are a technician's job.

Frequently asked questions

Related guides