search

bwssytems / ha-bridge

Home automation bridge that emulates a Philips Hue light system and can control other systems such as a Vera, Harmony Hub, Nest, MiLight bulbs or any other system that has an http/https/tcp/udp interface. This is a compact impl to run on small format computers. This is impl started from this project https://github.com/armzilla/amazon-echo-ha-bridge.
Apache License 2.0
1.45k stars 198 forks source link

ha-bridge incompatible with Amazon Echo Dot Gen. 3? #1092

Closed jayjupdhig closed 5 years ago

jayjupdhig commented 5 years ago

We are developing a home automation system, until now we used the Amazon Echo Dot Gen. 2 without any problems.

Now we tested the Gen. 3 version... but so it seems, it does not work anymore with.

Are there any compatibility issues with the current ha-bridge version 5.2.2 and Amazon Echo Dot Gen. 3?

(The configuration of the device (Amazon Account) was successful - without any problems..)

Thank you for your feedbacks.

jayjupdhig commented 5 years ago

additional info: what we do is an emulation of philips hue devices with ha-bridge

bwssytems commented 5 years ago

There should not be any issues. Did you turn on traceupnp to see if the ha-bridge can read the echo's UPNP messages?

kosuodhmwa commented 5 years ago

https://github.com/bwssytems/ha-bridge/issues/1022

kosuodhmwa commented 5 years ago

https://www.reddit.com/r/homeautomation/comments/9z785f/my_echo_dot_3rd_gen_does_no_detect_habridge/

kosuodhmwa commented 5 years ago

Where can i find the "traceupnp" logs? Thx for feedback.

kosuodhmwa commented 5 years ago

There are 5 emulated philips hue lights, they will not be found anymore with echo dot gen. 3. With echo dot gen. 2, there are no problems...

I set "traceupnp" to "true", and log level to "trace". After that, i started a smart home device search on amazon's alexa website. Log is here:

