If your Google Home isn’t responding, check power, the microphone mute, and then restart it in that order. In most cases, the fix is a dead outlet or cable, a muted mic, a stale app connection, Wi‑Fi trouble, or one speaker that has drifted out of sync. A factory reset is usually not the first move.
What 'Google Home not responding' looks like
“Not responding” can mean a few different things. The symptom tells you where to look first.
The speaker may show no lights at all. It may ignore voice commands, fail to answer in the Google Home app, or stop casting from another device.
If the device is completely silent and dark, think power first. If it lights up but ignores “Hey Google,” think microphone mute or wake-word detection. If the app sees the speaker but voice does not work, the problem is usually not the phone. If casting fails while voice still works, the network or app connection is usually the better place to check.
Before you start
Use this order so you do not change too many things at once.
- Check whether the speaker is actually on before changing settings.
- Know which symptom you have: no lights, no voice reply, no app control, or failed casting.
- If one speaker is affected and the others are fine, treat it as a device-specific problem first.
- If the issue began across several speakers at once, look harder at Wi‑Fi or account state.
A quick note on the symptom itself: Google’s Assistant community has had reports where devices stopped responding to certain questions, while other actions still worked. That is a reminder that partial failures happen and are not always a full device outage.
Check whether the speaker is actually awake and powered
Start here before touching settings. Look for any status light, startup sound, or sign that the speaker is receiving power. If it looks dead, the simplest explanation is often the right one: the outlet, power cable, or adapter is the problem.
- Unplug the power cable from the speaker, then plug it back in firmly.
- If that does nothing, try a different outlet that you know works with another device.
- If the speaker has a removable power cable, check that it is seated all the way at both ends.
A speaker that never lights up, never chimes, and never shows any sign of life is usually a power issue, not a Google Assistant problem. If it is clearly dead on two known-good outlets, stop treating it like an app problem and recheck the hardware path instead.
Make sure the microphone isn't muted
A muted microphone can make a healthy-looking Google Home seem broken. The device may still have power and may still show up in the app, but it will not answer voice commands because it is not listening.
Check the physical microphone mute button or switch on the speaker. On many models, a muted mic is shown by a light or icon that makes the state obvious once you know where to look. The exact indicator depends on the model. If the mic is muted, unmute it and try the wake phrase again.
If voice still does nothing after unmuting, move on rather than assuming the speaker has failed. At that point, the problem may be the wake-word path, the app connection, or a device-specific glitch.
See whether the app or account is the real problem
A quick split test helps here. If the Google Home app can see the speaker, send commands to it, or cast to it, but voice still fails, the speaker is less likely to be offline and more likely to have a microphone, wake-word, or Assistant issue. If voice works but the app cannot control the device, the problem is more likely the app, account, or local phone connection.
On your phone, open the app and check whether the speaker appears online. Then try a simple action from the app, such as changing volume or starting playback. If that works, your Google account and device link are probably fine. If the app is stuck, signed into the wrong account, or never sees the speaker, the phone side needs attention before you blame the speaker itself.
If voice works but the app does not, check whether your phone is on the same Wi‑Fi network as the speaker and whether the app is signed into the correct Google account. If the app works but voice does not, the problem is usually not the router, so do not jump straight to network changes.
Refresh the connection in the least disruptive order
Use the least disruptive restart first, then work outward. The safest order is: restart the speaker, then restart the phone or app, then restart the Wi‑Fi router if needed. That order keeps you from changing more than one thing at once, which makes it easier to see what actually fixed the issue.
- Unplug the Google Home speaker for about 10 seconds, then plug it back in.
- On your phone, fully close the app and reopen it.
- If the app still behaves oddly, restart the phone.
- If the speaker still will not respond, restart the Wi‑Fi router and wait for the network to come back before testing again.
If the speaker starts working after step 1 or 2, stop there. You do not need to keep changing things once the symptom is gone. A router restart can look like it fixed the speaker when the real issue was a stale local connection that cleared only after the network refreshed.
How to spot a Wi‑Fi problem instead of a speaker problem
Wi‑Fi trouble usually shows up as more than one device acting up, repeated drops, or failed casting. If several Google Home devices fail at once, or if the speaker works for a bit and then disappears again, that points toward the network more than the speaker.
Other clues include the app showing the speaker as offline, casting failing from multiple phones, or voice commands working only some of the time. A single speaker that is totally dead is less likely to be a Wi‑Fi issue than a speaker that keeps connecting and disconnecting. If only your smart speakers are affected and your other internet devices are fine, the problem may still be local Wi‑Fi handling rather than a full internet outage.
When the router is the likely culprit, a restart is a reasonable first move. If that helps only briefly, check the Wi‑Fi band, the router’s device list, or whether the speaker is too far from the access point. I would not jump to a factory reset just because casting failed once.
What to do if only one Google Home device is affected
If one speaker is broken and the others still work, treat it as a device-specific problem first. That usually points to that speaker’s power source, microphone state, local setup, or a hardware glitch, not a whole-home outage.
Move the problem speaker close to the router for a test if you can do that safely. Then check whether the app sees that one device while the others stay normal. If the app can manage the other speakers but not this one, compare the problem device with a working one: look at power, mute state, and whether it still plays response sounds.
If only one device in a multi-speaker home will not answer, do not assume the account is broken. It is common to blame the Google account when the real issue is a single speaker that lost its connection or has a muted mic.
How to tell the fix worked
The fix has probably worked if the speaker answers a wake phrase, appears online in the Google Home app, and responds to a simple command without delay. Casting should also start normally if that was part of the problem. The key is not just one good response, but stable behavior for a few minutes after the fix.
Test more than one thing. Ask a short question, use the app to change volume, and try casting audio again. If the speaker works once and then drops offline again, you have not fully solved the underlying issue yet. That usually means there is still a power, Wi‑Fi, or device-specific problem hiding underneath the first symptom.
When a factory reset is the right last step
A factory reset is a last step, not the first one. Use it after power, microphone, app, account, speaker restart, phone restart, and router restart have all been tried in a clean sequence. In many homes, reset is overused and fixes less than people expect.
Reset is more appropriate when one device stays unresponsive after all reversible checks, or when it remains stuck to a bad setup state and nothing else changes the behavior. The exact reset method depends on the Google Home model you own, so check the current official Google instructions for that device before you try it. That matters because the button sequence or reset behavior can differ by model.
If you reset, set the speaker up again only after you have confirmed the phone is on the correct Google account and the Wi‑Fi network is ready. If the device still will not respond after a reset, the next step is model-specific support, not more resets.
Conclusion
If the speaker is still stuck after these checks, stop repeating the same restart and move to model-specific support or a hardware check.
Frequently Asked Questions
What if Google Home works in the app but not by voice?
That usually points to the speaker itself, not the router. Check the microphone mute button first, then restart the speaker and test wake-word response again. If the app can control it but voice stays dead, the problem is often local to that device’s mic or Assistant listening state.
What if voice works but the Google Home app doesn't?
That usually points to the phone, app, account, or local network connection. Confirm the app is signed into the right Google account, restart the app and phone, and make sure the phone is on the same Wi‑Fi network as the speaker. If voice still works, the speaker itself is probably fine.
Should I reset Google Home if it's offline?
Not right away. Try power, mute, the speaker restart, the app, and the router first, because those fixes are reversible and often solve the problem. Use a factory reset only after the device still will not respond and you have checked the current reset steps for your exact model.