Say "Hey Google," And Your Phone Listens Instantly. Say Anything Else, And Nothing Happens.

That gap isn't an accident. On an Android phone, Gemini runs a persistent, always-on listening process at the operating system level. It can hear its own wake word with the screen off, read whatever's on your screen, and act inside other apps through privileged programming interfaces. Say anything to a competing assistant on the same phone, and nothing happens, because Google never built Android to listen for it. That was a choice Google made about its own operating system, not a technical ceiling.

On 16 July 2026, the European Commission decided that decision wasn't Google's to make alone anymore.

What Brussels actually ordered

The Commission issued two binding specification decisions against Google under the EU's Digital Markets Act. The one that matters here forces Google to give rival AI assistants the same system-level access to Android that Gemini already has. That covers eleven specific features across four categories. Rivals get to register their own wake word and home-button trigger instead of leaving both to Google alone. They get the same access to on-screen content, the microphone, the camera and sensor data, with the user's consent. And they can execute tasks inside Gmail, Maps, Messages and other apps through the same structured programming interfaces Gemini uses, calling the same on-device Gemini Nano models instead of routing every request to the cloud.

Roughly 60% of EU mobile users carry an Android device. Without this order, every AI assistant that isn't Gemini was competing for their attention from inside an app icon, while Google's own assistant sat one level up, baked into the operating system itself.

None of it lands immediately. Five of the eleven features are sensitive enough that Google can still require certification, with draft terms due by 1 February 2027 and final terms by 1 May 2027. The features that matter most on a real device, wake-word registration, screen context, cross-app actions, are due in Android 18 by 1 August 2027. Letting several competing assistants each hold their own wake word at the same time doesn't arrive until Android 19, a full year after that. The proceeding itself opened back in January 2026. Getting Google to open its own front door took six months of formal process and a compliance calendar that runs into 2028.

To be fair to Google, its objection isn't baseless. Kent Walker, Alphabet's president of global affairs, argued the same day that phone manufacturers currently vet any app requesting this level of device access, and that the Commission's order removes that check without fully replacing it. That's a legitimate security question, not just a company protecting its turf, and it's one regulators and Google will keep arguing about as the 2027 deadlines get closer.

The detail that caught my eye

The Open Home Foundation, the non-profit behind Home Assistant, wasn't a bystander in this. Their own Android developer was invited by the European Commission to consult directly on what Android interoperability should look like, because Home Assistant has spent years trying to give people an assistant and an automation platform that isn't locked to one company's hardware. That's the same organisation behind the platform sitting at the centre of most of my installs.

KNX never needed anyone's permission

Here's what struck me reading through the timeline. It took a European regulator the better part of two years, two rounds of published proposals, and a compliance schedule running to 2028, just to get one company to let competitors talk to its own operating system on equal terms.

KNX has worked the other way since 1990. Any certified device from any of the 500-plus manufacturers building on the standard already reads and writes the same group addresses on the same bus. Nobody had to petition anyone for that, and nobody controls a certification tier that a rival's product has to clear before it's allowed to fully participate. It was built open from the group address up, because no single manufacturer owned the standard to begin with.

I'll be honest about where this comparison stretches thin. KNX is a wired field-bus protocol for lighting, climate, shading and access control. What the EU just ordered is interoperability at the level of a phone's operating system and its voice assistant, an entirely different problem on an entirely different layer of the stack. I'm not claiming KNX and Android interoperability are the same fight. But the underlying principle holds either way: an ecosystem is only as open as its most tightly controlled layer allows it to be, and somebody always has to decide whether that gate gets built at all.

Why this matters for what goes in your walls

Voice assistants and phone operating systems will keep needing this kind of correction, because a single company controlling the layer everyone else has to build on top of will always be tempted to keep the good parts for itself. That's not a criticism unique to Google. It's what happens whenever one vendor owns the platform.

The automation backbone in your home doesn't have to work that way. When lighting, climate, security and shading run on an open bus that no single manufacturer owns, and the intelligence layer on top is Home Assistant, hosted locally rather than depending on one company's cloud roadmap, you're not waiting on anyone's compliance deadline to add a new device, switch a supplier, or bring in a specialist your original installer never heard of. That was true in 1990 and it's still true now, regardless of what Brussels has to order Google to do next.

Just a conversation about what the project needs.

wayne@knxlogic.co.za | 082 564 3982 | www.knxlogic.co.za