A EUR119.99 launch that arrived five weeks late

Google's Home Speaker went on sale in Germany on 4 August 2026, priced at EUR119.99 including VAT and sold through the Google Store, MediaMarkt and Saturn in Porcelain and Hazel finishes, according to Google's own German product announcement. The price sits roughly EUR20 above the device's 99.99 US dollar list price, a gap in line with standard eurozone VAT and distribution adjustments rather than anything unusual.

Germany was not first in line. Google had already sold the same speaker in 18 other countries, including neighbouring Austria and Switzerland, from 25 June 2026, and German coverage of the launch openly describes it as delayed against Google's own spring 2026 timeline. For a company that treats Germany as its largest EU hardware market, a staggered rollout of this length is itself notable: the product Google is selling into that market on day one is not the freshest build of the hardware, it is a device that has already been on sale, and iterated on, elsewhere for over a month.

What is inside: Gemini for Google Home, and a Thread hub

Google markets the speaker around 'Gemini for Google Home': natural multi-step commands handled in one instruction, contextual follow-up questions without repeating a wake phrase, and continuous conversation mode across all supported languages, per Google's own product page. A Google Home Premium subscription layers on Gemini Live dialogue, camera-footage search on compatible Nest cameras and automated home briefings; buyers who purchase before 30 September 2026 get six months of Premium free.

Underneath the assistant layer sits a second, quieter role: the speaker is a Thread border router that also functions as a Matter controller, meaning it can bridge Thread-based sensors, door locks and lighting directly into a smart-home network without a separate hub, per independent German technical coverage of the launch. That border-router role is the one piece of this launch that is not primarily about Gemini at all, and it is where the story gets more interesting than a product-launch write-up suggests.

The gap: Thread 1.3 hardware after the industry moved to 1.4

That border router runs Thread 1.3. The Thread Group, the industry body that governs the protocol, has since published Thread 1.4.1 as its current specification, and, per coverage of the rollout, made Thread 1.4 the sole certification standard for new border routers as of 1 January 2026 -- more than seven months before Google's German launch. Thread 1.4 is not a cosmetic revision: it adds credential sharing for faster, more secure device onboarding, standardizes IPv6 connectivity across the mesh, and improves network diagnostics and routing reliability.

Reporting on the 1.4 transition explicitly places Google Home among the ecosystems still 'at varying stages of testing and rollout', alongside Amazon and Samsung SmartThings, while Apple had already shipped 1.4 support in tvOS 26. None of this means Google's speaker is non-functional or unsafe -- Thread is built for backward compatibility at the mesh level, and a 1.3 border router will still talk to most current devices. What it means is that Google entered its biggest EU hardware market with a flagship smart-home hub running a protocol version the industry itself had already superseded before the product reached German shelves.

Why this matters beyond one speaker

For a EU or UK business specifying a Thread- or Matter-based deployment -- an integrator wiring up a smart building, a hospitality group standardizing room controls, a facilities team choosing sensors for a new site -- the practical lesson is not 'avoid Google'. It is that a recognisable brand and a fresh launch date are not, on their own, evidence of current-spec compliance. Thread and Matter are still young enough, and moving fast enough, that individual SKUs can lag the spec their own maker helped write, and the gap will not show up on a spec sheet or a retail listing; it only surfaces once mixed-version networks start producing the connectivity instability and failed automations that reporting on the 1.4 rollout already documents across brands.

The fix is procedural, not dramatic: verify the actual protocol version per device and per firmware build before it goes into a deployment plan, ask the vendor directly whether a Thread 1.4 update is committed and dated, and treat 'Thread-certified' as a starting point for due diligence rather than the end of it. Google's own Germany launch is proof that even the company steering the ecosystem will ship a device that is already behind its own standard on day one.