Since today, the openHAB 2.2.0-SNAPSHOT distro is able to integrate with Google Home. This is done the same way as for Amazon Echo (without using the skill), i.e. by the Hue Emulation add-on, which makes openHAB expose arbitrary items as lights by mimicking a Philips hue bridge. Kudos to @digitaldan who made the necessary changes to that add-on, so that Google Home correctly recognises openHAB as a Hue bridge.
There is one caveat, though: Google Home does not listen to the port it is told, but always expects the hue bridge to be available on port 80 - this means that you have to configure openHAB to use port 80 instead of 8080 for the webserver (check the docs on how to do that) and for using port 80, you need to make sure to run it as root.
If you want to see it in action, check out this video on YouTube (sorry, it is one of the rare ones that I did in German).
P.S.: There is also work underway to have an official openHAB Action for Google Home, but this might still take a while - if you are interested, follow the linked topic for updates.
Google Home - Actions (API) now available!
Glad to hear that @Kai! When do you expect to release 2.2.0 to have the feature in production?
What do you mean with “run as root”?
Hue-Emulation already works with alexa.
I’ve installed openhabian and its nginx-proxy, so OH is reachable at port 80.
Is it a difference to use Assistant vs. Home?
And did I miss the “run as root”-thing?
When do you expect to release 2.2.0 to have the feature in production?
Sorry, no date yet. I hope we will see some progress on the automatic build pipeline, which will reduce the effort of building new releases tremendously, so that we can increase the frequency.
That’s a good point - for openhabian with NGINX as a reverse proxy on port 80, no change should be needed (as long as you do not configure any authentication, which is actually one of the main purposes of NGINX here ).
So does it actually work or does it run in a timeout?
There might be - you are redirected to account.meethue.com, which looks as if this tries to do a Cloud-Integration. In my video you might see that the redirect goes to hue-adapter.appspot.com, which is not hosted by Philips, but probably just holds the code to do local discovery through UPnP.
I’m running in a timeout.
It starts at hue-adapter.appspot.com, too - but from there I’m redirected to the account.meethue-Site.
Which Phone / Android-Version do you use?
I’m having the same issue. I wonder if it’s a regional issue (I’m in the US).
@mashborn I may have found a workaround that might work for you. I tried installing the Hue app to see if it would connect the emulation to the meevue account. Unfortunately I’m running Android O and the app sees the bridge and then crashes.
I’m running Android O, too.
While trying to connect to to the hue-emulation I plug off my “real” hue-bridge.
Do you think, it could be possible to connect the emulated bridge to the cloudservice?
I’m not sure, was just experimenting to see if that would work. If I get a chance I’ll reset it back up on OpenHab and try to run the Hue app on my tablet which has an older version of Android.
Update: Unfortunately didn’t work with Hue App on an older Android. App crashes there as well. I do have an old 5x on N, that I’ll try with once I get it reauthed on my account just to see if it’s an O issue since we have that in common.
But what if you have several lamps in same place?
As I gather, hue emulation looks at the label to determine what items are called.
Then I got to Google Home application and add the items (now devices) in respective rooms for instance Kitchen.
What do you guys think is best practice to name the items?
Also, i am having trouble to use a dimmer, to actually set it at for instance 40%.
What would the command be? Anyone tested it?
I have the same problem. Dimming is not working. Which commands are supported by Google Home.
I do have an old 5x on N, that I’ll try with once I get it reauthed on my account just to see if it’s an O issue since we have that in common.
So I got my old Nexus 5X running with Android N and Google Assistant. I can confirm it took me to the same meethue based signup and couldn’t find my Hue. So I’m back to wondering if it’s a regional issue as to which authorization site you end up at and if you can do it locally or not.
I’m in the US and have no problem running discovery so long as I have forwarded TCP port 80 to port 8080 on the primary (only physical) network interface of my RPI3.
Forgive me if those are painfully obvious, but I have been known to overlook the painfully obvious in the past.
I can also confirm that Google Home does not “know” how to set dimmer levels, it knows only how to handle OFF/ON.
Thanks @scottk I have all those setup the same. Do you also end up at the meethue site for registering the hub?
When I had GH run discovery, it did not connect to the meethue site, rather it connected to hue-adapter.appspot.com, which I guess is available via mDNS.
I wonder what’s going on the backend that some of us are getting sent to the hue-adapter.appspot.com and then redirected to meethue while others stay on the appspot.com. This seems to be the common thread between who can connect and who can’t.
Thinking it through a bit more, are you connecting a Home device or just Google Assistant (I’m doing the later)?
I am using the Google Home app, version 1.24.37.4, on my Note 4 to run discovery. I have one chromecast and one GH that are registered to my Google identity.
I think that is my mistake, I don’t have a physical Google Home device, just trying to connect Google Assistant to it.