core: google assistant integration / unable to add test app

Hi,

my environment is quite complex:

Synology NAS with hass 0.104.0 running in docker container, host network, port 8123 ipv4 Synology Reverse Proxy, dns name ha.hauptsache.myds.me, port 443, using let’s encrypt cert

Internet access via cable DSLite, ipv6 only incoming 😦 This means if you try to reach the dns name via ipv4 it won’t work. only ipv6

Anyway, so far the reverse proxy works fine and I can access my hass installation via the android companion app remotely (via cell network, German Vodafone) and locally via WiFi.

The problem is the google assistant integration. I read the documentation and setup the whole environment to connect to ha.hauptsache.myds.me.

This works: In Google Home app I click on the “+” to add new devices and I select my test app. The home assistant webpage appears. I enter my credentials and the app shows a popup which tells me in German “sie werden angemeldet” (translated: logging in).

This doesn’t work: After a few seconds the popup disappears and I’m back in the “Konten verwalten” (manage accounts) screen. my test app is still not listed under the assigned services section.

Now I wonder, what am I missing? How can I debug this? Things I found in the logfile:

2020-01-17 15:11:28 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/google_assistant/report_state.py", line 45, in async_entity_state_listener
    if entity_data == old_entity.query_serialize():
  File "/usr/src/homeassistant/homeassistant/components/google_assistant/helpers.py", line 442, in query_serialize
    deep_update(attrs, trt.query_attributes())
  File "/usr/src/homeassistant/homeassistant/components/google_assistant/trait.py", line 1288, in query_attributes
    ERR_NOT_SUPPORTED, "Querying state is not supported"
homeassistant.components.google_assistant.error.SmartHomeError: Querying state is not supported

2020-01-17 17:35:10 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/google_assistant/report_state.py", line 45, in async_entity_state_listener
    if entity_data == old_entity.query_serialize():
  File "/usr/src/homeassistant/homeassistant/components/google_assistant/helpers.py", line 442, in query_serialize
    deep_update(attrs, trt.query_attributes())
  File "/usr/src/homeassistant/homeassistant/components/google_assistant/trait.py", line 1288, in query_attributes
    ERR_NOT_SUPPORTED, "Querying state is not supported"
homeassistant.components.google_assistant.error.SmartHomeError: Querying state is not supported

2020-01-21 13:19:20 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/google_assistant/report_state.py", line 45, in async_entity_state_listener
    if entity_data == old_entity.query_serialize():
  File "/usr/src/homeassistant/homeassistant/components/google_assistant/helpers.py", line 442, in query_serialize
    deep_update(attrs, trt.query_attributes())
  File "/usr/src/homeassistant/homeassistant/components/google_assistant/trait.py", line 1288, in query_attributes
    ERR_NOT_SUPPORTED, "Querying state is not supported"
homeassistant.components.google_assistant.error.SmartHomeError: Querying state is not supported

Screenshot_2020-01-21-16-02-01-836_com google android googlequicksearchbox Screenshot_2020-01-21-16-02-17-165_com android chrome Screenshot_2020-01-21-16-02-32-757_com google android googlequicksearchbox

About this issue

Original URL
State: closed
Created 4 years ago
Comments: 82 (27 by maintainers)

Most upvoted comments

also - hold on. Maybe i’m missing something. if i set expose_by_default: false and I add 2 lights and nothing more GA linking FAILS

if i set expose_by_default: true it automatically adds ALL lights GA linking succeeds

It cant just be bad data, as exposing all devices in that domain would make the problem worse (or the same) not better?

jaburges on Sep 4, 2020

Decided to start this Google Assistant integration endeavor two days ago. Was basically stuck at the same connection issue when trying to link in the Google Home app. I was able to finally link it though, but I don’t know if this was due to maybe a time thing or a small change I did. The change itself was setting the role of the service account you created (and have set under service_account in configuration.yaml) to Owner within the IAM page in GCP (mine was set to Editor initially)

Hopefully this provides some insight into this issue

A slight clarification. The change to owner was made to the default service account, not to the one you would create with the JSON key:

tempsnip

Essentially, the one with [Your_Project_ID]@appspot.gserviceaccount.com

I changed it by clicking on the Pencil edit under Inheritance, then changing the Role to Project -> Owner

Sciph3r on May 15, 2020

Just full clean installed 0.107.7 on another ubuntu server (18.04). Same issue.

2020-04-08 01:59:27 DEBUG (MainThread) [homeassistant.components.http.view] Serving /auth/providers to 172.30.33.3 (auth: False)
2020-04-08 01:59:28 DEBUG (MainThread) [homeassistant.components.http.view] Serving /auth/login_flow to 172.30.33.3 (auth: False)
2020-04-08 01:59:37 DEBUG (MainThread) [homeassistant.components.http.view] Serving /auth/login_flow/b1e0fbb9b381479c8523496458ab0fd1 to 172.30.33.3 (auth: False)
2020-04-08 01:59:45 DEBUG (MainThread) [homeassistant.components.http.view] Serving /auth/login_flow to 172.30.33.3 (auth: False)

My time zone is UTC+8 Asia/Shanghai. The date in log is 1 hour later than real time.

CodeInDreams on Apr 7, 2020

Exactly same issue here. No useful logs.

CodeInDreams on Mar 21, 2020

You are exposing all switches all covers and all lights. Please reduce your exposed entities to a minimum to start with. I suspect it’s covers that is causing problem.

elupus on Jan 22, 2020