Response error execute intent but google home mini/ google home app always return success
See original GitHub issueI response error execute intent
for offline devices like the following code:
const {smarthome} = require('actions-on-google');
const app = smarthome();
// ...
app.onExecute((body, headers) => {
// TODO Send command to device
return {
requestId: body.requestId,
payload: {
commands: [{
ids: ["456"],
status: "ERROR",
errorCode: "offline"
}]
}
};
});
But google home mini/ google home app say “you got it, turn xxx on/off”.
Issue Analytics
- State:
- Created 4 years ago
- Comments:11 (5 by maintainers)
Top Results From Across the Web
Errors and exceptions | Cloud-to-cloud | Google Home
This document lists the officially-supported errors and exceptions for smart home devices. Please use these given errors and exceptions codes in the intent...
Read more >Troubleshoot Assistant not connecting - Google Nest Help
Unplug your Google Nest or Home speaker or display. Wait for 10 seconds, then plug it back in. Wait for the device to...
Read more >Account linking succeeds, error message is reported ... - GitHub
Unable to SYNC test devices in Google Home companion app #26 ... (i.e returns empty array in SYNC response) and it says account...
Read more >Google Home not getting a valid assistant response when ...
I have integrated google assistant into my own app. When executing an action for a LIGHT device type, such as turning it on/off,...
Read more >How to Set Up a Smart Home - Google Store
Nest Audio speakers come with Google Assistant , a voice assistant that helps you get things done. Just say “Hey Google” followed by...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Ok, i have the same problème, and i finally find the solution. You’r
ids []
need to containstring
notint
so just useid.toString
. It work for me.I’m not able to reproduce this issue,