Google Assistant ON Raspberry P
What’s required?
· A Raspberry Pi ( Any Model )
· A basic speaker with a 3.5 mm aux connection
· A USB microphones
· A mouse and keyboard
Step 1: Formatting the SD CardThe very first thing that we need to do is to format our SD card. Let’s use the SD Association's Formatting Tool which is recommended by the official Raspberry Pi Foundation.
Once installed, launch the application and click ‘Option’ You need to change the option for ‘FORMAT SIZE ADJUSTMENT’ to ‘ON’.
Now click ‘OK’ and double check that we are formatting the correct drive, then click ‘Format’. This shouldn’t take too long, just wait for the confirmation that the drive was formatted successfully before you move onto the next step.
Step 2: Preparing the SD CardNext we need to download the Voice Kit microSD card image for the Raspberry Pi. You can download the image from https://drive.google.com/file/d/0B_a_ek9WAhJdVzktSFQwS0Mzb2M/view
In order to transfer the image that we just downloaded onto our SD card we are going to use a program called Etcher.io. It’s free, open source and does not require installation.
Once you’ve downloaded Etcher, run the program and you should see a screen like the one above. It can take a minute or two to load so if it doesn’t load right away be patient.
Click ‘Select image’ and navigate to the voice kit image that we just downloaded Once selected double check that you are writing the contents onto the correct disk. Assuming that we have the correct disk selected then click ‘Flash!’.
It can take around 20 minutes or more to write the image to your SD card
Step 3: Power Up That Pi!As soon as the SD card is ready we can put the microSD card into our Raspberry Pi. At this point we also need to connect our power lead, HDMI cable, keyboard, mouse, monitor, speaker and USB microphone. Hopefully your setup should look something like mine.
I am using a wireless keyboard and mouse so don’t freak out if you end up with a couple of extra cables with your own setup!
With the power cable plugged in allow your Raspberry Pi to boot up and you will soon be presented with the standard Pixel desktop.
Step 4: Initial ConfigurationGrab your cursor and navigate to the Raspberry Pi logo at the top left of your screen. From the dropdown select ‘Preferences’ and then ‘Raspberry Pi Configuration’.
Next, go to ‘Interfaces’ and enable 'SSH'.
Now click on the WiFi logo at the top right of the screen and select your WiFi network. If your WiFi is password protected you will prompted to enter that in. The green tick confirms that we connected successfully and we’re ready to move onto the next step.
Step 5: Updating the InstallationThis is about as advanced as this tutorial gets. We are going to use the dev terminal to update the Google Assistant SDK, Project Kit & dependencies to ensure we have the latest versions. Do not panic if none of this makes much sense to you but it is essential that we do not skip this step. Just do exactly as this tutorial says being careful not to make any typos and it will all work out just fine.
So, panic over, let’s begin! Double click on the desktop icon name ‘Start dev terminal’.
You should see a scary looking dev terminal window like the one above.
Next type the following commands into the terminal exactly as they appear below. There are 9 commands here and each should be entered separately in the order in which they appear. After typing each command hit ‘Enter’ on your keyboard before moving onto the next one. Some of the commands will take a few seconds to complete so be patient waiting for each to finish before moving onto the next one.
cd ~/assistant-sdk-python
git checkout master
git pull origin master
cd ~/voice-recognizer-raspi
git checkout master
git pull origin master
cd ~/voice-recognizer-raspi
rm -rf env
scripts/install-deps.sh
Step 6: Preparing the Configuration FilesNext we need to backup our existing configurations files and bring over the newest versions that were just updated. Here’s 4 more commands for you to do just that. These can be done in the same dev terminal that we were just using. Once again, they must be done in this order and should be typed precisely as they appear below:
cp ~/.config/status-led.ini ~/.config/status-led.ini~
cp ~/.config/voice-recognizer.ini ~/.config/voice-recognizer.ini~
cp ~/voice-recognizer-raspi/config/status-led.ini.default ~/.config/status-led.ini
cp ~/voice-recognizer-raspi/config/voice-recognizer.ini.default ~/.config/voice-recognizer.ini
Step 7: Setting Up the HotwordWe now need to change the trigger for our Google AIY project kit so that it responds to our voice when we speak the words ‘ OK Google ’.Type the following command into the dev terminal:
nano ~/.config/voice-recognizer.ini
This will produce this even scarier window.
Within this new window, look for the following code:
# Select the trigger: gpio (default), clap, ok-google.
# trigger = clap
We need to change this code to:
# Select the trigger: gpio (default), clap, ok-google.
trigger = ok-google
If you use the arrow keys on your keyboard you will notice a curser appears. Using the arrow keys, bring the curser down to the line of text that we are trying to change. Using the backspace key on your keyboard delete the line of text that we are trying to change and retype it just like the example above.
Notice that I have also removed the # symbol, it is important we do not include the # in this new line of text.
I have attached a before and after screenshot of what this should all look like (encase I lost you there).
Assuming your window looks exactly like mine we can close and save the changes. Hold ‘Ctrl’ on your keyboard and press ‘X’ to close the window. We will then be prompted to save the changes we made, press ‘Y’ and then hit ‘Enter’ on your keyboard. The window will now close and the changes have been saved.
To ensure the changes have taken affect we need to restart the service. Type the following command into the terminal window and hit ‘Enter’:
command into the terminal window and hit ‘Enter’:
sudo systemctl restart voice-recognizer.service
Step 8: Audio Configuration (Part 1)Right now Google Assistant more or less alive and ready to serve.. Congratulations!
However, before you get too excited, you cannot hear each other. That’s because the Google AIY Project Image was configured to work with the hardware that was shipped with the kit. Since we are using a standard aux speaker and usb microphone we need to tweak some of the configuration.
Once again we will use the same dev terminal window, this time type:
sudo leafpad /boot/config.txt
This will open a text window. Scroll to the very bottom of the document and remove the # in front the the line dtparam=audio=on and insert a # in front of the two lines below it.
After you have made these changes it should exactly like this:
# Enable audio (loads snd_bcm2835)
dtparam=audio=on
#dtoverlay=i2s-mmap
#dtoverlay=googlevoicehat-soundcard
I have also attached a screenshot to show you what this will look like.
Go to ‘File’ then click ‘Save. You can now close the document.
Step 9: Audio Configuration (Part 2)Back in the dev terminal again, type:
sudo leafpad /etc/asound.conf
When you hit ‘Enter’ a new text document will open. This time delete ALL the text within the document and replace it with the following:
pcm.!default { type asym capture.pcm "mic" playback.pcm "speaker"}pcm.mic { type plug slave { pcm "hw:1, 0" }}pcm.speaker { type plug slave { pcm "hw:0, 0" }}
pcm.!default {
type asym
capture.pcm "mic"
playback.pcm "speaker"
}
pcm.mic {
type plug
slave {
pcm "hw:1,0"
}
}
pcm.speaker {
type plug
slave {
pcm "hw:0,0"
}
}
Again I have attached a screenshot showing you what this will look like.
Once again save and close the document.
Now it is time to reboot your Raspberry Pi. Click on the Raspberry Pi logo at the top left of your screen and click on ‘Shutdown’ then ‘Reboot’.
After you have rebooted the Pi we have just one more tweak to make. Double click on the ‘Start dev terminal’ icon once again and type the following:
leafpad /home/pi/voice-recognizer-raspi/checkpoints/check_audio.py
In this final document you need to locate the line of code that reads:
VOICEHAT_ID = ‘googlevoicehat’
Change this to:
VOICEHAT_ID = ‘bcm2835’
Once you have made these changes, just as we did before, save then close this document.
Step 10: Testing the Audio
On the desktop there is a file called ‘Check audio’. Double click on this and follow the prompts to ensure that both the speak and microphone is working.
If you followed this Instructable correctly there should be no problems. However if you cannot hear anything, double check that the volume is turned up and that your Raspberry Pi is using ‘Analog’ for sound output. You can do this by right-clicking on the sound icon at the top of the screen. ‘Analog’ should be ticked just like the example in the screenshot.
Assuming you passed the audio check, we can move onto the next step.
Step 11: Connecting to the Cloud
Before Google Assistant will give us answers to life’s burning questions we need to connect her to Google’s Cloud Services.
This is easy to do but if you haven’t been in the cloud before then it may seem a bit daunting at first.
Here’s what we need to do:
1) On the Raspberry Pi open up the Chrome internet browser and go to the Cloud Console: https://console.cloud.google.com/
2) Sign in with an existing Google account or sign up if you do not have one.
3) Create a new project and give it a name. I called mine ‘Google Pi’
4) Using the search bar start typing ‘Google Assistant’ and you should see the ‘Google Assistant API’. Click on it and then when the next page loads click ‘Enable’ to activate the API.
5) Go to ‘API Manager’ then ‘Credentials’ and create an ‘OAuth 2.0 client’.
6) Click ‘Create credentials’ and select ‘OAuth client ID’. If you have never been in the cloud before then you will now be prompted to configure your consent screen. You’ll need to name your app, I called mine 'Raspberry Pi'. All other fields can be left blank.
7) In the Credentials list, find your new credentials and click the download icon on the right.
8) The chrome browser will now download a small JSON file with all your credentials stored safely inside. Find this file and rename it to ‘assistant.json’ then move it to /home/pi/assistant.json.
9) Finally, go to the Activity Controls page: https://myaccount.google.com/activitycontrols and turn on the following services: Web and app activity, Location history, Device information, Voice and audio activity. Be sure to log in with the same Google account as before!
If you got stuck at any point during this stage, do not freak out, Google has done an excellent job at documenting this process with screenshots for each step over on the Google AIY Kit website.
Step 12: Final TestingIf everything was setup correctly in the cloud we are now ready to talk to Google. Using the ‘Start dev terminal’ command window again, type the following:
src/main.py
This will wake up our assistant but since this is the first time that we are connecting to Google’s Services, a web browser will open and you will need to login to Google to give permission for the Raspberry Pi to access the Google Assistant API. Again making sure that you use the same Google account logins as you did before.
Once you have logged in successfully and granted permission you will be prompted to close the window. The command window will now look like the screenshot attached confirming that everything was setup correctly.
Go ahead, ask a question, she’s listening!
Before you get too excited though, we are not quite finished. When you have finished playing, close the window, to do this just use the white cross at the top right of the window.
Step 13: Setting Up Google Assistant on Startup
I promised you that our Google Assistant would startup automatically when we power up the Raspberry Pi. To do this, open a fresh command window using the ‘Start dev terminal’ icon on the desktop. Type the following line of code into your terminal window and hit ‘Enter’ on your keyboard:
sudo systemctl enable voice-recognizer
Step 14: The Finish Line
Reboot your Raspberry Pi. If you have followed all these instructions carefully then Google Assistant should be running in the background when the Pi loads up.
Comments