Google Home devices hit by odd bug that stops them answering simple queries
News auto_awesomeAI

Google Home devices hit by odd bug that stops them answering simple queries

By Android Mobiles Newsroom •14 Oct 2026 •4 min read
share bookmark
bolt Quick Read

What’s happening?

Users of Google Home smart speakers and displays have started posting on Reddit that the voice assistant suddenly stops answering everyday questions. A typical complaint reads like this: when asked whether Columbus Day is a federal holiday, the device replies with the generic “I’m sorry, I don’t understand that,” even though it can still define the term federal holiday.

Another common scenario involves kitchen‑related queries – asking for a chocolate chip cookie recipe or a pasta sauce tip – and receiving the same error message. Strangely, the same devices continue to set timers, launch music, and pull live sports scores without any hiccup.

Who is affected?

The problem seems to be confined to the older Google Assistant‑based Home experience. Several Reddit posters specifically mention they are running the classic Assistant firmware rather than the newer Gemini for Home platform that Google rolled out earlier this year. So far, no user has reported the issue on a Gemini‑enabled device, and the Android Authority article notes that the bug has not been observed on that version.

Why might this be happening?

Google has not issued an official statement, but a few theories are circulating in the community:

  1. Partial API failure – The assistant’s knowledge‑graph queries that handle factual information may be timing out, while the more procedural commands (timers, alarms) use a different backend that remains functional.
  2. Transition to Gemini – Some commenters speculate that the glitch could be an unintended side‑effect of Google nudging users toward the newer Gemini model, but there is no evidence to support this claim.
  3. Firmware regression – A recent over‑the‑air update for legacy devices might have introduced a regression in the natural‑language processing stack.

Until Google confirms the root cause, these remain educated guesses.

What can UK users do right now?

If you own a Google Home speaker or Nest Hub and are experiencing the issue, try the following steps:

If none of these actions help, keep an eye on Google’s support forums and the Android Authority article for any official patch notes.

Impact on smart‑home setups and contract deals

For UK shoppers who bundle a Google Home device with a mobile contract, the bug could be a minor annoyance but not a deal‑breaker. Most carriers include the speaker as a complimentary add‑on, and the hardware itself is usually covered by a one‑year warranty. If the problem proves widespread, you may be able to request a replacement or a firmware‑updated unit from the retailer.

From a broader perspective, the incident highlights the importance of software stability in the smart‑home ecosystem. When a voice assistant can’t answer basic queries, it undermines the convenience factor that convinces many buyers to upgrade their home Wi‑Fi or switch to a data‑rich mobile plan.

When will it be fixed?

Android Authority has reached out to Google for comment and promised to update the story once a response is received. In the meantime, the community’s consensus is that the issue is temporary and will likely be addressed in a forthcoming OTA (over‑the‑air) patch aimed at legacy Assistant devices.

Bottom line

If you rely on your Google Home for daily information, keep your firmware up‑to‑date and consider switching to the newer Gemini platform where possible. Stay tuned for further updates as Google works to resolve the glitch.

Source: Android Authority — Irritating Google Home bug refuses to answer your basic questions (published 7 Sep 2026).
auto_awesomeCreated with AI 14 Oct 2026

Related articles