Nest Thermostat E294 Error Code: Meaning, Causes & Fix

R wire is required — Google's master help-code table defines E294 with exactly that sentence, and routes it to 'Troubleshoot wires in Home app'.

E294 is a configuration code wearing a power code's clothes, and reading it correctly saves a lot of breaker-flipping. It belongs to Google's wire-configuration group for the newer Home-app-configured thermostats (the group is E255, E257, E258, E264, E269, E294, E405, E414 and E419), and Google states the group's cause plainly: you'll get this code if the wires in your thermostat weren't configured properly in the Home app. In other words, as far as the thermostat's setup knows, there is no R wire — the one wire every heating and cooling system uses to deliver power to the thermostat — even though a wire may be physically sitting in the base. The mismatch can run in either direction: an R wire connected at the base but never entered (or entered in the wrong place) during app setup, or wiring information carried over from a setup that no longer matches what is on the wall. That is why Google's documented fix for the whole group is not a wiring repair but a configuration rebuild: factory-reset the thermostat and add it back in the Google Home app, paying extra attention when you re-enter the wiring information. E294 must also be separated from its near neighbours, because Google documents them as different reports. E298 ('No system power', on the Nest Thermostat) and E448 (the same 'No system power' alert on the Learning Thermostat 4th gen) are genuine power failures: Google's dedicated No-power article lists their causes as incorrect wiring, a system that requires a C wire with none connected, the HVAC system powered off at the breaker, fuse box or switch or a power cut, or another equipment issue preventing the system from sending power — and its diagnostic screen is Settings > Equipment > Wiring info, where a wire that isn't sending voltage shows grey. E294 says the setup lacks an R wire; E298/E448 say the system isn't sending power. A thermostat can move between them — fix a configuration so the R wire is properly declared, and a real power loss underneath it may then report honestly as E298/E448 — which is why the order of work matters: configuration first, power second, never the reverse.

What causes the E294 code on a Nest thermostat?

The wiring was not configured properly in the Google Home app

Google's stated cause for the entire E294 group, verbatim in substance: the wires in the thermostat weren't configured properly in the Home app. The R wire the thermostat requires was not entered, was entered against the wrong connector, or the setup was completed from wiring information that doesn't match the base — a photo of a previous thermostat read wrongly, or a setup finished before the wires were final.

The R wire is connected at the base but was never declared in setup

The physical/configuration split is the heart of this code: a wire can sit correctly in the R connector while the app's wiring record contains no R wire at all. Google's undetected-wire article describes the same gap for wires generally — a wire detected in a connector but not entered into the app during setup shows as 'unspecified' in the Home app ('unconfigured' on the thermostat or in the Nest app) — and an undeclared wire the thermostat requires is exactly what 'R wire is required' reports.

The wires are in the wrong connectors, so the declared R wire isn't where setup expects it

Google's fix flow for this group ends, if the reset alone doesn't cure it, at the physical check: 'check that your system wires are connected to the right connectors — use the wiring diagram the app gave you during setup to move the wires to the right connectors.' An R feed landed in the wrong connector during installation produces a thermostat whose configuration and whose base disagree about the most important wire it has.

A real no-power condition underneath the configuration fault (the E298/E448 story)

Google's No-power article is careful to list its own causes separately — incorrect wiring, a C-wire-required system with no C wire connected, the system powered off, or another equipment issue stopping power reaching the thermostat wires — because a configuration fix can unmask them. If E294 clears after the reset and re-setup and is replaced by E298 or E448, nothing has gone wrong: the thermostat can now see its R wire properly, and is reporting, accurately, that no power is arriving on it. From there the diagnosis leaves this page and follows the No-power flow.

Setup was interrupted or carried over from a previous thermostat or home

Google's prescribed cure — a factory reset and a fresh add in the Home app — is also the diagnostic tell: this group of codes is generated by setup state, and setup state survives ordinary restarts. A setup abandoned half-finished, a thermostat moved from another system, or wiring information edited in one app and not the other all leave the configuration in a state the thermostat can't reconcile with its base, and E294 is how it says so when the wire at issue is R.

Checks to run before you replace anything

