August 2, 2026
Amazon and Google have both replaced their voice assistants with generative AI versions this year: Alexa+ on Amazon's side, Gemini for Home on Google's. Both rollouts have been widely covered, and both have generated real friction with existing users. For anyone with, or considering, a professionally integrated Lutron, Savant, Control4, or Crestron system, it's worth separating what actually changes from what's just noise in the tech press.
Amazon rolled out Alexa+ broadly to Prime members this year, an automatic upgrade for many existing Echo device owners rather than an opt-in choice. Google has been replacing Google Assistant with Gemini for Home across Nest speakers and displays, starting in the US and expanding by region through 2026, alongside a new Gemini-native Google Home Speaker. Both moves represent a real technology shift: the assistants now use large language models capable of understanding multi-step requests and holding a more natural conversation, instead of the rigid command-matching the previous generation relied on.
The complaints aren't really about the AI itself. They're about control and predictability. Amazon removed a Do Not Send Voice Recordings privacy option as part of the Alexa+ rollout, which frustrated longtime users who had specifically opted out of that data handling. Some Prime members found themselves automatically upgraded without asking for it. On Google's side, the rollout has been confusing largely because of timing: it's arriving region by region, so two households with identical hardware might be running different assistants depending on where they live, and switching a Nest or Google Home speaker over to Gemini can't currently be reversed on that device once it's done. None of this is a reliability problem with the underlying smart home control. It's a rollout and communication problem layered on top of it.
Lutron, Savant, Control4, and Crestron all support voice control through Alexa and Google Assistant at the command level, and that compatibility is not going away as the underlying assistants get smarter, it's the same voice command bridge either company has offered for years. The lighting, shading, security, and climate control on a properly designed estate system doesn't run through Alexa or Google at all; voice is a convenience layer sitting on top of a system that keeps working identically whether you say good night to a keypad button, an app, or a voice assistant. If Amazon or Google changes something about how their assistant behaves, worst case, a voice command needs to be re-set up. The system underneath it, and every other way of controlling it, keeps working exactly as it did before.
The one place this is genuinely worth a conversation with your integrator is if voice control is a primary way your household uses the system day to day, rather than a backup to keypads and the app. If that's the case, ask which assistant your platform integrates with most cleanly. Savant, as covered in our piece on Apple HomeKit integration, tends to be the most natively Apple-friendly of the professional platforms, which matters less for the Alexa and Gemini question specifically but is part of the same underlying decision: how much of your day-to-day control do you want routed through a third-party consumer assistant, versus a keypad or app that answers directly to your integrator rather than to Amazon's or Google's product roadmap.
Alexa+ and Gemini for Home are, in a sense, both trying to solve the same coordination problem that Matter is solving from the standards side: too many disconnected consumer devices, not enough of them working together predictably. A smarter voice layer on top of a fragmented DIY smart home genuinely helps. It's a much smaller improvement on top of a system that was already unified before the AI assistant showed up, which is the position a well-designed Lutron, Savant, or Control4 estate is already in. The assistant gets smarter. The house was already working.
We configure voice integration as part of the standard programming scope on any platform that supports it, and we keep an eye on changes like this specifically so a client doesn't have to. If Amazon or Google changes something that affects a voice command on your system, that's a five-minute fix during a routine service visit, not a reason to worry about the system itself. If you're deciding on a platform now and voice control matters to your household, it's worth raising directly at the site visit, alongside the other platform-fit questions worth asking before signing off on a system.
.svg)
