No, that shouldn’t matter. It should just find it. I’ve done some digging and other people have said upnp doesn’t matter either. I have a unifi secure gateway which is essentially the same as an edgerouter. Do you have any special settings in set your router? Anything that you did that is unique in comparison to a normal setup?
I have plenty of reserved IP addresses on the DHCP and an IPSec VPN tunnel configured. Other than that it’s all pretty default. This has to be something else. Is there any detailed documentation on how to set this up? Or is it just the component page?
In this video the guy says that I need to have the Philips Hue skill enabled in the alexa app. I tried that but the skill can’t be enabled because it cannot find any hue devices on my network. Which doesn’t make sence because HA is running the emulated_hue which should broadcast as a bridge gen1.
Also, I don’t know if this was required but I had no alexa: entry in my configuration.yaml so I added it, but still no luck.
There’s so much miss information around here. And that is 100% incorrect (Unless you have 2 hue bridges), then one would be done through normal discovery and the second would be done through the phillips hue skill.
That should be all you need. It’s all I have. You could turn on debug in logging and view the HA logs during discovery. Not sure if that will help. Unfortunately, this seems like you’d need to debug it on alexa’s side.
So this leads me to believe that your router is doing something on your network that is blocking the communication.
And just to clarify, this communication between emulated hue and alexa is 100% local. It does not go to the cloud and back.
I could see my echo was on the right wifi network so I ran my echo (gen 1) through the setup process again to reconnect it to the same wifi network and it finally worked
If he means that he simply re-run the setup wizard for alexa, I’ve already done that. Reset to factory defaults, de-register from the alexa app, and re-register again. Nothing.
What doesn’t make sense to me is, why doesn’t the Hue skill in Alexa, find the emulated_hue as a gen1 device? Even if this step is not needed, the Hue skill should still detect the emulated_hue presence on my network.
Not sure. It should find it but it’s not. I’d be willing to bet that the actual hue hardware would have the same issue on your network. If i was in your shoes, I would be trying to debug the alexa / network side of this issue. Your emulated hue setup is good.
So I went through the whole process of setting up haaska, with a successful test at the end of the guide. Alexa still can’t find any devices
The thing is, I am running a lot of services on this network and I have never had any problems whatsoever. I don’t know what’s so special about the alexa setup.
In that other thread petro mentioned NOT explicitly searching for hue and I’ve also seen others mention using voice control on the specific echo that is gen 1 or gen 2 (I believe I did the former however I was so excited to get it working again that I promptly forgot what did the trick ). Anyway here’s the discovery procedure from the other thread:
And tonight it got hosed again but just mostly. I can do “Alexa, turn off/on all the lights and it works.” 3 of my 10 lights work and there appears to be no rhyme or reason for why some work and not others. My WAF is like the Hindenburg. Resetting the echo did the trick again and lost all the reminders on that device again
Are you getting any errors relating to emulated_hue when starting HA? If this is exactly how you have your config in the yaml file, then your spacing is wrong. You need two spaces like;
emulated_hue:
host_ip: 192.168.1.35
off_maps_to_on_domains:
- script
- scene
Eh, that shouldn’t matter because the -'s represent a list. The indentation after the - is considered an indentation in this regard. People just like the look of the double space better.
Couldn’t be more basic. No errors in the log
2019-06-27 22:52:45 INFO (SyncWorker_16) [homeassistant.loader] Loaded hue from homeassistant.components.hue
again