Google Assistant on Hass.io

rwgamer · December 10, 2017, 5:32pm

Good Morning, I installed Google Assistant in Hass.io on my Raspberry Pi B+, it does not work because when I try to get into the web gui tells me that the page is unreachable, how do I solve it? can you give me more information on the official website? the “google_assistant.json” file in which folder should I put it?

abaer · December 12, 2017, 8:08am

Hi everyone,

I second this question, and I’d like to add some details. I assume that I might have the same problem as rwgamer. And I fear that he is not being specific enough to trigger any response. However, I don’t want to open a new question while this one isn’t answered yet.

Installed hass.io on my Raspi (First Gen). Everything has been working so far. Added a few sensors etc.

Now I wanted to install the “Google Assistant” add-on (BTW: Not a very smart move to have both a “Google Assistant” hass.io add-on and a Google Assistant component for the “normal” home assistant). I intend to use my raspi as a Google Home device to voice-control … the world. Everything. In my home.

Anyway: I install it (version v0.0.3-p5) via the “store” icon. The configuration interface showns up. Then, I put the “google_assistant.json” into the /share/ folder, using samba.

When I try to start the assistant, the trouble starts: Nothing happens. Seemingly, the buttons change, and the “state” changes to “started”.

However, when I refresh the config page, the state changes back to “stoppped”
Opening the web UI does not work - there is simply nothing answering port 9324; neither locally nor over the inet, neither on https nor on http
I get no log entries. No sound configuration, no errors, nothing. It’s just dead.

The only thing I can get with “hassio supervisor logs”:

17-12-12 08:02:37 INFO (SyncWorker_0) [hassio.dock.interface] Clean homeassistant/armhf-addon-google_assistant docker application
17-12-12 08:02:59 INFO (SyncWorker_0) [hassio.dock.addon] Start docker addon homeassistant/armhf-addon-google_assistant with version 0.0.3-p5

But as I said, it won’t start up.

As a first help to debug this, can anyone point me to a way to make the Assistant more verbose, or where to get detailled logs from a docker image?

rwgamer · December 12, 2017, 5:45pm

right I have your same problem

abaer · December 15, 2017, 11:28am

What hardware are you running Hass.IO on?

cosinus · December 15, 2017, 12:12pm

I have just set it up myself on a raspeberry pi 3.
The first thing I installed was the duckdns addon.
Created an account on duckdns and added this line in the duckdns addon config:

{
  "lets_encrypt": {
    "accept_terms": true,
    "certfile": "fullchain.pem",
    "keyfile": "privkey.pem"
  },
  "token": "4g839fj3-f0d0-4f43-4f4f-000000000f6g",
  "domains": [
    "myhome.duckdns.org"
  ],
  "seconds": 300
}

In the configuration.yaml I added this lines:

http:
  # Secrets are defined in the file secrets.yaml
  api_password: !secret http_password
  # Uncomment this if you are using SSL/TLS, running in Docker container, etc.
  # base_url: example.duckdns.org:8123

  base_url: https://myhome.duckdns.org:8123
  ssl_certificate: /ssl/fullchain.pem
  ssl_key: /ssl/privkey.pem

Then I made a roule on my gateway to forward request to port 443 to 192.168.1.9:8123
Where 192.168.1.9 is my hassio box.
Now I was able to connect to https://myhome.duckdns.org:8123 with my phone in celluar/4g/lte mode. It’s important that the above are in place before you try to integrate google.

The rest of the process was just to follow the addons page:

github.com

home-assistant/hassio-addons/blob/master/google_assistant/README.md

# Home Assistant Add-on: Google Assistant SDK

A virtual personal assistant developed by Google.

![Supports aarch64 Architecture][aarch64-shield] ![Supports amd64 Architecture][amd64-shield] ![Supports armhf Architecture][armhf-shield] ![Supports armv7 Architecture][armv7-shield] ![Supports i386 Architecture][i386-shield]

## About

[Google Assistant][google-assistant] is an AI-powered voice assistant that runs on the Raspberry Pi and x86 platforms and interact via the [DialogFlow][dialogflow-integration] integration with Home-Assistant. You can also use [Google Actions][google-actions] to extend its functionality.

