Google Home’s quieter update is about making the right device respond

Google Home’s October 29 update makes compatible Matter energy monitors more informative and tackles a collection of failures that can make a smart home feel unpredictable. The useful distinction is that this is several updates across an app, an early-access voice assistant and device firmware—not one switch that gives every household every feature.

The official release notes say the Android app can now show both current power and cumulative energy consumption for supported Matter plugs and monitors. It also distinguishes closure types such as garage doors, windows and blinds instead of presenting them all as a generic gate.

Power and energy answer different questions

The new readings describe two different quantities. Power is the rate of consumption at a particular moment; energy is the amount accumulated over time. Google lists milliwatts for the real-time reading and kilowatt-hours for the total.

That distinction helps explain why a low reading does not necessarily mean an appliance has used little energy. A device drawing modest power for many hours can accumulate more consumption than a more demanding one used briefly. The practical benefit of showing both is that a smart plug becomes more useful for understanding a pattern, rather than merely confirming that something is switched on.

The hardware must actually measure the relevant values. Matter compatibility alone does not establish that every plug contains energy-monitoring hardware or exposes the data needed by the app. The release note explicitly limits the display to supported devices.

For doors and blinds, the improvement is less numerical but similarly practical. The right icon and controls help distinguish what a device does. A screen that treats a cabinet, window and garage door as the same generic object asks the user to supply context the software already ought to understand.

A voice command should affect the intended room

The Gemini for Home early-access section addresses moving audio between rooms, distinguishing media sleep timers from ordinary timers and reducing unsolicited “didn’t understand” responses. It also fixes a case where a volume request for another room could affect the speaker receiving the instruction when the intended device could not be found.

That last behavior illustrates the trust problem in home automation. Failing to find the requested speaker is understandable; silently changing a different one is harder to interpret. Predictability depends on an action being attached to the right target, not simply on the assistant recognizing a volume-related phrase.

These are early-access assistant changes. They do not establish that Gemini for Home is available in every country, language or household where the Google Home app can be installed. The independent overview of the update likewise covers several parts of the ecosystem, which should not be mistaken for one uniform rollout.

Older hardware gets less visible repairs

The camera section includes reconnection fixes for several first-generation Nest cameras migrated into Google Home. It also addresses an iOS event-timeline error and a foldable-phone case in which a full-screen live stream could remain on a loading spinner after the phone changed shape.

Those repairs matter because a camera’s usefulness depends on reaching the image when it is needed. A better object-recognition claim is of little comfort if a brief network interruption leaves the camera stalled.

The update therefore has two kinds of value: new information from compatible devices and fewer surprises from existing ones. In our smart-home coverage, the latter deserves as much attention as another headline feature. A home that reliably changes the right speaker’s volume has solved a real problem, even when the successful result is that nobody notices the software at all.