"Can't reach" error on ANY works with google integration

[SirDester]

Hello all,

I have Google Assistant configured mainly with HomeAssistant integration, where I have all my domotic devices.

Trying to connect any external provider (not only HomeAssistant) I receive a "can't reach" error, and the account linking never succeed.

Starting from yesterday my integrations failed to respond, and any try to bring them back by simply reauthorizing didn't work. Initially I thought on a problem on the Google Cloud Project used by HomeAssistant and so I created a new project with new service account credentials from scratch, with the same results.

Then I unlinked all the integrations and tried to restart from empty device list. The result is wrost than before because now I can't reauthorize ANY external service.

Then I started to directly link some other integrations where I have devices (Mitshubishi Melcloud for climates, eWelink for some domotic appliances, Smart Things or Shelly for other appliances). The single login on every application is fine, but after the redirect back to google home app the process always completes with a "can't reac xxxxxx app".

I'm thinking Google broke something in the third party integration authentication process.
Do you have any similar issue ?

Basically I can't use any voice controlled device with Google home and can't add them again.

[maedacortez]

Hi sirDester,

Thanks for reaching out. I understand that you're having inconvenience  with Google Integrations. To better understand your situation, please answer the following questions:

• Are you experiencing this issue when trying to link a third-party device to the Google Home app?
• Is the issue specifically with the Google Home app or any Nest devices?
• If so, please let me know the apps and devices that are affected.

I look forward to your response.

Regards,

Manuel

[SirDester]

Hello, sorry for late answer.

It seems that after a week the problem solved itself, so I think that it could be some transient issue with account linking on Google side.

I just tried linking the MelCloud app and the process completed fine.

Just to complete the scenario, the issue was related to almost any third-party device I was trying to add to Google Home app (I tried MelCloud from Mitsubishi climates, eWelink for Sonoff devices, Smart Life for other brands devices and mainly the Google Project for Home Assistant integration).

The authentication on the third party site always worked, the oauth token was correctly released to the Google Home App but the app always ended with "can't reach xxxx" error.

The Issue was specific to Google Home app because I don't have any other Nest devices (only some old Google Assistant and some Google-mini, that worked without any issues).

For now I hope that this issue don't come back 🙂