Direct answer
For the Nest Learning Thermostat (4th gen), time zone, placement, calibration, stale cloud state and sensor hardware should be separated. First, compare local device value with app history and a reference.
What this covers
- Nest Learning Thermostat (4th gen) (GA05551)
- Google Nest/Home device; Matter/Thread role, wired/battery power, subscription and Google Home migration vary.
- The specific fault this record addresses: shows the wrong time, state or sensor reading
What it does not cover
- ×The same symptom on a different Google Nest product line, which has its own record and its own cited source
- ×An on-screen error code whose meaning has not been checked against this exact model's manual
- ×Live electrical, gas, sealed-system, internal battery-cell or structural repair — a technician boundary, not a self-service step
Differential
What actually causes this, and how to tell them apart
These are ordered by how often each one is the answer, not by how easy it is to try. The point of the middle column is that two causes producing the same headline symptom rarely produce the same detail — that detail is what tells you which one you have before you change anything.
- 1
The app is showing a cached value, not a current one
What separates it The reading is plausible but stale, and it refreshes when the app is reopened or pulled down. The timestamp beside the value is the giveaway and is routinely ignored.
How to confirm Read the timestamp on the value itself. A correct sensor and a stale display is the most common version of this complaint.
- 2
The home's time zone rather than the device's clock
What separates it Everything is offset by a whole number of hours, including event history and schedules. The home has its own time zone setting that defaults to wherever it was created.
How to confirm Check the home or hub's time zone rather than the phone's. A whole-hour offset is essentially always this.
- 3
Placement is producing a genuinely correct but unrepresentative reading
What separates it The value is consistently offset in one direction. A thermostat above a radiator, in direct sun, on an exterior wall or near a draught reads its own microclimate accurately and the room wrongly.
How to confirm Compare against a separate thermometer placed beside the device, then one in the middle of the room. A device that agrees with its neighbour and disagrees with the room is placed badly, not faulty.
- 4
Self-heating from the device's own electronics
What separates it Temperature reads consistently high by a small, stable margin. Every powered device generates heat, and a sensor inside that enclosure measures some of it.
How to confirm A small stable offset is characteristic. Many devices offer a calibration adjustment for exactly this, which is a correction rather than a workaround.
- 5
A remote sensor is selected instead of the one being read
What separates it The displayed value does not match the device you are standing next to. Multi-sensor systems average or switch between sensors on a schedule.
How to confirm Check which sensor is currently active for the period in question rather than assuming it is the one on the wall.
- 6
The device has lost its clock and not resynchronised
What separates it Timestamps are wrong by an arbitrary amount rather than a whole number of hours, often after a power cut. A device that boots before the network is available can start with no valid time.
How to confirm Restart it once the network is confirmed up and check whether timestamps correct themselves.
- 7
The sensor itself has drifted or failed
What separates it The reading is implausible, changes erratically, or does not respond to a real change in conditions at all.
How to confirm Reach this only after the others are excluded. A sensor that fails to move when conditions genuinely change is different from one that reads a real microclimate.
Before you touch a setting
Record this first — changing settings destroys the evidence
Every item below stops existing the moment a reset, re-pair or settings change is made. Written down first, they are what separates the causes above; recovered afterwards, they are guesswork.
- The timestamp shown beside the value, not just the value. A correct sensor with a stale display is the most common form of this complaint.
- The size and direction of the error: a whole number of hours, a small stable offset, or an erratic difference. Each points somewhere different.
- A reference reading taken beside the device and a second one taken in the middle of the room.
- The home or hub's time zone setting, read there rather than on the phone.
- Which sensor is currently active if the system has more than one.
- Whether the problem began after a power cut, a network outage or a move.
Read the timestamp before the value
ReversibleA stale display of a correct reading is the most common version of this complaint, and it is settled in one look. Pull to refresh and see whether the value changes before investigating the sensor at all.
Classify the size of the error
ReversibleA whole number of hours is a time zone. A small stable offset is placement or self-heating. An erratic or implausible difference is the sensor. These three share no steps, and the classification costs nothing.
Check the home's time zone, not the phone's
ReversibleThe home has its own time zone and location, defaulting to wherever it was created. A whole-hour offset across readings, history and schedules is essentially always this, and the phone's own clock being correct proves nothing about it.
Compare against a reference beside the device, then in the room
ReversibleA device that agrees with a thermometer next to it and disagrees with the middle of the room is reading its own microclimate accurately. That is a placement finding, and no calibration corrects it honestly.
Account for self-heating before calibrating
ReversibleA small, stable, always-high offset is the device's own electronics warming its sensor. Where a calibration adjustment is offered, this is what it is for — a correction with a known cause rather than a workaround for an unknown one.
Confirm which sensor is actually active
ReversibleMulti-sensor systems average across sensors or switch between them on a schedule, so the value shown may legitimately not be the one on the wall in front of you. Check the active sensor for the period in question.
Restart once, after confirming the network is up
ReversibleA device that boots before the network is available can start with no valid time and never resynchronise. Timestamps wrong by an arbitrary amount after a power cut are this, and one restart in the right order fixes it.
Confirm the reading responds to a real change
ReversibleChange the conditions deliberately and watch. A sensor that does not move when conditions genuinely change has failed; one that moves correctly but reads a consistent offset has not.
Model-specific
What is true of this model and not of its siblings
Generic advice for the product line fails here. Each item below is a property of this specific model family that changes which of the steps above apply to you.
- Model scope
- GA05551. Google Nest/Home device; Matter/Thread role, wired/battery power, subscription and Google Home migration vary.
- Display
- A 2.7-inch (68 mm) diameter circular liquid crystal display at 600 x 600 pixels. Round and high resolution — not the 2.4-inch 240 x 320 rectangular panel in the cheaper Nest Thermostat, which is the quickest way to tell which model you actually have.
- Sensors
- A Soli sensor for Motion Sense, plus temperature, humidity and ambient light. Soli is radar rather than a passive infrared detector, so its presence behaviour differs from the plain motion sensor in the Nest Thermostat.
- Power
- Powered from HVAC system wiring with a built-in rechargeable lithium battery. This is a sealed rechargeable cell — not the 2 AAA alkaline batteries used by the Nest Thermostat. 'Replace the batteries' is not a step on this model, so a low-power symptom here is a wiring or charging investigation.
- Consumption
- Less than 1 kWh per month.
- C wire
- Patented Power Sharing technology; Google states it is designed to work whether or not the home has a common (C) wire, and that in limited cases — fewer than 1% — a C wire or a Nest Power Connector may be necessary to guarantee sufficient power in all conditions.
- Wi-Fi
- 802.11n on 2.4 GHz and 5 GHz. Dual-band.
- HVAC stages
- Works with most 24V systems — gas, electric, oil, forced air, heat pump and radiant. It controls heating in 1, 2 and 3 stages (W1, W2, W3); cooling in 1, 2 and 3 stages (Y1, Y2, Y3); heat pump up to 3 stages with 1 or 2 stages of auxiliary/alternate and emergency heat (O/B, AUX, AUX2, E); fan (G, G2, G3); power (C, RH, RC); humidifier and dehumidifier (HUM, DEHUM); and ventilation (VENT). That is far beyond the single-stage-plus-one the Nest Thermostat supports.
- Connector limits
- Google states the * connector can accept only ONE of W3, Y3, G3, E, HUM or DEHUM. The AQ+ and AQ- connectors accept only Y3, or 1-wire or 2-wire VENT, HUM or DEHUM. On a system that needs more than one of those, this constraint decides the installation before anything else does.
- Power path
- Drawn from the HVAC control wiring. A dedicated common wire supplies continuous power; without one, the thermostat charges from the heating circuit and can hold enough charge for the display while failing at sustained radio use.
- Symptom boundary
- This record covers Google Nest Nest Learning Thermostat (4th gen) when it shows the wrong time, state or sensor reading. A different symptom on the same hardware, or this symptom on a different Google Nest product line, has its own record with its own causes and its own cited source.
Stop boundary
When this stops being a self-service repair
Continuing past any one of these costs more than the repair saves — in safety, in warranty, or in evidence a technician needs.
- !The reading does not respond to a deliberate, real change in conditions, which is a failed sensor rather than a configuration problem.
- !Correcting placement would require moving a thermostat, which is HVAC wiring work rather than a settings change.
- !The device is being relied on as the sole medical, fire, freeze or security guarantee. No consumer sensor is specified for that, whatever it currently reads.
- !Readings are erratic in a way that has caused the heating or cooling system to behave abnormally — short cycling or failing to reach setpoint.
Evidence ledger
Sources behind this answer
Visible sources support the visible claims. Home Product Support records the publisher, the fact used and the review date; community reports can suggest an issue but do not become a published fact on their own.
Where the manufacturer's article stops. Google Nest Help publishes this as "Google Nest thermostat help". Official Google Nest thermostat setup, scheduling, HVAC and Wi-Fi help. What that article does not carry is the model boundary — it is written for a product line, and GA05551 is the scope applied here. Where a control label, terminal, indicator pattern or reset sequence differs on your unit, the manual for that exact model is the authority, not this page and not the article.
Exact questions
Common follow-ups
How do I tell the Learning Thermostat from the cheaper Nest Thermostat?+
Look at the screen. The Learning Thermostat (4th gen) has a 2.7-inch circular display at 600 x 600 pixels; the Nest Thermostat has a 2.4-inch rectangular 240 x 320 panel behind a mirrored lens. That is the fastest reliable check, and it matters because the two have genuinely different wiring capabilities.
Can I replace the batteries in the Learning Thermostat?+
No — it uses a built-in rechargeable lithium battery charged from the HVAC wiring, not the 2 AAA alkaline cells used by the Nest Thermostat. So a low-power symptom on this model is a wiring or charging investigation, and swapping batteries is not a step that exists here.
Does it need a C wire?+
Google states it is designed to work with or without one, using its Power Sharing technology, and that in fewer than 1% of cases a C wire or a Nest Power Connector may be needed to guarantee sufficient power in all conditions. So the answer is normally no, with a small and specifically acknowledged exception.
How many heating and cooling stages does it support?+
Up to 3 stages of heating (W1, W2, W3) and 3 of cooling (Y1, Y2, Y3), plus heat pump up to 3 stages with 1 or 2 stages of auxiliary or emergency heat. That is substantially more than the Nest Thermostat, which handles one stage of each plus a second stage of either — the main reason to choose this model on a complex system.
Can it run my humidifier and ventilation at the same time?+
Watch the connector limits. Google states the * connector accepts only ONE of W3, Y3, G3, E, HUM or DEHUM, and the AQ+/AQ- connectors accept only Y3 or 1-wire or 2-wire VENT, HUM or DEHUM. On a system needing several of those, this constraint decides the installation before anything else.
Does it support 5 GHz Wi-Fi?+
Yes — 802.11n on both 2.4 GHz and 5 GHz.
Why does it wake when I walk past and my old one did not?+
It uses a Soli radar sensor for Motion Sense rather than a passive infrared detector. Radar responds differently to approach and to movement behind objects, which is why its presence behaviour does not match the plain motion sensor in the Nest Thermostat.
The reading looks wrong but the device seems fine.+
Read the timestamp beside the value before anything else. A stale display of a perfectly correct reading is the most common version of this complaint, and pulling to refresh settles it in one look.
Everything is out by exactly an hour.+
That is the home's time zone, not the device's clock. The home has its own time zone and location setting that defaults to wherever it was created, and the phone's clock being correct tells you nothing about it. Whole-hour offsets are essentially always this.
My thermostat reads warmer than the room.+
Compare it against a thermometer placed right beside it, then against one in the middle of the room. Agreeing with its neighbour and disagreeing with the room means it is reading its own microclimate accurately — a placement finding rather than a fault, and calibrating it away would be hiding a real measurement.
Should I calibrate the offset out?+
Only where the cause is known. A small, stable, always-high reading is usually self-heating from the device's own electronics, and calibration is the intended correction for exactly that. Calibrating away an offset caused by placement makes the number look right and the control worse.
The app shows a different temperature from the display on the wall.+
Check which sensor is active. Multi-sensor systems average across sensors or switch between them on a schedule, so the displayed value may legitimately come from a different room than the one you are standing in.
Timestamps went wrong after a power cut.+
A device that boots before the network is available can start with no valid time and never resynchronise. The distinguishing feature is that the error is an arbitrary amount rather than a whole number of hours. One restart, after the network is confirmed up, normally fixes it.
How do I tell a bad sensor from bad placement?+
Change the conditions deliberately. A badly placed sensor reads a real microclimate and moves correctly when conditions change. A failed sensor does not move at all, or moves erratically. That single test separates them where comparing numbers does not.
Can I rely on this for a freezer or a medication store?+
No. No consumer sensor is specified as a sole guarantee for medical, fire, freeze or security purposes — the reporting is duty-cycled, the alerting is best-effort, and nothing tells you when it has stopped. Anything that matters needs a layer designed to fail loudly.
It was right for months and now it is not.+
Look for what changed around it rather than at the device: furniture moved, a radiator or vent uncovered, sun reaching it at a new time of year, or a draught from a door now in use. A sensor reading a changed environment correctly is the most common explanation for a device that was fine and now is not.
Does this answer apply to every Google Nest model?+
No. It is scoped to GA05551. Google Nest/Home device; Matter/Thread role, wired/battery power, subscription and Google Home migration vary.
What should I record before troubleshooting wrong reading or time?+
Record the complete model identifier, exact message or indicator, software/firmware where visible, the operating stage and what still works.
Why is a factory reset not the first step?+
A reset can erase accounts, networks, maps, schedules or preferences without distinguishing wrong reading, time. The ordered checks preserve that evidence.
When should I stop and use qualified service?+
Do not use consumer sensors as the sole medical, fire, freeze or security guarantee.
Answer for the exact device and software version shown above.