2019-05-23 20:34:39,290 [main] INFO  com.bwssystems.HABridge.HABridge - HA Bridge startup sequence...
2019-05-23 20:34:39,346 [main] INFO  com.bwssystems.HABridge.BridgeSettings - reading from config file: data/habridge.config
2019-05-23 20:34:41,610 [main] INFO  com.bwssystems.HABridge.HABridge - HA Bridge (v5.2.2) initializing....
2019-05-23 20:34:41,651 [main] INFO  spark.staticfiles.StaticFilesConfiguration - StaticResourceHandler configured with folder = /public
2019-05-23 20:34:41,685 [main] INFO  com.bwssystems.HABridge.SystemControl - System control service started....
2019-05-23 20:34:41.758:INFO::Thread-0: Logging initialized @3428ms to org.eclipse.jetty.util.log.StdErrLog
2019-05-23 20:34:41,785 [main] INFO  com.bwssystems.HABridge.util.UDPDatagramSender - Initializing UDP response Socket...
2019-05-23 20:34:41,794 [main] INFO  com.bwssystems.HABridge.util.UDPDatagramSender - UDP response Socket initialized to: 50000
2019-05-23 20:34:41,804 [main] INFO  com.bwssystems.HABridge.plugins.http.HTTPHome - HTTP Home created.
2019-05-23 20:34:41,816 [main] INFO  com.bwssystems.HABridge.plugins.harmony.HarmonyHome - Harmony Home created. No Harmony devices configured.
2019-05-23 20:34:41,821 [main] INFO  com.bwssystems.HABridge.plugins.NestBridge.NestHome - Nest Home created. No Nest configured.
2019-05-23 20:34:41,825 [main] INFO  com.bwssystems.HABridge.plugins.hue.HueHome - Hue passthru Home created. No Hue passtrhu systems configured.
2019-05-23 20:34:41,829 [main] INFO  com.bwssystems.HABridge.plugins.hal.HalHome - HAL Home created. No HAL devices configured.
2019-05-23 20:34:41,832 [main] INFO  com.bwssystems.HABridge.plugins.mqtt.MQTTHome - MQTT Home created. No MQTT Clients configured.
2019-05-23 20:34:41,837 [main] INFO  com.bwssystems.HABridge.plugins.hass.HassHome - HomeAssistant Home created. No HomeAssistants configured.
2019-05-23 20:34:41,840 [main] INFO  com.bwssystems.HABridge.plugins.homewizard.HomeWizardHome - HomeWizard Home created. No HomeWizard gateways configured.
2019-05-23 20:34:41,843 [main] INFO  com.bwssystems.HABridge.plugins.exec.CommandHome - Command Home for system program execution created.
2019-05-23 20:34:41,849 [main] INFO  com.bwssystems.HABridge.plugins.tcp.TCPHome - TCP Home created.
2019-05-23 20:34:41,855 [main] INFO  com.bwssystems.HABridge.plugins.udp.UDPHome - UDP Home created.
2019-05-23 20:34:41,868 [main] INFO  com.bwssystems.HABridge.plugins.vera.VeraHome - Vera Home created. No Veras configured.
2019-05-23 20:34:41,871 [main] INFO  com.bwssystems.HABridge.plugins.fibaro.FibaroHome - Fibaro Home created. No Fibaros configured.
2019-05-23 20:34:41,875 [main] INFO  com.bwssystems.HABridge.plugins.domoticz.DomoticzHome - Domoticz Home created. No Domoticz devices configured.
2019-05-23 20:34:41,878 [main] INFO  com.bwssystems.HABridge.plugins.somfy.SomfyHome - Somfy Home created. No Somfys configured.
2019-05-23 20:34:41,884 [main] INFO  com.bwssystems.HABridge.plugins.lifx.LifxHome - LifxDevice Home created. No LifxDevices configured.
2019-05-23 20:34:41,888 [main] INFO  com.bwssystems.HABridge.plugins.openhab.OpenHABHome - OpenHAB Home created. No OpenHABs configured.
2019-05-23 20:34:41,892 [main] INFO  com.bwssystems.HABridge.plugins.fhem.FHEMHome - FHEM Home created. No FHEMs configured.
2019-05-23 20:34:41,900 [main] INFO  com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - Broadlink Home created. No Broadlinks configured.
2019-05-23 20:34:41,941 [main] WARN  com.bwssystems.HABridge.dao.GroupRepository - Error reading the file: data/group.db - Does not exist or is not readable. continuing...
2019-05-23 20:34:41,942 [main] INFO  com.bwssystems.HABridge.devicemanagmeent.DeviceResource - HABridge device management service started....
2019-05-23 20:34:41,942 [Thread-0] INFO  spark.embeddedserver.jetty.EmbeddedJettyServer - == Spark has ignited ...
2019-05-23 20:34:41,947 [Thread-0] INFO  spark.embeddedserver.jetty.EmbeddedJettyServer - >> Listening on 0.0.0.0:80
2019-05-23 20:34:41.960:INFO:oejs.Server:Thread-0: jetty-9.4.z-SNAPSHOT, build timestamp: 2017-11-21T22:27:37+01:00, git hash: 82b8fb23f757335bb3329d540ce37a2a2615f0a8
2019-05-23 20:34:42,027 [main] INFO  com.bwssystems.HABridge.hue.HueMulator - Hue emulator service started....
2019-05-23 20:34:42.048:INFO:oejs.session:Thread-0: DefaultSessionIdManager workerName=node0
2019-05-23 20:34:42.048:INFO:oejs.session:Thread-0: No SessionScavenger set, using defaults
2019-05-23 20:34:42.058:INFO:oejs.session:Thread-0: Scavenging every 600000ms
2019-05-23 20:34:42.128:INFO:oejs.AbstractConnector:Thread-0: Started ServerConnector@1173db7{HTTP/1.1,[http/1.1]}{0.0.0.0:80}
2019-05-23 20:34:42.130:INFO:oejs.Server:Thread-0: Started @3806ms
2019-05-23 20:34:42,132 [main] INFO  com.bwssystems.HABridge.upnp.UpnpSettingsResource - Description xml service started....
2019-05-23 20:34:42,164 [main] INFO  com.bwssystems.HABridge.upnp.UpnpListener - UPNP Discovery Listener starting....
2019-05-23 20:34:42,166 [main] INFO  com.bwssystems.HABridge.upnp.UpnpListener - UPNP Discovery Listener running and ready....
^Croot@jm-has:/opt/habridge# java -Dserver.port=80 -jar ha-bridge-5.2.2.jar
2019-05-23 20:35:02,404 [main] INFO  com.bwssystems.HABridge.HABridge - HA Bridge startup sequence...
2019-05-23 20:35:02,460 [main] INFO  com.bwssystems.HABridge.BridgeSettings - reading from config file: data/habridge.config
2019-05-23 20:35:04,728 [main] INFO  com.bwssystems.HABridge.HABridge - HA Bridge (v5.2.2) initializing....
2019-05-23 20:35:04,770 [main] INFO  spark.staticfiles.StaticFilesConfiguration - StaticResourceHandler configured with folder = /public
2019-05-23 20:35:04,806 [main] INFO  com.bwssystems.HABridge.SystemControl - System control service started....
2019-05-23 20:35:04.879:INFO::Thread-0: Logging initialized @3480ms to org.eclipse.jetty.util.log.StdErrLog
2019-05-23 20:35:04,907 [main] INFO  com.bwssystems.HABridge.util.UDPDatagramSender - Initializing UDP response Socket...
2019-05-23 20:35:04,916 [main] INFO  com.bwssystems.HABridge.util.UDPDatagramSender - UDP response Socket initialized to: 50000
2019-05-23 20:35:04,927 [main] INFO  com.bwssystems.HABridge.plugins.http.HTTPHome - HTTP Home created.
2019-05-23 20:35:04,940 [main] INFO  com.bwssystems.HABridge.plugins.harmony.HarmonyHome - Harmony Home created. No Harmony devices configured.
2019-05-23 20:35:04,946 [main] INFO  com.bwssystems.HABridge.plugins.NestBridge.NestHome - Nest Home created. No Nest configured.
2019-05-23 20:35:04,950 [main] INFO  com.bwssystems.HABridge.plugins.hue.HueHome - Hue passthru Home created. No Hue passtrhu systems configured.
2019-05-23 20:35:04,954 [main] INFO  com.bwssystems.HABridge.plugins.hal.HalHome - HAL Home created. No HAL devices configured.
2019-05-23 20:35:04,959 [main] INFO  com.bwssystems.HABridge.plugins.mqtt.MQTTHome - MQTT Home created. No MQTT Clients configured.
2019-05-23 20:35:04,963 [main] INFO  com.bwssystems.HABridge.plugins.hass.HassHome - HomeAssistant Home created. No HomeAssistants configured.
2019-05-23 20:35:04,967 [main] INFO  com.bwssystems.HABridge.plugins.homewizard.HomeWizardHome - HomeWizard Home created. No HomeWizard gateways configured.
2019-05-23 20:35:04,971 [main] INFO  com.bwssystems.HABridge.plugins.exec.CommandHome - Command Home for system program execution created.
2019-05-23 20:35:04,975 [main] INFO  com.bwssystems.HABridge.plugins.tcp.TCPHome - TCP Home created.
2019-05-23 20:35:04,992 [main] INFO  com.bwssystems.HABridge.plugins.udp.UDPHome - UDP Home created.
2019-05-23 20:35:04,996 [main] INFO  com.bwssystems.HABridge.plugins.vera.VeraHome - Vera Home created. No Veras configured.
2019-05-23 20:35:04,999 [main] INFO  com.bwssystems.HABridge.plugins.fibaro.FibaroHome - Fibaro Home created. No Fibaros configured.
2019-05-23 20:35:05,003 [main] INFO  com.bwssystems.HABridge.plugins.domoticz.DomoticzHome - Domoticz Home created. No Domoticz devices configured.
2019-05-23 20:35:05,007 [main] INFO  com.bwssystems.HABridge.plugins.somfy.SomfyHome - Somfy Home created. No Somfys configured.
2019-05-23 20:35:05,012 [main] INFO  com.bwssystems.HABridge.plugins.lifx.LifxHome - LifxDevice Home created. No LifxDevices configured.
2019-05-23 20:35:05,017 [main] INFO  com.bwssystems.HABridge.plugins.openhab.OpenHABHome - OpenHAB Home created. No OpenHABs configured.
2019-05-23 20:35:05,022 [main] INFO  com.bwssystems.HABridge.plugins.fhem.FHEMHome - FHEM Home created. No FHEMs configured.
2019-05-23 20:35:05,031 [main] INFO  com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - Broadlink Home created. No Broadlinks configured.
2019-05-23 20:35:05,070 [main] WARN  com.bwssystems.HABridge.dao.GroupRepository - Error reading the file: data/group.db - Does not exist or is not readable. continuing...
2019-05-23 20:35:05,071 [main] INFO  com.bwssystems.HABridge.devicemanagmeent.DeviceResource - HABridge device management service started....
2019-05-23 20:35:05,074 [Thread-0] INFO  spark.embeddedserver.jetty.EmbeddedJettyServer - == Spark has ignited ...
2019-05-23 20:35:05,080 [Thread-0] INFO  spark.embeddedserver.jetty.EmbeddedJettyServer - >> Listening on 0.0.0.0:80
2019-05-23 20:35:05.094:INFO:oejs.Server:Thread-0: jetty-9.4.z-SNAPSHOT, build timestamp: 2017-11-21T22:27:37+01:00, git hash: 82b8fb23f757335bb3329d540ce37a2a2615f0a8
2019-05-23 20:35:05,159 [main] INFO  com.bwssystems.HABridge.hue.HueMulator - Hue emulator service started....
2019-05-23 20:35:05.183:INFO:oejs.session:Thread-0: DefaultSessionIdManager workerName=node0
2019-05-23 20:35:05.183:INFO:oejs.session:Thread-0: No SessionScavenger set, using defaults
2019-05-23 20:35:05.193:INFO:oejs.session:Thread-0: Scavenging every 660000ms
2019-05-23 20:35:05.263:INFO:oejs.AbstractConnector:Thread-0: Started ServerConnector@8dd341{HTTP/1.1,[http/1.1]}{0.0.0.0:80}
2019-05-23 20:35:05.265:INFO:oejs.Server:Thread-0: Started @3873ms
2019-05-23 20:35:05,268 [main] INFO  com.bwssystems.HABridge.upnp.UpnpSettingsResource - Description xml service started....
2019-05-23 20:35:05,299 [main] INFO  com.bwssystems.HABridge.upnp.UpnpListener - UPNP Discovery Listener starting....
2019-05-23 20:35:05,302 [main] INFO  com.bwssystems.HABridge.upnp.UpnpListener - UPNP Discovery Listener running and ready....
2019-05-23 20:35:38,433 [main] INFO  com.bwssystems.HABridge.upnp.UpnpListener - UPNP Discovery Listener - ended, restart found
2019-05-23 20:35:38,434 [main] INFO  com.bwssystems.HABridge.HABridge - HA Bridge (v5.2.2) reinitialization requessted....
2019-05-23 20:35:38,434 [main] INFO  com.bwssystems.HABridge.HABridge - Going to close all homes
2019-05-23 20:35:38,434 [main] INFO  com.bwssystems.HABridge.HomeManager - Manager close homes called....
2019-05-23 20:35:38,435 [main] INFO  com.bwssystems.HABridge.HomeManager - Closing home: com.bwssystems.HABridge.plugins.tcp.TCPHome
2019-05-23 20:35:38,435 [main] INFO  com.bwssystems.HABridge.HomeManager - Closing home: com.bwssystems.HABridge.plugins.NestBridge.NestHome
2019-05-23 20:35:38,435 [main] INFO  com.bwssystems.HABridge.HomeManager - Closing home: com.bwssystems.HABridge.plugins.hal.HalHome
2019-05-23 20:35:38,435 [main] INFO  com.bwssystems.HABridge.HomeManager - Closing home: com.bwssystems.HABridge.plugins.NestBridge.NestHome
2019-05-23 20:35:38,436 [main] INFO  com.bwssystems.HABridge.HomeManager - Closing home: com.bwssystems.HABridge.plugins.lifx.LifxHome
2019-05-23 20:35:38,436 [main] INFO  com.bwssystems.HABridge.HomeManager - Closing home: com.bwssystems.HABridge.plugins.somfy.SomfyHome
2019-05-23 20:35:38,436 [main] INFO  com.bwssystems.HABridge.HomeManager - Closing home: com.bwssystems.HABridge.plugins.http.HTTPHome
2019-05-23 20:35:38,436 [main] INFO  com.bwssystems.HABridge.HomeManager - Closing home: com.bwssystems.HABridge.plugins.openhab.OpenHABHome
2019-05-23 20:35:38,436 [main] INFO  com.bwssystems.HABridge.HomeManager - Closing home: com.bwssystems.HABridge.plugins.hal.HalHome
2019-05-23 20:35:38,437 [main] INFO  com.bwssystems.HABridge.HomeManager - Closing home: com.bwssystems.HABridge.plugins.homewizard.HomeWizardHome
2019-05-23 20:35:38,437 [main] INFO  com.bwssystems.HABridge.HomeManager - Closing home: com.bwssystems.HABridge.plugins.fhem.FHEMHome
2019-05-23 20:35:38,437 [main] INFO  com.bwssystems.HABridge.HomeManager - Closing home: com.bwssystems.HABridge.plugins.http.HTTPHome
2019-05-23 20:35:38,437 [main] INFO  com.bwssystems.HABridge.HomeManager - Closing home: com.bwssystems.HABridge.plugins.udp.UDPHome
2019-05-23 20:35:38,438 [main] INFO  com.bwssystems.HABridge.HomeManager - Closing home: com.bwssystems.HABridge.plugins.hal.HalHome
2019-05-23 20:35:38,438 [main] INFO  com.bwssystems.HABridge.HomeManager - Closing home: com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome
2019-05-23 20:35:38,438 [main] INFO  com.bwssystems.HABridge.HomeManager - Closing home: com.bwssystems.HABridge.plugins.exec.CommandHome
2019-05-23 20:35:38,438 [main] INFO  com.bwssystems.HABridge.HomeManager - Closing home: com.bwssystems.HABridge.plugins.http.HTTPHome
2019-05-23 20:35:38,438 [main] INFO  com.bwssystems.HABridge.HomeManager - Closing home: com.bwssystems.HABridge.plugins.hass.HassHome
2019-05-23 20:35:38,439 [main] INFO  com.bwssystems.HABridge.HomeManager - Closing home: com.bwssystems.HABridge.plugins.harmony.HarmonyHome
2019-05-23 20:35:38,439 [main] INFO  com.bwssystems.HABridge.HomeManager - Closing home: com.bwssystems.HABridge.plugins.hal.HalHome
2019-05-23 20:35:38,439 [main] INFO  com.bwssystems.HABridge.HomeManager - Closing home: com.bwssystems.HABridge.plugins.udp.UDPHome
2019-05-23 20:35:38,439 [main] INFO  com.bwssystems.HABridge.HomeManager - Closing home: com.bwssystems.HABridge.plugins.hue.HueHome
2019-05-23 20:35:38,439 [main] INFO  com.bwssystems.HABridge.HomeManager - Closing home: com.bwssystems.HABridge.plugins.harmony.HarmonyHome
2019-05-23 20:35:38,439 [main] INFO  com.bwssystems.HABridge.HomeManager - Closing home: com.bwssystems.HABridge.plugins.tcp.TCPHome
2019-05-23 20:35:38,440 [main] INFO  com.bwssystems.HABridge.HomeManager - Closing home: com.bwssystems.HABridge.plugins.http.HTTPHome
2019-05-23 20:35:38,440 [main] INFO  com.bwssystems.HABridge.HomeManager - Closing home: com.bwssystems.HABridge.plugins.mqtt.MQTTHome
2019-05-23 20:35:38,440 [main] INFO  com.bwssystems.HABridge.HomeManager - Closing home: com.bwssystems.HABridge.plugins.domoticz.DomoticzHome
2019-05-23 20:35:38,440 [main] INFO  com.bwssystems.HABridge.HomeManager - Closing home: com.bwssystems.HABridge.plugins.http.HTTPHome
2019-05-23 20:35:38,440 [main] INFO  com.bwssystems.HABridge.HomeManager - Closing home: com.bwssystems.HABridge.plugins.exec.CommandHome
2019-05-23 20:35:38,441 [main] INFO  com.bwssystems.HABridge.HomeManager - Closing home: com.bwssystems.HABridge.plugins.http.HTTPHome
2019-05-23 20:35:38,443 [Thread-16] INFO  spark.embeddedserver.jetty.EmbeddedJettyServer - >>> Spark shutting down ...
2019-05-23 20:35:38.465:INFO:oejs.AbstractConnector:Thread-16: Stopped ServerConnector@8dd341{HTTP/1.1,[http/1.1]}{0.0.0.0:80}
2019-05-23 20:35:38.467:INFO:oejs.session:Thread-16: Stopped scavenging
2019-05-23 20:35:38,472 [Thread-16] INFO  spark.embeddedserver.jetty.EmbeddedJettyServer - done
2019-05-23 20:35:43,443 [main] INFO  com.bwssystems.HABridge.BridgeSettings - reading from config file: data/habridge.config
2019-05-23 20:35:43,473 [main] INFO  com.bwssystems.HABridge.HABridge - HA Bridge (v5.2.2) initializing....
2019-05-23 20:35:43,474 [main] INFO  spark.staticfiles.StaticFilesConfiguration - StaticResourceHandler configured with folder = /public
2019-05-23 20:35:43,477 [main] INFO  com.bwssystems.HABridge.SystemControl - System control service started....
2019-05-23 20:35:43,479 [Thread-17] INFO  spark.embeddedserver.jetty.EmbeddedJettyServer - == Spark has ignited ...
2019-05-23 20:35:43,480 [Thread-17] INFO  spark.embeddedserver.jetty.EmbeddedJettyServer - >> Listening on 0.0.0.0:80
2019-05-23 20:35:43.480:INFO:oejs.Server:Thread-17: jetty-9.4.z-SNAPSHOT, build timestamp: 2017-11-21T22:27:37+01:00, git hash: 82b8fb23f757335bb3329d540ce37a2a2615f0a8
2019-05-23 20:35:43,481 [main] INFO  com.bwssystems.HABridge.util.UDPDatagramSender - Initializing UDP response Socket...
2019-05-23 20:35:43,482 [main] INFO  com.bwssystems.HABridge.util.UDPDatagramSender - UDP response Socket initialized to: 50000
2019-05-23 20:35:43,483 [main] INFO  com.bwssystems.HABridge.plugins.http.HTTPHome - HTTP Home created.
2019-05-23 20:35:43.484:INFO:oejs.session:Thread-17: DefaultSessionIdManager workerName=node02019-05-23 20:35:43,484 [main] INFO  com.bwssystems.HABridge.plugins.harmony.HarmonyHome - Harmony Home created. No Harmony devices configured.

