Your thermostat stopped listening. The app still works. That matters.

If you told a speaker to turn the heat up this week and got “Sorry, I can’t reach the Nest Thermostat right now,” you were not imagining it, and it was not your wi-fi. Google Home users have been hitting exactly that message while the Google Home app keeps adjusting the same thermostat perfectly well. That gap — voice fails, app works — is worth more than the inconvenience, because it quietly reveals what a voice command has been doing all along.

Does your State Treasury Department have money that's owed to you?

Search your name and state to check if unclaimed funds may be listed in official records. State agencies hold unclaimed property when accounts, refunds, or deposits go uncollected.

Millions of records exist across the U.S., and your name could appear in one of them. This search reviews public records for possible matches tied to your name.

Start your search to see what may be associated with your name.

Search For Money

Here is what has been reported, and I want to be careful about the boundary between what is established and what isn’t.

Android Authority reported on July 24 that Google Home users are losing hands-free control of their Nest Thermostats. The symptom is consistent: a spoken command through a Google Home speaker returns “Sorry, I can’t reach the Nest Thermostat right now,” while the same thermostat responds normally to the Google Home app. Android Headlines covered it as a Google Home bug. Android Authority says it has asked Google for comment and had not received one at the time of writing.

What is not established, and I’d rather say so plainly than round it off: nobody has confirmed how widespread this is. The reporting describes a cluster of user reports rather than a verified global outage. No source I could find specifies which thermostat generations are affected, and one user reported the problem resolving the next day. It may well be fixed by the time this reaches you.

And one more, because it’s the kind of thing that gets rounded off: nobody outside Google actually knows the cause. “Bug” is the press’s read, and it’s a reasonable one — the failure is intermittent and it cleared up on its own for at least one person. But Google hasn’t said anything at all, so treat “it’s a bug” as the most likely explanation rather than a confirmed one. As it happens, it doesn’t change a single thing below, which is rather the point.

Which is exactly why I want to talk about it now, while the failure is fresh enough to learn from. A bug that gets quietly fixed teaches you nothing if you weren’t paying attention while it was broken.

When you say “set the temperature to 70,” it feels like flipping a switch. It is not. It is a round trip, and it looks roughly like this:

your voice → the speaker → Google’s voice service → Nest’s device service → your thermostat

Every one of those arrows is a place it can fail. And the detail that makes this week genuinely instructive is the one people are treating as a footnote: the app still works.

Sit with that for a second, because it rules almost everything out. If the app can change the temperature, then your thermostat is powered and online. Your wi-fi is fine. Your router is fine. Your account is fine. The device is fine. The only thing that broke is a link in the middle that you never knew existed — somewhere between the voice service and the device service — and you had no way of knowing it was a separate thing until the day it stopped.

That is the whole lesson, and it isn’t really about Google. Anything you control by voice is a dependency, not a switch. It depends on a chain of services owned by someone else, maintained on their schedule, and it can fail all by itself while every part you can see looks perfectly healthy.

The useful question, on any device in your house, is not “does voice work?” It is:

For a lamp, the answer is “I walk over and turn the knob,” and that’s fine. For a thermostat, it’s “I open the app,” which is mildly annoying. For a door lock, a garage door, or a medical reminder, the answer had better be something you have actually tested.

I want to offer this gently, because the tech press will file this week under “minor annoyance” and for a lot of people that’s true. You get up, you open the app, you move on.

But look at the word everyone files this under: convenience.

That word is doing real damage, and it’s worth turning over. “Convenience feature” is why a voice outage gets triaged as minor, why it ships without a status message, and why the fix isn’t urgent. It describes the majority experience accurately — and it is exactly wrong for the people who need it most.

If you have arthritis, limited mobility, low vision, tremor, or you’re managing the house from a chair or from bed, voice isn’t a shortcut you’re taking. It’s the interface. And “just use the app” is not a fallback — it is a different task, and often a harder one: find the phone, unlock it, open an app, hit a small target accurately. The people for whom voice control matters most are precisely the people with the least workable Plan B. And because a voice path fails silently, nobody gets warned. There’s no notification that says “hands-free control is down today.”

That asymmetry is the thing I’d want a reader to carry away. When a convenience feature breaks, the cost isn’t spread evenly across everyone who uses it. It lands hardest on the people who weren’t using it as a convenience. So if you are setting up a house for a parent — or for your own later years, which is the honest way to think about it — the fallback path isn’t an afterthought. It’s the actual design decision.

Best for: Nothing to buy this week. This is a “check what you already own” issue.

Skip if: You don’t use voice control for anything that matters. If your speaker only plays music and sets kitchen timers, this week’s news costs you nothing — though the Plan B question below is still worth ten minutes.

Setup difficulty: Easy. Everything below is checking and testing, not installing.

Monthly cost: $0.

Privacy note: Nothing new this week. But it’s worth noticing what this failure reveals: your spoken command was travelling to at least two separate cloud services before it reached a device sitting in your hallway. That’s the normal design, not a scandal — it’s just worth knowing it’s true, because it’s also why the thing works when you’re away from home.

