Alexa Not Finding Nest Thermostat: Skill, Account, Then Discover

Alexa usually fails to “discover” a Nest thermostat because the accounts and skill link are wrong — not because Wi‑Fi discovery is broken. Nest does not pair to Echo over local Bluetooth like a speaker. You link a Google Account to Amazon through the official Google Nest skill, confirm the thermostat is in the Google Home app, grant Partner Connections permission when needed, then ask Alexa to discover devices. Legacy Nest-only skills are obsolete; Workspace Google Accounts can block migration; and Alexa will refuse some Nest modes even when the device is linked.

Research guide for homeowners whose Echo cannot find or control a Nest / Google Nest thermostat. I’m not a Google or Amazon support agent. What follows is synthesized from Google Nest Help, the official Google Nest Alexa skill listing, and account-migration docs — not invented pairing anecdotes.

This guide was substantially rewritten and re-fact-checked in August 2026.

Key takeaways

• Discovery is a cloud account link, not a same-SSID “find my thermostat” scan.
• Use the Google Nest skill (from Google LLC). Old Nest-branded skills were retired after the 2023 cutover.
• The thermostat must live in the Google Home app under a Google Account (legacy Nest accounts must migrate first).
• After linking, say “Alexa, discover my devices” — and if you added a thermostat later, turn on permissions under Partner Connections first.
• Linked ≠ controllable: Eco, Off, Emergency Heat, and Emergency Shutoff block Alexa control per Google.

What “not discovering” usually means

People use the same phrase for three different failures:

1. No Nest thermostat appears in the Alexa app after discovery.
2. The thermostat appears but voice commands do nothing or return an error.
3. Alexa finds cameras/doorbells from the same skill but not the thermostat (or the reverse).

Those need different checks. Google’s own help for controlling Nest products with Amazon Alexa is explicit: Nest thermostats are supported by the Google Nest skill alongside cameras and doorbells. Older third-party listicles that imply “only cams work with Alexa” are wrong for current product support — but feature coverage still differs by device and region, and Google notes that some Nest features cannot be controlled by Alexa at all.

Correct order: account → Home app → skill → permissions → discover

My honest read of the official docs: most discovery failures are order-of-operations problems. Do this sequence once, cleanly, before factory-resetting anything.

1. Confirm the thermostat works in Google Home

Google’s Alexa setup page starts with: add the Nest device in the Google Home app. If temperature control already fails in Home, Alexa will not magically fix Wi‑Fi, HVAC wiring, or a dead Nest. Fix Home first.

If you still use the older Nest app path, Google requires that you have migrated the Nest Account to a Google Account. Google’s Alexa help is explicit that the skill is only available to users with a Google Account, and that certain Google Accounts — including Google Workspace accounts — can’t be used for migration. That is a hard stop: no amount of “discover devices” will invent a supported account. (The migration FAQ discusses moving to a Workspace account with admin caveats; the hard “can’t be used for migration” line lives on the Alexa control help page.)

2. Enable the Google Nest skill the way Google documents

Google’s preferred path is from Home, not from hunting random skills:

1. Open the Google Home app.
2. Confirm you are on the Google Account that owns the thermostat.
3. Open Home settings → Services → Amazon Alexa skill.
4. Follow the prompts into the Alexa app and complete the link.

The official skill listing from Google LLC on Amazon’s skill store matches that story: set up the Nest thermostat in Google Home first, migrate legacy Nest accounts if needed (Google Nest skill for Alexa), then enable the skill and sign in with the same Google Account.

When you search Skills in Alexa, pick Google Nest by Google LLC — not a leftover “Nest” skill from the Works-with-Nest era. Google’s help on Works with Nest ending and its community cutover post state that after September 29, 2023, legacy Nest skills for Alexa were no longer supported; users needed the Google Nest skill on a migrated Google Account. If an old Nest skill is still enabled, disable it, remove stale Nest devices from Alexa, then enable the current skill from Home.

