Slow response when using Google Home to control Philips Hue devices

[Bernt]

(I have also reported this from within the Google Home app)

Problem: In a Google Nest network, all Phillips Hue devices are responding very slowly (10 seconds or so) through Google Home a day or two after either restarting the network or performing a factory reset of the network. The network performance is good in other respetcs.The problem occurs both with speech commands and by using in the Google Home app on the phone. After a restart of the network it works as expected for some hours or a couple of days.

I realize others have reported similar issues, but since I have done extensive testing the last month I think it is worth reporting a summary of my results, which may be of help when fixing this issue. I just mention here what seems significant, but can report more details if nescessary. 

1. Even though Hue products slow down, other smart devices do not slow down when using Google Home to control them (in my case several power plugs from Deltaco and a couple of heat pumps). The problem is specifically related to Philips Hue.
2. Google home commands to Philips Hue devices produce a 10 sec. delay on the wifi and also from internet, outside the wifi. BUT: Philips Hue devices respond immediately when being controlled from the Philips Hue app both from the internet and from inside the wifi. This excludes a number of possible errors with radio channel congestion and routing, I guess.
3. Restarting the Philips Hue bridge has no effect, neither has reconnecting Philips Hue to Google Home. This would suggest that the problem does not originate in the bridge. 
4. I have tested a number of physical setups of the Philips Hue bridge without any change. I have connected it to a Google wifi ethernet port and to the Nest Wifi ethernet port. It makes no difference. 
5. A very surprising discovery (or maybe not so surprising): When changing DNS setup and confirming it in Google Home, the Philips Hue devices will in many cases start to respond quickly. I guess the network is restarted when changing DNS? According to my “research” the specific DNS setting chosen does not matter much in this case.  

Some more details which I doubt have any significance, due to point 2 above: My home network consist of a Nest Wifi router, a Nest wifi point, and three Google wifi pucks connected by switches and cable to the router.

I greatly appreciate Google Home, but would really like the control of Philips Hue devices to be as smooth and immediate as expected in a modern network! 

[Croinkei]

To whoever has problems with this check out this Reddit solution, it fixed it for me:

"I was able to fix this by pairing as matter.

In hue app go to -Smart home- other apps - get the pairing code and copy it.

In Home app go to Devices- Add - new device. 

My hue hub was visible there, just pasted the pairing code and all was good. Well I had to place the lights into correct rooms."

I tried everything else I could imagine before finding this solution.

Hope it helps!

[Sirak97]

Hello!

I found the code in the HUE app, but when I go to the Home app > Devices > Add Device. I am told to choose in a list. I tried to click the search bar and paste the code but nothing happens. What did i miss?

Thanks for the help!

[beartunes]

it's also faster if you use alexa. i use both google and alexa devices, for when google is 'down', and alexa is working plus my old echo plus 2, has a 'hub' in it and it def responds quicker to turning hue stuff on or off.   this issue re-appeared in 2024 sometime in may or june and has been bugging me since. restart of hue router, restart of modem and wifi router and reconnecting hue 'skill' to google, has no effect.