First, navigate to the AIY-voice-kit-python folder and run the source code

cd AIY-voice-kit-python

source env/bin/activate

cd src

Then use 'sudo nano' into either 'assistant_grpc_demo.py' or 'assistant_library_demo.py'

The different between the two files is that assistant_grpc_demo.py uses the button to trigger Google Assistant and assistant_library_demo.py uses the activation word "Ok, Google" to trigger the Google Assistant.

For both of these files you only need to add ONE line of code:

status_ui.set_trigger_sound_wave('/home/pi/googlestart.wav')

This assumes you have placed your start sound in the /home/pi/ folder and named it googlestart.wav. Change these based on whatever you named your file and wherever you located it.

The line of code we are looking for is below:

status_ui.status('listening')

We want to add our new line of code BEFORE that line of code...

For the 'assistant_library_demo.py' example it can be found here:

elif event.type == EventType.ON_CONVERSATION_TURN_STARTED: # And now add our code status_ui.set_trigger_sound_wave('home/pi/googlestart.wav') status_ui.status('listening')

For the 'assistant_grpc_demo.py' example it can be found here:

button.wait_for_press() # And now add our code status_ui.set_trigger_sound_wave('/home/pi/googlestart.wav') status_ui.status('listening')

This assumes you have placed your start sound in the /home/pi/ folder and named it googlestart.wav. Change these based on whatever you named your file and wherever you located it.

Hit CTRL-X & Y to save everything.

***NOTE: I have found something a little goofy. For the 'assistant_library_demo.py' adding the trigger sound seems to not make any difference in the function of the speech recognition. For the 'assistant_grpc_demo.py' though, it seems when you have the trigger sound implemented it cuts off the first word or two that you say. Not totally sure why. Still trying to figure it out.