Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

HueEmulation binding not working with Docker

See original GitHub issue

Seems that the way this binding was thought, is not going to work with Docker. I’m getting the following log messages:

23:13:16.069 [TRACE] [tion.internal.HueEmulationUpnpServer] - Got SSDP Discovery packet from 172.17.0.3:50883
23:13:16.070 [TRACE] [tion.internal.HueEmulationUpnpServer] - Sending to 172.17.0.3 : HTTP/1.1 200 OK
CACHE-CONTROL: max-age=100
EXT:
LOCATION: http://172.17.0.3:8080/api/discovery.xml
SERVER: FreeRTOS/7.4.2 UPnP/1.0 IpBridge/1.10.0
ST: urn:schemas-upnp-org:device:basic:1
USN: uuid:601df881-c2ed-476e-a741-1fa0313d9b39::urn:Belkin:device:**

Even after setting the property discoveryIp, the binding is assigning an internal docker ip which is obviously not exposed and thus it will never going to be reach out by the Amazon Echo.

Issue Analytics

State:
Created 7 years ago
Comments:17 (6 by maintainers)

Top GitHub Comments

1reaction

jrbloemhofcommented, Mar 28, 2017

I didn’t have a chance to really look at this in-depth, but I would assume it’s the same issue as was recently solved for Sonos Controller (see https://github.com/SoCo/SoCo/pull/444 ) - if the Hue Emulator is auto-detecting it’s own IP address, it will be sending out the Docker container’s local IP address rather than the host’s ethernet IP, so it gets broadcast messages from devices, but then points the device to connect to a wrong / unreachable IP.

0reactions

bradleyscottcommented, Feb 16, 2017

I’m also finding the same problem. I was previously running Home Assistant in docker and had some issues but resolved them when I found Hue was looking to find the emulator on port 80. Has anyone resolved this?