mirror of
https://github.com/home-assistant/home-assistant.io.git
synced 2025-07-18 23:06:58 +00:00
Add troubleshooting step for re-enabling test if syncing doesn't work (#9274)
This commit is contained in:
parent
796df5f388
commit
6d63ab7e7d
@ -235,6 +235,8 @@ The request_sync service may fail with a 404 if the project_id of the Homegraph
|
||||
3. Enable Homegraph API to the new project.
|
||||
4. Generate a new API key.
|
||||
5. Again, create a new project in the [Actions on Google console](https://console.actions.google.com/). Described above. But at the step 'Build under the Actions SDK box' choose your newly created project. By this, they share the same `project_id`.
|
||||
|
||||
Syncing may also fail after a period of time, likely around 30 days, due to the fact that your Actions on Google app is techincally in testing mode and has never been published. Eventually, it seems that the test expires. Control of devices will continue to work but syncing may not. If you say "Ok Google, sync my devices" and get the response "Unable to sync Home Assistant", this can usually be resolved by going back to your test app in the [Actions on Google console](https://console.actions.google.com/) and clicking `Simulator` under `TEST`. Regenerate the draft version Test App and try asking Google to sync your devices again.
|
||||
|
||||
### {% linkable_title Troubleshooting with NGINX %}
|
||||
|
||||
|
Loading…
x
Reference in New Issue
Block a user