1. Read the code's routing before touching anything: Google sends E294 to 'Troubleshoot wires in Home app', not to 'Troubleshoot power'. Breakers and wire-pulling are not the first moves for this code — the Home app's wiring record is.
2. Compare the app's wiring record with the base: in the Google Home app, open the thermostat's wiring/equipment settings and note exactly which wires the app believes are connected, and whether an R (or Rc/Rh) wire is among them. A record with no R wire, on a thermostat that plainly has one, is the fault already found.
3. Turn system power OFF at the breaker, fuse box or system switch, pull the display, and photograph the base wiring before changing anything: confirm there is a wire in the R connector (or the correct Rc/Rh arrangement for your system), fully seated with 1/3 to 1/2 inch of clean, straight copper and the connector button staying down. That photograph is also the record Google's flow tells you to re-enter from.
4. Check the declared wires against the equipment, not just the base: Google's flow for this group says that if you don't have the wiring diagram, refer to the picture of your old thermostat's wires from installation — and if you don't have that either, access the system's control board, take a picture of the wires there, and use it to enter the wires into the app. The control board is the ground truth for which wire is really R.
5. Decide which report you actually have: if Wiring info (Settings > Equipment > Wiring info) shows wires in grey — Google's No-power article's sign that a wire isn't sending voltage, with all-grey wires pointing at a system that is powered off — you may be looking at the E298/E448 power story underneath, and its causes (system off, C-wire-required system, equipment fault) join the list once the configuration is corrected.

How to fix nest e294?

1. Do Google's documented fix for this group, in its order: factory-reset the thermostat, then add it back in the Google Home app, paying extra attention to the instructions when you re-enter your wiring information — enter the R wire (and every other wire) exactly as it is connected at the base and at the control board. This deliberate reset is the cure for a configuration code, unlike a power code, where resetting cures nothing.
2. Correct the physical side if the comparison exposed it: with power off, move any wire that is in the wrong connector to match the wiring diagram the app gives you during the new setup, reseat the R wire fully (clean straight copper, button staying down), reattach the display until it clicks, and restore power.
3. If E294 is replaced by E298 or E448 after a clean re-setup, switch flows, don't repeat the reset: work Google's No-power article — confirm the system is powered at the breaker, fuse box and system switch, check Wiring info for grey wires, reseat grey wires with power off, and connect a C wire or install the Nest Power Connector if yours is one of the system types Google names as requiring one (heat-only, cool-only, zone-controlled and heat pump systems).
4. If the thermostat still reports E294 after a careful factory reset, a correct re-entry of verified wiring, and wires proven to be in the right connectors, Google's flow for this group is exhausted — contact a local professional / Nest Pro to verify the system's wiring, because the disagreement is now between the equipment's actual wiring and what the thermostat can be configured to accept.
5. Do not 'fix' E294 by entering an R wire the system doesn't have, or by moving wires at the base to match a wrong app record: the configuration must describe the real system. A thermostat configured for wires that aren't there will simply trade E294 for a different wiring code — or worse, call for equipment it can't control.

The part that usually fails: No part — E294 is a configuration state, not a component failure

Nothing has worn out. The 'part' at fault is the wiring record in the Google Home app, corrected by Google's factory-reset-and-re-add flow with verified wiring information. A part only enters the story if the code unmasks a real E298/E448 power loss underneath — and then the failed thing is in the equipment's power delivery, diagnosed by a professional, not in the thermostat.

How to reset nest thermostat e294?

E294 is the rare Nest code where a reset IS the documented fix — but it is a specific reset, done a specific way. Google's flow for the wire-configuration group: reset the thermostat to factory defaults, add it back in the Google Home app (Tap Add at the top of the home screen and follow the on-screen instructions), and pay extra attention when re-entering the wiring info. A plain restart is not a substitute — it preserves the very configuration that produced the code. And the reset only cures the configuration half of the story: if a genuine power loss (the E298/E448 causes) is sitting underneath, the code that replaces E294 after a clean setup is information, not failure — follow the No-power flow for it instead of resetting again.

