Unfortunately another Samsung Evo card seems to be damaged (third in the past two years), meaning I had to restore a snapshot to a new card (different type of card). All works fine, except for Google Assistant. So I did what I did last time: go into the Google Assistant app, unlink the [test] device I created according to the Google Assistant docs on Hass.io, restart Hass.io and my phone just to be sure and add the [test] device again. It prompts me with the Hass.io login screen and accepts my credentials, however, next it says “Couldn’t update the setting. Check your connection.”
When I check the home-assistant.log file it gives me [homeassistant.components.http.ban] Login attempt or request with invalid authentication from 108.177.64.xx
Does anybody know what happened and how I can make Google Assistant talk to Hass.io? I did find a few (mainly older) topics here, but no solution.
I had a very similar problem and managed to fix it. In my case I believe it’s because my Google account was attempting to log into HA using my old HA credentials from my previous setup.
To fix this, I went into Google Actions, clicked on the Test tab, click Settings at the top right, and clicked Unlink. Afterwards, I was presented with the HA login screen again in the Google Home app and was able to link my devices.
Even though I did not see an unlink button there, I did see there was no test active. I activated it and then I could add it to Google Assistant again. It took me a few tries to actually add devices though. Also, Google Assistant didn’t recognise the devices afterwards, but Google Home did, maybe it needs some time to sync.