Google Home's August update fixes Spotify, broadcasts and kelvin, not Gemini's ambitions

Google started rolling out a Google Home update on August 20 whose voice-facing items are improved Spotify request recognition, a reworked broadcast flow, and the ability to set light color temperature by voice to a specific kelvin value ^[1][2]. Read as a product signal rather than a changelog, it says the assistant is being repaired, not extended.

Take the three voice changes one at a time. Google's own wording on music is that it has "improved how [it] recognize[s] the songs, artists, and playlists you request on Spotify" ^[3], with no metric attached. 9to5Google reports that longtime users have found song requests hit or miss, and that general commands often get mistaken for music requests, producing random tunes at an uncomfortable volume ^[12]. Broadcasts now become two steps: you ask Gemini to broadcast, wait, then dictate the message ^[4]. Splitting one utterance into two is a reasonable trade when the single-shot parse is unreliable, but it is a trade, and it costs a turn every time. The kelvin control is the clearest case of all: setting a precise color temperature was already possible in the app, and what changed is that voice can now reach it ^[5]. That is plumbing between an existing setting and the microphone.

The rest of the update is the same shape. The app is getting consistent temperature units across all devices and support for European-style door locks ^[7]. Google says there should be fewer crashes on iOS and offline camera controls that stay consistent through connection problems ^[8], which follows recent support for more third-party cameras ^[9]. On Android, a bug that pinned camera streams at 360p is fixed, so affected cameras should stream at full resolution when the connection allows ^[10]. And a failed payment on Google Home Premium will now produce a clear alert instead of a silent lapse in features and camera storage ^[11]. By count, six non-voice fixes to three voice ones ^[13].

Two of those items are worth dwelling on because they are not assistant work at all. A camera stuck at 360p is a broken product for anyone who bought the camera to see faces, and a billing failure that quietly removes camera storage is a data-loss risk dressed as a subscription lapse. Those are the kinds of defects that accumulate when a platform is adding device classes faster than it is hardening the existing ones ^[9].

The context matters for how to weigh all of this. 9to5Google notes that recent Google Home updates have mostly gone to Gemini for Home and to the polish it needs, because it remains in early access ^[6]. An assistant that still needs its music intents disambiguated from its general intents, and its broadcast command split in half to survive contact with users, is not a system waiting on new features. It is a system working through its error rate.

What to watch: whether the next few changelogs continue to be repair work or start listing capabilities, which would indicate Google thinks the base is stable; whether Gemini for Home exits early access before or after the recognition complaints quiet down ^[6]; and whether the two-step broadcast survives contact with people who used the one-liner ^[4].