yesterday
Hello,
Device configuration
Description of the issue
All Smart Home API commands work correctly when called directly.
The integration also passes all tests in Developer Console → Cloud‑to‑Cloud → Test Suite with no errors.
However, when issuing the voice command:
“Turn on MY‑DEVICE”
the Assistant (Gemini) responds with:
“I’m sorry, I wasn’t able to turn on MY‑DEVICE. There seems to be an issue with the device.”
Despite this spoken error:
In other words, the voice response is incorrect, but the command execution, device behavior, and Home app state are all correct.
SYNC:
Answered! Go to the Recommended Answer.
yesterday
When you issue a voice command to "Turn on," Gemini/Assistant performs a validation check. If it sees activeThermostatMode: none, it interprets this as the device being in a "stalled" or "idle" state despite the SUCCESS status, which triggers the "There seems to be an issue" fallback speech.
The voice command "Turn on [Device]" maps to action.devices.commands.OnOff.
We recommend few options to fix this:
yesterday
When you issue a voice command to "Turn on," Gemini/Assistant performs a validation check. If it sees activeThermostatMode: none, it interprets this as the device being in a "stalled" or "idle" state despite the SUCCESS status, which triggers the "There seems to be an issue" fallback speech.
The voice command "Turn on [Device]" maps to action.devices.commands.OnOff.
We recommend few options to fix this:
9 hours ago
Thank you! All works now.