openhab-addons: HueEmulation binding not working with Docker

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.

About this issue

Original URL
State: closed
Created 8 years ago
Comments: 17 (6 by maintainers)

Commits related to this issue

Added nullness annotations to 'ThingActions' and 'ThingHandlerService' (#1317) * Minor code improvements; Added nullness annotations to ThingActions and ThingHandlerService * Revert renaming of 'thi... — committed to Flole998/openhab-addons by cweitkamp 4 years ago

Most upvoted comments

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.

jrbloemhof on Mar 28, 2017