2 weeks ago
I've tried creating some really simple scripted Home automations using the starter:
starters:
- type: assistant.event.OkGoogle
eventData: query
is: test phrase
and a simple action to turn a light on with no Conditions...
But when I try to trigger them using the test phrase with Gemini on my Pixel, it recognises it's supposed to start a routine/automation ("Okay, starting your routine" and "You used a command to start an automation that can be edited in the Home app") but then a second later it shows another message "It looks like there isn't an automation set up for that yet". Which is completely contradicting itself - and nothing further happens. Nothing shows up in the Home activity tab and I can't see any way to further diagnose this.
Am I doing something wrong here? I tried switching to using the old Google Assistant on my phone but that did nothing either and didn't generate any messages at all.
Thanks
Answered! Go to the Recommended Answer.
a week ago
The assistant.event.OkGoogle
starter isn't triggering your automation properly. This is a known issue with the Gemini integration on Pixel devices.
When you say the test phrase, Gemini recognizes it should start a routine but then fails to find/execute it, giving conflicting messages.
Instead of using assistant.event.OkGoogle
as the starter, create a custom voice command starter with your exact phrase. Go to:
This bypasses the OkGoogle event handler and uses direct phrase matching, which is more reliable with Gemini.
If that still fails: The issue may be Gemini not properly handing off to the Home automation system. Try temporarily switching your default assistant back to Google Assistant (not Gemini) in your phone settings to test if the automation works there.
This is a Gemini integration bug we're tracking. Report it through the Home app feedback with your exact setup details.
a week ago
Thanks - can you tell me where the custom voice command starter is, I can't see it in the Scripting documentation?
I've already tried using Google Assistant instead of Gemini, it does nothing either and doesn't even bother to give an error or tell you it's recognised it as a routine.
a week ago
To find the custom voice command starter option in the Google Home app:
If the "Voice command" option isn't visible as a starter type, make sure your Google Home app is fully updated.
Regarding Google Assistant doing nothing - that's actually expected behavior if you haven't created the automation yet. Once you set up the automation with the voice command starter, Google Assistant will recognize and execute it when you say the phrase.
The key difference: assistant.event.OkGoogle
is an event-based trigger (which has the Gemini bug), while "Voice command" is direct phrase matching (which works reliably).
a week ago
The assistant.event.OkGoogle
starter isn't triggering your automation properly. This is a known issue with the Gemini integration on Pixel devices.
When you say the test phrase, Gemini recognizes it should start a routine but then fails to find/execute it, giving conflicting messages.
Instead of using assistant.event.OkGoogle
as the starter, create a custom voice command starter with your exact phrase. Go to:
This bypasses the OkGoogle event handler and uses direct phrase matching, which is more reliable with Gemini.
If that still fails: The issue may be Gemini not properly handing off to the Home automation system. Try temporarily switching your default assistant back to Google Assistant (not Gemini) in your phone settings to test if the automation works there.
This is a Gemini integration bug we're tracking. Report it through the Home app feedback with your exact setup details.
a week ago
Thanks - can you tell me where the custom voice command starter is, I can't see it in the Scripting documentation?
I've already tried using Google Assistant instead of Gemini, it does nothing either and doesn't even bother to give an error or tell you it's recognised it as a routine.
a week ago
To find the custom voice command starter option in the Google Home app:
If the "Voice command" option isn't visible as a starter type, make sure your Google Home app is fully updated.
Regarding Google Assistant doing nothing - that's actually expected behavior if you haven't created the automation yet. Once you set up the automation with the voice command starter, Google Assistant will recognize and execute it when you say the phrase.
The key difference: assistant.event.OkGoogle
is an event-based trigger (which has the Gemini bug), while "Voice command" is direct phrase matching (which works reliably).
Friday
Hi - thanks but that's not using the scripting? That's just using the built-in automation wizard.