How to set up Gemini for Home voice commands
Move Google speakers and displays to Gemini for Home: early-access signup, the version requirements, the one-way upgrade flow, and the first voice commands to verify Gemini is actually responding.
Before the upgrade button, check the gates
Setting up Gemini for Home voice commands is not the same as trying a new app feature. As of this guide’s Aug. 25, 2026 publication date, Google still documents Gemini for Home as an early-access migration with account, country, language, app-version, and device-firmware requirements — and the switch from Google Assistant to Gemini cannot be reverted after you upgrade. Google’s minimums include a personal Google Account rather than a Workspace account, Google Home app 4.1 or later, Cast firmware 3.76 or later on speakers, and Fuchsia 28 or later on smart displays. Early-access availability is documented as country- and language-dependent, so re-check the current list before treating any speaker banner as permission to proceed. [1][2]
That sounds fussy until the speaker is in the kitchen, someone is cooking, and the family timer suddenly depends on a migration you cannot undo. Run the checks first, then request access.
| Preflight check | What has to be true before you continue |
|---|---|
| Google account | Use a personal Google Account. Google documents Gemini for Home eligibility separately from Workspace accounts. [1] |
| Country and language | Early access must be available in your country and language. Google documented 20 early-access countries and 10 languages at crawl time, but that list may have changed by publication. [1] |
| Google Home app | Update the Google Home app to version 4.1 or later before looking for the Gemini for Home early-access path. [1] |
| Speakers | Google speakers need Cast firmware 3.76 or later. Check the device firmware before assuming an invitation or banner will work. [1] |
| Smart displays | Nest displays need Fuchsia 28 or later. Displays are not cleared just because the phone app is current. [1] |
| Household timing | Do the migration when no one is depending on active timers, alarms, media playback, or a routine that has to fire immediately. |
If any row is uncertain, pause there. The useful setup question is not whether Gemini is more capable in theory; it is whether the actual speaker or display that controls your lights, music, alarms, and routines is eligible today.
Request early access in the order Google expects
Google’s documented setup path starts outside the tempting “tap whatever appears” instinct. First, your Google Groups settings must allow group invitations: turn on the option that lets group managers add you to their groups, shown as “Add me to their groups.” Then use the Google Home app path: profile icon, Home settings, Early Access. After you request access, wait for the invitation rather than hunting for a hidden Gemini switch. Google’s flow then continues through an “Introducing Gemini for Home” notification and the “Get started” prompts in the Home app. [2]
9to5Google’s early-access walkthrough shows the same broad signup sequence from the user side: enable the relevant Google Groups setting, enter Early Access through Google Home settings, then wait for the Gemini for Home invitation before upgrading. Treat that as helpful color on the process, not a replacement for Google’s current eligibility page. [3]
- Open your Google Groups settings and allow “Add me to their groups.”
- Open the Google Home app with the personal Google Account that manages the home.
- Tap your profile icon.
- Go to Home settings.
- Open Early Access.
- Request Gemini for Home early access, then wait for the invitation.
- When invited, use the “Introducing Gemini for Home” notification and follow the “Get started” prompts.
Do not read the absence of an invitation as a mystery bug. It can simply mean one of the gates has not been met, the invitation has not arrived, or availability has not reached your country-language combination.
Treat the Assistant-to-Gemini upgrade as the commitment point
The “Introducing Gemini for Home” notification is where the setup changes from signup to migration. Google says that once you upgrade from Assistant to Gemini for Home, you cannot switch back to Google Assistant. That warning belongs before the tap, not after a feature tour. [1][2]
Pick a boring moment to do it. Stop any active cooking timers you cannot afford to lose track of. Warn anyone who relies on voice-controlled lights, alarms, or media. If a routine is due to run in the next few minutes, wait. None of that makes the setup difficult; it just keeps the household from becoming the test bench.
If you run a dense Google Home setup, keep your automations notes nearby. Gemini for Home can help with smart-home control, but migration day is not the time to redesign every routine. For deeper routine work after the voice assistant is stable, use NestGrid’s Google Home automations guide.
Verify that Gemini, not Assistant, is answering
After the prompts finish, do not stop at “the app accepted the upgrade.” The speaker or display has to prove that the new assistant is the one taking voice commands.
Start with the simplest identity check: say, “Hey Google, who are you?” Google says Gemini identifies itself as a language model. Google also documents a voice-name clue: Gemini for Home uses plant-named voices such as Pothos, while Google Assistant uses color-named voices such as Red. [1]
Then run ordinary commands. A migration is only useful if the boring jobs still work.
| What to test | Example voice command | What you are checking |
|---|---|---|
| Basic smart-home control | “Hey Google, turn on the kitchen lights.” | The speaker can still reach a room device and execute a direct command. Google’s smart-home command examples continue to use “Hey Google” phrasing. [4] |
| Dimming or device adjustment | “Hey Google, dim the living room lights.” | Gemini is not only hearing device names; it is applying a supported control action. [4] |
| Media | “Hey Google, play music on the kitchen speaker.” | Media requests still route to the expected speaker or display. Google lists media among Gemini for Home features that do not require Premium. [2] |
| Timers and alarms | “Hey Google, set a timer for 10 minutes.” | The household utility jobs still work after migration. Google lists alarms and timers among non-Premium Gemini for Home capabilities. [2] |
| Lists, notes, or reminders | “Hey Google, add milk to my shopping list.” | Everyday assistant memory tasks still land where your household expects them. [2] |
| Calendar | “Hey Google, what’s on my calendar today?” | Calendar access is still responding through the migrated assistant. [2] |
Keep the first pass narrow. If “turn on the kitchen lights” fails, do not jump straight to a long, conversational multi-device request. Check whether the device name, room, account, and home membership are right in the Google Home app before blaming Gemini’s language model.
Separate free voice commands from Premium features
The first-command test should focus on the features Google documents as available without Google Home Premium: smart-home controls, media, alarms and timers, calendar, notes, lists, and reminders. Those are the commands most homes notice immediately if they break. [2]
Google places Gemini Live, camera-history search, and Home Brief behind Google Home Premium. Google describes Premium plans as starting at $10 per month, but subscription packaging and pricing can change; confirm the current offer in the Google Home app or on Google’s current plan page before paying just to test a setup step. [2]
Once the basic commands pass, Google’s own “100 things to try” list is a useful source for broader phrasing ideas — follow-up questions, more natural household requests, and more ambitious smart-home prompts. Save that for after the migration has passed the dull checks. [5]
If the first commands do not behave cleanly
A failed first command does not automatically mean the Gemini upgrade failed. Work backward from the control path. Is the same device visible in the Google Home app? Is it assigned to the room name you used? Does a simpler command work? Does another speaker in the same home respond differently?
For Matter devices or hub-dependent accessories, voice assistant setup may expose a controller or bridge problem that was already there. If your issue is less “Gemini did not migrate” and more “which platform is actually controlling this device,” NestGrid’s Matter and hub compatibility guide is the better next stop.
At this point the setup task is complete only if three things are true: your account and devices passed Google’s current eligibility checks, the one-way upgrade finished through the Home app prompts, and the speaker or display can prove Gemini is responding through identity, voice-name, and ordinary household command tests.
References
- Learn about Gemini for Home voice assistant, Google Help.
- Get started with Gemini for Home features, Google Help.
- Gemini for Google Home: How to sign up for early access, 9to5Google, Oct. 31, 2025.
- Control your home devices by voice, Google Help.
- 100 things to try with your Gemini for Home voice assistant, Google, June 2026.