Google Home throwing errors

Google Home is throwing these errors a couple times per minute:

What should I do?

1 Like

Rebooted. It s̶t̶o̶p̶p̶e̶d̶ ̶ slowed down a little, but still happening.

I had a bunch of these, then I removed some devices and added some new ones and it shrunk down to 1 entry like that coming in. It is still there as well for me. Have a ticket in with a Thermostat issue as well.
It's all new I suppose.

Any tips on deciphering which device it is?

Wow no. I made a lot of changes to my setup (Christmas) and I deleted and re-added a lot of devices...
Other than starting over I don't know what to say. I have a feeling the driver will get to a more stable version as these issues are pouring in and get fixed. But until then a purge might be best...

Okie doke. I'll purge and start over. I was fooling around with a sensative strip earlier today. (which are terrible btw, I've never despised anything more) But yeah, I was adding and removing stuff. I also added a GE outdoor outlet and subsequently added that to GH. So there's been a fair bit of shuffling around over here.

1 Like

Shot in the dark but did you tell Google to "sync my devices" after making the changes?


Do what?

If that's a necessary step I've never done it. But I just did, and she's syncing devices for "Heeyoobitat" and Nest. :slight_smile:

Yeah the huebitat comment cracks me up :rofl: No idea if that will help the errors but when I've changed devices around in the past that's what I always have do to get the old devices removed from GH/GA and pick up the new ones, after adding them in the GH integration in HE.

1 Like

I've issued that command so frequently it comes up as a Siri Recommendation on iOS...
Why doesn't Google at least do this every 15 mins at the least.
I know Alexa requires it too...

Glad we can find this info.
My parents would give up after it didn't show up when they changed things.

1 Like

Hue-bitat: What happens when Philips and Hubitat have a lovechild.



I'm getting the errors described above as well as this:

app:9932018-12-07 06:09:15.340 pm errorsyncResponse Error: {
  "error": {
    "code": 403,
    "message": "The caller does not have permission",
    "status": "PERMISSION_DENIED"
, giving up for now

Is it working?
Don't throw the baby out with the water.

I'm sure the next update will fix it... Although they've been quiet here.
They're not obligated to say they're fixing it in case they can't fit it in.