New devices do not appear in Google Home anymore

[rare flower]

Hi, I have just started with Home Assistant and so far, mostly everything worked out just fine. Sadly, the smoth sailing voyage ended today, as I am unable to see one new device on Google Home. Google Home is connected via Nabu Casa Home, and all the other devices I configured earlier this week are available and work just fine. Today I added a smart socket, zigbee protocol, via the tuya zigbee-gateway. I tried both, tuyalocal and the "official" tuya integration. The device can be added to Home Assistant with both integrations and works fine, but it just does not show up on Google Home. I made sure that the entities are available for the Voice Assistant and I disconnected and re-installed the smart socket. The problem persists, though.

I noticed that when trying to re-connect Nabu Casa, after entering my credentials and allowing acces, I get an error message from Google Home App that Nabu Casa is not reachable. Nevertheless, all the devices configured in Google Home that came frome Home Assistant, do work just fine.

What is going on? Where to start? Servers seem to be fine...

[hot stream]

There's a button for that.
https://my.home-assistant.io/redirect/voice_assistants/

[rare flower]

Yes, I know that toggle switch. Of course, it was "on". I toggled the "big switch" above for Goggle Assistant as a whole to off, then to "on" again. And sure enough, all my devices that were available before are now gone from Google Home, but I still cannot connect Nabu Casa to Google Home. Bummer.

[hot stream]

Ok.
Make sure your external access is working correctly then, and make sure you are not using a self signed cert because Google will not accept that and needs access from the cloud.
Also often PiHole or AdGuard messes with the DNS and can mess this up. If you don't have it set right, it does what it wants.

[rare flower]

External access to the Home Assistant web frontend via that loooooong URL does work absolutely fine. I did not make an changes to my DNS in the last 8 months, and about 8 hours ago, I was still able to see all my devices in Google Home. It stopped working at around 13:00h CEST.

[crystal quarry]

that Nabu Casa is not reachable
In this context it is "Home Assistant by Nabu Casa" that is not being reached, and that is your HA server.

When exposing something Google doesn't like, or too many entities at one time, Google might complain with this.

Do you get the same response when you say "Ok google sync my devices?"

And then, to compare, unexpose the Tuya entity and try the same thing.

Ah I wasn't caught up when replying...how many entities are exposed when trying to link Google to HA now?

The number appears in the corner of the Google Assistant card

under Voice Assistants in settings

[rare flower]

30 entities, to be exact.

When saying the German equivalent to "sync my devices", nothing happens. But since Nabu Casa isn't connected to Google Home anymore, there are not devices to snyc anyway.

One other clue: Whenever I try to ad Home Assistant Cloud by Nabu Casa to Google Home, I can directly click on "allow access" without having to enter any credentials.

[crystal quarry]

yeah a cache issue there

[rare flower]

CREDENTIALS!!!!!! I went into my Nabu Casa Cloud settings, chose a new password, then logged out, logged back in, clicked "logout from all devices", logged of in HA from the cloud service, then logged in and suddenly all the devices popped back up in Google Home - without re-adding Nabu Casa in Google home, which is... crazy?! It just was all back...

[crystal quarry]

that's one way to go about it I suppose!

does this include the tuya entity?

[rare flower]

It includes all the entities, even the one that was missing at aorund noon.

Credentials/caching seems to have been the culprit. I might add, though, that home.google.com is super slow for adding automations as well, so it might be on the Google end, and not on the Nabu Casa side...

[crystal quarry]

yes Google Assistant has always been slow, which is why I suggest limiting the number of exposed entities when linking for the first time, or re-linking, and then if that works exposing more in controlled groups, but 30 is kind of in the "good" range. I've seen people try to throw hundreds of entities at it at once, and Google doesn't do well with that

[rare flower]

The whole system seems a little fragile, yeah. This credential/caching shouldn't really exist as a problem - just don't cache that, Google... Well. It works now, and I hope it stays like that. Thanks for helping me find the way through this dungeon @crystal quarry and @hot stream!