Nest help codes don't clear like appliance fault codes. Google states the rule for E codes plainly: they are critical, the thermostat won't allow you to control heating or cooling, and the message won't go away until the cause has been fixed — so the 'reset' for an E code is repairing its cause (power restored, wire reseated, configuration corrected) and letting the thermostat re-detect a healthy system. N codes are the opposite kind of message: if the system is running normally, Google's low-power guidance says you can dismiss the message and keep using the thermostat. Two genuine resets exist at the edges: a manual restart (on Nest Thermostat E and 3rd-gen Learning Thermostat, press and hold the ring for about 10 seconds until the screen turns off — Google reserves this for a stuck or frozen thermostat), and a factory reset, which Google's wire-configuration flow (the E294 group) uses deliberately: reset to factory defaults, add the thermostat back in the Google Home app, and re-enter the wiring info carefully. Neither reset repairs a standing power or wiring fault.

Why does the E294 code keep coming back?

An E294 that returns after a verified factory reset and careful re-setup means the configuration keeps diverging from the base: wires being moved at the equipment or the base without the app record being updated, a setup repeatedly completed from an old wiring photo that no longer matches the system, or a system whose actual wiring (for example a shared or jumpered R arrangement from a previous thermostat) can't be represented as entered. Stop re-resetting — each return is telling you the record and the reality disagree somewhere a photo of the control board, compared line by line with the app, will find faster than another reset will.

How to stop E294 coming back

• The wiring was not configured properly in the Google Home app: Google's stated cause for the entire E294 group, verbatim in substance: the wires in the thermostat weren't configured properly in the Home app. The R wire the thermostat requires was not entered, was entered against the wrong connector, or the setup was completed from wiring information that doesn't match the base — a photo of a previous thermostat read wrongly, or a setup finished before the wires were final.
• The R wire is connected at the base but was never declared in setup: The physical/configuration split is the heart of this code: a wire can sit correctly in the R connector while the app's wiring record contains no R wire at all. Google's undetected-wire article describes the same gap for wires generally — a wire detected in a connector but not entered into the app during setup shows as 'unspecified' in the Home app ('unconfigured' on the thermostat or in the Nest app) — and an undeclared wire the thermostat requires is exactly what 'R wire is required' reports.
• The wires are in the wrong connectors, so the declared R wire isn't where setup expects it: Google's fix flow for this group ends, if the reset alone doesn't cure it, at the physical check: 'check that your system wires are connected to the right connectors — use the wiring diagram the app gave you during setup to move the wires to the right connectors.' An R feed landed in the wrong connector during installation produces a thermostat whose configuration and whose base disagree about the most important wire it has.

Retrieving stored fault codes on Nest thermostats

Nest surfaces help codes in two places: as a message with a code on the thermostat's own display, and in the Nest or Google Home app (TD codes, for example, appear in the app during setup, sometimes paired with an m15 message on the thermostat screen). The diagnostic screen that matters most is Settings > Equipment > Wiring info: it draws every connected wire, and a wire that isn't sending voltage shows grey — on a no-power alert, all-grey wires point at the system supply, a single grey wire at that wire's connection. Settings > Equipment also hosts the system Test mode that runs heat, fan and cooling on demand (and the Furnace Heads-Up test on equipped models). History lives in the same menus — Quick View > History on Learning Thermostats, Settings > History on Thermostat E — as Energy History rather than a fault log, so note a code down (or photograph the display) before it clears: once power returns, an E code leaves no trace in the history screens an owner can open.

Other Nest thermostat error codes

See the full list on the Nest Thermostat error codes hub.

Codes E294 gets confused with

E74 — No power to Rh wire detected — Google's master help-code table groups E4, E24 and E74 under exactly that sentence, and routes the group to 'Troubleshoot power'. E74 is the heating-side member of Nest's split-power family.

E195 — No power to R wire detected — Google's master help-code table defines E195 with exactly that sentence, and routes it to 'Troubleshoot power'. E195 is the single-R rendering of Nest's no-power family.

Frequently asked questions

Related guides

Facts on this page were checked against manufacturer documentation: support.google.com · support.google.com · support.google.com · support.google.com · support.google.com · support.google.com · support.google.com · support.google.com · support.google.com · support.google.com · support.google.com · support.google.com · support.google.com