Google Assistant: "Could not update settings" / "/api/error_log served" if more than a certain number of my devices are set to be sent

another approach, is maybe to make the rooms already manually in the google home app, so HA doesnt need to make the rooms

but for now , i wait on response on gthub

I still have a config question, so if you expose everything to true as default, then you need to expose: false for every entity you don’t use, right?

So 20 switches, you only want to expose 5, you need to have all 20 entitys configured in Google config with 5 to true and 15 to false, correct?

Had a chance to look through the JSON and do some final testing.

I now have it working with my original config minus the room settings. expose_by_default: false, and just calling out the devices I want.

I’m fairly sure now that the issue occurs if a request to sync a service contains 20 or more devices which specify a roomHint.

Or more simply, if you use room on more than 20 of the entities in your google_assistant: entity_config: section when you first link google assistant (including after unlinking) it’ll fail.

Interestingly resyncing (i.e., by saying “Ok Google, Sync Devices”) actually seems to sync up correctly until you have 21 devices with rooms, not 20.

This seems to be on google’s end, not Home Assistant’s, since HA is just sending JSON that follows the spec.

No idea why occasionally I was also getting the error when it worked. I think that is just a generic error message and maybe something else also caused it unrelated to our problem.

I still have a config question, so if you expose everything to true as default, then you need to expose: false for every entity you don’t use, right?

Yes.

There are three ways to limit what gets show to google:

  1. expose_by_default: false, then manually expose: true each item
  2. specify types of devices in exposed_domains: (i.e., - lights is all lights)
  3. expose_by_default: true, or not stated (defaults to true) then manually expose: false each item you don’t want appearing

expose_by_default: false seems to be working fine for me now. No idea why it was iffy for my sometimes.

thnx for info, thx to you i have it up and running again; well sort off :slight_smile:
there is still a cache issue betweel the google home app and google assistant itself
1 hour ago, when i was testing with the rooms, i stll had 19 devices linked with rooms
so i unlinked succesfull, did sync my devices to make sure the link was really gone
but still those 19 x devices are still visible in home app
then i exposed my normal config, with 62 entities without rooms

in google home app, i still see 19 x devices linked with rooms,but if you go deeper in the settings itself the place where you link, i see my 62 x devices and no rooms there
so if you go to the settings, then actually in background it opens the google app, not the google home app
because in google app, you can also link services, you dont even need the google home app
so there is an issue between home app and google app, nothing we can do …

If anyone comes across this topic with the same issue I’ve posted the update google have sent me in this topic, which I’ll likely keep posting any updates in since it is more active.

TL:DR They know about the issue and it has been assigned to the engineering team.

I have the sam problem, get the “Could not update settings”.
Any suggestions? Thanks

{
 insertId: "xxx"  
 logName: "projects/xxx/logs/actions.googleapis.com%2Factions"  
 receiveTimestamp: "2019-12-01T15:53:38.811670858Z"  
 resource: {…}  
 severity: "ERROR"  
 textPayload: "SYNC: Request ID *** failed with code: BACKEND_FAILURE"  
 timestamp: "2019-12-01T15:53:38.806243279Z"  
}

config:

project_id: !secret ga_project
api_key: !secret api-ga
expose_by_default: false
entity_config:
  light.lounge:
    room: lounge room
    expose: true

the http view log:

2019-12-01 23:49:40 DEBUG (MainThread) [homeassistant.components.http.view] Serving /auth/providers to 192.168.17.1 (auth: False)
2019-12-01 23:49:40 DEBUG (MainThread) [homeassistant.components.http.view] Serving /auth/login_flow to 192.168.17.1 (auth: False)
2019-12-01 23:49:40 DEBUG (MainThread) [homeassistant.components.http.view] Serving /manifest.json to 192.168.17.1 (auth: False)
2019-12-01 23:49:48 DEBUG (MainThread) [homeassistant.components.http.view] Serving /auth/login_flow/a7cd55da73ce45a39c041df5fb29a351 to 192.168.17.1 (auth: False)
2019-12-01 23:49:53 DEBUG (MainThread) [homeassistant.components.http.view] Serving /auth/login_flow to 192.168.17.1 (auth: False)
2019-12-01 23:49:53 DEBUG (MainThread) [homeassistant.components.http.view] Serving /manifest.json to 192.168.17.1 (auth: False)
2019-12-01 23:49:54 DEBUG (MainThread) [homeassistant.components.http.view] Serving /auth/token to 108.177.73.19 (auth: False)

Same here.

Has anyone solved this problem? I have exactly the same problem as @cyberdie and @bingooo