When trying to generate credentials with the authorization tool, the tool prompts you to visit a URL and sign in to your Google account. The page then displays an error message (for example, "Something went wrong").
- Make sure you enabled the Google Assistant API and configured the OAuth consent screen in Configure a Developer Project and Account Settings.
The Google Assistant responds Actually, there are some basic settings that need your permission first...
- Set activity controls for the account that you used when setting the authorization code.
Voice recognition issues
Assistant responds I don't know how to help with that or I don't understand.
- Verify that your voice was recognized properly. Check the sample code output for a transcript of the user request. You can also look at my activity. You can play the audio received by the Assistant to check for audio quality issues. If you hear excessive noise or if the audio is distorted, check that your microphone is configured properly or try a different microphone.
Assistant does not recognize a trait that you added to a model.
Make sure the trait was added to the model (see Register Traits for the Device).
If you generated a device instance for a model, the device instance will not automatically update when its model is changed by other users. You need to manually re-register the device instance using the registration command line tool or the REST API. You can find the device instance ID in the output of the sample.
Device Actions issues
The Google Assistant responds saying that your app is not supported on your device.
- In the Actions Console, you can set the surface capabilities of your Assistant app. If you set screen output to be required, your custom actions will not function. The Google Assistant SDK does not support screen capabilities at this time.
- Troubleshooting section of the Google Assistant Service sample README
Still having trouble? See our Support page.