Product1 publisher2 min readPublished
Google Home's fifteen-item update is almost entirely repair work
The Google Home changelog itemises fifteen fixes, including widgets that kept polling cameras while the phone sat locked. In the same release, Google opened device state and event history to outside AI agents.
The Product Desk · Product desk
What happened
- droid-life reports at least 15 changes heading to the Google Home app and Gemini for Home, and says most of them are not new features.
- The app changelog lists more reliable multi-account switching, with fewer "Home not found" errors and fewer preference resets for people running several Google accounts.
- Gemini for Home, still in early access, gets five voice assistant fixes covering follow-up questions, broadcasts, personal playlists, Live Mode self-interruptions and TV streaming on smart displays.
Compiled by The Product DeskSomething wrong?How this is made
Why it matters
- exposure Google says any agent supporting MCP tool calls, including Claude, Hermes and OpenClaw, can reach devices and event history, so the people who live in the house become readable by software the account holder picks.
- constraint Agent answers can only be as good as the state the platform reports, and the grayed-out sensor and detector tile bug is listed as resolved only in this release.
- decision Households running battery cameras now have a reason to revisit widgets they pulled off the home screen, and a reason to check whether recharge intervals actually lengthen after the update lands.
Google's release note has an answer for doorbell cameras on rechargeable packs that keep needing a charge. The app's home screen widgets were polling in the background, and pausing that polling when the screen is off, locked or running a screensaver saves battery on the phone and on connected cameras [3].
The count of at least 15 that droid-life reports holds up against the itemised list [1]. Five entries sit under Gemini for Home's voice assistant [10], seven under Google Home app quality improvements [3][4][5][6][7][8][9], and three are camera stream fixes, two on Android and one on iOS [16]. That is fifteen [1]. Each entry names something that was failing: account switching threw "Home not found" errors and reset preferences [4], Wi-Fi pairing stalled during setup [6], and Google TV crashed on startup [7].
Two of the fifteen concern smoke and carbon monoxide devices [2]. Detector tiles, along with sensors and cameras, could appear grayed out after you came back from a device controller screen, which Google lists as resolved [5]. Separately, Google is rolling out notification changes so smoke and CO alarms show current device status in the app [9].
Everything else on the list repairs behavior that already shipped. The one addition is Google Home MCP, now in early access, which droid-life describes as a first step toward letting AI agents interact with your Google Home [17][3]. Google said, in a passage quoted by droid-life: "Any agent that supports calling MCP tools, such as Google Antigravity, Claude, Hermes, OpenClaw or others, can now interact with all of the devices and event history in the Google Home ecosystem" [18]. droid-life's examples include asking an agent to look into cameras to tell you what your kids did after school, how long lights were left on over the past week, and how many loads of laundry were done [19]. Agents can also assemble a custom dashboard [20].
So the read path opens to third-party agents in the same release that documents tiles misreporting device state [5][17]. An agent has no tile to gray out, so what you get is a sentence, and the sentence reads the same whether the state behind it is fresh or three hours stale.
The forcing question is whether the agent is reading state or changing it, and whether a wrong answer is an annoyance or a safety event. A stale answer about lights or laundry counts leaves you with an incorrect number of hours [19]. A wrong read on a smoke or CO detector is the safety case, and those are the two entries Google spent this release fixing [2].
What to watch
- Whether Google Home MCP moves out of early access, and whether agents get write actions on locks and thermostats alongside reads.
- Whether any of these fifteen entries reappears in a later changelog, which would mean the fix did not hold.
- Whether Google publishes per-agent permissions or an audit trail showing which agent read which camera event history.