3. Grant Partner Connections for newly added devices

This is the trap Google documents clearly and many “Wi‑Fi tips” pages miss. If the skill was already linked for other Nest gear, and you install a thermostat later, discovery will fail until you authorize the new device:

1. Google Home → profile → Home settings → Services → Partner Connections.
2. Tap Amazon Alexa.
3. Turn on permissions for the new thermostat.
4. Say “Alexa, discover my devices.”

That same “Alexa, discover my devices” line is Google’s documented next step after enabling the skill and after adding devices.

4. Assign the thermostat a room and test with Google’s command patterns

Once the thermostat shows in Alexa, use the name Alexa lists. Google’s examples include setting a target temperature, asking what the thermostat is set to, and switching modes (Heat, Cool, Heat•Cool, or Eco — depending on equipment). Alexa treats Heat•Cool differently than a single setpoint: Google’s example notes that asking for 72°F maps onto a range such as roughly 68–75°F on the Nest side.

When Alexa “sees” Nest but will not control temperature

Google lists hard blocks. Alexa cannot control the Nest thermostat when:

• It is set to an Eco Temperature
• It is in Off mode
• It uses Emergency Heat
• There is an Emergency Shutoff (Nest Protect / carbon monoxide emergency paths)

Those look like “Alexa is broken” from the couch. Check the Nest/Home status first. Also remember: some Nest features simply are not exposed to Alexa even when linking succeeds — Google says so up front.

Troubleshooting matrix (honest, not padded)

Symptom	Likely cause	What to try
Discover finds nothing Nest-related	Wrong/legacy skill, wrong Google Account, or skill never linked	Disable old Nest skills; enable Google Nest from Home; re-link with the Home-app account
Cameras appear, thermostat does not	Partner Connections off for the thermostat, or thermostat not in Home	Add thermostat in Home; toggle Amazon Alexa permission for that device; rediscover
Thermostat appears; voice fails	Eco / Off / Emergency Heat / Shutoff, or Heat•Cool range confusion	Change mode in Home; use Google’s command patterns; verify name in Alexa
Skill enable fails at Google sign-in	Legacy Nest account, Workspace account, or multi-account mix-up	Finish migration docs; switch to a personal Google Account that owns the home
Worked for months, then vanished	Relink expired, permissions toggled, or Nest removed from Home	Disable/re-enable skill (Amazon troubleshooting path Google points to); recheck Partner Connections

Network myths vs what actually matters

Same-house Wi‑Fi still matters for each product’s own cloud connection — Nest must stay online to Google, Echo must stay online to Amazon — but Alexa is not discovering the thermostat by scanning your LAN the way it discovers some Matter/Bluetooth devices. Obsessing over “put both on 2.4 GHz” is a weak first move if the skill was never linked under the right Google Account.

Useful network checks, in order:

• Nest shows online in Google Home.
• Echo shows online in the Alexa app.
• Phone can open both apps on the same Amazon and Google identities you intend to link.
• Guest-network / AP isolation / VPN on the phone during OAuth can interrupt the skill link — finish linking on a normal LAN path.

Model and generation differences are real. Google’s compatibility and feature lists change over time; voice commands and Matter local paths (where offered on specific Nest Thermostat hardware) are not identical to every Learning Thermostat generation. When versions disagree, trust Google’s current Alexa help page and your model’s Home-app status over a 2022 blog list. I am not going to invent a universal “Gen 3 always works / Gen X never works” table that Google does not publish as a single static chart.

Resets: when they help, when they waste an hour

Soft restart of the Echo (unplug ~1 minute) and a Nest restart from the device or app can clear stuck sessions after a successful relink. That is reasonable.

Factory reset of Echo or Nest should be last. It does not replace the account/skill/permission sequence above. If discovery fails because Partner Connections is off, wiping the Echo only adds re-setup work.

Microphone mute on the Echo blocks voice discovery commands; it does not explain a missing device tile after an in-app discovery. Unmute if you are testing by voice; use the Alexa app Devices → Add Device path if you prefer silent discovery.

