Component/platform:
Emulated Hue
Description of problem:
Google assistant tries to connect to HUE services and can't find any hue bridge.
Last comment is mine, that's the problem but that's not the solution.
Google assistant was released to millions of android devices and using google assistant on a phone it's mandatory to connect to HUE Cloud and HUE Cloud doesn't let you connect to it. Also, the latest Google Home apps also do the same.
This component doesn't work anymore using Google Assistant as per latest google versions.
Maybe update the docs as it only works for Alexa now.
Still seems to work for me but I do have a Hue bridge on my network so I'm wondering if that allows you to get around this new requirement.
As reported on the post that @Danielhiversen mentioned, if you unlink your account and try to add it back you can't do it anymore as it tries to go through the hue cloud.
I can confirm the same functionality change in the latest home control setup for google assistant. My wife's phone just got google assistant and I cannot link her account to emulated hue. Fortunately, since google home/assistant and emulated hue are already linked on my account, they still work.
Any chance for the emulated bridge to be seen as a "real bridge" from Philips side? So that we can register the emulated bridge as a "real" bridge in Hue app/account?
Okay, so if I understand correctly, the only way to link Home Assistant to Google Home is either 1) have a physical Hue Bridge or 2) have a physical Google Home device - not just the Google Home app and/or Google Assistant - and use an old version of the Google Home software.
Given this, could https://home-assistant.io/components/emulated_hue/ be updated to make it clear that the Google Home example will only work in one of those scenarios? At the moment it's actively misleading.
I've just wasted an hour trying to do something which I now realise is impossible, because that page told me it should work, and it would be good if other people didn't have to.
There is an " edit this page on GitHub" button
On Sat, Jul 1, 2017, 4:11 AM Aneurin notifications@github.com wrote:
Okay, so if I understand correctly, the only way to link Home Assistant to
Google Home is either 1) have a physical Hue Bridge or 2) have a physical
Google Home device - not just the Google Home app and/or Google Assistant -
and use an old version of the Google Home software.Given this, could https://home-assistant.io/components/emulated_hue/ be
updated to make it clear that the Google Home example will only work in one
of those scenarios? At the moment it's actively misleading.I've just wasted an hour trying to do something which I now realise is
impossible, because that page told me it should work, and it would be good
if other people didn't have to.—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/home-assistant/home-assistant/issues/6454#issuecomment-312423449,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAWorAVs6ioFcKw3ZFr_mzWGWXrltGmcks5sJhtSgaJpZM4MUGK1
.
Well sure, but I don't really know what I should edit it to; I certainly don't have a high degree of confidence. I feel it would be bad form to edit somebody else's project wiki without a solid understanding of the topic.
Shall I just go ahead and take a stab anyway?
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment :+1:
From what I read the past hour it seems that this issue is proudly presented by Philips. :disappointed:
Each google account you want to talk to the emulated hue must be the primary account on at least one google home. We have two google homes in our house, I'm primary on one, my wife on the other. We are each added as a secondary account to the other google home so multi-user works and both accounts (including from phone's google assistant) can work with the emulated hue. We do not have a physical philips hue (light or hub).
I have a been running the HABridge with Alexa and have had no issues. I have been running in circles to get around the HUE issue with Google Assistant. I even purchased a Philips Hue Bridge and threw it on my network to see if that could find the emulated HUE bridge or devices. No luck. The only thing I have not tired is going back to an old version of Google Assistant and seeing if that can find the devices, add them to my account, and keep them after the upgrade. Anyone have any such success?
Hi DrJJC,
You won't have any lucky doing any of those options. Take a look at the Google Assistant component, HA now supports Google Assistant natively and with that comes much better integration.
Most helpful comment
Okay, so if I understand correctly, the only way to link Home Assistant to Google Home is either 1) have a physical Hue Bridge or 2) have a physical Google Home device - not just the Google Home app and/or Google Assistant - and use an old version of the Google Home software.
Given this, could https://home-assistant.io/components/emulated_hue/ be updated to make it clear that the Google Home example will only work in one of those scenarios? At the moment it's actively misleading.
I've just wasted an hour trying to do something which I now realise is impossible, because that page told me it should work, and it would be good if other people didn't have to.