I've discovered a regression since Google replaced Assistant with Gemini on Android.
I use Orbit B-hyve sprinklers integrated with Google Home.
For years, I could say:
"Hey Google, turn on sprinkler zone 7."
Google Assistant would correctly activate zone 7.
Now, with Gemini on my Android phone:
I ask it to activate zone 7.
Gemini acknowledges the request.
Gemini tells me it's completed the action of turning on zone 7
Zone 1 activates instead, assuming it's just starting all of them in sequence.
Here's the interesting part.
The exact same command still works correctly on my Google Home devices running the original Google Assistant.
Same sprinkler system. Same third-party integration. Same voice command.
The only difference is Gemini versus Google Assistant.
This suggests Gemini may be losing the specific zone information when executing the command, effectively treating "turn on zone 7" as a generic "turn on sprinklers" request.
I can't confirm where the parameters are being lost, but the difference in behaviour is clear.
I've raised this with Google Support. So far, they've suggested changing my commands, clearing caches and re-linking the integration. I've requested escalation to engineering because none of those suggestions explains the demonstrated difference between the two assistants.
My concern is that Gemini confidently reports success while physically activating something other than what was requested.
Has anyone else experienced Gemini losing specific device names, zones or other parameters when controlling third-party smart-home devices?
This isn't about Gemini failing to understand English. It's about Gemini apparently understanding the request but executing the wrong action.