Core: Google Assistant Integration sync duplicates with invisible devices

[DavidFW1960]

Home Assistant release with the issue:

0.83.0b0

Last working Home Assistant release (if known):

Not 100% sure
Operating environment (Hass.io/Docker/Windows/etc.):

Hass.io Generic Linux Install on Debian
Component/platform:

Description of problem:
So today I reconfigured my mesh repeater and reconfigured the SSID on a few devices.
Google Assistant stopped working so I went in and enabled the test app again (this is the manual configured component)

It all worked when I re-linked.
It all works if I say 'hey google sync my devices"

However if I use the Sync Service, it seems to duplicate the devices - I can not SEE any duplicates but I can no longer control any of my devices. I can control a room - say hey google turn on lights in the lounge room and it says ok turning on 2 lights - but I only have one in that room. If I say turn on the lounge light it says it does not know which lounge light...

Delete the app and reling and verbally sync and it all works.

The only other thing I did when I first linked it was I set it to not expose everything by default as I ended up with 63 devices instead of 23....

Otherwise everything is working perfectly.

I duplicated this behaviour a few times before logging the issue.

Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):

Traceback (if applicable):

Additional information:

[scfigg]

I can confirm I have the same problem. I've only tried syncing by saying "sync my devices" though. I only exposed certain things in my configuration though - which could be similar to you. Any idea how to exclude certain items from syncing without not exposing the group then?

[SteveDinn]

I had seen this as well, but with the HA cloud configuration via Nabu Casa. It went away after I removed and re-added the service. Haven't seen it since. Sync'ed my devices many times since then.

[ahayworth]

I have a persistent, annoying problem with duplicate devices - but I also have it for other integrations (notably Harmony). There's an open community support thread about it, and Google seems to have acknowledged there is a problem: https://support.google.com/googlehome/thread/506752
I also opened an issue on the actions-on-google/smart-home-nodejs repo: https://github.com/actions-on-google/smart-home-nodejs/issues/202

There seems to be some problem on the google home graph backend, and worse, no exposed endpoint for end users to delete devices. Unlinking a service is supposed to clear out all devices, but as I pointed out in the github issue, that doesn't always seem to work reliably.

FWIW, the HA code for google sync operates according to my best understanding of the google smart home integration docs: you ask Google to sync, Google sends a SYNC request, and HA responds with a list of current devices. I don't think the bug is in HA.

But it is incredibly annoying. I've noticed that my duplicates go away after some time - at least a few days. I hope yours do too. :-/

[DavidFW1960]

Thanks @ahayworth much appreciated. I just unlinked and then relinked and only use Google to sync and seems I was lucky that fixed it. Glad it's probably not Home Assistant causing this. I daresay Google will just quietly fix it and pretend there was never a problem.

Yes it is bloody annoying when GA plays dumb and says it doesn't know which coffee-maker you are talking about. The 'phantom' ones don't show and even if they did, as you point out there is no way for the user to delete them.

[dr808]

I'm having similar problems, however, with 0.83 now no matter what I ALL devices sync. expose_by_default: false does nothing. Asking Google to sync just makes things worse. It used to be unlinking/relinking would work but now nothing but scripts, automations, everything.

[marchingphoenix]

I'm having similar problems, however, with 0.83 now no matter what I ALL devices sync. expose_by_default: false does nothing. Asking Google to sync just makes things worse. It used to be unlinking/relinking would work but now nothing but scripts, automations, everything.

See #18856

[marchingphoenix]

I have a persistent, annoying problem with duplicate devices - but I also have it for other integrations (notably Harmony). There's an open community support thread about it, and Google seems to have acknowledged there is a problem: https://support.google.com/googlehome/thread/506752
I also opened an issue on the actions-on-google/smart-home-nodejs repo: actions-on-google/smart-home-nodejs#202

There seems to be some problem on the google home graph backend, and worse, no exposed endpoint for end users to delete devices. Unlinking a service is supposed to clear out all devices, but as I pointed out in the github issue, that doesn't always seem to work reliably.

FWIW, the HA code for google sync operates according to my best understanding of the google smart home integration docs: you ask Google to sync, Google sends a SYNC request, and HA responds with a list of current devices. I don't think the bug is in HA.

But it is incredibly annoying. I've noticed that my duplicates go away after some time - at least a few days. I hope yours do too. :-/

Closing as "google's fault"

[madgeni]

I'd like this reopened - i have the same issue, and there's no method for resolving it

[marchingphoenix]

Problem is google side, nothing to do here. No reason to re-open.

[madgeni]

urgh, i can't read sorry!

[techyforyou]

I just finished a week long process with Grace on the tier 3 support team. We found the issue in my case was coming from Googles 2 step verification. If you have it turned on go turn it off. It fixed my duplicate issue immediately!