My take: I don’t think Google did anything wrong here. Whatever this turns out to be — and again, they haven’t told anyone — it reads like an ordinary fault rather than a decision, and it may already be fixed. What bothers me slightly is that there was no signal — no banner in the app, no “voice control is currently degraded” note — so the only way to find out was to stand in your hallway talking to a speaker that wasn’t answering. For most of us that’s a shrug. For someone who depends on it, an hour of that is genuinely upsetting, and a one-line status message would have cost Google nothing. Assume the failure will happen again, somewhere, on some device, and build accordingly.

This works on any brand — Google, Amazon, Apple, Samsung. You’re not testing whether voice works. You’re testing what happens when it doesn’t.

That’s the routine. It costs nothing, takes about ten minutes, and it’s the same list whether this week’s bug affected you or not.

Here’s the timing that made me want to write this issue rather than skip it.

On July 23 — one day before the thermostat reports — 9to5Google reported that Google expanded Gemini for Home’s conversational memory. Per that reporting, “the window across the entire Gemini for Home experience is now 15 minutes.” In practice it means follow-up commands stop needing full context: you say “Hey Google, turn on the kitchen lights,” and minutes later you can say “Hey Google, dim it to 50%” without naming the kitchen lights again.

Google also brought Gemini Live to the first-generation Google Home Mini and Nest Hub, reached by saying “Hey Google, let’s chat.” One caveat the headlines mostly left out: that one needs a Google Home Premium subscription. Nice that decade-old hardware is getting new life; worth knowing it arrives with a monthly bill attached rather than as a free update.

This is a genuinely nice improvement. Conversational follow-ups are one of those things that sound trivial and then remove a real, small daily friction — particularly if naming devices precisely is tiring, which for a lot of people it is.

But notice what’s actually being extended. The assistant is being given more memory, more context, and more autonomy over the same chain of services that, one day later, could not reach a thermostat. More capability layered onto a path whose failure mode you now know.

That isn’t an argument against the feature. It’s an argument for knowing which layer you’re depending on. A smarter assistant that can’t reach the device is still an assistant that can’t reach the device.

And here’s the part that runs against instinct: for anything that genuinely matters, the dumber option is the more reliable one, precisely because it’s dumber. A plain temperature schedule stored on the thermostat has almost no dependencies — it doesn’t need to hear you, parse you, remember what you said four minutes ago, or reach two cloud services to act. A conversational routine needs all of that to go right. Every bit of intelligence you add to a control is another link in the chain, and chains fail at links. That’s not an argument for living in 2005. It’s an argument for keeping your most important routines boring.

One thing to do this week: try the follow-up phrasing once, so you know whether it works on your setup — rollouts like this arrive in stages and yours may not have it yet. Then look at your most important routine and ask whether it depends on the assistant understanding you, or on a schedule that runs whether anyone speaks or not. Prefer the second one for anything that matters.

1. Let your Nest cameras take the July firmware update.
9to5Google reports a July 2026 firmware rollout for the Nest Cam Indoor (wired, 3rd gen), Nest Cam Outdoor (wired, 2nd gen), and Nest Doorbell (wired, 3rd gen). The listed changes are unglamorous in the best way: more reliable connectivity, smoother setup, fixed Activity Zones, improved app reliability, and camera settings applying correctly. If you’ve had an Activity Zone quietly not working, this is the update that may fix it. Free, and it should arrive on its own — worth confirming it landed rather than assuming.

2. Do step 3 of the Plan B audit, even if you skip the rest.
Just once: open the app and change something you normally change by voice. Thirty seconds. The point isn’t the thermostat — it’s finding out now, rather than on the night it matters, whether you’re still logged in.

Moving your important routines onto Gemini’s conversational automations.

Google has been adding automation guidance to Gemini for Home, and setting up automations by just describing what you want is a real improvement over building them by hand. It will probably be the right way to do this eventually.

I’d wait a cycle before moving anything that matters onto it. Not because the feature is bad, but because this week handed us a small, well-timed reminder that the conversational layer and the device-control layer are separate things that can fail independently. A lighting scene is a fine thing to experiment with. Heat, locks, and anything tied to medication or a daily routine are better left on a plain schedule that runs without a conversation, at least until this generation of the feature has a few uneventful months behind it.

Nothing to do here. Just don’t rush the migration, and there’s no cost to waiting.

When you set up voice control in your home, was it mainly for convenience — or because reaching the device itself is genuinely difficult for you or someone you live with?

I ask because it changes what I should be writing. If a meaningful number of you are in the second group, then “just use the app” is a lazy fallback for me to keep offering, and I’d rather find you better answers. Hit reply — one line is plenty.

Most weeks the useful thing is a product. This week it was a failure, which is often more educational: you learn more about how your house actually works in the ten minutes something is broken than in the year it quietly works. Ten minutes, one audit, nothing to buy.

If you run the Plan B audit and find something with no fallback at all, reply and tell me what it was — that’s exactly the kind of gap I’d like to cover properly in a future issue.