-
-
Notifications
You must be signed in to change notification settings - Fork 7.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Manual Google Assistant needs new setup instructions #35867
Comments
Hey there @home-assistant/cloud, mind taking a look at this feedback as it has been labeled with an integration ( Code owner commandsCode owners of
|
Would you be able to update the guide with the steps that you took? |
I'll look at it if I get some time this week, sure. |
I think the migration is causing some inconsistencies but I just wrote up the part of the process that's different with the Google Home Developer Console (as compared to the Actions Console). Create Project in Google Home Developer Console
Finish Setup.
I think the rest is essentially the same. |
|
Wow thank you i couldnt find this anywere else... works perfect One question on the documentation says taht it can work locally and in the step 17 yos stated taht skip local for now, do you have any idea how to make it work locally? |
follow the rest of the steps in the hass instructions page. the local fulfillment stuff is all in the same page |
Why haven't the official documentation been updated yet? |
but in the page it sends you yo Actions google console to upload a fiile but there is no way to do that beacuse it says that is view only... Conversational Actions have been sunset. Changes can't be made to any actions. You can still view the Actions for a limited time. |
how could I invite a family member to add devices to their google home? |
thank u for the updated guide, worked as expected for me! |
Thanks for the guide @y8s ! Finally got it working, unfortunately I can't get "local fulfillment" to work, If I enable it following tho original documentation, then "sync my devices" command gets me an error. I guess I'll settle for the cloud version for the time being ... |
When is the official documentation going to be updated @ the website? |
Steps to Configure Google Assistant through the Google Home Developer ConsoleControl your devices with Google Home speakers and have them appear in the Google Home app Google Assistant, integrated with Home Assistant, allows you to control your smart devices via Google Home. To do this, you must set up an integration between both using the Google Home Developer Console, enabling device synchronization, and configuring your Steps to Set Up Google Assistant with Home Assistant:
Additional Steps to Enable Local Fulfillment:
References:
|
Thanks @sharklatan for the clear write-up! Comments and review on the updated instructions:
This step group is essentially redundant, "APIs & Services" is not available under "Analytics" and in step group 4 you describe anyway how to access this page instead. I suggest removing this step group.
In the current web interface (20241127.8), the detailed steps are:
The current web interface does not provide an option to choose the path, you can just upload it and press Submit. For the same reason, I needed to manually copy the file into
I was a bit confused that we're now back at the Google Cloud Platform. Couldn't these steps moved earlier into step group 4?
"Check configuration" does not exist, but it seems that it is enough to press "Quick reload" in the Restart menu (under Settings > System > Power icon (in the top right corner)), any error in the YAML will be displayed when attempting this. After that, restart the home assistant entirely.
As many users might come from a Windows background and it's a subtle difference, I'd suggest maybe noting explicitly that the extension must be
The google_assistant:
project_id: YOUR_PROJECT_ID
service_account: !include /config/SERVICE_ACCOUNT.JSON
# ...
These steps have apparently not yet been updated since Actions were sunset? I found them by doing:
Finally, the last step is missing in your updated list:
Edit: Resolved that by adding the project_id to the yml above (see change history of this comment) and restarting the home assistant completely. Now I am seeing no exposed devices ... Edit 2: I'm also confused that this description says we should be able to expose single entities to a "Google Assistant" voice assistant, but I can't see this voice assistant in my home assistant ... Edit 3: I set Edit 4: Edit 3 is exactly what the docs suggest: " |
should read:
|
Thank you soooo much |
3 days ago I followed the above guide with HA 2024.12.5. It succeeded initially, but then after 1-2 days it has been failing with google assistant replying "cannot reach [project name]", whenever I turn on some light or I request to "sync my devices". I've tried unlinking and relinking, it worked for few minutes and then same problem again. While browsing console.home.google.com to identify any problematic places on my project configuration, I noticed that company profile was missing, although I had added some as indicated in this guide. One change - easy to notice - is that it now requires 192pixel logo, while few days back it was requiring 144 pixels, as this guide describes. I filled in the necessary fields in the company profile as required by google, and now the profile is 'In review' state and the integration works again. But it looks like there are some ongoing changes, which are causing problems. Perhaps this guide needs to be revisited once these changes are finalized. Has anyone noticed similar problems? |
I set mine up on Sunday, and it didn't need a company profile, and testing now it still only wants a 144px icon. Your error sounds like a connectivity issue, have you checked the logs for your external access? |
I have again same problem. Devices went to 'offline' state. The Company Profile is still In Review, so it seems this was not the problem, you are right. Now, I unlinked and when trying to re-link I get a message I see error logs on the home assistant, "Request for https://homegraph.googleapis.com/v1/devices:reportStateAndNotification failed: 404" appears 17 times. I did change the service account and refreshed the SERVICE_ACCOUNT.JSON as one of the troubleshooting steps suggests. I've been also clearing the chrome cache on the Android and also changing username/password for the login (from google home app to HA when adding devices). At some point it is working for few minutes or hours, but then devices go to OFFLINE and stay there. I use DuckDNS and NGINX for connectivity. |
I've the same scenario as mentioned by @athanassis . Using DuckDNS and NGINX and tried to pair the [test]homeassistant app again in Google Home, but without success.. I get the same error with: can't reach [test]homeassistant, try again. The weird part is, that it prompts me to login with my Home Assistant login, that's al working fine. When that's done, it starts spinning, and then give me a snackbar notify with the can't reach. On my cloud console I see the following error: SYNC: Request ID 14294252617453170120 failed with code: BACKEND_FAILURE_URL_TIMEOUT It looks like some stuff is changing at Googles end, breaking some of this stuff. I've successfully followed all steps above, but seems like after re-pairing it breaks. Anyone with some suggestions? |
I also have the same problem, I unlinked and when I linked again I got the error "can't reach [test]homeassistant, try again." after entering my HA credentials. I also use duckdns and nginx. |
That might be related but it feels more likely that it isn't, could someone open a new issue and link it here so we don't fill this one with troubleshooting? Could you also include screenshots and an example of an affected domain? It's important to know where the error's actually appearing, and my suspicion is DNS (DuckDNS has had downtime in the recent past). |
I've created a new issue in the core project: home-assistant/core#135163 I can't directly mention this issue, because of the different project seems like. Hopefully there are some answers :) |
Apologies for asking what is likely a simple question. The IP Address and port of my home assistant instance? (Which didn't work for me) |
Thank you everyone here, I have run through the steps outlined by @y8s , @sharklatan and @LinqLover and finished the setup and it works as expected. |
Hi Guys, I followed the isntructions, but for some reason the Google Home app won't show my [test]HAFulep It looks like this at the moment: default_config: frontend: automation: !include automations.yaml google_assistant: Any idea why it won't show up in Google Home app? |
I see a mismatch here with the Service_Account.json you mention, and the !include statement with all capitals. I think those must be the same. |
You need to enter your DDNS domain name in the Authorization URL field, not just the IP address and port of your Home Assistant (HA) instance. For Google to access your HA instance, you must ensure it is reachable via a public domain name and that your instance has an SSL certificate (https). This setup requires either opening the necessary ports or setting up remote access for your Home Assistant. This step is not included in the guide because it is a prerequisite: Google must be able to access your HA installation through a domain address secured with SSL (https). Without this, the authorization process won’t work. |
Did anyone manage to get it to work with tailscale?
I'm getting the same error when trying to set up the cloud-to-cloud integration. Is this because of the tailscale domain? |
If you're using Tailscale Funnel, that should work, but I'd be cautious about exposing your HA instance to the global internet. I've set mine up on a secret domain using a wildcard TLS certificate (a bit like Plex do), but I don't think that's possible with Tailscale. Google doesn't require the URL to be anything in particular other than HTTPS, but HomeAssistant won't support URL prefixes, so there's no other reasonable way to have the URL shared only with Google. |
Thank you for providing the detailed step-by-step instructions, @y8s 🙏 |
fixed in #37085 |
It wasn't much but I'm happy to help in any tiny way! |
I managed to fix it by trying a different app icon. I downloaded a new icon, didn't even change the name, and it worked. |
So... followed the steps. Started the Google Home app -> Add device -> Works with Google Home -> the integration -> logging in HA In the google console, the log says: I should also mention that on the project page, in "Project details" there is: |
You don't need to certify your integration, so don't worry about that. That's Google's API "please back off" error, so maybe try giving it an hour, and check if your API usage seems high when that updates on the dashboard. |
Feedback
Was trying to add the Google Assistant functionality for non nabu casa people and ran into the depreciation of Google actions.
The actions page pushed you to use the developer console instead (actions is now view only and you can't add new ones).
The good news is that after some playing around, doing it through the new Google Home Developer Console seems to work. And other than a few changes to the process, has basically the same elements. I think you just leave it at the point before testing and add your service account, update hass configuration, then you can add it to Google home on your phone.
So the steps just need to be reworked to match the new console.
URL
https://www.home-assistant.io/integrations/google_assistant/
Version
2024.11.2
Additional information
No response
The text was updated successfully, but these errors were encountered: