Follow from video choice, it will leads to smart home anyway.
Watch it all the way through. It was what I was looking for, it help me wire the parms to what fields. It also showed me what’s important and what you just need to enter to make the UI happy. It also showed me what to expect.
Watching the video and reading. Point of clarification. On the “Add fulfillment URl”
Lets say my connection to my HA from the outside world is “https://myha.com”. When I enter in that URL, I log one with password “HAisCool” which is my HA password.
configuration.yaml
http:
api_password: HAisCool
So my fulfillment URL is “https://myha.com/api/google_assistant?api_password=HAisCool” correct?
So when I am setting up the account linking, it would be the same URL for Authorization URL?
Then I would use the value that is in my client_id: value?
Also, I deleted my first project/action and created a new one. They both show up when I click +. Do I have to delete it somewhere else also?
If your configuration uses 443 as port than this is correct.
No. Its https://myha.com/api/google_assistant/auth?api_password=HAisCool (mind the /auth).
No. It will be removed in some weeks automatically.
That was it. Can’t wait till it removes the dead one, they both are named the same. Now on how to use it 
Has anyone tried if it also works with input.booleans???
Light, switch and scripts works…
project_id: !secret google_project_id
api_key: !secret google_homegraph_api_key
expose_by_default: false
entity_config:
switch.test_light_1:
name: Test Light 1
aliases:
- test light 1
- light number 1
- gratia light 1
- first light
expose: true
room: Office
input_boolean.security_night_mode:
name: Night Mode
aliases:
- night mode
expose: true
room: Office
script.pioneer_volume_up:
name: Pioneer Volume up
aliases:
- pioneer volume up
- sony volume up
expose: true
room: OfficeI use Lights, Switches and Input_booleans. I don’t have any scripts but they are supported I think
Scripts show up as “scenes” on the Google Home App.
I just tried to change my Google Assistant setup in HA to use a new email address / google ID. I created a new project etc in google (logged in with the new Google email address) as per the docs and updated the project_id and api_key in my config. When I try to run the google assistant request sync service I get:
request_sync request failed: 403 b’{\n “error”: {\n “code”: 403,\n “message”: “The caller does not have permission”,\n “status”: “PERMISSION_DENIED”\n }\n}\n’
which I figured was an api key issue. I have a few api keys to choose from in the google api console, so which one do we use? I have tried them all without success…
does anyone have any tips to try here?
Did you check ip_bans.yaml - 403 forbidden usually means I’m locked out of Home Assistant
nothing in the ip_ban list
Don’t the instructions down the bottom say you need to re-setup the homegraph link?
I changed my URL’s there today to use IPv6 and had to unlink/relink ang it’s all sweet so not a Google problem.
I enabled the homegraph API, if thats what you mean.
So you followed the instructions here https://www.home-assistant.io/components/google_assistant/#troubleshooting-the-request_sync-service
So you relinked your app in your phone? Does it work? Can you say ‘Hey Google Sync my Devices’?
oops, forgot to unlink / relink with new project ID 
1 Like
after everything I did yesterday to get the request_sync to work… today after making some yaml changes it wont work again… now I get:
