Nest Thermostat Wire-Not-Detected Codes (E157, E158, E184, E194): Meaning & Fixes

E157, E158, E184 and E194 are Nest's wire-not-detected reports: a wire the thermostat needs has failed the test the base runs on every connector, mechanically and electrically. This guide explains how that detection actually works — including why stranded wire can never pass it and why Google's fix is always the same cut-and-re-strip — then walks each code by its wire: Y1 for cooling, W1 for heating, G for the fan, and R, the power wire whose detection failure underlies all the others. One careful reseat cures the mechanical half of this family completely; whatever survives that reseat is telling you something different, and this guide teaches you to hear it.

How a Nest base detects a wire: two tests, both must pass

Google's undetected-wire article states the mechanism plainly: most Google Nest thermostats detect wires by testing them mechanically — is a wire inserted into the connector? — and electrically — is there electrical current on the wire? If a required wire fails either test, you may get a 'wires aren't detected' message or a similar report, and you may not be able to finish setup. (One documented exception matters: the Nest Thermostat 2020 doesn't use a mechanical detector — it works from the wiring information you input in the Google Home app, which is why configuration and detection blur together on that model.) Every code in this guide is one of those two tests failing, and the two failures feel identical on screen while being opposite in the wall. A mechanical failure is a contact problem: the wire is not fully inserted, its end is crooked or corroded, too little copper is exposed, or the connector button hasn't stayed down — Google's tell, repeated in every flow, is that if the button doesn't stay down when you let go, the wire isn't fully inserted and the thermostat won't detect it. An electrical failure is a signal problem: the wire is seated perfectly and still carries nothing the thermostat can measure, because the run is broken, the wire isn't connected to anything live at the equipment end, or it was never the wire its label claims. That split dictates the whole method of this guide: reseat first, because reseating is free and cures the mechanical half completely — and if a properly reseated wire still isn't detected, believe the electrical half and stop re-seating it. One more Google rule frames everything below: Nest thermostats require solid-core copper wire, 18 to 22 gauge. Stranded wire is not supported, and wire thinner than 22 gauge may be too thin for the thermostat to sense at all.

The one fix Google prescribes for every undetected wire

Before the per-code sections, learn the single procedure Google gives for all of them, because it never varies. Turn power to the system off at the system switch or fuse box first — Google heads the article with this, to protect the system and the thermostat from damage. Pull the thermostat display off the base. Pull out one wire and inspect it: the exposed part should be 1/3 to 1/2 inch long, clean and straight. Cut and re-strip any crooked or corroded wire ends — don't try to straighten a corroded end back to life; Google's instruction is to cut it and expose fresh copper. Re-insert the wire and confirm the connector's button stays down; if it doesn't, the wire isn't fully inserted and won't be detected. Repeat with each wire — not just the reported one, because a base disturbed for one wire often has a second marginal connection hiding behind the first code. Push the display back onto the base until you hear a click, and turn the system power back on. Two supporting rules complete the method. If a wire shows as present in the base but the app disagrees, you may be in Google's second category — unconfigured or unspecified: a wire detected in a connector but not entered into the app during setup shows as 'unspecified' in the Google Home app and 'unconfigured' on the thermostat, and the fix there is to configure it in the app (Settings, Thermostat, Wiring, Update Wiring) rather than to touch the copper again. And if your wiring is stranded, no amount of re-stripping fixes it: Google directs you to reinstall the previous thermostat and have a professional replace or adapt the wiring with solid-core wire. Everything in the four code sections that follow is this procedure, aimed at one wire at a time.

E157 — Y1 wire not detected

Google's master table defines E157 in five words: 'Y1 wire not detected', routed to Troubleshoot wiring. Y1 is the first-stage cooling call — the wire that tells the air conditioner or heat pump to cool — so an E157 means the thermostat cannot account for the wire its cooling depends on: it failed the mechanical test, the electrical test, or both. Run Google's procedure on the Y1 wire specifically: power off, display off, Y1 out, inspect the end, cut and re-strip to 1/3 to 1/2 inch of clean straight copper if it is crooked, corroded, painted or short, re-insert until the connector button stays down, display back with a click, power on. Then read the result like a diagnostician. If E157 clears, the failure was mechanical and the story is over. If E157 stands on a wire that is now provably seated, the failure is electrical: the Y1 run isn't delivering a signal — a break in the wall, a wire disconnected or never connected at the equipment's control board, or a wire in the Y1 connector that isn't Y1 at all. A common install-time variant deserves a check before the pro call: compare the base against the wiring diagram the app gave you during setup and against a photo of the equipment's control board if you have one, because a Y1 landed in the wrong connector reports as an undetected Y1 just as faithfully. What E157 is not: it is not 'no power to Y1' — Google publishes that as a separate family (E10, E30, E66 and relatives, the cold-weather shutoff group) — and it is not a cooling breakdown. The equipment may be perfect; the thermostat simply cannot see the wire it would use to call it.

E158 — W1 wire not detected

E158 is E157 translated to heat: Google's table defines it as 'W1 wire not detected', routed to Troubleshoot wiring. W1 is the first-stage heating call on a conventional system — the wire that tells the furnace or boiler-side equipment to make heat — so an undetected W1 leaves the thermostat with no accounted way to call for its primary heat, and setup or heating control stops there. The procedure is identical, aimed at W1: power off at the switch or fuse box, display off, pull the W1 wire, inspect it, cut and re-strip crooked or corroded ends to 1/3 to 1/2 inch of clean straight copper, re-insert until the button stays down, repeat for any other suspect wires while the display is off, click the display back, restore power. The judgement afterwards is also identical: a cleared E158 was a contact; a standing E158 on a proven connection is an electrical absence — the run, the equipment-end connection, or the wire's identity. Two W1 contexts are worth adding. On a heat pump system, heating calls are shared between the compressor wires and auxiliary heat, so a W1/AUX configuration question can sit behind an E158 that reseating won't cure: check the app's wiring record against the base, because a wire the base can see but the app never configured is Google's 'unconfigured/unspecified' case, fixed in the app, not at the copper. And note the counterpart code for calibration: Google documents 'no power to W1' separately in its low-power and power families, which is a detected wire receiving nothing — a different report, with the power flow as its fix, from E158's not-detected-at-all. Keeping those two apart is the whole skill here: detection failures are cured at the connector or in the app, power failures are cured at the supply or in the equipment, and swapping the two fix paths is how a thirty-minute job becomes a weekend.

E184 — Check G wire (and why this code appears in two Google lists)

E184 needs an honest introduction, because Google itself lists it two ways, and pretending otherwise produces bad troubleshooting. In the master help-code table, E184 is defined as 'Check G wire', routed to Troubleshoot wiring. In Google's dedicated overcurrent article, the same code appears in the overcurrent group (E52-E58, E102-E108, E182, E183, E188) and in that article's wire table, where E54, E104 and E184 are all assigned to the G wire. The G wire is the fan wire — it calls the blower that moves heated and cooled air — so both listings point at the same connector, from two directions: a G wire the thermostat can't properly account for, and a G wire on which current behaviour is wrong. The owner procedure is therefore the union of both articles, done in a safe order. Start with detection, because it is the check you can complete: power off, display off, reseat the G wire to Google's standard (1/3 to 1/2 inch of clean straight copper, fully inserted, button staying down), and verify against your wiring diagram that the G connector holds exactly one wire and that it is the right wire — Google's overcurrent flow adds that connector discipline explicitly: one wire per connector, no jumper wires, the wire the diagram says. If E184 clears, it was connection or detection. If it returns on wiring you have proven correct, Google's overcurrent article gives the verdict for its whole group: the cause is likely a worn or failed relay or transformer on the system's control board rather than the thermostat, and the next step is a professional service visit — with the code and its wire (E184 = G) as the information to hand over.

E194 — R wire not detected (the detection failure behind the power codes)

Google's table defines E194 as 'R wire not detected', and its position in the family makes it the most consequential code in this guide. R is the power wire — the feed every other wire's report depends on — and E194 is its detection failure, the mirror of E195's power failure: in E195 the thermostat sees an R wire and measures no power on it, while in E194 the wire fails the detection test itself, mechanically, electrically, or both. That distinction is worth holding onto mid-troubleshooting, because the two codes share a first move (the reseat) and diverge completely afterwards. Work E194 with Google's standard procedure on the R wire: power off before touching anything, display off, R wire out and inspected, cut and re-stripped to 1/3 to 1/2 inch of clean straight copper if the end is crooked, corroded or short, re-inserted until the connector button stays down, display clicked back, power restored. On split-power bases, apply the same reading to the R-family position your system uses — the detection logic is the same for the Rc/Rh arrangement, and a power feed that fails detection there underlies the no-power reports covered in this site's power guide. If a freshly reseated, visibly sound R wire still isn't detected, the failure is electrical and downstream: the run from the equipment carries nothing the base can sense, or doesn't reach the equipment at all — a disconnect at the control board, a broken run, or a wire that was never R. That is professional diagnosis, and it is urgent in a way the other codes in this guide are not: a thermostat that cannot detect its power wire cannot be powered properly, cannot finish setup, and cannot control anything, so an E194 that survives one careful reseat is a book-the-visit code, not a keep-trying code.

Stranded wire, thin wire and the wires that can never pass

Some undetected-wire codes are not faults to repair but physics to accept, and Google is unusually blunt about both categories. Stranded wire first: Nest thermostats don't support stranded wires — they require solid-core copper. A stranded conductor (each 'wire' a bundle of fine strands) doesn't present the connector with the single firm end its mechanical detection and contact are built around, and strands splay, break and corrode at the cut end. If your low-voltage wiring is stranded, Google's instruction is not a workaround but a reversal: reinstall your previous thermostat and contact a local professional to have the thermostat wiring replaced or adapted with solid-core wire so it can work with Nest thermostats. Any guide that tells you to twist, tin or fold stranded wire until a Nest accepts it is contradicting the manufacturer. Thin wire second: Google specifies that Nest thermostats require wires between 18 and 22 gauge, the standard range for residential heating and cooling, and warns that anything smaller than 22 gauge could be too thin for a Nest thermostat to detect — the electrical test itself can't sense it reliably. A house wired with undersized thermostat cable can therefore produce rotating undetected-wire codes on connections that look perfect, and the fix is the same as for stranded wire: professional replacement of the run, not repeated reseating. Put the two rules together and they explain the otherwise puzzling case of the code that migrates — Y1 today, W1 tomorrow, R after the weekend. Migrating detection failures on sound-looking connections usually mean the wire stock itself is wrong for the base, and diagnosing the material once is cheaper than reseating the whole base forever.

When reseating is finished: reading a wire that still won't detect

Google's undetected-wire article is short, and its brevity is itself the guidance: strip and fix the wire, configure any unspecified wire in the app, and beyond that the documented paths end at a professional. So treat the endpoint as a decision rule, not a defeat. A code that clears on reseating was mechanical — note which wire it was, because a connection that worked loose once (a short strip, a stiff wire under tension, a connector disturbed by a display pulled off roughly) can work loose again, and a repeat on the same wire within a season deserves a proper re-strip with the full 1/3 to 1/2 inch of fresh copper rather than another push. A code that survives a correct reseat, on solid-core wire of the right gauge, with the app's wiring record agreeing with the base, is an electrical absence: the thermostat is reporting, truthfully, that no signal reaches that connector. The remaining suspects all live beyond the base — the wire run in the wall, the connection at the equipment's control board, a wire misidentified at both ends — and they are diagnosed with access and instruments the owner flow doesn't assume. Hand the professional the precise evidence: the code, the wire, what the end looked like (corroded, short, painted), and whether the code is original or a return. And hold one boundary firmly while you wait: never move a wire to a different connector to make a detection code go away unless your wiring diagram says it belongs there. A thermostat that detects every wire in the wrong places has not been fixed — it has been taught to call the wrong equipment, which is the one outcome worse than an honest E157, E158, E184 or E194 on the screen.

Key takeaways

• One procedure for all four codes: power off, cut and re-strip to 1/3 to 1/2 inch of clean straight copper, re-insert until the connector button stays down, display back until it clicks.
• Button won't stay down = wire not fully inserted = wire not detected. That single observation settles most mechanical detection failures before any re-strip.
• Stranded or thinner than 22-gauge wire can never pass Nest's detection reliably — Google's answer is professional replacement with solid-core wire, not a better reseat.

Resetting the Nest thermostat

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.

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