Can't add Hue bulbs in Google Home app
Finally got myself a Hue starter kit yesterday. They are amazing and setup was pretty easy... Until I tried to add them in the Google Home app.
I tried setting them up the standard way in the Home app by going to Add --> Set up device --> Have something already set up? --> Philips Hue. Then it redirects me to the Hue website and prompts me to allow Google to control my Hue devices. When I click "Allow", I'm taken back to the Google Home app, specifically the device setup page. It loads/spins for a couple of seconds and then it just does nothing. Nothing is changed inside the app and when asking my Google Home to turn off the lights it says no lights are connected. On account.meethue.com, it does show Google under the Cloud apps, but the Home app seems unaware of the link with Hue.
I've looked around and it seems I'm not the only one with this problem. Two common suggestions were to (1) try it with a different phone and to (2) tell Google Assistant to "sync devices". I tried with a different phone but got the same result. Asking Google Assistant to "sync devices" doesn't do anything either. It just says that I don't have any devices that support syncing.
Has anyone here had the same problem? Any suggested solutions? Thanks!
EDIT: I've found somewhat of a workaround. Check my comment for more details.
Posted Feb 24, 2019, 9:34 PM UTC · edited
Okay so after getting in touch with Philips Hue support I've come up with somewhat of a workaround, but it's far from ideal.
I created a new Google account, added it in the Google Home app and then created a new Home. After going through the steps to link Philips Hue, it did the same thing as before where the app would take me back to the "Set up a device" screen, spin for a couple of seconds and then just stay on that screen. I thought the linking process had failed again but when I refreshed the home page of the Home app a few times, the bulbs all magically showed up.
So, all good right? No.
It seems that in the process of doing this, I somehow completely bricked my main Google Account. When I try to switch to this account in the Home app, the app isn't able to load the home screen, settings or anything else. It gives me the "not connected to the internet" error even though I'm clearly connected to the internet and it has absolutely no problem doing anything when I switch back to the newly created Google Account. The app is completely unresponsive on my main Google account. I can't add or unlink device, can't view the devices, nothing.
So since I'm unable to unlink my other devices (Google Home and Mi box) from my main account, I've found nothing better than just factory resetting these devices and adding them to the new Google account. Tomorrow I'll check out if there's any way to reset my main Google account in order to get all the devices back on there, and if I do, I'll be sure to update this post.
EDIT: Okay, I finally got my issues resolved. I had two different issues and I'll describe how I fixed them here:
Issue #1: The issue where nothing on the Home app loaded when I logged into it with my main account, however, no problems if I logged into it with a secondary account. This issue is most definitely a Google server-side issue, which somehow corrupts Google accounts. After hours with support they finally had a "Senior Specialist from the Google Home support team" contact me. He instructed me to create a feedback report with a special keyword in it so he could find my report. 24 hours later, I logged in to the Home app with my main account and everything loaded again. I could delete all the corrupt Homes and could once again link/unlink devices... except Hue bulbs. The Home app still didn't want to connect to my Philips Hue account. That's issue #2, fixed that aswell. If you have Issue #1, I suggest contacting support and stressing very strongly that this is a Google server-side issue and that only a Google engineer/specialist can fix your account.
Issue #2: The issue where you link your Hue account in the Home app but no bulbs show up. The issue seems to be different for everyone, but this is how I fixed it: