"Couldn't find Hue Bridge", Emulated Hue Help w/ Google Home Device

Not sure what else I can be doing wrong…

I have emulator_hue working so that I can browse both:
http://192.168.1.124/description.xml
and
http://192.168.1.124/api/pi/lights

  1. and tried with with and without specifying ‘exposed_domains’ setting to ‘light’ and then ‘group’

  2. Downloaded and installed Google Home APK 1.19.26 on my android phone.

I still get the same “Couldn’t Find Hue Bridge” page only this time it does indeed go to ‘https://hue-adapter.appspot.com/client/

So thats it. I’m not sure what else to try to get this working…I also can’t seem to get the same working with the Echo either.

UPDATE –
I eventually got it working with the Google Home by simply using the AiO RPi version (+Old version of Home android app), rather then the dockerized one.
Likely to do with all the networking hoops. I will eventually want to get it working with Docker as well though.

1 Like

I have successfully connected Google Home and Alexa on my Hass.io running on a RPI3, I was only able to pair it with Google Home using apk version 1.19.26 and after that I updated the apk and everything keeps working as expected, Google Home keeps updating all my devices as I make changes on Hass.

I had some trouble again connecting Google Home and Alexa at the same time this is how it worked for me in the end on my config:

emulated_hue:
  type: google_home
  host_ip: xxx.xxx.x.xxx
  listen_port: 80

emulated_hue 1:
  type: alexa

Thought I would share my experience as an iPhone user with no Android devices in the house. I got my Google Home connected with emulated_hue after some effort.

  • Tried RemixOS in a Virtual Box on my Macbook Pro. The mouse was too slow/unresponsive, so I gave up out of frustration.
  • Resized a partition on my Windows machine and installed RemixOS.
  • Downloaded 1.19.26 APK, but it still didn’t work (I didn’t have the “Home Control” and other extended options in the hamburger menu of Google Home)
  • Downgraded the Google app to an APK version from a similar time frame (~ Nov 2016). It said the install failed, but it seemed to help somehow.
  • Somehow ended up in what seemed like Google Play settings where I had to signin to my Google account again.
  • Finally got the Home Control and other options in Google Home.

At some point, I had the options in Google Home but clicking them had no effect (it would do nothing and remain with the menu open and a dark screen on the right side). I think that is when I decided to try downgrading the Google app, I’ve no idea if it actually helped though, since it said the install failed.

I will also add, as an Australian Google Home user, I had huge frustrations trying to get anything to work in the iPhone Google Home app until I switched my iPhone to the United States region. Then all the options showed up straight away.

Just want to add to the thread. Received a google home the other day. Changed emulated_hue to port 80. Alexa and google home can use the emulated_hue just fine. Did not specific type. Used the latest google home app to get it paired to the bridge.

Incredible! Nice work. My Raspberry Pi is a useless brick. Since then I bought a device from www.iotathome.com which promised to connect Siri, Alexa, and Google to my Broadlink devices, but it also failed. Then I bought a Android tablet just to run as a bridge with Tasker and that only worked for Alexa. Then Broadlink released a new app to connect Alexa, but it doesn’t work with Siri or Google Home device. Terrible mess. I have so many devices now and still cant use voice control to reliably turn on/off Broadlink SP3 devices and RM Pro devices from voice.

Come to my house and help me!

@HendrixHunter Try this config on your Pi:

emulated_hue:
  type: google_home
  listen_port: 8300
  advertise_port: 80

Then execute this from SSH:

iptables -t nat -A PREROUTING -p tcp -m tcp --dport 80 -j REDIRECT --to-ports 8300

I use this setup since Google Home only likes port 80, but port 80 has restrictions I can’t be bothered to bypass so I’ve remapped anything coming to port 80 to hit port 8300. This setup works flawlessly for me, give it a shot.

If you get an error that iptables doesn’t exist, just apt-get install iptables it.

Hope this helps.

4 Likes

Also the only way I could get it to work that I didn’t see mentioned here but find on a GitHub discussion were the following steps

  • factory reset Google Home by pressing mic button for 15 secs
  • launch 1.20.x Home app on android and reset up Google Home
  • re-add emulated_hue via Hue connector in 1.20.x Home App
  • Home should detect huebridge at this point. If not, keep trying to add
    via hue connector. If not, try rebooting home and restart HA and clearing
    data of Home App in android device.
  • Test a hue device. If doesnt work, try rebooting HA and Home and repeat steps

Can anyone post the correct apk? I’m using an Android S7 Nougat device and don’t have a google home device

I have the exact same issue, still getting “Couldn’t Find Hue Bridge”

What comes up when you hit http://:80/api/pi/lights ?

1 Like

The link works…

I manged to fix it somehow, I run HA bridge and then the hue registration worked in the goggle home app.
Afterwords I disabled the HA bridge and re-enabled the emulated hue bridge, and it worked becuase the google home app already had the hue registered

Just to save your time, no real Google Home, no worky!

Nothing to work at all? Ive got google assistant on my phone and on hass.io, can i get it paired up?

IFTTT, no need for emulated_hue

Thanks, but don’t I have to go in and make every single voice command?

I’m actually thinking about getting Phillips hue, can I get emulated hue working with Google assistant if I have a physical hue bridge?

Which bit of ‘no’ is confusing you?

I read somewhere that if you have a physical hue bridge, then emulated works? Or is it only if you have a physical Google home?

You haven’t read that anywhere, you may have read of others who thought it might help but the two are completely unrelated. Emulated_hue just ‘looks like’ Hue connected light bulbs to other devices, nothing more than that.

ahh right thanks, looks like i’ll have to wait for google to release their mini google home that competes with the echo dot, and then i can get one of them. then using an older apk of the home app i should be able to connect it?

In theory, yes :slight_smile: