Report: Google Home speakers download gigabytes while sitting idle

Some Google Home Speaker owners are reporting enormous background downloads, raising concerns for households with limited internet data allowances as Google rolls out a fix. ^{[1] [2]}

The clearest measured example comes from a speaker tracked by a 9to5Google reporter: it downloaded 17 GB in 24 hours despite receiving no voice commands or streaming any media during that period. Of that, 9.99 GB arrived at 3 a.m. Pacific time. Its total over 30 days reached 132 GB. ^[2]

The reports point chiefly to the new Google Home Speaker. They do not establish a fault across Google's smart-home range, and another lightly used speaker checked in a different household downloaded just two GB in a month. ^[2]

Google told 9to5Google that "a fix is already rolling out that should address this for users." The company has not confirmed the suggested explanation, a firmware update that repeatedly fails to download or install. ^{[1] [2]}

For owners, the useful first step is to check how much data the speaker is actually using. A device can appear idle while its network connection tells a different story.

A quiet speaker, a busy connection

On October 13, the same speaker tracked by 9to5Google downloaded 41 GB. That single day's traffic accounted for almost a third of its measured 30-day total. ^[2]

Other owners have described still larger totals. A Reddit user reported more than 200 GB of use per day, according to The Verge's October 20 account. That figure is an owner's report, not an independently verified measurement. ^[1]

A commenter on 9to5Google said that, among 14 Google speakers of different types, one of the newest models transferred 25 GB in 24 hours while unused. That account also remains an individual report. ^[2]

The contrast within the reporter's own checks is useful. The speaker that downloaded 132 GB in 30 days used roughly 66 times as much data as the other household's speaker did over a month. That does not establish what normal usage should be, but it shows why a single expected allowance for every Home Speaker would be misleading. ^[2]

The reporter also checked other Google Home and Nest devices and did not see the same pattern, including on Nest Hubs sharing the affected speaker's home network. ^[2]

The accounts surfaced over the week preceding The Verge's October 20 article, with 9to5Google publishing its measurements on October 19. The Verge said it had asked Google for more information about the cause and which devices were affected. ^{[1] [2]}

A fix before a confirmed explanation

A failed firmware update is one possible explanation raised in the reports. Firmware is the software that controls the device itself. If a download or installation fails and is attempted repeatedly, the repeated transfers could account for heavy background traffic. That remains a hypothesis, not Google's confirmed diagnosis. ^{[1] [2]}

Google's statement promises action without supplying a technical explanation. The cause, the contents of the downloads, the affected models and software versions, and the number of owners involved remain unknown. There is also no confirmed account of overage charges or service disruption, or a way identified by Google for owners to confirm that the fix has reached their speaker. ^{[1] [2]}

For a household with a capped internet plan, the practical concern is straightforward: background downloads count against an allowance even when nobody has asked the speaker to play anything. The reported totals make checking worthwhile before the next bill, rather than waiting for an audible sign that something is wrong.

A data allowance covers the household's other internet use too. An unattended speaker consuming a large share leaves less room for the activity people actually chose, whether that is streaming, downloading files or making video calls.

How to check your speaker

Most routers let owners inspect data use for individual connected devices. That device-level view is the place to look, because a household's overall total will also include its other internet activity. ^[2]

For Nest Wifi users, 9to5Google gives a specific route through the Google Home app: open the Wifi tab, choose Devices, select the speaker, then open Device usage graphs. Those graphs can display one-day, seven-day and 30-day periods. ^[2]

Look at both the recent total and the longer window. A large overnight transfer is easier to spot in a short view, while a month's history can show whether heavy use has accumulated over time. Compare those records with when the speaker was actually used, rather than treating any background activity as proof of this fault.

Google says its fix is rolling out. Whether it stops the excessive downloads is the next test. ^{[1] [2]}