Google Assistant not linking anymore

Configuration
41

I think you can safely take it out (
google_assistant_name) , and just use friendly_name and aliases

42

I followed your suggestion but still can’t link back

43

it says in the GH app, "Succesfully linked the [test] CLaudio app …

but no device is added … ???

44

I started from scracth (created new app in developer console amd all the rest) … still the same result … linking succesfully but no device showing.

Did it change something?

google_assistant:
  project_id: hassio2018
  client_id: cccccccccccccccc
  access_token: ccccccccccccccc
  expose_by_default: false
  api_key: ccccccccccccccc
  exposed_domains:
    - switch
    - light
    - script
    - media_player
    - scene
    - group
45

Just thought I would share my recent experience with google assistant linking.

When I first set it all up (as per the component docs) it worked, though it added everything in my Home Assistant config into Google Assistant. I tried the request_sync command but that was returning the request_sync request failed: 400 error mentioned on the docs.

I ended up setting everything up a couple of times before it was working correctly, I set expose_by_default: false and for the devices I want to add to Alexa and Google I use the customize.yaml file e.g.

light.yaml

- platform: rfxtrx
  automatic_add: False
  devices:
    710010041030000:
      name: lava_lamp
    710010041040000:
      name: dining_lamp

customize.yaml

light.dining_lamp:
  friendly_name: Dining Lamp
  google_assistant: true
  emulated_hue_hidden: false
  emulated_hue_name: "Dining Lamp"
light.lava_lamp:
  friendly_name: Lava Lamp
  emulated_hue_hidden: false
  emulated_hue_name: "Lava Lamp"
  google_assistant: true
  google_assistant_type: light

I am not sure this is the correct way to do it as I am relatively new to hass (a couple of weeks) but have been fiddling with home automation, voice control (custom Alexa Skills) and OpenHAB for a couple of years.

Today I wanted to add another socket to turn on the christmas tree lights.

switches.yaml

- platform: rfxtrx
  automatic_add: False
  devices:
    710010041010000:
      name: socket_01

customize.yaml

switch.socket_01:
  google_assistant: true
  google_assistant_type: switch
  emulated_hue_hidden: false
  friendly_name: Christmas tree
  emulated_hue_name: "Christmas tree"

Worked in Hass but it wasn’t showing up in the Google Home app.

Reluctant to unlink and link my account again (and having to assign all the devices to rooms again) I tried calling the request_sync service again. It didn’t work, all I got was the same 400 error as before.

So I unlinked and expected to see the account [test] House Name under Add new but it wasn’t there. I waited a few min, but still nothing.

I then found this thread and was about to try renaming things to see if that triggered anything. Before I did I went to https://console.actions.google.com to see if there was anything there that was obviously wrong. I clicked Test draft and within a few seconds it popped back up on my phone under Add new. I linked accounts and the devices were there including the new “Christmas Tree” switch.

Out of curiosity I tried the request_sync call again, went to the log expecting to see the error, and whilst there was an error it was timed 10 minutes before. Which was a first, so just to be sure I clicked it again and still no error.

I then changed to change the name (using the web ui > Configuration > Customization) from “Christmas tree” to “Christmas lights”, saved it, called the request_sync service and in a few seconds the change appeared on my phone (after doing the usual “pull down to refresh”).

Woohoo.

I then tried changing the name using the yaml file

customize.yaml

switch.socket_01:
  google_assistant: true
  google_assistant_type: switch
  emulated_hue_hidden: false
  friendly_name: Christmas fairy lights
  emulated_hue_name: "Christmas tree"

Saved the file, clicked each of the Reload buttons (Core, Groups, Automation, Scripts) and nothing (worth noting that I didn’t have to restart Hass). I then looked in the web ui customization bit again, and the name was appearing as “Christmas fairy lights” but my phone wasn’t picking up the new name.

Of course, I had forgotten to call request_sync, after I made the call again, it still wasn’t appearing with the new name in the yaml file.

Even though I could see the new name “Christmas fairy lights” in the web ui (so it must have read the file correctly) I had to also click Save (even though I hadn’t made any changes in the web ui) in order for it to work. After another request_sync, within a few seconds it was appearing on my phone as “christmas fairy lights”. Maybe the last step of having to click Save would not have been required if I had restarted Hass,

Conclusion:

It seems it does still work as intended (i am using hass.io v60) without having to change the name with letters or numbers or adding aliases.

As the above was mainly about changing the name because the adding of the device was achieved initially by unlinking the account, I also tried adding some new devices. Edited the config files, saved them, restarted Hass, checked phone a few times and saw no new devices were appearing, called request_sync and within a new seconds (and a refresh) the new devices appeared on my phone.

Yay

edit: I thought I would provide my google_assistant config in case it helps

google_assistant:
  project_id: something-123456
  client_id: random80characters
  access_token: random80characters
  api_key: XXX
  agent_user_id: [email protected]
  expose_by_default: false

As per the note at the bottom of the docs I created the project in the Google Console first, then when creating an Action I used the project-id already set (it appeared in a dropdown when I went to give it a name)

1 Like
46

Is this still an issue? I had it all working, but since the latest hassio I got errors on the input_boolean. So I tried to unlink and link again, but unfortunately I cannot get it linked back again. I get the “test app” in the google home app, but after trying to link it gives the error “something went wrong, try again”.

I looked in the logs, but there is no error, I rebuild the app and still get the same message. I tried to expose only one light, or expose everything, still no success.

Anybody got advice? I don’t know what else I can do or check to find out what the problem is.

47

Go through the config all again. I think Google added something… I had a similar problem and just went through it all again and got it working.

48

apart from input_boolean. you also have to remove type:

49

Hey all.
Just a quick note of how i got it finding my devices again without having to add aliases to all my devices.

  1. I went to https://console.actions.google.com/ and selected my project
  2. Clicked on ‘Test Draft’
  3. On the next page, top right click the reset icon.
  4. When I then tried to relink in the Google Home app, all devices showed up.

I’m not sure if this is a coincidence or if it did in fact reset the project, but its worth a try.

50

@SuperSean, thanks for this. This worked for me when my test app no longer showed up in Google Home after unlinking.