You can simply say "Ok Google" following by your command, and Google Assistant will answer your request.

## ℹ️ Integration your mobile or Google/Nest Home with Home Assistant

If you want to integrate your Google Home or mobile phone running Google Assistant, with Home Assistant, then you want the [Google Assistant integration][google-assistant-integration].

[amd64-shield]: https://img.shields.io/badge/amd64-yes-green.svg
[armhf-shield]: https://img.shields.io/badge/armhf-no-red.svg
[armv7-shield]: https://img.shields.io/badge/armv7-yes-green.svg
[dialogflow-integration]: https://www.home-assistant.io/integrations/dialogflow/

This file has been truncated. show original

The only problem was that the mic newer detected in the log: I was able to get it working anyway with this config. This is a speaker jack connected and a usb webcam for mic.

{
  "mic": "1,0",
  "speaker": "0,0",
  "client_secrets": "google_assistant.json"
}

Now I can ask google for jokes. I have still not managed to integrate lights.

abaer · December 15, 2017, 3:42pm

Thanks for sharing this. However, we have a different problem - the addon doesn’t even start.

Edit - you mentioned that you are running everything on a PI 3, without problems. That actually goes towards my suspicion that the PI 1 I’m using does simply not have enough RAM. Therefore my question to rwgamer, because he does not mention the generation of his PI.

abaer · December 19, 2017, 9:53am

Suspicion confirmed: Installed everything on a PI 3 Model B+, and everything works as expected.

I guess it’s the lack of RAM.

rwgamer · January 9, 2018, 8:55am

I used Raspberry Pi 1 B+

rwgamer · January 9, 2018, 9:00am

So I have to buy a Raspberry Pi 3 to make Google Assistant work?
If I buy the Raspberry Pi 3 can I pass the backup of Hass.io from the Raspberry Pi 1 B + to the Raspberry Pi 3? How can I do?

abaer · January 9, 2018, 9:26am

I guess that means that - simply not enough RAM. I can tell you that you’ll enjoy the experience much more, because the PI 3 is much faster. For example, on the Pi 1, I was never sure whether a config change worked, or whether the PI just took ages wo work on it. The PI 3 restarts modules instantly, which make the 30+ Euro i spent worthwhile.

To switch, I just popped my SD card from the PI 1 into the PI 3, and everything worked … allmost:

Of course the IP address changed, so I needed to change the routing on my router
The PI3 uses a Micro SD card, so I had to duplicate my full size SD card from the PI1 onto a Micro SD
I used Acronis True Image to do that, you need to do an image copy
Even if you use a Micro SD in your PI 1, I would certainly make a backup before using it in the PI 3

Enjoy!

rwgamer · January 9, 2018, 9:51am

Can I directly pass the micro sd from RPi1 B+ to RPi3? Does not need the hass.io version for RPi3?
What microphone do you recommend for Google Assistant? Can I configure Google Assistant for command turn on the lights and turn off the lights (I use two Sonoff Basic with firmware Tasmota and MQTT)?

abaer · January 9, 2018, 10:29am

Oops, you may be right - I think I tried it both ways: The PI 1 card worked in the PI 3, but my current installation is nevertheless based on a new install, where I copied the files from /config, and configured all modules manually, based on the old configuration (made some screenshots, and saved the JSON configurations via copy / paste into a temporary text file).

I used a very cheap USB sound card from the Bay, and a standard 3.5mm jack PC microphone that I had lying around. Both weren’t used on my PC because they offered very bad performance, but on the PI, they perform remarkably well (from about 1-2m distance). BTW: I don’t think that the PI 3’s audio jack offers an input, but I’m not sure.

Big disapointment: Only English voice control at the moment.

With Google Assistant, you have to differ the 2 occurrences within hass.io:

The add-on we are talking about “just” gives you the voice-based assistant you know from your phone. The assistant will not know anything about your local installation. At first, I used IFTTT (Google Assistant “if” trigger, Webhooks “then that” action) to trigger services and script via the API on my hass.io installation.
The component (configuration.yaml: “google_assistant:”) actually exposes your Home Assistant device to the Google Home app, and integrates HA with Google Home

