I'm trying out Google Home. It seems to support Hue lights on the same network, so I thought it should work like Echo or Harmony remote (Have 3 Echos and 1 Harmony, all works with the bridge).
Home doesn't detect the bridge. Ran a tcpdump on the VM hosting ha-bridge and I see multicast packets (SSDP and MDNS) from the phone running the 'Google Home' control app, but don't see any packets from the Google Home device. Any suggestions?
emiliosic
All 36 comments
I'm wondering if Google Home is trying to use the Hue internet api instead of the local upnp find. If that is the case, this will not work of course.
bwssytems
on 4 Nov 2016
It has the option to use either it is waiting for a button press i believe how can we simulate this action ?
robertw
on 4 Nov 2016
I'm also stuck at the waiting for the button press.
Go3Team
on 4 Nov 2016
The ha-bridge is in button always pushed mode.
bwssytems
on 4 Nov 2016
Ok so that does not solve the problem how can we help to figure this out .......
robertw
on 4 Nov 2016
Please turn on the trace upnp flag in the settings and post your log.
Thanks
bwssytems
on 4 Nov 2016
2016-11-04 16:17:21,285 [main] INFO com.bwssystems.HABridge.HABridge - HA Bridge (v3.2.1) starting....
2016-11-04 16:17:21,474 [main] INFO com.bwssystems.HABridge.BridgeSettings - reading from config file: data/habridge.config
2016-11-04 16:17:22,081 [main] INFO com.bwssystems.HABridge.HABridge - HA Bridge initializing....
2016-11-04 16:17:22,199 [main] INFO com.bwssystems.HABridge.SystemControl - System control service started....
2016-11-04 16:17:23.280:INFO::Thread-0: Logging initialized @6216ms
2016-11-04 16:34:56,163 [Thread-0] INFO spark.webserver.JettySparkServer - == Spark has ignited ...
2016-11-04 16:34:56,214 [Thread-0] INFO spark.webserver.JettySparkServer - >> Listening on 0.0.0.0:8081
2016-11-04 16:34:56.244:INFO:oejs.Server:Thread-0: jetty-9.3.z-SNAPSHOT
2016-11-04 16:34:57.047:INFO:oejs.ServerConnector:Thread-0: Started ServerConnector@1bed92c{HTTP/1.1,[http/1.1]}{0.0.0.0:8081}
2016-11-04 16:34:57.090:INFO:oejs.Server:Thread-0: Started @8397ms
2016-11-04 16:34:58,556 [main] INFO com.bwssystems.harmony.HarmonyServer - setup initiated ....
2016-11-04 16:35:07,742 [main] INFO com.bwssystems.harmony.HarmonyServer - activity changed: [-1] PowerOff
2016-11-04 16:35:07,757 [main] INFO com.bwssystems.harmony.HarmonyServer - setup initiated ....
2016-11-04 16:35:10,862 [main] INFO com.bwssystems.harmony.HarmonyServer - activity changed: [-1] PowerOff
2016-11-04 16:35:11,519 [main] INFO com.bwssystems.HABridge.devicemanagmeent.DeviceResource - HABridge device management service started....
2016-11-04 16:35:11,583 [main] INFO com.bwssystems.HABridge.upnp.UpnpSettingsResource - Hue description service started....
2016-11-04 16:35:11,596 [main] INFO com.bwssystems.util.UDPDatagramSender - Initializing UDP response Seocket...
2016-11-04 16:35:11,608 [main] WARN com.bwssystems.util.UDPDatagramSender - UDP Response Port is in use, starting loop to find open port for 20 tries - configured port is: 50001
2016-11-04 16:35:11,610 [main] INFO com.bwssystems.util.UDPDatagramSender - UDP response Seocket initialized to: 50003
2016-11-04 16:35:11,668 [main] INFO com.bwssystems.HABridge.hue.HueMulator - Hue emulator service started....
2016-11-04 16:35:11,720 [main] INFO com.bwssystems.HABridge.upnp.UpnpListener - UPNP Discovery Listener starting....
2016-11-04 16:35:11,725 [main] INFO com.bwssystems.HABridge.upnp.UpnpListener - UPNP Discovery Listener running and ready....
2016-11-04 16:36:53,542 [main] INFO com.bwssystems.HABridge.upnp.UpnpListener - UPNP Discovery Listener - ended, restart found
2016-11-04 16:36:53,544 [main] INFO com.bwssystems.HABridge.HABridge - HA Bridge (v3.2.1) reinitialization requessted....
2016-11-04 16:36:53,596 [main] INFO spark.webserver.JettySparkServer - >>> Spark shutting down ...
2016-11-04 16:36:53.629:INFO:oejs.ServerConnector:main: Stopped ServerConnector@1bed92c{HTTP/1.1,[http/1.1]}{0.0.0.0:8081}
2016-11-04 16:36:53,639 [main] INFO spark.webserver.JettySparkServer - done
2016-11-04 16:36:53,648 [main] INFO com.bwssystems.HABridge.BridgeSettings - reading from config file: data/habridge.config
2016-11-04 16:36:53,665 [main] INFO com.bwssystems.HABridge.HABridge - HA Bridge initializing....
2016-11-04 16:36:53,670 [main] INFO com.bwssystems.HABridge.SystemControl - System control service started....
2016-11-04 16:36:53,675 [Thread-23] INFO spark.webserver.JettySparkServer - == Spark has ignited ...
2016-11-04 16:36:53,676 [Thread-23] INFO spark.webserver.JettySparkServer - >> Listening on 0.0.0.0:8081
2016-11-04 16:36:53.678:INFO:oejs.Server:Thread-23: jetty-9.3.z-SNAPSHOT
2016-11-04 16:36:53.686:INFO:oejs.ServerConnector:Thread-23: Started ServerConnector@1222ede{HTTP/1.1,[http/1.1]}{0.0.0.0:8081}
2016-11-04 16:36:53,694 [main] INFO com.bwssystems.harmony.HarmonyServer - setup initiated ....
2016-11-04 16:36:53.696:INFO:oejs.Server:Thread-23: Started @125002ms
2016-11-04 16:36:55,738 [main] INFO com.bwssystems.harmony.HarmonyServer - activity changed: [-1] PowerOff
2016-11-04 16:36:55,756 [main] INFO com.bwssystems.harmony.HarmonyServer - setup initiated ....
2016-11-04 16:36:57,623 [main] INFO com.bwssystems.harmony.HarmonyServer - activity changed: [-1] PowerOff
2016-11-04 16:36:57,668 [main] INFO com.bwssystems.HABridge.devicemanagmeent.DeviceResource - HABridge device management service started....
2016-11-04 16:36:57,671 [main] INFO com.bwssystems.HABridge.upnp.UpnpSettingsResource - Hue description service started....
2016-11-04 16:36:57,672 [main] INFO com.bwssystems.util.UDPDatagramSender - Initializing UDP response Seocket...
2016-11-04 16:36:57,674 [main] WARN com.bwssystems.util.UDPDatagramSender - UDP Response Port is in use, starting loop to find open port for 20 tries - configured port is: 50001
2016-11-04 16:36:57,675 [main] INFO com.bwssystems.util.UDPDatagramSender - UDP response Seocket initialized to: 50003
2016-11-04 16:36:57,727 [main] INFO com.bwssystems.HABridge.hue.HueMulator - Hue emulator service started....
2016-11-04 16:36:57,730 [main] INFO com.bwssystems.HABridge.upnp.UpnpListener - UPNP Discovery Listener starting....
2016-11-04 16:36:57,732 [main] INFO com.bwssystems.HABridge.upnp.UpnpListener - UPNP Discovery Listener running and ready....
2016-11-04 16:37:08,629 [main] INFO com.bwssystems.HABridge.upnp.UpnpListener - UPNP Discovery Listener - ended, restart found
2016-11-04 16:37:08,630 [main] INFO com.bwssystems.HABridge.HABridge - HA Bridge (v3.2.1) reinitialization requessted....
2016-11-04 16:37:08,666 [main] INFO spark.webserver.JettySparkServer - >>> Spark shutting down ...
2016-11-04 16:37:08.674:INFO:oejs.ServerConnector:main: Stopped ServerConnector@1222ede{HTTP/1.1,[http/1.1]}{0.0.0.0:8081}
2016-11-04 16:37:08,682 [main] INFO spark.webserver.JettySparkServer - done
2016-11-04 16:37:08,690 [main] INFO com.bwssystems.HABridge.BridgeSettings - reading from config file: data/habridge.config
2016-11-04 16:37:08,704 [main] INFO com.bwssystems.HABridge.HABridge - HA Bridge initializing....
2016-11-04 16:37:08,708 [main] INFO com.bwssystems.HABridge.SystemControl - System control service started....
2016-11-04 16:37:08,712 [Thread-45] INFO spark.webserver.JettySparkServer - == Spark has ignited ...
2016-11-04 16:37:08,714 [Thread-45] INFO spark.webserver.JettySparkServer - >> Listening on 0.0.0.0:8081
2016-11-04 16:37:08.715:INFO:oejs.Server:Thread-45: jetty-9.3.z-SNAPSHOT
2016-11-04 16:37:08.724:INFO:oejs.ServerConnector:Thread-45: Started ServerConnector@ee0973{HTTP/1.1,[http/1.1]}{0.0.0.0:8081}
2016-11-04 16:37:08.729:INFO:oejs.Server:Thread-45: Started @140036ms2016-11-04 16:37:08,727 [main] INFO com.bwssystems.harmony.HarmonyServer - setup initiated ....
2016-11-04 16:37:10,425 [main] INFO com.bwssystems.harmony.HarmonyServer - activity changed: [-1] PowerOff
2016-11-04 16:37:10,435 [main] INFO com.bwssystems.harmony.HarmonyServer - setup initiated ....
2016-11-04 16:37:12,341 [main] INFO com.bwssystems.harmony.HarmonyServer - activity changed: [-1] PowerOff
2016-11-04 16:37:12,377 [main] INFO com.bwssystems.HABridge.devicemanagmeent.DeviceResource - HABridge device management service started....
2016-11-04 16:37:12,381 [main] INFO com.bwssystems.HABridge.upnp.UpnpSettingsResource - Hue description service started....
2016-11-04 16:37:12,382 [main] INFO com.bwssystems.util.UDPDatagramSender - Initializing UDP response Seocket...
2016-11-04 16:37:12,383 [main] WARN com.bwssystems.util.UDPDatagramSender - UDP Response Port is in use, starting loop to find open port for 20 tries - configured port is: 50001
2016-11-04 16:37:12,384 [main] INFO com.bwssystems.util.UDPDatagramSender - UDP response Seocket initialized to: 50003
2016-11-04 16:37:12,433 [main] INFO com.bwssystems.HABridge.hue.HueMulator - Hue emulator service started....
2016-11-04 16:37:12,435 [main] INFO com.bwssystems.HABridge.upnp.UpnpListener - UPNP Discovery Listener starting....
2016-11-04 16:37:12,438 [main] INFO com.bwssystems.HABridge.upnp.UpnpListener - UPNP Discovery Listener running and ready....
robertw
on 4 Nov 2016
11-04-2016 13:38:32.990 INFO UPNP Discovery Listener - ended, restart found com.bwssystems.HABridge.upnp.UpnpListener
11-04-2016 13:38:32.991 INFO HA Bridge (v3.2.1) reinitialization requessted.... com.bwssystems.HABridge.HABridge
11-04-2016 13:38:32.993 INFO >>> Spark shutting down ... spark.webserver.JettySparkServer
11-04-2016 13:38:32.997 INFO done spark.webserver.JettySparkServer
11-04-2016 13:38:32.998 INFO reading from config file: data/habridge.config com.bwssystems.HABridge.BridgeSettings
11-04-2016 13:38:33.000 INFO HA Bridge initializing.... com.bwssystems.HABridge.HABridge
11-04-2016 13:38:33.001 INFO System control service started.... com.bwssystems.HABridge.SystemControl
11-04-2016 13:38:33.010 INFO HABridge device management service started.... com.bwssystems.HABridge.devicemanagmeent.DeviceResource
11-04-2016 13:38:33.011 INFO Hue description service started.... com.bwssystems.HABridge.upnp.UpnpSettingsResource
11-04-2016 13:38:33.011 INFO Initializing UDP response Seocket... com.bwssystems.util.UDPDatagramSender
11-04-2016 13:38:33.011 WARN UDP Response Port is in use, starting loop to find open port for 20 tries - configured port is: 50000 com.bwssystems.util.UDPDatagramSender
11-04-2016 13:38:33.012 INFO UDP response Seocket initialized to: 50001 com.bwssystems.util.UDPDatagramSender
11-04-2016 13:38:33.013 INFO == Spark has ignited ... spark.webserver.JettySparkServer
11-04-2016 13:38:33.014 INFO >> Listening on 0.0.0.0:8085 spark.webserver.JettySparkServer
11-04-2016 13:38:33.029 INFO Hue emulator service started.... com.bwssystems.HABridge.hue.HueMulator
11-04-2016 13:38:33.042 INFO UPNP Discovery Listener starting.... com.bwssystems.HABridge.upnp.UpnpListener
11-04-2016 13:38:33.043 INFO Traceupnp: eth1 ... has addr /fe80:0:0:0:6a05:caff:fe03:67e2%eth1 com.bwssystems.HABridge.upnp.UpnpListener
11-04-2016 13:38:33.043 INFO Traceupnp: eth1 ... has addr /192.168.1.101 com.bwssystems.HABridge.upnp.UpnpListener
11-04-2016 13:38:33.043 INFO Traceupnp: Adding eth1 to our interface set com.bwssystems.HABridge.upnp.UpnpListener
11-04-2016 13:38:33.044 INFO Traceupnp: eth0 ... has addr /fe80:0:0:0:6a05:caff:fe03:6fa1%eth0 com.bwssystems.HABridge.upnp.UpnpListener
11-04-2016 13:38:33.044 INFO Traceupnp: eth0 ... has addr /10.0.0.101 com.bwssystems.HABridge.upnp.UpnpListener
11-04-2016 13:38:33.044 INFO Traceupnp: Adding eth0 to our interface set com.bwssystems.HABridge.upnp.UpnpListener
11-04-2016 13:38:33.044 INFO Traceupnp: lo ... has addr /0:0:0:0:0:0:0:1%lo com.bwssystems.HABridge.upnp.UpnpListener
11-04-2016 13:38:33.044 INFO Traceupnp: lo ... has addr /127.0.0.1 com.bwssystems.HABridge.upnp.UpnpListener
11-04-2016 13:38:33.045 INFO Traceupnp: Adding lo to our interface set com.bwssystems.HABridge.upnp.UpnpListener
11-04-2016 13:38:33.046 INFO UPNP Discovery Listener running and ready.... com.bwssystems.HABridge.upnp.UpnpListener
11-04-2016 13:38:33.998 INFO Traceupnp: upnp device settings requested: from 192.168.1.106:8085 com.bwssystems.HABridge.upnp.UpnpSettingsResource
11-04-2016 13:38:33.998 INFO Traceupnp: upnp device settings template filled with address: 192.168.1.101 and port: 8085 com.bwssystems.HABridge.upnp.UpnpSettingsResource
11-04-2016 13:38:54.163 INFO Traceupnp: isSSDPDiscovery found message to be an M-SEARCH message. com.bwssystems.HABridge.upnp.UpnpListener
11-04-2016 13:38:54.163 INFO Traceupnp: isSSDPDiscovery found message to be valid under strict rules - strict: true com.bwssystems.HABridge.upnp.UpnpListener
11-04-2016 13:38:54.163 INFO Traceupnp: SSDP packet from 192.168.2.97:46165, body: M-SEARCH * HTTP/1.1
HOST: 239.255.255.250:1900
MAN: "ssdp:discover"
MX: 2
ST: ssdp:all
com.bwssystems.HABridge.upnp.UpnpListener
11-04-2016 13:38:54.163 INFO Traceupnp: sendUpnpResponse discovery responseTemplate1 is <<
CACHE-CONTROL: max-age=100
EXT:
LOCATION: http://192.168.1.101:8085/description.xml
SERVER: Linux/3.14.0 UPnP/1.0 IpBridge/1.15.0
hue-bridgeid: 6805CAFFFE0367E2
ST: upnp:rootdevice
USN: uuid:2f402f80-da50-11e1-9b23-6805ca0367e2::upnp:rootdevice
com.bwssystems.HABridge.upnp.UpnpListener
11-04-2016 13:38:54.164 INFO Traceupnp: sendUpnpResponse discovery responseTemplate2 is <<HOST: 239.255.255.250:1900
CACHE-CONTROL: max-age=100
EXT:
LOCATION: http://192.168.1.101:8085/description.xml
SERVER: Linux/3.14.0 UPnP/1.0 IpBridge/1.15.0
hue-bridgeid: 6805CAFFFE0367E2
ST: uuid:2f402f80-da50-11e1-9b23-6805ca0367e2
USN: uuid:2f402f80-da50-11e1-9b23-6805ca0367e2com.bwssystems.HABridge.upnp.UpnpListener
11-04-2016 13:38:54.164 INFO Traceupnp: sendUpnpResponse discovery responseTemplate3 is <<HOST: 239.255.255.250:1900
CACHE-CONTROL: max-age=100
EXT:
LOCATION: http://192.168.1.101:8085/description.xml
SERVER: Linux/3.14.0 UPnP/1.0 IpBridge/1.15.0
hue-bridgeid: 6805CAFFFE0367E2
ST: urn:schemas-upnp-org:device:basic:1
USN: uuid:2f402f80-da50-11e1-9b23-6805ca0367e2com.bwssystems.HABridge.upnp.UpnpListener
11-04-2016 13:39:17.034 INFO Traceupnp: isSSDPDiscovery found message to be an M-SEARCH message. com.bwssystems.HABridge.upnp.UpnpListener
11-04-2016 13:39:17.034 INFO Traceupnp: isSSDPDiscovery found message to be valid under strict rules - strict: true com.bwssystems.HABridge.upnp.UpnpListener
11-04-2016 13:39:17.034 INFO Traceupnp: SSDP packet from 10.0.0.127:12892, body: M-SEARCH * HTTP/1.1
MX: 5
ST: upnp:rootdevice
MAN: "ssdp:discover"
User-Agent: UPnP/1.0 DLNADOC/1.50 Kodi
Connection: close
Host: 239.255.255.250:1900
com.bwssystems.HABridge.upnp.UpnpListener
11-04-2016 13:39:17.035 INFO Traceupnp: sendUpnpResponse discovery responseTemplate1 is <<
CACHE-CONTROL: max-age=100
EXT:
LOCATION: http://192.168.1.101:8085/description.xml
SERVER: Linux/3.14.0 UPnP/1.0 IpBridge/1.15.0
hue-bridgeid: 6805CAFFFE0367E2
ST: upnp:rootdevice
USN: uuid:2f402f80-da50-11e1-9b23-6805ca0367e2::upnp:rootdevice
com.bwssystems.HABridge.upnp.UpnpListener
11-04-2016 13:39:17.035 INFO Traceupnp: sendUpnpResponse discovery responseTemplate2 is <<HOST: 239.255.255.250:1900
CACHE-CONTROL: max-age=100
EXT:
LOCATION: http://192.168.1.101:8085/description.xml
SERVER: Linux/3.14.0 UPnP/1.0 IpBridge/1.15.0
hue-bridgeid: 6805CAFFFE0367E2
ST: uuid:2f402f80-da50-11e1-9b23-6805ca0367e2
USN: uuid:2f402f80-da50-11e1-9b23-6805ca0367e2com.bwssystems.HABridge.upnp.UpnpListener
11-04-2016 13:39:17.035 INFO Traceupnp: sendUpnpResponse discovery responseTemplate3 is <<HOST: 239.255.255.250:1900
CACHE-CONTROL: max-age=100
EXT:
LOCATION: http://192.168.1.101:8085/description.xml
SERVER: Linux/3.14.0 UPnP/1.0 IpBridge/1.15.0
hue-bridgeid: 6805CAFFFE0367E2
ST: urn:schemas-upnp-org:device:basic:1
USN: uuid:2f402f80-da50-11e1-9b23-6805ca0367e2com.bwssystems.HABridge.upnp.UpnpListener
11-04-2016 13:39:17.035 INFO Traceupnp: isSSDPDiscovery found message to be an M-SEARCH message. com.bwssystems.HABridge.upnp.UpnpListener
11-04-2016 13:39:17.035 INFO Traceupnp: isSSDPDiscovery found message to be valid under strict rules - strict: true com.bwssystems.HABridge.upnp.UpnpListener
11-04-2016 13:39:17.035 INFO Traceupnp: SSDP packet from 10.0.0.127:12892, body: M-SEARCH * HTTP/1.1
MX: 5
ST: upnp:rootdevice
MAN: "ssdp:discover"
User-Agent: UPnP/1.0 DLNADOC/1.50 Kodi
Connection: close
Host: 239.255.255.250:1900
com.bwssystems.HABridge.upnp.UpnpListener
11-04-2016 13:39:17.035 INFO Traceupnp: sendUpnpResponse discovery responseTemplate1 is <<
CACHE-CONTROL: max-age=100
EXT:
LOCATION: http://192.168.1.101:8085/description.xml
SERVER: Linux/3.14.0 UPnP/1.0 IpBridge/1.15.0
hue-bridgeid: 6805CAFFFE0367E2
ST: upnp:rootdevice
USN: uuid:2f402f80-da50-11e1-9b23-6805ca0367e2::upnp:rootdevice
com.bwssystems.HABridge.upnp.UpnpListener
11-04-2016 13:39:17.035 INFO Traceupnp: sendUpnpResponse discovery responseTemplate2 is <<HOST: 239.255.255.250:1900
CACHE-CONTROL: max-age=100
EXT:
LOCATION: http://192.168.1.101:8085/description.xml
SERVER: Linux/3.14.0 UPnP/1.0 IpBridge/1.15.0
hue-bridgeid: 6805CAFFFE0367E2
ST: uuid:2f402f80-da50-11e1-9b23-6805ca0367e2
USN: uuid:2f402f80-da50-11e1-9b23-6805ca0367e2com.bwssystems.HABridge.upnp.UpnpListener
11-04-2016 13:39:17.035 INFO Traceupnp: sendUpnpResponse discovery responseTemplate3 is <<HOST: 239.255.255.250:1900
CACHE-CONTROL: max-age=100
EXT:
LOCATION: http://192.168.1.101:8085/description.xml
SERVER: Linux/3.14.0 UPnP/1.0 IpBridge/1.15.0
hue-bridgeid: 6805CAFFFE0367E2
ST: urn:schemas-upnp-org:device:basic:1
USN: uuid:2f402f80-da50-11e1-9b23-6805ca0367e2com.bwssystems.HABridge.upnp.UpnpListener
11-04-2016 13:39:54.162 INFO Traceupnp: isSSDPDiscovery found message to be an M-SEARCH message. com.bwssystems.HABridge.upnp.UpnpListener
11-04-2016 13:39:54.162 INFO Traceupnp: isSSDPDiscovery found message to be valid under strict rules - strict: true com.bwssystems.HABridge.upnp.UpnpListener
11-04-2016 13:39:54.162 INFO Traceupnp: SSDP packet from 192.168.2.97:46165, body: M-SEARCH * HTTP/1.1
HOST: 239.255.255.250:1900
MAN: "ssdp:discover"
MX: 2
ST: ssdp:all
com.bwssystems.HABridge.upnp.UpnpListener
11-04-2016 13:39:54.162 INFO Traceupnp: sendUpnpResponse discovery responseTemplate1 is <<
CACHE-CONTROL: max-age=100
EXT:
LOCATION: http://192.168.1.101:8085/description.xml
SERVER: Linux/3.14.0 UPnP/1.0 IpBridge/1.15.0
hue-bridgeid: 6805CAFFFE0367E2
ST: upnp:rootdevice
USN: uuid:2f402f80-da50-11e1-9b23-6805ca0367e2::upnp:rootdevice
com.bwssystems.HABridge.upnp.UpnpListener
11-04-2016 13:39:54.162 INFO Traceupnp: sendUpnpResponse discovery responseTemplate2 is <<HOST: 239.255.255.250:1900
CACHE-CONTROL: max-age=100
EXT:
LOCATION: http://192.168.1.101:8085/description.xml
SERVER: Linux/3.14.0 UPnP/1.0 IpBridge/1.15.0
hue-bridgeid: 6805CAFFFE0367E2
ST: uuid:2f402f80-da50-11e1-9b23-6805ca0367e2
USN: uuid:2f402f80-da50-11e1-9b23-6805ca0367e2com.bwssystems.HABridge.upnp.UpnpListener
11-04-2016 13:39:54.163 INFO Traceupnp: sendUpnpResponse discovery responseTemplate3 is <<HOST: 239.255.255.250:1900
CACHE-CONTROL: max-age=100
EXT:
LOCATION: http://192.168.1.101:8085/description.xml
SERVER: Linux/3.14.0 UPnP/1.0 IpBridge/1.15.0
hue-bridgeid: 6805CAFFFE0367E2
ST: urn:schemas-upnp-org:device:basic:1
USN: uuid:2f402f80-da50-11e1-9b23-6805ca0367e2com.bwssystems.HABridge.upnp.UpnpListener
11-04-2016 13:40:10.208 INFO Traceupnp: isSSDPDiscovery found message to be an M-SEARCH message. com.bwssystems.HABridge.upnp.UpnpListener
11-04-2016 13:40:10.209 INFO Traceupnp: isSSDPDiscovery found message to be valid under strict rules - strict: true com.bwssystems.HABridge.upnp.UpnpListener
11-04-2016 13:40:10.209 INFO Traceupnp: SSDP packet from 10.0.0.127:12892, body: M-SEARCH * HTTP/1.1
MX: 5
ST: upnp:rootdevice
MAN: "ssdp:discover"
User-Agent: UPnP/1.0 DLNADOC/1.50 Kodi
Connection: close
Host: 239.255.255.250:1900
com.bwssystems.HABridge.upnp.UpnpListener
11-04-2016 13:40:10.209 INFO Traceupnp: sendUpnpResponse discovery responseTemplate1 is <<
CACHE-CONTROL: max-age=100
EXT:
LOCATION: http://192.168.1.101:8085/description.xml
SERVER: Linux/3.14.0 UPnP/1.0 IpBridge/1.15.0
hue-bridgeid: 6805CAFFFE0367E2
ST: upnp:rootdevice
USN: uuid:2f402f80-da50-11e1-9b23-6805ca0367e2::upnp:rootdevice
com.bwssystems.HABridge.upnp.UpnpListener
11-04-2016 13:40:10.210 INFO Traceupnp: sendUpnpResponse discovery responseTemplate2 is <<HOST: 239.255.255.250:1900
CACHE-CONTROL: max-age=100
EXT:
LOCATION: http://192.168.1.101:8085/description.xml
SERVER: Linux/3.14.0 UPnP/1.0 IpBridge/1.15.0
hue-bridgeid: 6805CAFFFE0367E2
ST: uuid:2f402f80-da50-11e1-9b23-6805ca0367e2
USN: uuid:2f402f80-da50-11e1-9b23-6805ca0367e2com.bwssystems.HABridge.upnp.UpnpListener
11-04-2016 13:40:10.210 INFO Traceupnp: sendUpnpResponse discovery responseTemplate3 is <<HOST: 239.255.255.250:1900
CACHE-CONTROL: max-age=100
EXT:
LOCATION: http://192.168.1.101:8085/description.xml
SERVER: Linux/3.14.0 UPnP/1.0 IpBridge/1.15.0
hue-bridgeid: 6805CAFFFE0367E2
ST: urn:schemas-upnp-org:device:basic:1
USN: uuid:2f402f80-da50-11e1-9b23-6805ca0367e2com.bwssystems.HABridge.upnp.UpnpListener
11-04-2016 13:40:10.210 INFO Traceupnp: isSSDPDiscovery found message to be an M-SEARCH message. com.bwssystems.HABridge.upnp.UpnpListener
11-04-2016 13:40:10.210 INFO Traceupnp: isSSDPDiscovery found message to be valid under strict rules - strict: true com.bwssystems.HABridge.upnp.UpnpListener
11-04-2016 13:40:10.210 INFO Traceupnp: SSDP packet from 10.0.0.127:12892, body: M-SEARCH * HTTP/1.1
MX: 5
ST: upnp:rootdevice
MAN: "ssdp:discover"
User-Agent: UPnP/1.0 DLNADOC/1.50 Kodi
Connection: close
Host: 239.255.255.250:1900
com.bwssystems.HABridge.upnp.UpnpListener
11-04-2016 13:40:10.211 INFO Traceupnp: sendUpnpResponse discovery responseTemplate1 is <<
CACHE-CONTROL: max-age=100
EXT:
LOCATION: http://192.168.1.101:8085/description.xml
SERVER: Linux/3.14.0 UPnP/1.0 IpBridge/1.15.0
hue-bridgeid: 6805CAFFFE0367E2
ST: upnp:rootdevice
USN: uuid:2f402f80-da50-11e1-9b23-6805ca0367e2::upnp:rootdevice
com.bwssystems.HABridge.upnp.UpnpListener
11-04-2016 13:40:10.211 INFO Traceupnp: sendUpnpResponse discovery responseTemplate2 is <<HOST: 239.255.255.250:1900
CACHE-CONTROL: max-age=100
EXT:
LOCATION: http://192.168.1.101:8085/description.xml
SERVER: Linux/3.14.0 UPnP/1.0 IpBridge/1.15.0
hue-bridgeid: 6805CAFFFE0367E2
ST: uuid:2f402f80-da50-11e1-9b23-6805ca0367e2
USN: uuid:2f402f80-da50-11e1-9b23-6805ca0367e2com.bwssystems.HABridge.upnp.UpnpListener
11-04-2016 13:40:10.211 INFO Traceupnp: sendUpnpResponse discovery responseTemplate3 is <<HOST: 239.255.255.250:1900
CACHE-CONTROL: max-age=100
EXT:
LOCATION: http://192.168.1.101:8085/description.xml
SERVER: Linux/3.14.0 UPnP/1.0 IpBridge/1.15.0
hue-bridgeid: 6805CAFFFE0367E2
ST: urn:schemas-upnp-org:device:basic:1
USN: uuid:2f402f80-da50-11e1-9b23-6805ca0367e2com.bwssystems.HABridge.upnp.UpnpListener
11-04-2016 13:40:54.174 INFO Traceupnp: isSSDPDiscovery found message to be an M-SEARCH message. com.bwssystems.HABridge.upnp.UpnpListener
11-04-2016 13:40:54.175 INFO Traceupnp: isSSDPDiscovery found message to be valid under strict rules - strict: true com.bwssystems.HABridge.upnp.UpnpListener
11-04-2016 13:40:54.175 INFO Traceupnp: SSDP packet from 192.168.2.97:46165, body: M-SEARCH * HTTP/1.1
HOST: 239.255.255.250:1900
MAN: "ssdp:discover"
MX: 2
ST: ssdp:all
com.bwssystems.HABridge.upnp.UpnpListener
11-04-2016 13:40:54.175 INFO Traceupnp: sendUpnpResponse discovery responseTemplate1 is <<
CACHE-CONTROL: max-age=100
EXT:
LOCATION: http://192.168.1.101:8085/description.xml
SERVER: Linux/3.14.0 UPnP/1.0 IpBridge/1.15.0
hue-bridgeid: 6805CAFFFE0367E2
ST: upnp:rootdevice
USN: uuid:2f402f80-da50-11e1-9b23-6805ca0367e2::upnp:rootdevice
com.bwssystems.HABridge.upnp.UpnpListener
11-04-2016 13:40:54.175 INFO Traceupnp: sendUpnpResponse discovery responseTemplate2 is <<HOST: 239.255.255.250:1900
CACHE-CONTROL: max-age=100
EXT:
LOCATION: http://192.168.1.101:8085/description.xml
SERVER: Linux/3.14.0 UPnP/1.0 IpBridge/1.15.0
hue-bridgeid: 6805CAFFFE0367E2
ST: uuid:2f402f80-da50-11e1-9b23-6805ca0367e2
USN: uuid:2f402f80-da50-11e1-9b23-6805ca0367e2com.bwssystems.HABridge.upnp.UpnpListener
11-04-2016 13:40:54.175 INFO Traceupnp: sendUpnpResponse discovery responseTemplate3 is <<HOST: 239.255.255.250:1900
CACHE-CONTROL: max-age=100
EXT:
LOCATION: http://192.168.1.101:8085/description.xml
SERVER: Linux/3.14.0 UPnP/1.0 IpBridge/1.15.0
hue-bridgeid: 6805CAFFFE0367E2
ST: urn:schemas-upnp-org:device:basic:1
USN: uuid:2f402f80-da50-11e1-9b23-6805ca0367e2com.bwssystems.HABridge.upnp.UpnpListener
11-04-2016 13:41:04.516 INFO Traceupnp: isSSDPDiscovery found message to be an M-SEARCH message. com.bwssystems.HABridge.upnp.UpnpListener
11-04-2016 13:41:04.517 INFO Traceupnp: isSSDPDiscovery found message to be valid under strict rules - strict: true com.bwssystems.HABridge.upnp.UpnpListener
11-04-2016 13:41:04.517 INFO Traceupnp: SSDP packet from 10.0.0.127:12892, body: M-SEARCH * HTTP/1.1
MX: 5
ST: upnp:rootdevice
MAN: "ssdp:discover"
User-Agent: UPnP/1.0 DLNADOC/1.50 Kodi
Connection: close
Host: 239.255.255.250:1900
com.bwssystems.HABridge.upnp.UpnpListener
11-04-2016 13:41:04.517 INFO Traceupnp: sendUpnpResponse discovery responseTemplate1 is <<
CACHE-CONTROL: max-age=100
EXT:
LOCATION: http://192.168.1.101:8085/description.xml
SERVER: Linux/3.14.0 UPnP/1.0 IpBridge/1.15.0
hue-bridgeid: 6805CAFFFE0367E2
ST: upnp:rootdevice
USN: uuid:2f402f80-da50-11e1-9b23-6805ca0367e2::upnp:rootdevice
com.bwssystems.HABridge.upnp.UpnpListener
11-04-2016 13:41:04.517 INFO Traceupnp: sendUpnpResponse discovery responseTemplate2 is <<HOST: 239.255.255.250:1900
CACHE-CONTROL: max-age=100
EXT:
LOCATION: http://192.168.1.101:8085/description.xml
SERVER: Linux/3.14.0 UPnP/1.0 IpBridge/1.15.0
hue-bridgeid: 6805CAFFFE0367E2
ST: uuid:2f402f80-da50-11e1-9b23-6805ca0367e2
USN: uuid:2f402f80-da50-11e1-9b23-6805ca0367e2com.bwssystems.HABridge.upnp.UpnpListener
11-04-2016 13:41:04.517 INFO Traceupnp: sendUpnpResponse discovery responseTemplate3 is <<HOST: 239.255.255.250:1900
CACHE-CONTROL: max-age=100
EXT:
LOCATION: http://192.168.1.101:8085/description.xml
SERVER: Linux/3.14.0 UPnP/1.0 IpBridge/1.15.0
hue-bridgeid: 6805CAFFFE0367E2
ST: urn:schemas-upnp-org:device:basic:1
USN: uuid:2f402f80-da50-11e1-9b23-6805ca0367e2com.bwssystems.HABridge.upnp.UpnpListener
11-04-2016 13:41:04.518 INFO Traceupnp: isSSDPDiscovery found message to be an M-SEARCH message. com.bwssystems.HABridge.upnp.UpnpListener
11-04-2016 13:41:04.518 INFO Traceupnp: isSSDPDiscovery found message to be valid under strict rules - strict: true com.bwssystems.HABridge.upnp.UpnpListener
11-04-2016 13:41:04.518 INFO Traceupnp: SSDP packet from 10.0.0.127:12892, body: M-SEARCH * HTTP/1.1
MX: 5
ST: upnp:rootdevice
MAN: "ssdp:discover"
User-Agent: UPnP/1.0 DLNADOC/1.50 Kodi
Connection: close
Host: 239.255.255.250:1900
com.bwssystems.HABridge.upnp.UpnpListener
11-04-2016 13:41:04.518 INFO Traceupnp: sendUpnpResponse discovery responseTemplate1 is <<
CACHE-CONTROL: max-age=100
EXT:
LOCATION: http://192.168.1.101:8085/description.xml
SERVER: Linux/3.14.0 UPnP/1.0 IpBridge/1.15.0
hue-bridgeid: 6805CAFFFE0367E2
ST: upnp:rootdevice
USN: uuid:2f402f80-da50-11e1-9b23-6805ca0367e2::upnp:rootdevice
com.bwssystems.HABridge.upnp.UpnpListener
11-04-2016 13:41:04.518 INFO Traceupnp: sendUpnpResponse discovery responseTemplate2 is <<HOST: 239.255.255.250:1900
CACHE-CONTROL: max-age=100
EXT:
LOCATION: http://192.168.1.101:8085/description.xml
SERVER: Linux/3.14.0 UPnP/1.0 IpBridge/1.15.0
hue-bridgeid: 6805CAFFFE0367E2
ST: uuid:2f402f80-da50-11e1-9b23-6805ca0367e2
USN: uuid:2f402f80-da50-11e1-9b23-6805ca0367e2com.bwssystems.HABridge.upnp.UpnpListener
11-04-2016 13:41:04.518 INFO Traceupnp: sendUpnpResponse discovery responseTemplate3 is <<HOST: 239.255.255.250:1900
CACHE-CONTROL: max-age=100
EXT:
LOCATION: http://192.168.1.101:8085/description.xml
SERVER: Linux/3.14.0 UPnP/1.0 IpBridge/1.15.0
hue-bridgeid: 6805CAFFFE0367E2
ST: urn:schemas-upnp-org:device:basic:1
USN: uuid:2f402f80-da50-11e1-9b23-6805ca0367e2com.bwssystems.HABridge.upnp.UpnpListener
Go3Team
on 4 Nov 2016
I believe that was the orig bridge not the ha
robertw
on 4 Nov 2016
@robertw You still need to set the trace upnp flag and save the config
@Go3Team What is the ip of the google home?
bwssytems
on 4 Nov 2016
home ip 192.168.1.228
robertw
on 4 Nov 2016
Ok, try running the ha-bridge on port 80. Google may have hard coded that for the Philips Hue default.
bwssytems
on 4 Nov 2016
moved to 80 no go times out looking
robertw
on 4 Nov 2016
Turn This on too:
"setting DEBUG for com.bwssystems.HABridge.hue.HueMulator component. Changing this and then selecting the Update Log Levels button applies the new log settings."
bwssytems
on 4 Nov 2016
set as per debug and reran pair hope i did it right i see alot of debug info????
robertw
on 4 Nov 2016
In the logs tabs, do you see that setting set to debug when you select the "+"?
bwssytems
on 4 Nov 2016
new log
ok set log to debug tried again to find hub and omg hub found and paired here is the whole log something is a bit hinky though response was fast but as i ran through it it slowed to a crawl and speed back up just fyi......
robertw
on 4 Nov 2016
ok unpaired it and tried to repair no luck timed out i will keep trying ......
robertw
on 4 Nov 2016
192.168.2.97
Go3Team
on 5 Nov 2016
I spun up a fresh vm, running it on port 80. I was able to pair it and successfully turned on and off the test lighting. Now to add more lighting things.
Go3Team
on 5 Nov 2016
Update it seems if echo is online and trying to pair Google home it fails remove echo from network set port 80 and all seems to work fine but if I put echo back online a try to discover will not find hb unless I reboot router the both units online and working very strange any thoughts....
robertw
on 5 Nov 2016
Now it worked for me. Upgraded from 3.1.0 to 3.2.1, and GHome picked it up
emiliosic
on 5 Nov 2016
It doesn't appear to be the 3.2.1. I updated and still stuck at the push button to link screen. I've also put it on port 80, restarted everything multiple times without connecting. Anyone with any other ideas?
dvuder
on 5 Nov 2016
Now working great:
https://www.youtube.com/watch?v=e_tHWj8MGkQ
&
https://www.youtube.com/watch?v=LO8GbvaZroI
Go3Team
on 5 Nov 2016
I can confirm that you need the changes in version 3.2.0 or greater and you need to run on port 80.
TheOriginalAndrobot
on 5 Nov 2016
So port 80 is a requirement?
mwguttman
on 5 Nov 2016
Yes, unfortunately the port setting that is presented in the discovery process is ignored by the Home device. A "real" hue bridge runs on port 80, so they must have hard-coded that value.
They also use a more strict discovery process, hence the changes introduced in v3.2.0.
TheOriginalAndrobot
on 5 Nov 2016
FYI, I just submitted a pull request that adds documentation for using the Google Home w/ ha-bridge.
TheOriginalAndrobot
on 5 Nov 2016
This is great news. Looks like the caveat is to take your echo offline before discvoery.
bwssytems
on 5 Nov 2016
Make sure you pull skype or anything else off port 80. Wasted two hours trying to figure that out before it worked
dvuder
on 5 Nov 2016
I didn't see this mentioned but I had to give the java bin permission to run on port 80 in Ubuntu since it's a privileged port.
sudo setcap 'cap_net_bind_service=+ep' /usr/lib/jvm/java-8-oracle/jre/bin/java
I was able to pair successfully.
mwguttman
on 5 Nov 2016
@bwssytems What do you mean by take your Echo offline before discovery? Is that if you already have HA-Bridge setup?
VPsych
on 6 Nov 2016
@VPsych Unplug it.... That is what another posted above to get it to pair. Then plug it back in after the Google Home has paired
bwssytems
on 6 Nov 2016
I have several Google Home and an Amazon Echo and I had no issues with discovery with all of them connected.
TheOriginalAndrobot
on 6 Nov 2016
great that this works. Will be updating my website as well.
bwssytems
on 8 Nov 2016
Hey @robertw, how to tell the Google Home App to use a local request to connect to the HA Bridge? When I choose Home control -> Devices -> Add -> Philips Hue, it opens the browser with https://hue-adapter.appspot.com.
andrecarlucci
on 12 Mar 2017
Related issues
sieropoli
路
4Comments
rmohsenn
路
5Comments
Lorccan
路
4Comments
Desmo996
路
6Comments
pattont
路
5Comments
Most helpful comment
Hey @robertw, how to tell the Google Home App to use a local request to connect to the HA Bridge? When I choose Home control -> Devices -> Add -> Philips Hue, it opens the browser with https://hue-adapter.appspot.com.