Google Home speaker not working on my google account, other accounts it works ok.

[Guust]

I Have a problem with my google Home.

It started having problems with steering my hue system and i found out is was not working very well anymore in normal questions too.

When i ask the time, the leds start spinning, thats it. when i make a joke...it answers...standard answer for standard guestions.,

What i have tried so far searching for about 25 hours now: (and factory default speaker every time after that)

- remove macfiltering from my wifi - no result.

-using different wifi from another router - no result.

 -using a hotspot from a phone and setting it up that way - no result

 - using a tablet and setting it up with a tablet, no result.

- using a borrowed google home mini. no result.

- resetting all kinds of stuff like voice recognising. no result

- deleting files and information in the google account. no result.

-Setting it up with or without voice recognition, no result.

- trying to connect to my hue, askes for permissions and then not working, not loading the lights in google home.

- trying probably more then i can remember......no results.

Installing the Google home on another google account works fine!!! but i cannot use my hue anymore, because the connection crashed, and maybe when i get it set up with my google account it might work again.

So my conclusion is there must be something with my google account that messes up thing!!!but what???

Does anybody have an idea for me? i am getting pretty desperate, and cannot find an answer nowhere.

Greets,

Guust,

Netherlands

[Fenella128]

Hi Guust,

First off, hats off to your dedication—you’ve practically earned a PhD in "Google Home Troubleshooting"! It sounds like your Google Home might need a new name, perhaps “Troublebot 3000” or “The Stubborn Spinster” given all the spinning LEDs and its uncooperative attitude. 😉

Now, back to fixing the issue. Based on everything you’ve tried, it really does seem like your Google account is the culprit. Here are a few more things you can test:

1. Account Permissions and Third-Party Access

• Visit Google Account Security Settings and review any apps with access.
• Remove anything related to Hue or third-party apps that look suspicious, then re-link them.

2. Clear Google Home Data

• Head to My Activity on Google and filter for "Google Assistant" or "Google Home."
• Erase all past interactions—it might help Google Home forget whatever grudge it’s holding against you.

3. Re-Link Hue Devices

• Completely unlink Hue from your Google account in the Home app.
• Ensure both the Hue app and Google Home app are fully updated.
• Re-link step by step, and cross your fingers (or toes, for extra luck).

4. A Fresh Setup Experiment

• Factory reset Google Home, and temporarily set it up with a second (new) Google account.
• Test it out, give it a nice name like “Temporary Tinker” to see if it behaves better.
• If it works smoothly, try switching back to your original account and linking Hue again.

5. Call in the Experts

When all else fails, contact Google Support. Let them know your “Troublebot 3000” refuses to cooperate, even after countless hours of love and attention.

Hopefully, these tips help, and your Google Home starts acting like the helpful assistant it was meant to be. Keep us updated, and good luck taming your little gadget gremlin! 😊

Greets,

[Guust]

Thx for your help Fennela128!!

  for the clear reply. I will use your numbers for reading easy.

Number 1 and 2;  I had tried"that  already, but i have looked into it again and cannot find any issues there.

Number 3 does not work, even after removing the link from both hue and google side.

Number 4 is part of my "work around solution i allready have implemented

What I did to work around:

factory reset speaker.

Build it up with another google account that works.

And then I still could not connect the hue and google account....something is also wrong there.

So I connected them with Matter!!! Ask for a connection code in the Matter section of Hue app.

this works also!! not as fast and nice, but it works

So with workarounds it is functioning again!

Thx for the help!