I have followed the tutorial here several times, and am still having the same issue:
Towards the final step, when I try to add my device to Home Assitant (iOS) I get the following error:
{"message": "missing project_id in redirect_uri"}
I’ve tried creating new projects from scratch and going through the tutorial again, but no dice. I know that those two variables exist in the assistant.json, but not in project.json in the tutorial.
You should redact your client ID and access tokens. Still thinking about this issue.
EDIT:
Now that I say that, you’re client ID looks weird to me. I don’t recall seeing anything .com in my strings that were generated by running the command in the walk-thru.
So I recreated my action again in google, and removed the client_id and access_token that I had. These where the google project ones. I regenerated new credentials and tried again. Making some progress it seems.
{"message": "invalid client id"}
I doubled checked the id and it matches in configuration.yaml and my google action.
I’ve gotten further now. I put my google action credentials in the client_id and access_token again, and the error went away. Now I can see the connection hitting my HA server, but on my iOS device it continues as if the device is going to be added, but then errors out with “Something went wrong, try again”
I’m not sure what you mean by addon. I am using the raspberry pi version of google assistant. For my phone it’s an iphone6s with HA and Google Assistant app installed.
yes, it is. And you can use it aside the component. In some way it works better because for example you can ask for the state of your sensors, but obviously you also have to use dialogflow to make it work. Anyway, I asked if you were using the addon because I have the same error when GA asks me if i want to “link” my test app. If I don’t it works anyway but if i could be able to link it probably I’d could use my test app commands directly, without asking to GA to talk to my test app
So, the issues in the instructions are that the client_id and acess_id have to be the ones given by google, not randomly generated ones, that got me through the first error, the second error was because I have several google accounts, and with the confusion the action was setup in a different account that I expected.
The FINAL resolution, where google assistant would be about to install the device, but then fail is because your HAS has to be running on 443 (for ssl) not 8123. I got around this by setting a firewall rule.
Thanks everyone for your help. Now to figure out how to make this work with my assistant on RPI
I didn’t get the client_id and acces_token from anywhere on the site i just made it up randomly put it in to my configuration file and copy pasted it in the account linking tap on the actions page. And every thing seems gto be working as it should.
The only thing i took from the actions page was the project id (which is the last part of the url, whne you have the project open in the browser)
I used the client_id and client_secret from the assistant.json file that you downloaded when you setup your project in google cloud. Now I’m not sure if the random codes work, but this worked for me.