Direct answer
For the Nest Learning Thermostat (4th gen), controller eligibility, setup code, prior fabric, Thread/Wi-Fi and multi-admin support should be resolved. First, identify the exact protocol/controller and confirm active hub eligibility.
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: will not connect through Matter, HomeKit or another platform
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 device is still commissioned to a fabric it can no longer reach
What separates it It appears in the old controller and works in none, or joins a new controller and drops out within minutes. A reset clears local settings on several implementations without clearing commissioning data.
How to confirm Remove it from every previous controller BEFORE resetting the hardware. Doing it in the other order is the single most common way this ends up unrecoverable without support.
- 2
The setup code has already been consumed
What separates it The code scans and is rejected as invalid or expired. Codes are consumed per commissioning attempt and a partially completed attempt can use one.
How to confirm Generate a fresh code from the manufacturer's own app rather than rescanning the printed label.
- 3
The platform does not support this device type
What separates it The device commissions successfully and some capabilities are missing on one platform. Standards cover a defined set of device types and attributes, and manufacturer-specific features fall outside them.
How to confirm Compare the capability list against what the standard defines for that device type. Missing extras is expected behaviour, not a fault.
- 4
The controller's own version is too old
What separates it Commissioning fails on one controller and succeeds on another. Support arrives in controller software releases, and an older hub simply does not know the device type.
How to confirm Check the controller's version against the manufacturer's stated requirement before changing anything on the device.
- 5
Multi-admin sharing was skipped in favour of a second commissioning
What separates it Adding the device to a second platform removed it from the first. Multi-admin exists precisely to avoid this, and commissioning again from scratch is not the same operation.
How to confirm Use the sharing or pairing-code flow from within the platform that already has it, rather than starting fresh from the printed code.
- 6
The device is on a network segment the controller cannot reach
What separates it Both are online and cannot find each other. IoT VLANs, guest networks and client isolation all break local discovery, which these protocols depend on.
How to confirm Put both on the same segment with isolation off for the test. Discovery here is local, not cloud-mediated.
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.
- Every controller and platform this device has ever been commissioned to, including ones no longer in use.
- The exact protocol involved and the exact controller version, both read rather than assumed.
- Whether the device commissions and then drops, or never commissions at all — these are different failures.
- Whether the setup code was printed or generated fresh in the manufacturer's app.
- Which network segment each of the device and the controller is on, and whether client isolation is enabled.
Remove it from every previous controller before touching the hardware
Reset / data riskThis order is the whole game. A reset clears local settings without clearing commissioning data on several implementations, and a device that still believes it belongs to an unreachable fabric will keep trying to rejoin it rather than accepting a new one — a state that frequently needs manufacturer support to clear.
Check the controller's version against the requirement
ReversibleSupport for a device type arrives in controller software, not in the accessory. Commissioning that fails on one controller and succeeds on another is a version gap, and nothing done to the device will close it.
Generate a fresh setup code rather than rescanning the label
ReversibleCodes are consumed per commissioning attempt and a partially completed attempt can use one. The printed label is a starting point, not a permanent credential.
Use multi-admin sharing to add a second platform
ReversibleCommissioning from scratch on a second platform can remove the device from the first. The sharing flow from inside the platform that already holds it is a different operation and is the one that keeps both.
Put the device and the controller on the same network segment
ReversibleDiscovery here is local rather than cloud-mediated, so IoT VLANs, guest networks and client isolation all break it while leaving both devices apparently online. Test with isolation off before concluding anything.
Confirm control from both platforms before finishing
ReversibleA device that works on the new platform and has silently dropped off the old one is a half-completed job. Test both, and test one of them away from the home network.
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 will not connect through Matter, HomeKit or another platform. 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 device is locked to a fabric that no longer exists and will not accept a new commissioning after a documented reset. This generally needs the manufacturer.
- !The capability you need is not defined by the standard for this device type, which no configuration will produce.
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 "Set up, manage, and control Matter-enabled devices with Google Home". Genuinely cross-product Google Home Matter/multi-platform article, not device-specific. Verified reachable and content-matched via the Browser tool 2026-08-28. 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.
I reset it and now nothing can add it.+
That is the order problem, and it is the most common serious mistake on this symptom. A reset clears local settings without clearing commissioning data on several implementations, so the device still believes it belongs to a fabric it cannot reach and keeps trying to rejoin it. Removing it from the old controller first is what avoids this.
It joins and then disappears within minutes.+
That is the same disagreement seen from the other side — the device is being pulled back toward a fabric it still holds credentials for. It is not a signal problem, and improving the network will not change it.
The QR code says invalid.+
Setup codes are consumed per commissioning attempt, and a partially completed attempt can use one. Generate a fresh code in the manufacturer's own app instead of rescanning the printed label, which is a starting point rather than a permanent credential.
Adding it to a second platform removed it from the first.+
Commissioning from scratch is not the same operation as sharing. Multi-admin exists precisely so a device can belong to two platforms at once, and it is started from inside the platform that already holds the device — not from the printed code.
Some features are missing on one platform.+
Standards define a fixed set of device types and attributes, and manufacturer-specific extras fall outside them. Missing extras on a cross-platform integration is expected rather than broken, and the manufacturer's own app remains the place those features live.
Both devices are online and cannot find each other.+
Discovery here is local rather than cloud-mediated, so an IoT VLAN, a guest network or client isolation will break it while leaving both perfectly online. Put both on the same segment with isolation off before investigating anything else.
Is it worth using the manufacturer's app as well?+
Usually yes. The standard covers the common capabilities; the manufacturer's app covers everything else, including firmware updates and the settings that are not in the standard. Treating cross-platform control as a replacement rather than an addition is what produces most of the missing-feature complaints.
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 Matter or HomeKit?+
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 Matter, HomeKit. The ordered checks preserve that evidence.
When should I stop and use qualified service?+
Keep setup codes private and do not reset locks/alarms casually.
Answer for the exact device and software version shown above.