This week’s widespread Google Home and Nest outage left a lot of people staring at frozen Nest Hub screens, dead speakers, and Assistant commands that vanished into the void. If your lights stopped responding, your thermostat forgot its schedule, or your Nest Mini went silent halfway through a timer, you are not alone. Reports piled up across Reddit, X, and the r/googlehome community for most of the day, and Google eventually acknowledged the incident on its status dashboard.
When Google Home and Nest speakers stop responding, “try restarting” is not enough. You want to know whether the speaker is even on the network, what firmware it is running, which automation misfired, and where the voice request actually landed. Good Google Nest speaker diagnostics on Android come from a small stack of apps that each answer one of those questions. We tested seven of them during and after the outage to see which ones actually surfaced useful signal.
What to look for
Not every controller app is a diagnostic tool. When we picked the seven below, we weighed five things:
- Device firmware visibility. Can we see the exact build running on each Nest speaker or Hub, and confirm it matches the current release?
- LAN discovery. When a Nest Mini disappears from the Home app, is it still reachable at its local IP, or has it dropped off the network entirely?
- Automation history. Does the app log which routines ran, which ones failed, and what triggered them?
- Voice-command log. Can we replay the last few things Assistant heard so we know whether it misinterpreted the request or never received it?
- Remote reboot. Can we power-cycle a stuck speaker without unplugging it and walking to the kitchen?
At a glance
| App | Best for | Free plan | Starting price | Google account required |
|---|---|---|---|---|
| Google Home | Official device console and reboot | Yes | Free | Yes |
| Google Assistant | Replaying recent voice interactions | Yes | Free | Yes |
| Fing | LAN scans to find speakers off Wi-Fi | Yes | $6.99/mo Premium | No |
| Nest | Legacy cameras and thermostats | Yes | Free (Nest Aware from $8/mo) | Yes |
| Home Assistant | Self-hosted state history for Nest | Yes | Free (Nabu Casa $6.50/mo) | No |
| Sesame Assistant Shortcut | Fast routine testing from the launcher | Yes | Free | Yes |
| Bluetooth Scanner | Bluetooth pairing checks | Yes | Free | No |
The seven apps we tested
#1. Google Home — Best for the official device console and remote reboot
The Google Home app is the first place to look, and during the outage it was also the first place to break. Once it recovered, though, it was the only app that showed per-device status, firmware build, group membership, and the “Reboot device” shortcut buried under each speaker’s settings. The Cast log inside a device’s diagnostic panel is genuinely useful when a Hub freezes mid-cast.
Where it falls short: During Google-side outages, the app itself often stops loading device state, which is the exact moment you need it. It also hides the firmware string three taps deep.
Pricing: Free.
Download: Google Play
Bottom line: Non-negotiable. Keep it installed and updated, but do not rely on it as your only diagnostic tool.
#2. Google Assistant — Best for replaying recent voice interactions
When a command fails, the question is usually “did Assistant mishear us, or did it never get the request?” The Assistant app’s activity view (via My Activity) shows the last handful of voice interactions with transcripts and audio playback. That single feature has resolved more “why did my lights not turn off” mysteries for us than any smart-home dashboard.
Where it falls short: Only shows requests that reached Google’s servers. If a Nest Mini is offline, nothing appears, which is itself a signal but not a useful one on its own.
Pricing: Free.
Download: Google Play
Bottom line: The fastest way to prove whether the speaker heard you at all.
#3. Fing — Best for spotting a Nest Mini that dropped off Wi-Fi
Fing is the LAN scanner we reach for when the Home app claims a speaker is “offline” and we want to verify. It enumerates every device on the local network, shows MAC vendor (Google’s OUI blocks are easy to spot), signal path, and last-seen timestamp. If your Nest Hub is missing from Fing’s scan but the phone is on the same SSID, the speaker is genuinely off the network, not just sulking in the app.
Where it falls short: The free tier caps some deeper features behind Fing Premium, and mesh networks with client isolation will hide devices from any LAN scanner.
Pricing: Free with ads; Premium from $6.99/month.
Download: Google Play
Bottom line: The single best “is the speaker actually on the network?” answer we have on Android.
#4. Nest — Best for legacy cameras and thermostats not yet migrated
The old Nest app is still alive because not every Nest camera and thermostat has been fully absorbed into Google Home. If your older Nest Cam Outdoor or first-generation Learning Thermostat behaves oddly during a Google-side incident, the Nest app often shows a different (and sometimes more accurate) status than Home does. Firmware version for older devices lives here, not in Home.
Where it falls short: Google keeps trimming what this app can do. Newer devices refuse to appear in it at all, so it is a partial view.
Pricing: Free. Nest Aware plans start at $8/month if you also want cloud video history.
Download: Google Play
Bottom line: Keep it around if you still own pre-migration Nest hardware.
#5. Home Assistant — Best for self-hosted state history and Nest integration
Home Assistant is the app we open when we want ground truth. With the Nest integration configured, every state change on every speaker, Hub, thermostat, and camera gets logged locally with timestamps. During the outage, our Home Assistant instance kept showing the last-known state and the exact moment cloud sync went silent, which no Google-owned app can do.
Where it falls short: You need a Home Assistant server running somewhere on your network first. It is the most powerful tool on this list and the one with the steepest setup.
Pricing: Free and open-source. Nabu Casa cloud is $6.50/month if you want remote access without opening ports.
Download: Google Play
Bottom line: The best diagnostic surface on Android, if you have already invested in the infrastructure.
#6. Sesame Assistant Shortcut — Best for fast routine testing from the launcher
When we are trying to reproduce a broken routine, tapping through the Home app is slow. Sesame indexes Assistant shortcuts and routines and drops them into the Android launcher as searchable entries. That means we can retrigger a specific routine dozens of times in a row to see which step is failing without touching the Home app.
Where it falls short: It surfaces shortcuts, not diagnostics. It will not tell you why a routine failed, only make it faster to retry.
Pricing: Free.
Download: Google Play
Bottom line: A quiet time-saver when you are debugging the same routine over and over.
#7. Bluetooth Scanner — Best for pairing checks between speaker and phone
Some Google Home and Nest speakers advertise Bluetooth even when Wi-Fi has fallen over. Bluetooth Scanner enumerates nearby BLE devices with RSSI, MAC, and advertised name. If a Nest Mini shows up in Bluetooth scan but not in the Home app, the speaker is powered and its radio stack is alive, which narrows the problem to Wi-Fi or the cloud side.
Where it falls short: Only useful during setup or when a speaker is stuck between the phone and a hub. Not a monitoring tool.
Pricing: Free.
Download: Google Play
Bottom line: A cheap way to prove a “dead” speaker is actually alive.
How to pick the right one
- You only want the official view: Google Home plus Google Assistant activity.
- The Home app says the speaker is offline and you do not trust it: Fing for the LAN, Bluetooth Scanner for the radio.
- You still run older Nest cameras or thermostats: Keep Nest installed alongside Google Home.
- You want a full timeline of every state change: Home Assistant with the Nest integration.
- You are debugging one specific routine over and over: Sesame Assistant Shortcut on the launcher.
FAQ
Why is my Google Nest speaker not responding?
Usually one of three things: the speaker has dropped off Wi-Fi, the Google Home cloud is having an incident (as it was this week), or a recent firmware update has left the device in a stuck state. Check the Home app first, then verify with a LAN scan in Fing. If the speaker is on the network but still unresponsive, a remote reboot from Google Home or a manual power cycle usually clears it.
Is there a Google Home status page I can check?
Yes. Google publishes device status at the Google Nest Help status dashboard, and the Google Workspace status page covers Assistant. Both were updated during this week’s outage. Downdetector and the r/googlehome subreddit are also good real-time signals when Google’s own dashboard is slow to update.
Can I see the firmware version running on my Nest Mini or Hub?
Open the Google Home app, tap the device, open its settings, and scroll to “Device information”. The Cast firmware version lives there. For older Nest cameras and thermostats, the same field is inside the legacy Nest app rather than Google Home.
Do any of these apps work offline or without a Google account?
Fing, Home Assistant, and Bluetooth Scanner all work without a Google account and without cloud access. That is precisely why they are on this list: when Google’s side is broken, the tools that do not depend on Google are the ones that still return useful information.