2019-05-23 20:35:43.484:INFO:oejs.session:Thread-17: No SessionScavenger set, using defaults2019-05-23 20:35:43,484 [main] INFO  com.bwssystems.HABridge.plugins.NestBridge.NestHome - Nest Home created. No Nest configured.

2019-05-23 20:35:43,484 [main] INFO  com.bwssystems.HABridge.plugins.hue.HueHome - Hue passthru Home created. No Hue passtrhu systems configured.
2019-05-23 20:35:43,484 [main] INFO  com.bwssystems.HABridge.plugins.hal.HalHome - HAL Home created. No HAL devices configured.
2019-05-23 20:35:43.484:INFO:oejs.session:Thread-17: Scavenging every 660000ms
2019-05-23 20:35:43,485 [main] INFO  com.bwssystems.HABridge.plugins.mqtt.MQTTHome - MQTT Home created. No MQTT Clients configured.
2019-05-23 20:35:43,485 [main] INFO  com.bwssystems.HABridge.plugins.hass.HassHome - HomeAssistant Home created. No HomeAssistants configured.
2019-05-23 20:35:43,486 [main] INFO  com.bwssystems.HABridge.plugins.homewizard.HomeWizardHome - HomeWizard Home created. No HomeWizard gateways configured.
2019-05-23 20:35:43,486 [main] INFO  com.bwssystems.HABridge.plugins.exec.CommandHome - Command Home for system program execution created.
2019-05-23 20:35:43,486 [main] INFO  com.bwssystems.HABridge.plugins.tcp.TCPHome - TCP Home created.
2019-05-23 20:35:43,486 [main] INFO  com.bwssystems.HABridge.plugins.udp.UDPHome - UDP Home created.
2019-05-23 20:35:43,487 [main] INFO  com.bwssystems.HABridge.plugins.vera.VeraHome - Vera Home created. No Veras configured.
2019-05-23 20:35:43,487 [main] INFO  com.bwssystems.HABridge.plugins.fibaro.FibaroHome - Fibaro Home created. No Fibaros configured.
2019-05-23 20:35:43,487 [main] INFO  com.bwssystems.HABridge.plugins.domoticz.DomoticzHome - Domoticz Home created. No Domoticz devices configured.
2019-05-23 20:35:43,487 [main] INFO  com.bwssystems.HABridge.plugins.somfy.SomfyHome - Somfy Home created. No Somfys configured.
2019-05-23 20:35:43,487 [main] INFO  com.bwssystems.HABridge.plugins.lifx.LifxHome - LifxDevice Home created. No LifxDevices configured.
2019-05-23 20:35:43,488 [main] INFO  com.bwssystems.HABridge.plugins.openhab.OpenHABHome - OpenHAB Home created. No OpenHABs configured.
2019-05-23 20:35:43,488 [main] INFO  com.bwssystems.HABridge.plugins.fhem.FHEMHome - FHEM Home created. No FHEMs configured.
2019-05-23 20:35:43,488 [main] INFO  com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - Broadlink Home created. No Broadlinks configured.
2019-05-23 20:35:43.492:INFO:oejs.AbstractConnector:Thread-17: Started ServerConnector@dae35{HTTP/1.1,[http/1.1]}{0.0.0.0:80}
2019-05-23 20:35:43.493:INFO:oejs.Server:Thread-17: Started @42100ms
2019-05-23 20:35:43,495 [main] WARN  com.bwssystems.HABridge.dao.GroupRepository - Error reading the file: data/group.db - Does not exist or is not readable. continuing...
2019-05-23 20:35:43,496 [main] INFO  com.bwssystems.HABridge.devicemanagmeent.DeviceResource - HABridge device management service started....
2019-05-23 20:35:43,500 [main] INFO  com.bwssystems.HABridge.hue.HueMulator - Hue emulator service started....
2019-05-23 20:35:43,504 [main] INFO  com.bwssystems.HABridge.HABridge - Traceupnp: upnp config address: 192.168.1.168-useIface:false on web server: 0.0.0.0:80
2019-05-23 20:35:43,505 [main] INFO  com.bwssystems.HABridge.upnp.UpnpSettingsResource - Description xml service started....
2019-05-23 20:35:43,507 [main] INFO  com.bwssystems.HABridge.upnp.UpnpListener - UPNP Discovery Listener starting....
2019-05-23 20:35:43,508 [main] INFO  com.bwssystems.HABridge.upnp.UpnpListener - Traceupnp: Interface: enxb827ebfd2258 valid usable IP address: /192.168.1.168
2019-05-23 20:35:43,509 [main] INFO  com.bwssystems.HABridge.upnp.UpnpListener - Traceupnp: Adding enxb827ebfd2258 to our upnp join interface set.
2019-05-23 20:35:43,510 [main] INFO  com.bwssystems.HABridge.upnp.UpnpListener - Traceupnp: Interface: lo valid usable IP address: /127.0.0.1
2019-05-23 20:35:43,510 [main] INFO  com.bwssystems.HABridge.upnp.UpnpListener - Traceupnp: Adding lo to our upnp join interface set.
2019-05-23 20:35:43,510 [main] INFO  com.bwssystems.HABridge.upnp.UpnpListener - UPNP Discovery Listener running and ready....
2019-05-23 20:35:45,485 [qtp11393817-28] INFO  com.bwssystems.HABridge.upnp.UpnpSettingsResource - Traceupnp: request of description.xml from: 192.168.1.203:80 filled in with address: 192.168.1.168:80
2019-05-23 20:36:10,451 [main] INFO  com.bwssystems.HABridge.upnp.UpnpListener - Traceupnp: SSDP M-SEARCH packet from 192.168.1.130:50000
2019-05-23 20:36:11,103 [main] INFO  com.bwssystems.HABridge.upnp.UpnpListener - Traceupnp: send upnp discovery template 1 with response address: 192.168.1.168:80 to address: /192.168.1.130:50000
2019-05-23 20:36:11,218 [qtp11393817-30] INFO  com.bwssystems.HABridge.upnp.UpnpSettingsResource - Traceupnp: request of description.xml from: 192.168.1.130:80 filled in with address: 192.168.1.168:80
2019-05-23 20:36:11,234 [qtp11393817-31] INFO  com.bwssystems.HABridge.hue.HueMulator - Traceupnp: hue api user create requested: {"devicetype": "Echo"} from address: 192.168.1.130
2019-05-23 20:36:11,755 [main] INFO  com.bwssystems.HABridge.upnp.UpnpListener - Traceupnp: send upnp discovery template 2 with response address: 192.168.1.168:80 to address: /192.168.1.130:50000
2019-05-23 20:36:12,407 [main] INFO  com.bwssystems.HABridge.upnp.UpnpListener - Traceupnp: send upnp discovery template 3 with response address: 192.168.1.168:80 to address: /192.168.1.130:50000
2019-05-23 20:36:12,408 [main] INFO  com.bwssystems.HABridge.upnp.UpnpListener - Traceupnp: SSDP M-SEARCH packet from 192.168.1.130:50000
2019-05-23 20:36:13,060 [main] INFO  com.bwssystems.HABridge.upnp.UpnpListener - Traceupnp: send upnp discovery template 1 with response address: 192.168.1.168:80 to address: /192.168.1.130:50000
2019-05-23 20:36:13,712 [main] INFO  com.bwssystems.HABridge.upnp.UpnpListener - Traceupnp: send upnp discovery template 2 with response address: 192.168.1.168:80 to address: /192.168.1.130:50000
2019-05-23 20:36:14,363 [main] INFO  com.bwssystems.HABridge.upnp.UpnpListener - Traceupnp: send upnp discovery template 3 with response address: 192.168.1.168:80 to address: /192.168.1.130:50000
2019-05-23 20:36:14,364 [main] INFO  com.bwssystems.HABridge.upnp.UpnpListener - Traceupnp: SSDP M-SEARCH packet from 192.168.1.130:50000
2019-05-23 20:36:15,015 [main] INFO  com.bwssystems.HABridge.upnp.UpnpListener - Traceupnp: send upnp discovery template 1 with response address: 192.168.1.168:80 to address: /192.168.1.130:50000
2019-05-23 20:36:15,667 [main] INFO  com.bwssystems.HABridge.upnp.UpnpListener - Traceupnp: send upnp discovery template 2 with response address: 192.168.1.168:80 to address: /192.168.1.130:50000
2019-05-23 20:36:16,254 [qtp11393817-30] INFO  com.bwssystems.HABridge.hue.HueMulator - Traceupnp: hue api user create requested: {"devicetype": "Echo"} from address: 192.168.1.130
2019-05-23 20:36:16,318 [main] INFO  com.bwssystems.HABridge.upnp.UpnpListener - Traceupnp: send upnp discovery template 3 with response address: 192.168.1.168:80 to address: /192.168.1.130:50000
2019-05-23 20:36:16,319 [main] INFO  com.bwssystems.HABridge.upnp.UpnpListener - Traceupnp: SSDP M-SEARCH packet from 192.168.1.130:50000
2019-05-23 20:36:16,971 [main] INFO  com.bwssystems.HABridge.upnp.UpnpListener - Traceupnp: send upnp discovery template 1 with response address: 192.168.1.168:80 to address: /192.168.1.130:50000
2019-05-23 20:36:17,623 [main] INFO  com.bwssystems.HABridge.upnp.UpnpListener - Traceupnp: send upnp discovery template 2 with response address: 192.168.1.168:80 to address: /192.168.1.130:50000
2019-05-23 20:36:18,274 [main] INFO  com.bwssystems.HABridge.upnp.UpnpListener - Traceupnp: send upnp discovery template 3 with response address: 192.168.1.168:80 to address: /192.168.1.130:50000
2019-05-23 20:36:18,275 [main] INFO  com.bwssystems.HABridge.upnp.UpnpListener - Traceupnp: SSDP M-SEARCH packet from 192.168.1.130:50000
2019-05-23 20:36:18,927 [main] INFO  com.bwssystems.HABridge.upnp.UpnpListener - Traceupnp: send upnp discovery template 1 with response address: 192.168.1.168:80 to address: /192.168.1.130:50000
2019-05-23 20:36:19,579 [main] INFO  com.bwssystems.HABridge.upnp.UpnpListener - Traceupnp: send upnp discovery template 2 with response address: 192.168.1.168:80 to address: /192.168.1.130:50000
2019-05-23 20:36:20,231 [main] INFO  com.bwssystems.HABridge.upnp.UpnpListener - Traceupnp: send upnp discovery template 3 with response address: 192.168.1.168:80 to address: /192.168.1.130:50000
2019-05-23 20:36:20,232 [main] INFO  com.bwssystems.HABridge.upnp.UpnpListener - Traceupnp: SSDP M-SEARCH packet from 192.168.1.130:50000
2019-05-23 20:36:20,885 [main] INFO  com.bwssystems.HABridge.upnp.UpnpListener - Traceupnp: send upnp discovery template 1 with response address: 192.168.1.168:80 to address: /192.168.1.130:50000
2019-05-23 20:36:21,398 [qtp11393817-31] INFO  com.bwssystems.HABridge.hue.HueMulator - Traceupnp: hue api user create requested: {"devicetype": "Echo"} from address: 192.168.1.130
2019-05-23 20:36:21,536 [main] INFO  com.bwssystems.HABridge.upnp.UpnpListener - Traceupnp: send upnp discovery template 2 with response address: 192.168.1.168:80 to address: /192.168.1.130:50000
2019-05-23 20:36:22,187 [main] INFO  com.bwssystems.HABridge.upnp.UpnpListener - Traceupnp: send upnp discovery template 3 with response address: 192.168.1.168:80 to address: /192.168.1.130:50000
kosuodhmwa commented 5 years ago

