I’ve been messing around with Home assistant and Nabu Casa for about 2 weeks now… My HA instance seems to have failed on me because of SD-card failure (new sd-card and disabled any logging of devices which I never use to keep down read/write)… Long story short Nabu Casa is not working anymore it is connected, my HA is open to the internet etc etc just as my previous setup (did a full reinstall + placed all my config back and some required extensions, the image of HA I have would just not boot after restoring).
It now ends in a 401 when pairing with the google home app which I can’t seem to find any help on through their website which makes sense since it’s a “1 click” solution. BUT I’m capable enough to do this myself so why spend $5 each day right?
The most recent tutorial is below and it has me confused since it seems I can’t just say ‘OK google, turn on my lights’ like with Nabu Casa, is this exclusive to them or am I just missing something or do I have the wrong tutorial… pointing me to the right information should be enough!! most tutorials seem greatly outdated both on HA and Google’s api platform…
I personally use HAASKA to control Alexa but the principle is exactly the same, DIY version of HA Cloud functionality.
I’ve had a look through that guide and it all seems pretty clear, end result is exactly the same whether you use that or HA Cloud, same as it is with HAASKA.
The example for use with both versions states you can say “OK Google, turn on garage lights” which is what I’d expect.
Someone with more experience of GA will probably be along eventually.
aha so eventhough it says things about having to use the name it’s a ‘false statement’? I can just use it the same as HA Cloud that’s good to know! I’ve done the entire tutorial anyway and am still stuck with the 401 error but looking at that right now since I now know that tutorial is sufficient
configuration.yaml is :
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: https://*******.duckdns.com:443
server_port: 443
ssl_certificate: /ssl/fullchain.pem
ssl_key: /ssl/privkey.pem
google_assistant:
project_id: ****
api_key: ****
exposed_domains:
- switch
- light
- group
All urls in ‘Actions on Google’ have ‘https://*****.duckdns.org:433/’ with the port explicitly shown to be sure and everything else is exactly as described by the tutorial on both hassio and the mentioned tutorial
it appears in the home assistant app, I can login with my HA credentials and then nothing
(in my opinion the one on hass is not complete since it’s for instance skipping the naming part which is required for it to work propperly)
I had the same issue configuring on IOS. I had to clear the cookies and website data from Safari to fix it. Go to Settings → Safari → Clear History and Website Data.
Totally not related to google home or hass apparently
