What I should have added in my previous reply is that when I get this error, the function still works…
eg:
Me: ‘Hey Google, turn off the kitchen lights’
kitchen lights DO turn off
Google Home: ‘Sure, turning off kitchen lights’, ‘Sorry, there was an error contacting the Home Assistant Cloud by Nabu Casa’
Me: ‘Well, it f’ing worked so WTF are you talking about b!tch…’ 
For me it doesn’t work at all but die graciously
Ok to add bit more details, i then unlinked the hassio app in GM and relinked again. Worked for next few times and back to square now…again same error…cant reach HA cloud at Nabu Casa
I am facing the same problem from time to time. Is a solution ongoing?
This is not the place to get support for Home Assistant Cloud. Please report issues either in #cloud on Discord or at https://www.nabucasa.com/support/
Thanks @balloob for information. In fact i have earlier reached out to clould support few months back but issue is not resolved. Nevermind i have raised a new ticket again now and hope it can be solved this time.
Did you ever get this issue resolved?
I have exactly the same issues (as do many other based on searching the web).
As it seems a common problem I would have thought there would be some feedback somewhere from someone, but I can’t find any answers as to what causes it or more importantly how to fix it.
I am left assuming there is no fix for it
Hi,
Same issues here. To me, it seems like google is timing out waiting for a response.
I’ve got the same problem as well sometimes.
I don’t know what causes this problem?
@frenck what can we do to debug this problem?
Getting several of these lately too. I’m going to try open a ticket with the support.
Just curious, any response or solution? I’m getting these messages om my Google Nest Hub as well.
More than likely its a timeout issue. Google sends the command to Nabu which sends it on to your HA system. google just doesn’t get a response in the time needed. Not much they can do when they are just the middle-man. It would be dependent on your home HA system sending the response to their servers, and their servers relaying it to Googles system.
It seems to be more complicated than that. If I issue a voice command when my Google home and my Android phone are in the same location I get the nabu casa error on the phone but the Hub command works just fine.
Are folks seeing this error on the Google home devices or on phones or both?
Yes. The same thing is happening here with my setup, exactly as you described. I would appreciate a solution as well.
I opened a ticket with the support and they just asked to try remove the additional family member to make a test which unfortunately was unsuccessful. I asked again for support and what I can try next.
To be honest I didn’t try it from my phone. I’ll give it a try
Just figured I’d throw my note in here that I too am having this same exact issue. The command always ends up working, but Google seems to time out before it gets whatever response it is looking for. Seems like the frequency it occurs at has increased noticably in the last month or two, too.
I get this ALL THE TIME. The commands work and stuff gets turned on and off, but it is really annoying.
I have been getting this way more frequently. What i am also noticing is that it only happens with certain device more often than others.
This becomes a nuisance as i try to control lights using the Google Display (ie. touch screen to adjust dim), but because it errors out, i am not able to contorl the lights from the Hub. However via voice it works but still reports not being able to connect.