Google Gemini Update Finally Fixes Spotify Playback and Voice Commands

Forbes reports that Google's late-August patch for the Google Home app and Gemini for Home isn't a flashy feature drop — it's a collection of targeted fixes aimed at the rough edges users have been complaining about since the assistant's early access rollout. If you've been wrestling with a smart speaker that ignores your playlist request, or a broadcast command that swallows half your sentence, the trigger conditions are finally getting rewritten. This is less "new gadget" and more "the runtime got debugged," which is exactly what the ecosystem needed.

The Spotify payload finally parses

The headline change is recognition, not recommendations. Gemini for Home now better parses requests aimed at specific songs, artists, and — crucially — personal playlists like your Liked Songs. There's a single gate in front of that logic, though: Personal Results has to be enabled in your Google account settings, otherwise the assistant treats your library as an unknown variable. If you've been shouting "Hey Google, play my Discover Weekly" into a Nest Hub and watching it confidently queue up a podcast instead, that's the misfiring lookup the update is meant to resolve.

Voice commands: broadcasts, kelvins, and European locks

Two structural changes to how the assistant handles multi-step intents. Broadcasts now accept a two-phase payload: trigger the function with "Hey Google, broadcast message," then deliver the actual message in a follow-up utterance. It reads like a basic webhook handshake — open the channel, then POST the body — and it removes the awkwardness of cramming your entire announcement into one breath.

Lighting control gets more granular too. You can now specify color temperature in exact kelvins ("make the living room lights 2,400 kelvins"), assuming your bulbs expose that attribute on the local network. The update also deepens support for European-style smart locks, splitting unlatch and unlock into independent actions and surfacing richer state strings like "Unlocked and latched" inside the app. Translation: less guesswork for routines that branch on door state.

Camera stream cleanup and the thermostat rounding bug

Several nagging reliability issues get patched alongside the voice improvements. iOS camera-stream crashes — the kind that force-quit the Home app mid-viewing — have been addressed, and viewing controls remain accessible even when a camera goes offline or loses its connection. On Android, the hard 360p stream lock has been lifted, which should let capable cameras negotiate a higher resolution again.

Thermostat logic got a quiet but useful fix as well. Temperature units (Celsius vs. Fahrenheit) are now consistent across the app, voice surface, and Nest hardware, and a specific iOS bug that rounded half-degree Fahrenheit setpoints down to whole numbers is resolved. If you've built automations around precise threshold values, now's the moment to re-verify those triggers before assuming the new build matches your old YAML.

Net effect: no new toys, but the existing ones stop throwing exceptions quite so often. Worth a manual app update on every household device — the rollout appears staggered, and some Nest speakers won't see it until they ping home.