Disillusioned by post-educational life and shoved aside by a government who doesn’t want them there, both are trying to come to terms with their uncertain futures. Thanks to visa limitations, Ao is forced to return to Japan, leaving Bo in England.
#NO LONGER HOME KICK UPDATE#
I need to go to an appointment now, but sometime this evening or tomorrow I’ll submit and issue ticket to update the manual configuration instructions.Bo and Ao are graduating university and preparing to leave the flat they’ve lived in together for a year. Any unauthorized users which connect to this service should have no expectation of privacy or protection of their data."Īfter I had all that entered, I could link GA to HA without issue. " This application is intended for the private use of its developer. Otherwise, just upload the HA logo.įor the privacy policy, create a Google Doc that can be viewed by anyone with the link that says: It exposes smart home devices controlled by a local Home Assistant server to Google Assistant and by extension the Google Home mobile app.”įor the logo, my house had one already, so I used that. Long: “This Action is intended for personal use.
Short: “Connect Google Assistant to a private Home Assistant server” In order for this info screen to work correctly, you now must complete the “Enter information required for the Actions directory” portion of the Actions setup overview. If anyone has any additional debugging steps, please let me knowĪpparently Google has added a little splash screen to the flow that happens before it calls _DOMIAN]/auth/authorize. I’ve spent several hours debugging this, including dozens of forum posts, but nobody seems to have the same problem as me. I’ve verified that, , and are all accessible externally with a valid SSL cert. I’ve even tried restoring to my backup from last night where the config was set to expose_by_default: true and everything was working, but still no luck linking from the Google Home app. I’ve tried everything I can think of, including reinstalling the Home app, starting a new Google project and meticulously following the instructions from Google Assistant - Home Assistant, and checking all my firewall and reverse proxy rules. This page only shows up for about a 10th of a second before returning back to the list of integrations, with the error “Could not reach Home Assistant. The Google logo loads, but the Home Assistant logo looks like a broken image link (not sure if this is a clue or not). You can change this link in your Google Account”, including buttons to “Cancel” or “Continue”.
I haven’t been able to add my Home Assistant to Google Home since then.Įvery time I try to add Home Assistant, it turns the screen white for a second like it’s loading a page, then, for a split second, it flashes a screen with the title “Link an account to control Home Assistant on any device” and the text “This link will be available on devices or services where you’re signed in to your Google Account. In the process, I re-synced my Google Home app, but there were still too many devices, so I unlinked the app/integration and tried to re-link it, but that’s where the problems began. I recently decided to switch from expose_by_default: true to false and set my entity_config manually.
0 kommentar(er)
