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.

Docker on MacOS and ha-bridge

See original GitHub issue

I’m using the dockerized version of ha-bridge and am having issues with Alexa discovering the bridge. I had all of this working prior to trying docker.

Originally I had ha-bridge running on 80/tcp, but in docker, using 80 as a privileged port and trying to get that going proved to be an issue. So went back to using 8080, forwarded 8080/tcp 1900/udp and 50000/udp to the container and still having issues. The web interface works fine, just can’t get Alexa to discover it.

`2016-10-28 20:03:14,298 [main] INFO com.bwssystems.HABridge.HABridge - HA Bridge (v3.2.0) starting… 2016-10-28 20:03:14,347 [main] INFO com.bwssystems.HABridge.BridgeSettings - reading from config file: data/habridge.config 2016-10-28 20:03:14,575 [main] WARN com.bwssystems.HABridge.BridgeSettings - The upnp config address, 192.168.15.50, does not match any known IP’s on this host. 2016-10-28 20:03:14,576 [main] INFO com.bwssystems.HABridge.HABridge - HA Bridge (v3.2.0) initializing… 2016-10-28 20:03:14,629 [main] INFO com.bwssystems.HABridge.SystemControl - System control service started… 2016-10-28 20:03:15.064:INFO::Thread-0: Logging initialized @1891ms 2016-10-28 20:03:15,400 [Thread-0] INFO spark.webserver.JettySparkServer - == Spark has ignited … 2016-10-28 20:03:15,416 [Thread-0] INFO spark.webserver.JettySparkServer - >> Listening on 0.0.0.0:8080 2016-10-28 20:03:15.428:INFO:oejs.Server:Thread-0: jetty-9.3.z-SNAPSHOT 2016-10-28 20:03:15.610:INFO:oejs.ServerConnector:Thread-0: Started ServerConnector@5143fdc1{HTTP/1.1,[http/1.1]}{0.0.0.0:8080} 2016-10-28 20:03:15.612:INFO:oejs.Server:Thread-0: Started @2443ms 2016-10-28 20:03:15,955 [main] INFO com.bwssystems.harmony.HarmonyServer - setup initiated … 2016-10-28 20:03:18,934 [main] INFO com.bwssystems.harmony.HarmonyServer - activity changed: [-1] PowerOff 2016-10-28 20:03:18,970 [main] INFO com.bwssystems.HABridge.devicemanagmeent.DeviceResource - HABridge device management service started… 2016-10-28 20:03:19,073 [main] INFO com.bwssystems.HABridge.upnp.UpnpSettingsResource - Hue description service started… 2016-10-28 20:03:19,085 [main] INFO com.bwssystems.util.UDPDatagramSender - Initializing UDP response Seocket… 2016-10-28 20:03:19,096 [main] INFO com.bwssystems.util.UDPDatagramSender - UDP response Seocket initialized to: 50000 2016-10-28 20:03:19,380 [main] INFO com.bwssystems.HABridge.hue.HueMulator - Hue emulator service started… 2016-10-28 20:03:19,415 [main] INFO com.bwssystems.HABridge.upnp.UpnpListener - UPNP Discovery Listener starting… 2016-10-28 20:03:19,416 [main] INFO com.bwssystems.HABridge.upnp.UpnpListener - Traceupnp: eth0 … has addr /fe80:0:0:0:42:acff:fe11:2%eth0 2016-10-28 20:03:19,417 [main] INFO com.bwssystems.HABridge.upnp.UpnpListener - Traceupnp: eth0 … has addr /172.17.0.2 2016-10-28 20:03:19,417 [main] INFO com.bwssystems.HABridge.upnp.UpnpListener - Traceupnp: Adding eth0 to our interface set 2016-10-28 20:03:19,417 [main] INFO com.bwssystems.HABridge.upnp.UpnpListener - Traceupnp: lo … has addr /0:0:0:0:0:0:0:1%lo 2016-10-28 20:03:19,417 [main] INFO com.bwssystems.HABridge.upnp.UpnpListener - Traceupnp: lo … has addr /127.0.0.1 2016-10-28 20:03:19,418 [main] INFO com.bwssystems.HABridge.upnp.UpnpListener - Traceupnp: Adding lo to our interface set 2016-10-28 20:03:19,418 [main] INFO com.bwssystems.HABridge.upnp.UpnpListener - UPNP Discovery Listener running and ready… 2016-10-28 20:03:20,814 [main] INFO com.bwssystems.HABridge.upnp.UpnpListener - Traceupnp: isSSDPDiscovery found message to be an M-SEARCH message. 2016-10-28 20:03:20,815 [main] INFO com.bwssystems.HABridge.upnp.UpnpListener - Traceupnp: isSSDPDiscovery found message to be valid under strict rules - strict: true 2016-10-28 20:03:20,815 [main] INFO com.bwssystems.HABridge.upnp.UpnpListener - Traceupnp: SSDP packet from 172.17.0.1:46067, body: M-SEARCH * HTTP/1.1 MX: 1 ST: upnp:rootdevice MAN: “ssdp:discover” User-Agent: UPnP/1.0 DLNADOC/1.50 Platinum/1.0.5.13 Host: 239.255.255.250:1900 Connection: close

2016-10-28 20:03:20,818 [main] INFO com.bwssystems.HABridge.upnp.UpnpListener - Traceupnp: sendUpnpResponse discovery responseTemplate1 is <<<HTTP/1.1 200 OK HOST: 239.255.255.250:1900 CACHE-CONTROL: max-age=100 EXT: LOCATION: http://192.168.15.50:8080/description.xml SERVER: Linux/3.14.0 UPnP/1.0 IpBridge/1.15.0 hue-bridgeid: 000088FFFE00BBEE ST: upnp:rootdevice USN: uuid:2f402f80-da50-11e1-9b23-00008800bbee::upnp:rootdevice

2016-10-28 20:03:20,821 [main] INFO com.bwssystems.HABridge.upnp.UpnpListener - Traceupnp: sendUpnpResponse discovery responseTemplate2 is <<<HTTP/1.1 200 OK HOST: 239.255.255.250:1900 CACHE-CONTROL: max-age=100 EXT: LOCATION: http://192.168.15.50:8080/description.xml SERVER: Linux/3.14.0 UPnP/1.0 IpBridge/1.15.0 hue-bridgeid: 000088FFFE00BBEE ST: uuid:2f402f80-da50-11e1-9b23-00008800bbee USN: uuid:2f402f80-da50-11e1-9b23-00008800bbee

2016-10-28 20:03:20,822 [main] INFO com.bwssystems.HABridge.upnp.UpnpListener - Traceupnp: sendUpnpResponse discovery responseTemplate3 is <<<HTTP/1.1 200 OK HOST: 239.255.255.250:1900 CACHE-CONTROL: max-age=100 EXT: LOCATION: http://192.168.15.50:8080/description.xml SERVER: Linux/3.14.0 UPnP/1.0 IpBridge/1.15.0 hue-bridgeid: 000088FFFE00BBEE ST: urn:schemas-upnp-org:device:basic:1 USN: uuid:2f402f80-da50-11e1-9b23-00008800bbee

2016-10-28 20:03:20,823 [main] INFO com.bwssystems.HABridge.upnp.UpnpListener - Traceupnp: isSSDPDiscovery found message to be an M-SEARCH message. 2016-10-28 20:03:20,823 [main] INFO com.bwssystems.HABridge.upnp.UpnpListener - Traceupnp: isSSDPDiscovery found message to be valid under strict rules - strict: true 2016-10-28 20:03:20,824 [main] INFO com.bwssystems.HABridge.upnp.UpnpListener - Traceupnp: SSDP packet from 172.17.0.1:46067, body: M-SEARCH * HTTP/1.1 MX: 1 ST: upnp:rootdevice MAN: “ssdp:discover” User-Agent: UPnP/1.0 DLNADOC/1.50 Platinum/1.0.5.13 Host: 239.255.255.250:1900 Connection: close

2016-10-28 20:03:20,825 [main] INFO com.bwssystems.HABridge.upnp.UpnpListener - Traceupnp: sendUpnpResponse discovery responseTemplate1 is <<<HTTP/1.1 200 OK HOST: 239.255.255.250:1900 CACHE-CONTROL: max-age=100 EXT: LOCATION: http://192.168.15.50:8080/description.xml SERVER: Linux/3.14.0 UPnP/1.0 IpBridge/1.15.0 hue-bridgeid: 000088FFFE00BBEE ST: upnp:rootdevice USN: uuid:2f402f80-da50-11e1-9b23-00008800bbee::upnp:rootdevice

2016-10-28 20:03:20,827 [main] INFO com.bwssystems.HABridge.upnp.UpnpListener - Traceupnp: sendUpnpResponse discovery responseTemplate2 is <<<HTTP/1.1 200 OK HOST: 239.255.255.250:1900 CACHE-CONTROL: max-age=100 EXT: LOCATION: http://192.168.15.50:8080/description.xml SERVER: Linux/3.14.0 UPnP/1.0 IpBridge/1.15.0 hue-bridgeid: 000088FFFE00BBEE ST: uuid:2f402f80-da50-11e1-9b23-00008800bbee USN: uuid:2f402f80-da50-11e1-9b23-00008800bbee

2016-10-28 20:03:20,830 [main] INFO com.bwssystems.HABridge.upnp.UpnpListener - Traceupnp: sendUpnpResponse discovery responseTemplate3 is <<<HTTP/1.1 200 OK HOST: 239.255.255.250:1900 CACHE-CONTROL: max-age=100 EXT: LOCATION: http://192.168.15.50:8080/description.xml SERVER: Linux/3.14.0 UPnP/1.0 IpBridge/1.15.0 hue-bridgeid: 000088FFFE00BBEE ST: urn:schemas-upnp-org:device:basic:1 USN: uuid:2f402f80-da50-11e1-9b23-00008800bbee

Issue Analytics

State:
Created 7 years ago
Comments:9 (2 by maintainers)

Top GitHub Comments

1reaction

markstubbcommented, Oct 29, 2016

So, in other words, it won’t work on Docker for Mac then since the docker implementation runs on a hypervisor and can’t use host mode.

0reactions

aptalcacommented, Nov 2, 2016

hmm, this may perhaps be the issue: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1327442

It says that when multicast udp is forwarded, it changes the source address to docker’s internal IP.

I’ll look into it further. At least this gives me a starting point. Thanks.

You can close this issue.

Top Results From Across the Web

linuxserver/habridge - Docker Image

The Bridge handles basic commands such as "On", "Off" and "brightness" commands of the hue protocol. This bridge can control most devices that...

HA Bridge - GitHub

Home automation bridge that emulates a Philips Hue light system and can control other systems such as a Vera, Harmony Hub, Nest, MiLight...

MacOS Docker - YouTube

Don't have a Mac and need MacOS ? No problem, run it in a docker container.Website Guide: https://christitus.com/ docker - macos /Support My ......

linuxserver/habridge

Habridge emulates Philips Hue API to other home automation gateways such as an Amazon ... We utilise the docker manifest for multi-platform awareness....

Docker Macos - Chris Titus Tech

Don't have a Mac and need MacOS? No problem, run it in a docker container. Credit goes to this twitter user:.