The version i use is 5.2.2.

bwssytems commented 5 years ago

What is the IP of the gen 3 echo?

jayjupdhig commented 5 years ago

192.168.1.130 (this is my business account, "jmar83" the personal)

jayjupdhig commented 5 years ago

A few facts:

So, the devices will be bound on the second try. But when i say "Computer, Licht Büro einschalten" (which means "Computer, turn on light office" in german ;-)), the device will not be found. No connection. Also with ha-bridge on port 80.

The link button in ha bridge gui seems to be effectless when i search for smart home device on alexa website. No difference so it seems!

jayjupdhig commented 5 years ago

There seems to be a lot of issues with the current ha bridge and some alexa device (no just echo dot gen. 3!), there there is not one "step-by-step" manual in the whole internet to make it run.

Also the problems (and potential solutions) are VERY VERY different when i look on that page: https://github.com/bwssytems/ha-bridge/issues/1022

Some of them seems to run (and the people don't know why), others not...(and the people also don't know why ;-))

jayjupdhig commented 5 years ago

Additional info: The amazon echo dot gen. 3 i have was bougth in switzerland. Account was also set to switzerland.

jayjupdhig commented 5 years ago

No answer...?

jayjupdhig commented 5 years ago

Or no solution, so it seems??

bwssytems commented 5 years ago

