Yes. I can login using my external address, on port 8123.
I’m just going thorugh all the mistakes I made myself before getting the thing to work. And did you remember to set “Linking type” to “Authorization code” and not “implicit”?
Yes, it is set to Authorization code.
I appreciate all of your questions to check my setup.
And your SSL is still valid?
And you pushed the Actions button after finishing, and you enabled Homegraph API? That’s the last steps I can think of
Just to make it more difficult on myself, I changed from a self-signed certificate to a let’s encrypt one. That was a pain since my ISP blocks port 80, but I finally got it working.
Now, when I add my device in google assistant on my phone, it says it gets added, but I don’t see any of the actual devices that home assistant can control, like before. And when I click the add button again, it shows my [test] device name in the Add New section instead of the linked devices.
At least I’ve gone beyond the error message in this thread. Slight progress. Thanks for the push in the right direction.
Try removing expose_by_default: false from config yaml and see what happens.
It happened! I see my devices. Now hopefully I complete the setup again and things work! Thank you very very much!
I think the key takeaway for anyone else was the new let’s encrypt certificate, which I used acme.sh to generate using the duckdns API method.
Don’t mention it! That’s what we are here for. Our thanks goes to Paulus Schoutsen who gave us this great tool!
I had this problem on 0.84.1. Read through most of the thread before I clicked the⋮menu while the login page was displayed and noticed it had an option “Open with Firefox” (because Firefox is my default browser on Android).
I made Chrome my default browser and tried to link again. It worked!
Hi,
Now it’s my turn to have problem with this Google Assistant configuration.
The project in Google Console and the credentials have been setup correctly following the instructions. I have also tried creating a new projects and credentials but still no luck.
On my phone when I use "[test] mysite"
I can log in to the app, HASS accepts my ordinary login details. But then the "Could not update the setting. Please check your connection” message pops up on my phone.
My configuration:
logger:
default: warning
logs:
homeassistant.components.http: debug
homeassistant.components.google_assistant: debug
http:
ssl_certificate: Myfullchain.pem
ssl_key: Myprivkey.pem
base_url: mysite.duckdns.org:8123
google_assistant:
project_id: mysite-xx123x
api_key: obscureandlongstring
My Log:
This:
2018-12-20 14:47:57 INFO (MainThread) [homeassistant.components.http.view] Serving /auth/authorize to 192.168.1.1 (auth: False)
2018-12-20 14:47:58 INFO (MainThread) [homeassistant.components.http.view] Serving /auth/providers to 192.168.1.1 (auth: False)
2018-12-20 14:47:58 INFO (MainThread) [homeassistant.components.http.view] Serving /auth/login_flow to 192.168.1.1 (auth: False)
2018-12-20 14:47:58 INFO (MainThread) [homeassistant.components.http.view] Serving /manifest.json to 192.168.1.1 (auth: False)
gets me to the Logging in with "Home Assistant Local"
This, when I try to sign in:
2018-12-20 14:48:20 INFO (MainThread) [homeassistant.components.http.view] Serving /auth/login_flow/anotherlongstring to 192.168.1.1 (auth: False)
Then after 10 seconds it returns in to log with:
2018-12-20 14:48:31 INFO (MainThread) [homeassistant.components.http.view] Serving /auth/login_flow to 192.168.1.1 (auth: False)
2018-12-20 14:48:31 INFO (MainThread) [homeassistant.components.http.view] Serving /manifest.json to 192.168.1.1 (auth: False)
And then the dreaded "Could not update the setting. Please check your connection” message on my phone.
I have tried to log out from my Chrome account so I need to sign in again before entering in my HA login details. That didn’t help.
Anyone who could help me on how to debug this?
Did you try adding https://
Hi,
Yes, tried that, no luck.
But when I use Firefox the log looks different (different IP):
2018-12-20 15:39:47 INFO (MainThread) [homeassistant.components.http.view] Serving /auth/authorize to 95.199.153.212 (auth: False)
2018-12-20 15:39:47 INFO (MainThread) [homeassistant.components.http.view] Serving /auth/providers to 95.199.153.212 (auth: False)
2018-12-20 15:39:48 INFO (MainThread) [homeassistant.components.http.view] Serving /auth/login_flow to 95.199.153.212 (auth: False)
2018-12-20 15:40:02 INFO (MainThread) [homeassistant.components.http.view] Serving /auth/login_flow/anotherlongstring to 95.199.153.212 (auth: False)
Makes my suspect some networking issue.
192.168.1.1 would typically be your router IP whereas 95.199.153.212 is a Telia IP in Göteborg, Sweden (probably your ISP’s IP). I have no idea, why a change of browser would effect such a difference.
Did your SSL certificate run out?
Newly installed DuckDNS and Let’s Encrypt cert with the lightweight dehydrated script. Works from the outside with https. But how would I go about to test outgoing traffic from my machine to google?
Another thing that bother me is that I do not see anything from google_assistant in the log.
This case is far beyond my humble capabilities. Hopefully someone else can help you!
PS: Did you expose any domains?
Not explicitly, trusting the docs:
Expose_by_default
(boolean)(Optional)Expose devices in all supported domains by default
But I have tried with limiting it as well to only lights, no change. But I think the problem is earlier in the process since nothing in the log hints that google_assistant is called in the first place.