After trying the component, I actually just unlinked it from my Google Home again. Reason: At the moment, the automation that Google Home offers is way worse than what I can achive with IFTTT and scripts, and it was actually interfering with my IFTTT actions.

rwgamer · January 9, 2018, 10:52am

Thanks for answer.
In 10 days I will have the chance to buy the new RPi3 and then let me know

sibero80 · March 17, 2018, 3:54pm

Hello everyone, I’m a bit confused because I’m on the same page as the OP.
I have a RPI 2, with HASS.IO, I installed the Google Assistant Add-On, I was able to access the GUI to enter the TOKEN, but after the token is entered, the GA webserver stops.

This is the LOG I get when the Add-on starts but I talk to it, and nothing happens.

Thank you for your help.

[Info] Show audio device
**** List of PLAYBACK Hardware Devices ****
card 0: ALSA [bcm2835 ALSA], device 0: bcm2835 ALSA [bcm2835 ALSA]
  Subdevices: 8/8
  Subdevice #0: subdevice #0
  Subdevice #1: subdevice #1
  Subdevice #2: subdevice #2
  Subdevice #3: subdevice #3
  Subdevice #4: subdevice #4
  Subdevice #5: subdevice #5
  Subdevice #6: subdevice #6
  Subdevice #7: subdevice #7
card 0: ALSA [bcm2835 ALSA], device 1: bcm2835 ALSA [bcm2835 IEC958/HDMI]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
[Info] Setup audio device
[Info] Install/Update service client_secrets file

I just re-installed the Add On to get the first launch logs:

[Info] Show audio device
**** List of PLAYBACK Hardware Devices ****
card 0: ALSA [bcm2835 ALSA], device 0: bcm2835 ALSA [bcm2835 ALSA]
Subdevices: 8/8
Subdevice #0: subdevice #0
Subdevice #1: subdevice #1
Subdevice #2: subdevice #2
Subdevice #3: subdevice #3
Subdevice #4: subdevice #4
Subdevice #5: subdevice #5
Subdevice #6: subdevice #6
Subdevice #7: subdevice #7
card 0: ALSA [bcm2835 ALSA], device 1: bcm2835 ALSA [bcm2835 IEC958/HDMI]
Subdevices: 1/1
Subdevice #0: subdevice #0
[Info] Setup audio device
[Info] Install/Update service client_secrets file
[Info] Start WebUI for handling oauth2
[17/Mar/2018:14:17:22] ENGINE Listening for SIGHUP.
[17/Mar/2018:14:17:22] ENGINE Listening for SIGTERM.
[17/Mar/2018:14:17:22] ENGINE Listening for SIGUSR1.
[17/Mar/2018:14:17:22] ENGINE Bus STARTING
CherryPy Checker:
The Application mounted at ‘’ has an empty config.

[17/Mar/2018:14:17:22] ENGINE Started monitor thread ‘_TimeoutMonitor’.
[17/Mar/2018:14:17:22] ENGINE Started monitor thread ‘Autoreloader’.
[17/Mar/2018:14:17:22] ENGINE Serving on http://0.0.0.0:9324
[17/Mar/2018:14:17:22] ENGINE Bus STARTED
192.168.0.16 - - [17/Mar/2018:14:17:54] “GET / HTTP/1.1” 200 714 “” “Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.186 Safari/537.36”
[17/Mar/2018:14:18:12] ENGINE SystemExit raised: shutting down HTTP server
[17/Mar/2018:14:18:12] ENGINE Bus STOPPING
[17/Mar/2018:14:18:12] ENGINE HTTP Server cherrypy._cpwsgi_server.CPWSGIServer((‘0.0.0.0’, 9324)) shut down
[17/Mar/2018:14:18:12] ENGINE Stopped thread ‘Autoreloader’.
[17/Mar/2018:14:18:12] ENGINE Stopped thread ‘_TimeoutMonitor’.
[17/Mar/2018:14:18:12] ENGINE Bus STOPPED
[17/Mar/2018:14:18:12] ENGINE Bus EXITING
[17/Mar/2018:14:18:12] ENGINE Bus EXITED
[17/Mar/2018:14:18:12] ENGINE Waiting for child threads to terminate…