If Google Home keeps saying something went wrong, ask it for the weather once. If weather fails, follow Google’s speaker-connectivity steps: unplug the speaker for 10 seconds, let it reboot, then reboot the modem and router. Don’t factory-reset it yet.
If weather works but a light, lock, or scene fails, the speaker still has a path to Google. Listen for the device name in the reply and work on that one partner connection instead of rebuilding the whole Home.
One more check matters: did the requested action happen anyway? A completed action followed by an apology points to a late or missing confirmation, not proof that the command itself failed.
Google Home keeps saying something went wrong? The wording is the diagnosis
Everyone treats this as one error. It isn’t. Google publishes the phrases its assistant says, and they come from different layers of the system.
The Nest connectivity page lists the bare version. The developer error reference — written for the companies that build lights and locks, not for you — lists the rest, each tied to a specific error code their servers send back.
| What you hear | What actually failed |
|---|---|
| “Something went wrong. Try again in a few seconds.” | The speaker’s link to Google. Filed under connectivity issues. |
| “There was a glitch. Try again in a few seconds.” | Same thing. Google lists both on the same page. |
| “Sorry, something went wrong controlling [device]. Please try again.” | A transientError from that brand’s cloud. Try again later. |
| “Sorry, something went wrong and I’m unable to control your home device.” | A hardError from that brand’s cloud. Trying again won’t help. |
| “To get help with that, you’ll need to give me some more information.” | Not this problem. Your account’s activity controls are off. |
Notice what the table splits. If a device name appears in the sentence, the failure happened in that company’s servers and your speaker is only the messenger. If no device is named, the break is between your speaker and Google.
That distinction decides where to spend your next five minutes. A bare error starts with the speaker’s path to Google. A named-device error starts with that brand’s service, account link, and current status.
Why it happens when nothing in your house changed
A Google Home request depends on several handoffs. The speaker needs a working network path to Google, and a smart-home command may also need a linked brand’s service to answer.
Break any hop and you get the same apology, because from the speaker’s side every failure looks identical: it asked, and nothing arrived.
Which is why Google’s own fix list is entirely about radio and routing. Reboot the speaker, then the modem and router.
Move the speaker “to a different room away from devices that may cause interference” — the page names microwave ovens, baby monitors, and “other devices using the 2.4 GHz band.” If the errors are frequent, move it closer to the router.
There’s no factory reset anywhere in that list. Yet reset is the top answer on nearly every page ranking for this problem, and it costs you your settings.
Why a reset usually isn’t the fix
A reset is the most-recommended answer to this error and often the least useful one: the change that produced the error can be weeks old, and it can sit on the router rather than on the speaker being reset.
Which devices fail is the more useful clue. If the speakers that error are the ones in the far half of the house and the one next to the router never does, that pattern makes network coverage worth checking; it does not by itself establish the cause.
So read the map before the device: which units fail, which never do, and where each one sits relative to the router.
Check what changed on the network as well, and how far back. If your 2.4 GHz and 5 GHz networks share one name, confirm on the router which band each device actually joined.
Work through the router’s own settings and recent changes before touching anything with a reset pinhole. The same approach applies when a Google Home keeps dropping off Wi-Fi entirely.
Fix it in this order
- Ask it something with no device in it. “Hey Google, what’s the weather?” needs Google’s servers and nothing else. If that fails too, this is a network problem and steps 2 and 3 are your whole job.
- Unplug the speaker, then reboot the router. Ten seconds is enough for the speaker. Do them in that order, and wait for the router to come fully back before you test.
- Check whether distance is the pattern. If the speakers far from the router misbehave and the near ones don’t, you found it. Moving one speaker one room over is a five-minute test that beats an hour of settings.
- If only smart home commands fail, resync instead. Say “Ok Google, sync my devices” — that’s Google’s documented command, not folklore. It re-reads your device list from the partner.
- If one brand fails and the others are fine, relink that brand. Google Home app, Works with Google, then Reconnect account for that partner only. Don’t touch the speaker.
- Isolate one speaker before considering reset. Move the failing unit beside a working one and repeat the same weather request. If the failure follows that speaker after the official reboot steps, contact Google support before erasing it.
Steps 4 and 5 are where most people never get to, because they reset in step 2 and start over from nothing.
The error can fire while the command is already working
Here’s the part that makes people distrust their own ears, and it’s the strongest clue in the whole problem.
On the SmartThings forum, a member chasing this for weeks worked out what he was actually listening to:
“When I run it via GH voice, a few lights turn off and then there is a gap where GH states something went wrong. After 15 – 30 seconds, them remaining lights turn off.”
The lights obeyed. The error fired in the gap while they were still obeying. Another user in the same thread described scenes that ran “completely correctly” while the speaker announced a failure for each one, and reported that unlinking and relinking the whole account changed nothing.
The same signature turns up on Hubitat. In a 2020 thread, a member found his house mode was being set correctly every single time — the hub confirmed it — while the speaker apologized for the mode it had just successfully changed.
Two platforms show the same useful pattern: the action can finish after the spoken error. Those forum reports don’t prove which server was slow, but they do show why you should verify the result before resetting anything. Google’s developer documentation also distinguishes temporary partner errors from hard errors, so the complete reply matters.
Check the light or scene before you troubleshoot. If the action completed, the voice path and at least part of the partner path worked. Record the delay and test the same device in its own app; repeated late confirmations belong with that vendor’s support, not a factory reset.
What this error is not
Three dead ends worth crossing off, because each one has a whole page of advice behind it.
- It isn’t a listening problem. If the speaker’s lights spin when you speak, the microphone did its job. Mishearing you produces a different reply.
- It isn’t your privacy settings. When activity controls block a request, Google’s phrasing is “To get help with that, you’ll need to give me some more information” — a different sentence, and it names a fix. Turning Web & App Activity back on to chase a connection error just hands over data for nothing.
- It usually isn’t the speaker. When every speaker in the house errors at once, the one thing they share is the network. Investigate the thing they share.
Do this now: ask your speaker for the weather. If it fails, unplug the speaker for 10 seconds and reboot the network as Google directs. If weather works, repeat one named-device command and check whether the action happened before you resync or relink that partner.
More failures worth reading by their exact wording are in the smart home troubleshooting guide, and a bulb switched off at the wall is a different fault with a physical fix.
Bolt & Bulb covers what goes wrong after the unboxing: devices that drop off Wi-Fi, dimmers that flicker with LED bulbs, locks that will not fit a rental door. The site draws on manufacturer documentation, platform support pages and release notes, and attributed owner reports in public forums.