Some Google Home Speakers Are Downloading Gigabytes in the Background. Check Yours.

A smart speaker sitting on a shelf doing nothing should use almost no data. Some of Google's new Google Home Speakers are doing the opposite.

9to5Google's Abner Li reported on October 19 that his speaker, which hadn't been used for voice commands or music in the past day, "consumed 17 GB of data in 24 hours." At 3 a.m. Pacific it downloaded 9.99 GB in one go. On October 13 the same speaker pulled 41 GB. Over 30 days: 132 GB.

Google told 9to5Google that "a fix is already rolling out that should address this for users." Good. But Google didn't say what caused it, which version fixes it, or how many speakers were affected. So I wouldn't just assume yours is fine.

How bad is it, really?

Honestly, nobody outside Google knows yet. 9to5Google says "It's not clear if this is a widespread issue." Their second Home Speaker, in a different household and lightly used, downloaded only 2 GB in the past month. They also didn't see the problem on other Google Home and Nest devices, including several Nest Hubs in the same house as the affected speaker.

The 3 a.m. timing made 9to5Google guess it "could be related to failed attempts to download device firmware." That's a reasonable theory. Speakers usually update overnight, and a download that fails and starts over would look exactly like this. It is still a guess, not Google's explanation.

Who should care

If you have unlimited home internet, this is mostly an annoyance and a reason to install the fix.

If your plan has a data cap, it's real money. 9to5Google says that with several Home Speakers and a limited plan, this "could easily breach your cap, as some have found." One speaker doing 132 GB a month is a big bite. Two or three could blow through a cap on their own.

It also matters if your internet is slow or metered in some other way, like a cellular backup or a rural plan. A speaker hammering the connection at 3 a.m. isn't going to make anyone's Zoom call better at 9.

How to check your speaker

Most routers can show you how much data each device uses. The exact menu depends on the brand, but you're looking for a per-device or per-client usage view.

If you use Nest Wifi, 9to5Google gives the path: open the Google Home app, go to the Wifi tab at the top, then Devices, pick your speaker, and look at Device usage graphs. You can switch between 1-, 7- and 30-day views.

On other routers, look for a client list with a data or traffic column, and sort it by usage. Mesh systems and prosumer gear like UniFi usually show per-client totals. Some ISP-supplied routers do too, buried somewhere under "connected devices."

What I'd look for:

• Tens of gigabytes per day from a speaker you barely use. That's the bug pattern.
• Big spikes at the same hour overnight. That fits the failed-update theory.
• A sibling speaker that looks normal. Compare. If one Home Speaker is at 2 GB a month and another is at 100+, you know which one to worry about.

What to do if yours is affected

Google's fix is rolling out on its own schedule, and there isn't a published version number to check against. Here's what I'd do in the meantime:

1. Note today's numbers. Take a screenshot of the 7- and 30-day graphs so you can tell later whether the fix landed.
2. Leave it plugged in and online. Counterintuitive, but if the fix ships as an update, a speaker that's unplugged won't get it.
3. Check again in a few days. If daily usage drops to normal, you're done. If it doesn't, contact Google support with your screenshots. "My speaker downloaded 41 GB on one day" is a much better support ticket than "my internet feels slow."
4. If you're about to hit your cap, unplugging the speaker until the end of the billing cycle is a blunt but effective fix. Plug it back in after and see whether it's been patched.

The bigger lesson

This is a cloud speaker doing something its owner can't see, can't control, and only found out about from a router graph. That's the deal with most mainstream smart speakers. You don't manage their updates. They just happen.

I'm not saying ditch your Google speaker over one bug that Google acknowledged quickly. I am saying it's worth knowing where your router's per-device usage page is, and glancing at it once a month. It's the cheapest monitoring tool you already own, and it would have caught this one before the bill did.

If you've been weighing how much of your home should depend on a vendor's cloud, I went through what local control looks like in Google Home and elsewhere in my piece on local Matter control. A speaker that runs locally wouldn't magically avoid a bad firmware download. But you'd at least be the one deciding when it updates.