So, how are you running the ha-bridge (startup config)? what platform are you running on?

jayjupdhig commented 5 years ago

"java -jar ha-bridge.jar" on raspbian stretch with most current updates.

and i changed some logging options (upnp and general log level) in the ha-bridge gui...

bwssytems commented 5 years ago

what about your network setup?

bwssytems commented 5 years ago

I will be adding an older style upnp message to see if that helps. Others had success with going back to v3.2.1 which used a different upnp message style.

kosuodhmwa commented 5 years ago

Now i've done some research:

With Gen. 3 Echo devices, the smart home device search process on alexa website seems to work like a random generator... sometimes it found (some) devices, sometimes not. (And sometimes i have devices in the list i never had, e.g. "Bad" (which means bath). And also the echo device is in the smart home device list. (I never had that with Gen. 2)

If they will be found, i'm able to switch them when i run the HTTP daemon on port 80. (That behavior must be implemented from Amazon, so we can't change it.. e.g. with Port 81, it does not work while Gen. 2 works without any problem. And i didn't test Gen. 1, no idea how it works)

My Network setup: 192.168.80.0/24 Gateway 192.168.80.1 DNS 8.8.8.8 & 8.8.4.4 from Google UPnP off on Router, but i don't think that is relevant. (i read something about that in another discussion, but i can't see any relations between UPnp on router (=automatic port forwarding?) and HA-bridge's functionality)

The reason for the virtual network controller is the fact that on the physical adapter's IP an apache2 service is running for our web GUI.

tsgoff commented 5 years ago

same Problem with 5.2.2 - workaround old alexa as proxy to discover the devices

jayjupdhig commented 5 years ago

The only port 80 for gen 3 devices problem is amazon's work, but the device search (UDP uPNP) could be a problem of habridge.

In my case, the first search don't show any devices, then i need to search again in 5-7 seconds, then the devices (sometimes) will be found

jayjupdhig commented 5 years ago

if you have a webserver that already needs port 80, then set up a virtual lan adapter (type "macvlan") to run ha-bridge service on it with port 80

gcaruncho commented 5 years ago

Is it compatible with ECHO Input ?. In HaBridge I see all the devices but Alexa does not capture anything. Pi3/Domoticz

LOG 07-19-2019 14:48:12.478 INFO HA Bridge (v5.3.0RC11) initializing.... com.bwssystems.HABridge.HABridge 07-19-2019 14:48:12.478 INFO reading from config file: /home/pi/habridge/data/habridge.config com.bwssystems.HABridge.BridgeSettings 07-19-2019 14:48:12.500 INFO StaticResourceHandler configured with folder = /public spark.staticfiles.StaticFilesConfiguration 07-19-2019 14:48:12.506 INFO System control service started.... com.bwssystems.HABridge.SystemControl 07-19-2019 14:48:12.510 INFO == Spark has ignited ... spark.embeddedserver.jetty.EmbeddedJettyServer 07-19-2019 14:48:12.512 INFO >> Listening on 192.168.1.42:80 spark.embeddedserver.jetty.EmbeddedJettyServer 07-19-2019 14:48:12.515 INFO Initializing UDP response Socket... com.bwssystems.HABridge.util.UDPDatagramSender 07-19-2019 14:48:12.516 INFO UDP response Socket initialized to: 50000 com.bwssystems.HABridge.util.UDPDatagramSender 07-19-2019 14:48:12.516 INFO HTTP Home created. com.bwssystems.HABridge.plugins.http.HTTPHome 07-19-2019 14:48:12.516 INFO Harmony Home created. No Harmony devices configured. com.bwssystems.HABridge.plugins.harmony.HarmonyHome 07-19-2019 14:48:12.517 INFO Nest Home created. No Nest configured. com.bwssystems.HABridge.plugins.NestBridge.NestHome 07-19-2019 14:48:12.517 INFO Hue passthru Home created. No Hue passtrhu systems configured. com.bwssystems.HABridge.plugins.hue.HueHome 07-19-2019 14:48:12.517 INFO HAL Home created. No HAL devices configured. com.bwssystems.HABridge.plugins.hal.HalHome 07-19-2019 14:48:12.517 INFO MQTT Home created. No MQTT Clients configured. com.bwssystems.HABridge.plugins.mqtt.MQTTHome 07-19-2019 14:48:12.517 INFO HomeAssistant Home created. No HomeAssistants configured. com.bwssystems.HABridge.plugins.hass.HassHome 07-19-2019 14:48:12.518 INFO HomeWizard Home created. No HomeWizard gateways configured. com.bwssystems.HABridge.plugins.homewizard.HomeWizardHome 07-19-2019 14:48:12.518 INFO Command Home for system program execution created. com.bwssystems.HABridge.plugins.exec.CommandHome 07-19-2019 14:48:12.518 INFO TCP Home created. com.bwssystems.HABridge.plugins.tcp.TCPHome 07-19-2019 14:48:12.518 INFO UDP Home created. com.bwssystems.HABridge.plugins.udp.UDPHome 07-19-2019 14:48:12.519 INFO Vera Home created. No Veras configured. com.bwssystems.HABridge.plugins.vera.VeraHome 07-19-2019 14:48:12.519 INFO Fibaro Home created. No Fibaros configured. com.bwssystems.HABridge.plugins.fibaro.FibaroHome 07-19-2019 14:48:12.519 INFO Domoticz Home created. com.bwssystems.HABridge.plugins.domoticz.DomoticzHome 07-19-2019 14:48:12.520 INFO Somfy Home created. No Somfys configured. com.bwssystems.HABridge.plugins.somfy.SomfyHome 07-19-2019 14:48:12.520 INFO LifxDevice Home created. No LifxDevices configured. com.bwssystems.HABridge.plugins.lifx.LifxHome 07-19-2019 14:48:12.520 INFO OpenHAB Home created. No OpenHABs configured. com.bwssystems.HABridge.plugins.openhab.OpenHABHome 07-19-2019 14:48:12.520 INFO FHEM Home created. No FHEMs configured. com.bwssystems.HABridge.plugins.fhem.FHEMHome 07-19-2019 14:48:12.520 INFO Broadlink Home created. No Broadlinks configured. com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome 07-19-2019 14:48:12.521 INFO Mozilla IOT Home created. No Mozilla IOTs configured. com.bwssystems.HABridge.plugins.moziot.MozIotHome 07-19-2019 14:48:12.521 INFO HomeGenie Home created. No HomeGenies configured. com.bwssystems.HABridge.plugins.homegenie.HomeGenieHome 07-19-2019 14:48:12.531 WARN Error reading the file: data/group.db - Does not exist or is not readable. continuing... com.bwssystems.HABridge.dao.GroupRepository 07-19-2019 14:48:12.532 INFO HABridge device management service started.... com.bwssystems.HABridge.devicemanagmeent.DeviceResource 07-19-2019 14:48:12.542 INFO Hue emulator service started.... com.bwssystems.HABridge.hue.HueMulator 07-19-2019 14:48:12.550 INFO Traceupnp: upnp config address: 192.168.1.42 -useIface: true on web server: 192.168.1.42:80 com.bwssystems.HABridge.HABridge 07-19-2019 14:48:12.551 INFO Description xml service started.... com.bwssystems.HABridge.upnp.UpnpSettingsResource 07-19-2019 14:48:12.554 INFO UPNP Discovery Listener starting.... com.bwssystems.HABridge.upnp.UpnpListener 07-19-2019 14:48:12.557 INFO Traceupnp: Interface: eth0 matches upnp config address of IP address: /192.168.1.42 com.bwssystems.HABridge.upnp.UpnpListener 07-19-2019 14:48:12.558 INFO Traceupnp: Adding eth0 to our upnp join interface set. com.bwssystems.HABridge.upnp.UpnpListener 07-19-2019 14:48:12.560 INFO Create and run mDNS service. com.bwssystems.HABridge.upnp.UpnpListener 07-19-2019 14:48:12.573 INFO UPNP Discovery Listener running and ready.... com.bwssystems.HABridge.upnp.UpnpListener 07-19-2019 14:48:12.759 INFO Traceupnp: request of description.xml from: 192.168.1.22:80 filled in with address: 192.168.1.42:80 com.bwssystems.HABridge.upnp.UpnpSettingsResource 07-19-2019 14:48:32.852 INFO Traceupnp: sendUpnpNotify notifyTemplate1 com.bwssystems.HABridge.upnp.UpnpListener 07-19-2019 14:48:33.113 INFO Traceupnp: sendUpnpNotify notifyTemplate2 com.bwssystems.HABridge.upnp.UpnpListener 07-19-2019 14:48:33.375 INFO Traceupnp: sendUpnpNotify notifyTemplate3 com.bwssystems.HABridge.upnp.UpnpListener 07-19-2019 14:48:42.058 INFO Link button pressed.... com.bwssystems.HABridge.SystemControl 07-19-2019 14:48:53.656 INFO Traceupnp: sendUpnpNotify notifyTemplate1 com.bwssystems.HABridge.upnp.UpnpListener 07-19-2019 14:48:53.917 INFO Traceupnp: sendUpnpNotify notifyTemplate2 com.bwssystems.HABridge.upnp.UpnpListener 07-19-2019 14:48:54.179 INFO Traceupnp: sendUpnpNotify notifyTemplate3 com.bwssystems.HABridge.upnp.UpnpListener 07-19-2019 14:49:12.060 INFO Link button time ended.... com.bwssystems.HABridge.LinkButtonPressed 07-19-2019 14:49:14.459 INFO Traceupnp: sendUpnpNotify notifyTemplate1 com.bwssystems.HABridge.upnp.UpnpListener 07-19-2019 14:49:14.721 INFO Traceupnp: sendUpnpNotify notifyTemplate2 com.bwssystems.HABridge.upnp.UpnpListener 07-19-2019 14:49:14.982 INFO Traceupnp: sendUpnpNotify notifyTemplate3 com.bwssystems.HABridge.upnp.UpnpListener

jayjupdhig commented 5 years ago

I think there are problems with gen. 3 device. What generation is your "Echo Input" ?

gcaruncho commented 5 years ago

It's a new device, without a speaker, so, i imagine the latest generation...

jayjupdhig commented 5 years ago

Gen. 3 devices require that ha bridge runs on port 80, then the switch works without problems - as long the device search was successful, but it is not always...

I think there is more a problem with the method that ha-bridge is using to emulate philips hue devices. (On UDP / uPnP layer), so they won't be found sucessful. Mostly i need to start 2 device searches, with a minimal pause of 5-7 seconds..

gcaruncho commented 5 years ago

Ha Bridge uses port 80. Repeated searches do not work either

bwssytems commented 5 years ago

@gcaruncho In your trace above, what is the IP address of the Echo Input?

jayjupdhig commented 5 years ago

Alexa Gen. 3 devices use Port 80 (only).

HA-Bridge can be configured with different ports, e.g. 81 that works with Gen. 2 devices for example

gcaruncho commented 5 years ago

@gcaruncho In your trace above, what is the IP address of the Echo Input?

HA-Bridge IP 192.168.1.42. Port 80 (Domoticz is in the same Raspberry Pi 3) PC 192.168.1.22 Alexa 192.168.1.60

bwssytems commented 5 years ago

@gcaruncho I do not see in your log where the alexa is even trying to discover the ha-bridge. There should be a message from the ip address of 192.168.1.60. Please do multiple discover devices from Alexa while you have the Traceupnp on. Your current log only shows one minute of running.