Stay organized with collections
Save and categorize content based on your preferences.
Installing/upgrading the library
You get an error message similar to E: Unable to locate package python3-venv
while trying to configure a new Python virtual environment.
On older versions of Ubuntu, the meta package for the Python 3 virtual
environment (python3-venv) is not available. Use a fully-qualified version
instead:
sudo apt-get install python3-dev python3.4-venv
You get an error message similar to No matching distribution found
or <wheel> is not a supported wheel on this platform.
Check the hardware architecture:
uname -a Linux raspberrypi 4.9.24-v7+ #993 SMP Wed Apr 26 18:01:23 BST 2017 armv7l GNU/Linux
The library is only supported on hardware with linux-armv7l and linux-x86_64
architectures. For other hardware, use the Google Assistant Service
instead.
Credentials issues
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").
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.
Trait issues
Assistant does not recognize a trait that you added to a model.
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.
Hotword issues
Assistant does not seem to respond to sentences that begin with Ok Google or
Hey Google.
If you still get little to no recognition of your voice, try calibrating
your microphone sensitivity:
Terminate (Ctrl+C) any sample code that is currently running.
Run the following command:
export ASSISTANT_MIC_SENSITIVITY=-6
Run the sample code and try again. Go back to step 1, but keep lowering
the ASSISTANT_MIC_SENSITIVITY value in intervals of -6 (e.g., -6, -12,
-18, -24...) until you find that voice recognition is optimal. If you
get to -60, check your microphone.
Alarms and timers issues
The Assistant does not follow verbal commands (for example, pausing
or stopping a timer).
This is an issue if you have the StartStop
or OnOff trait enabled for a
given device model. Remove this trait from the device model and verbal
commands will work.
Podcast and news playback issues
The Assistant does not follow playback commands (for example, pausing
or stopping a podcast).
This is an issue if you have the StartStop
or OnOff trait enabled for a given
device model. Remove this trait from the device model and playback commands
will work.
Broadcast issues
The Assistant cannot broadcast messages from one device to the other.
Make sure to set the device location in the Google Assistant app.
Both devices must have the same address in the app.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2024-09-18 UTC."],[[["\u003cp\u003eThe Google Assistant Library for Python is deprecated; use the Google Assistant Service instead.\u003c/p\u003e\n"],["\u003cp\u003eThe library is supported only on hardware with linux-armv7l and linux-x86_64 architectures.\u003c/p\u003e\n"],["\u003cp\u003eFor credential issues, ensure the Google Assistant API is enabled and the OAuth consent screen is configured.\u003c/p\u003e\n"],["\u003cp\u003eTroubleshoot voice recognition by checking audio quality, microphone configuration, and user request transcript.\u003c/p\u003e\n"],["\u003cp\u003eFor device action issues, avoid requiring screen output in the Actions Console, as the SDK doesn't currently support it.\u003c/p\u003e\n"]]],["The Google Assistant Library for Python is deprecated; use the Google Assistant Service instead. Common issues include: virtual environment errors (install `python3-dev python3.4-venv`), hardware architecture mismatch (only `linux-armv7l` and `linux-x86_64` supported), credential errors (enable the API and OAuth), permission problems (set activity controls), voice recognition problems (check audio quality and microphone), trait issues (register traits and re-register devices), device action problems (don't require screen output), hotword issues (adjust mic sensitivity), and issues with certain traits (remove `StartStop` and `OnOff` traits).\n"],null,["# Troubleshooting the Google Assistant Library\n\n| **Warning:** The Google Assistant Library for Python is deprecated as of June 28th, 2019. Use the [Google Assistant Service](/assistant/sdk/guides/service/python) instead.\n\n\u003cbr /\u003e\n\nInstalling/upgrading the library\n--------------------------------\n\nYou get an error message similar to `E: Unable to locate package python3-venv`\nwhile trying to configure a new Python virtual environment.\n\n- On older versions of Ubuntu, the meta package for the Python 3 virtual\n environment (`python3-venv`) is not available. Use a fully-qualified version\n instead:\n\n ```\n sudo apt-get install python3-dev python3.4-venv\n ```\n\nYou get an error message similar to `No matching distribution found`\nor `\u003cwheel\u003e is not a supported wheel on this platform`.\n\n- Check the hardware architecture:\n\n ```\n uname -a\n Linux raspberrypi 4.9.24-v7+ #993 SMP Wed Apr 26 18:01:23 BST 2017 armv7l GNU/Linux\n ```\n\n \u003cbr /\u003e\n\n The library is only supported on hardware with linux-armv7l and linux-x86_64\n architectures. For other hardware, use the [Google Assistant Service](/assistant/sdk/overview#sdk_components)\n instead.\n\nCredentials issues\n------------------\n\nWhen trying to generate credentials with the authorization tool, the tool prompts\nyou to visit a URL and sign in to your Google account. The page then displays an\nerror message (for example, \"Something went wrong\").\n\n- Make sure you enabled the Google Assistant API and configured the OAuth consent screen in [Configure a Developer Project and Account Settings](/assistant/sdk/guides/library/python/embed/config-dev-project-and-account#config-dev-project).\n\nPermissions issues\n------------------\n\nThe Google Assistant responds *Actually, there are some basic settings that need\nyour permission first...*\n\n- [Set activity controls](/assistant/sdk/guides/activity-controls) for the account that you used when setting the authorization code.\n\nVoice recognition issues\n------------------------\n\nAssistant responds *I don't know how to help with that* or *I don't\nunderstand.*\n\n- 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](https://myactivity.google.com/myactivity?restrict=vaa). 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.\n\nTrait issues\n------------\n\nAssistant does not recognize a trait that you added to a model.\n\n- Make sure the trait was added to the model\n (see [Register Traits for the\n Device](/assistant/sdk/guides/library/python/extend/register-device-traits)).\n\n- If you generated a device instance for a model, the device instance will **not**\n automatically update when its model is changed by other users. You need to\n manually re-register the device instance using the [registration command line tool](/assistant/sdk/reference/device-registration/device-tool#register-device)\n or the [REST API](/assistant/sdk/reference/device-registration/register-device-manual#register-instance).\n You can find the\n [device instance ID](/assistant/sdk/guides/library/python/embed/run-sample#get-device-id)\n in the output of the sample.\n\nDevice Actions issues\n---------------------\n\nThe Google Assistant responds saying that your app is not supported on your\ndevice.\n\n- In the [Actions Console](https://console.actions.google.com/), 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.\n\nHotword issues\n--------------\n\nAssistant does not seem to respond to sentences that begin with *Ok Google* or\n*Hey Google*.\n\n- If you still get little to no recognition of your voice, try calibrating\n your microphone sensitivity:\n\n 1. Terminate (Ctrl+C) any sample code that is currently running.\n 2. Run the following command: \n\n ```\n export ASSISTANT_MIC_SENSITIVITY=-6\n ```\n 3. Run the sample code and try again. Go back to step 1, but keep lowering the `ASSISTANT_MIC_SENSITIVITY` value in intervals of -6 (e.g., -6, -12, -18, -24...) until you find that voice recognition is optimal. If you get to -60, check your microphone.\n\nAlarms and timers issues\n------------------------\n\nThe Assistant does not follow verbal commands (for example, pausing\nor stopping a timer).\n\n- This is an issue if you have the [StartStop](/assistant/sdk/reference/traits/startstop) or [OnOff](/assistant/sdk/reference/traits/onoff) trait enabled for a given device model. Remove this trait from the device model and verbal commands will work.\n\nPodcast and news playback issues\n--------------------------------\n\nThe Assistant does not follow playback commands (for example, pausing\nor stopping a podcast).\n\n- This is an issue if you have the [StartStop](/assistant/sdk/reference/traits/startstop) or [OnOff](/assistant/sdk/reference/traits/onoff) trait enabled for a given device model. Remove this trait from the device model and playback commands will work.\n\nBroadcast issues\n----------------\n\nThe Assistant cannot broadcast messages from one device to the other.\n\n- Make sure to set the device location in the Google Assistant [app](/assistant/sdk/reference/assistant-app/assistant-settings). Both devices must have the same address in the app.\n\nSupport\n-------\n\nStill having trouble? See our [Support](/assistant/sdk/support) page."]]