What Google says to do when the link is flaky

Google’s troubleshooting section for this integration points you to Amazon’s Alexa device/feature help for skill permission toggles and disable/re-enable steps, and calls out the Partner Connections path when a device does not show in Alexa after the skill is already on. That split is intentional: Google owns Nest permissions; Amazon owns skill session state on the Alexa side.

Practical loop that matches those docs:

1. Verify thermostat online in Home under the correct Google Account.
2. Confirm Amazon Alexa Partner Connections permission for that thermostat.
3. In Alexa, disable the Google Nest skill, remove orphan Nest device entries, re-enable from Home’s Amazon Alexa skill flow, then discover again.
4. Test a simple setpoint command using the Alexa device name.

When to stop DIY and contact support

• Migration or Workspace account limits block a Google Account you cannot change.
• The thermostat works in Home, skill links cleanly, Partner Connections is on, and discovery still returns nothing after a skill re-enable — escalate to Amazon Alexa support with the skill name, and Google Nest support with the Home structure.
• HVAC short-cycling, blank Nest display, or wiring errors — that is equipment service, not an Alexa problem.

Matter, “Works with Alexa,” and why versions disagree

Marketing pages for specific Nest Thermostat SKUs sometimes mention Alexa, Google Assistant, and Matter in the same breath. Those are not interchangeable setup paths. The skill link described above is the cloud integration Google documents for Nest thermostats broadly. Matter, where a particular hardware revision supports it, is a separate local/fabric join that still depends on compatible Echo hardware and a successful commissioning flow in the Alexa app.

Honest implication for troubleshooting: if a friend says “I just said discover devices and it worked,” they may have finished the Google Nest skill OAuth last year, joined Matter on a 2020 Nest Thermostat, or only ever needed camera permissions. Your failure mode can be different even with the “same brand.” When Google’s help page, the skill store text, and a retail box bullet disagree on nuance, prioritize the live Google Nest Alexa help article and what the Home app actually shows for your device.

Also expect feature skew. Camera live view on Echo Show is not available on speaker-only Echos — Google says so. Thermostat voice commands that work in Heat mode may fail in Eco. That is documented behavior, not a broken discovery tile.

Multi-home and multi-account gotchas

Homes with two Google Accounts (partners, roommate, landlord Wi‑Fi login) break linking more often than weak mesh nodes do. The skill must authorize the Google Account that owns the Nest structure in Home. Linking your personal Gmail while the thermostat sits in a spouse’s Home under another Gmail produces empty discovery results that look mysterious until you check the profile avatar in the Home app.

Amazon side: make sure the Alexa app is signed into the same Amazon account as the Echo you are testing. Voice profiles and kid accounts do not replace that. After a successful link, assign the thermostat to an Alexa room/group so routines and “Alexa, make it cooler” utterances resolve to the right endpoint.

If you recently moved Nest from the Nest app into Home, wait until the thermostat is stable online — connected status, setpoint changes stick — before enabling the Alexa skill. Linking during an incomplete migration is a classic way to get a skill that authorizes but returns no thermostat endpoint.

What not to bother with first

• Factory-resetting Nest to “force pairing mode” as step one — Nest is not in Bluetooth pairing with Echo for this integration.
• Buying a new Echo Dot before fixing Partner Connections permissions.
• Chasing 5 GHz vs 2.4 GHz myths while the thermostat is already online in Home on whatever band it uses.
• Third-party “Nest thermostat” skills that are not Google LLC’s Google Nest skill.

How this was researched

Primary sources for this rewrite: Google Nest Help on Alexa control and Nest-to-Google Account migration; the official Google Nest Alexa skill description; Google’s Works-with-Nest / legacy Alexa skill cutover help and community notice (September 2023). I did not run a multi-home lab of every Nest generation against every Echo. Where hardware generations differ, follow the live Google Help entry for your product rather than assuming parity.