Echo Dot not finding Home Assistant hue_bridge (Windows 10)

So I am trying to use HA to be able to use my Echo Dot to control my Yamaha receiver. I have successfully installed Home Assistant and got it up and running with hue_bridge. I can hit the http://192.168.1.123/description.xml and http://192.168.1.123/api/pi/lights pages and it brings up the information pasted below. Anytime I try to get Alexa to find devices on my network it can’t find anything. Also just to verify, I don’t have to install the Philips Hue “skill” on the dot in order for it to find the hue bridge correct? I am just getting into home automation so this is the first thing I’ve tried to do - any advice is greatly appreciated.

Configuration:

emulated_hue:
    type: alexa
    host_ip: 192.168.1.123
    listen_port: 80
    expose_by_default: true

Logs:

2017-07-16 12:03:01 WARNING (SyncWorker_1) [homeassistant.components.emulated_hue] Alexa type is deprecated and will be removed in afuture version
2017-07-16 12:03:02 ERROR (MainThread) [homeassistant.core] Error doing job: Exception in callback _ProactorReadPipeTransport._loop_reading(<_OverlappedF…op_reading()]>)
Traceback (most recent call last):
File “C:\Users\XXXXXXXXX\AppData\Local\Programs\Python\Python36\lib\asyncio\events.py”, line 127, in _run
self._callback(*self._args)
File “C:\Users\XXXXXXXXX\AppData\Local\Programs\Python\Python36\lib\asyncio\proactor_events.py”, line 190, in _loop_reading
data = fut.result() # deliver data later in “finally” clause
File “C:\Users\XXXXXXXXX\AppData\Local\Programs\Python\Python36\lib\asyncio\futures.py”, line 238, in result
raise InvalidStateError(‘Result is not ready.’)
asyncio.base_futures.InvalidStateError: Result is not ready.
2017-07-16 12:03:18 ERROR (MainThread) [homeassistant.core] Error doing job: Exception in callback _ProactorReadPipeTransport._loop_reading(<_OverlappedF…ed result=b’'>)
Traceback (most recent call last):
File “C:\Users\XXXXXXXXX\AppData\Local\Programs\Python\Python36\lib\asyncio\events.py”, line 127, in _run
self._callback(*self._args)
File “C:\Users\XXXXXXXXX\AppData\Local\Programs\Python\Python36\lib\asyncio\proactor_events.py”, line 188, in _loop_reading
self._closing)
AssertionError
2017-07-16 12:03:25 ERROR (MainThread) [homeassistant.core] Error doing job: Exception in callback _ProactorBasePipeTransport._call_connection_lost(None)
Traceback (most recent call last):
File “C:\Users\XXXXXXXXX\AppData\Local\Programs\Python\Python36\lib\asyncio\events.py”, line 127, in _run
self._callback(*self._args)
File “C:\Users\XXXXXXXXX\AppData\Local\Programs\Python\Python36\lib\asyncio\proactor_events.py”, line 136, in _call_connection_lost
self._sock.shutdown(socket.SHUT_RDWR)
OSError: [WinError 10038] An operation was attempted on something that is not a socket

/api/pi/lights

{“media_player.rxv675_a6a830”: {“modelid”: “HASS123”, “name”: “RX-V675 A6A830”, “state”: {“bri”: 215, “on”: true, “reachable”: true}, “swversion”: “123”, “type”: “Dimmable light”, “uniqueid”: “media_player.rxv675_a6a830”}, “media_player.rxv675_a6a830_zone_2”: {“modelid”: “HASS123”, “name”: “RX-V675 A6A830 Zone 2”, “state”: {“bri”: 0, “on”: false, “reachable”: true}, “swversion”: “123”, “type”: “Dimmable light”, “uniqueid”: “media_player.rxv675_a6a830_zone_2”}}

/description.xml

<root xmlns="urn:schemas-upnp-org:device-1-0">
<specVersion>
<major>1</major>
<minor>0</minor>
</specVersion>
<URLBase>http://192.168.1.123:80/</URLBase>
<device>
<deviceType>urn:schemas-upnp-org:device:Basic:1</deviceType>
<friendlyName>HASS Bridge (192.168.1.123)</friendlyName>
<manufacturer>Royal Philips Electronics</manufacturer>
<manufacturerURL>http://www.philips.com</manufacturerURL>
<modelDescription>Philips hue Personal Wireless Lighting</modelDescription>
<modelName>Philips hue bridge 2015</modelName>
<modelNumber>BSB002</modelNumber>
<modelURL>http://www.meethue.com</modelURL>
<serialNumber>1234</serialNumber>
<UDN>uuid:2f402f80-da50-11e1-9b23-001788255acc</UDN>
</device>
</root>

You should switch the Hue type to google_home to get rid of the first warning. There are a lot of errors in your log re asyncio. That might be the cause of your Alexa issues. How is your network setup? Is Alexa on the same subnet as HASS?

No need to add skills. Alexa should discover the hue entities automatically. Log into your Alexa app to see what/if anything was discovered.

So your saying that the type variable doesn’t matter with the hue bridge when trying to find it with Alexa vs google home?

Yes I saw the errors in the log I was hoping someone might have run into a similar issue with those errors and has found a work around - also I am not sure if those errors are related to the issue that I am having or if they are just unrelated issues with home assistant running on windows 10 (see https://github.com/home-assistant/home-assistant/issues/7022 )

Yes Alexa is running on the same subnet, at the moment there is only one subnet running on the house. The windows machine I am running hass on is wired into the router, Alexa via wifi obviously.

Yes I have been using the alexa app to run discovery many time, and nothing has come up.

Thanks.

1 Like

Try this…

 emulated_hue:
    type: google_home
    listen_port: 8300
    expose_by_default: true

Uses the new version but avoids the exposing port 80 issues. Just tried it on mine and all good, Echo and Harmony Hub find everything.