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

Amazon Echo still not recognize 5.4.0 #1270

Open Jean-Mercier opened 3 years ago

Jean-Mercier commented 3 years ago

Hello Thanks for the release

My device still not recognize by amazon echo. i try :

delete all on amazon side delete all device on ha-bridge side change upnp send delay renumber device

but amazon still not find any device (i have 3 different amazon echo, echo spot, echo dot)

i use a tplink router and upnp is available. habridge run on docker on synology

I don't find the problem.

my conf image

image

thanks

devel6236 commented 3 years ago

Did you use the "Link" Button or is it deactivated in your security settings?

You could try adjust the ID SEED to 400 and then renumber devices. Then search again.

Jean-Mercier commented 3 years ago

Thanks i already test to renumber and change the ID SEED i use the link button

bwssytems commented 3 years ago

Turn off the link button in the security settings. Turn the trace upnp calls on in the bridge control. Post the output of the log after you do a discover from alexa

heffneil commented 3 years ago

I have link button off. I found 55 devices - and they still don't respond.

heffneil commented 3 years ago

Did the same thing - renumbered devices in bridge, deleted all devices on Amazon's site, found 55. Now I can't get them to respond. Logs below:

Time Level Message Component 12-17-2020 09:59:35.790 INFO HA Bridge startup sequence... com.bwssystems.HABridge.HABridge 12-17-2020 09:59:36.110 INFO HA Bridge (v5.4.0) initializing.... com.bwssystems.HABridge.HABridge 12-17-2020 09:59:36.137 INFO reading from config file: data/habridge.config com.bwssystems.HABridge.BridgeSettings 12-17-2020 09:59:36.666 WARN The upnp config address, 192.168.1.203, does not match any known IP's on this host. Using default address: null com.bwssystems.HABridge.BridgeSettings 12-17-2020 09:59:42.201 INFO StaticResourceHandler configured with folder = /public spark.staticfiles.StaticFilesConfiguration 12-17-2020 09:59:42.295 INFO System control service started.... com.bwssystems.HABridge.SystemControl 12-17-2020 09:59:42.440 INFO Initializing UDP response Socket... com.bwssystems.HABridge.util.UDPDatagramSender 12-17-2020 09:59:42.446 INFO UDP response Socket initialized to: 50000 com.bwssystems.HABridge.util.UDPDatagramSender 12-17-2020 09:59:42.450 INFO HTTP Home created. com.bwssystems.HABridge.plugins.http.HTTPHome 12-17-2020 09:59:42.456 INFO Harmony Home created. No Harmony devices configured. com.bwssystems.HABridge.plugins.harmony.HarmonyHome 12-17-2020 09:59:42.458 INFO Nest Home created. No Nest configured. com.bwssystems.HABridge.plugins.NestBridge.NestHome 12-17-2020 09:59:42.459 INFO Hue passthru Home created. No Hue passtrhu systems configured. com.bwssystems.HABridge.plugins.hue.HueHome 12-17-2020 09:59:42.461 INFO HAL Home created. No HAL devices configured. com.bwssystems.HABridge.plugins.hal.HalHome 12-17-2020 09:59:42.462 INFO MQTT Home created. No MQTT Clients configured. com.bwssystems.HABridge.plugins.mqtt.MQTTHome 12-17-2020 09:59:42.464 INFO HomeAssistant Home created. No HomeAssistants configured. com.bwssystems.HABridge.plugins.hass.HassHome 12-17-2020 09:59:42.465 INFO HomeWizard Home created. No HomeWizard gateways configured. com.bwssystems.HABridge.plugins.homewizard.HomeWizardHome 12-17-2020 09:59:42.467 INFO Command Home for system program execution created. com.bwssystems.HABridge.plugins.exec.CommandHome 12-17-2020 09:59:42.468 INFO TCP Home created. com.bwssystems.HABridge.plugins.tcp.TCPHome 12-17-2020 09:59:42.471 INFO UDP Home created. com.bwssystems.HABridge.plugins.udp.UDPHome 12-17-2020 09:59:42.472 INFO Vera Home created. No Veras configured. com.bwssystems.HABridge.plugins.vera.VeraHome 12-17-2020 09:59:42.473 INFO Fibaro Home created. No Fibaros configured. com.bwssystems.HABridge.plugins.fibaro.FibaroHome 12-17-2020 09:59:42.475 INFO Domoticz Home created. No Domoticz devices configured. com.bwssystems.HABridge.plugins.domoticz.DomoticzHome 12-17-2020 09:59:42.476 INFO Somfy Home created. No Somfys configured. com.bwssystems.HABridge.plugins.somfy.SomfyHome 12-17-2020 09:59:42.479 INFO LifxDevice Home created. No LifxDevices configured. com.bwssystems.HABridge.plugins.lifx.LifxHome 12-17-2020 09:59:42.481 INFO OpenHAB Home created. No OpenHABs configured. com.bwssystems.HABridge.plugins.openhab.OpenHABHome 12-17-2020 09:59:42.483 INFO FHEM Home created. No FHEMs configured. com.bwssystems.HABridge.plugins.fhem.FHEMHome 12-17-2020 09:59:42.518 INFO Broadlink Home created. No Broadlinks configured. com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome 12-17-2020 09:59:42.520 INFO Mozilla IOT Home created. No Mozilla IOTs configured. com.bwssystems.HABridge.plugins.moziot.MozIotHome 12-17-2020 09:59:42.521 INFO == Spark has ignited ... spark.embeddedserver.jetty.EmbeddedJettyServer 12-17-2020 09:59:42.521 INFO >> Listening on 0.0.0.0:80 spark.embeddedserver.jetty.EmbeddedJettyServer 12-17-2020 09:59:42.522 INFO HomeGenie Home created. No HomeGenies configured. com.bwssystems.HABridge.plugins.homegenie.HomeGenieHome 12-17-2020 09:59:42.630 INFO HABridge device management service started.... com.bwssystems.HABridge.devicemanagmeent.DeviceResource 12-17-2020 09:59:42.732 INFO Hue emulator service started.... com.bwssystems.HABridge.hue.HueMulator 12-17-2020 09:59:42.810 INFO Traceupnp: upnp config address: 192.168.1.203 -useIface: false on web server: 0.0.0.0:80 com.bwssystems.HABridge.HABridge 12-17-2020 09:59:42.889 INFO Description xml service started.... com.bwssystems.HABridge.upnp.UpnpSettingsResource 12-17-2020 09:59:42.904 INFO UPNP Discovery Listener starting.... com.bwssystems.HABridge.upnp.UpnpListener 12-17-2020 09:59:42.905 INFO Traceupnp: Interface: en0 valid usable IP address: /192.168.1.203 com.bwssystems.HABridge.upnp.UpnpListener 12-17-2020 09:59:42.906 INFO Traceupnp: Adding en0 to our upnp join interface set. com.bwssystems.HABridge.upnp.UpnpListener 12-17-2020 09:59:42.906 INFO Traceupnp: Interface: lo0 valid usable IP address: /127.0.0.1 com.bwssystems.HABridge.upnp.UpnpListener 12-17-2020 09:59:42.906 INFO Traceupnp: Adding lo0 to our upnp join interface set. com.bwssystems.HABridge.upnp.UpnpListener 12-17-2020 09:59:42.906 INFO Create and run mDNS service. com.bwssystems.HABridge.upnp.UpnpListener 12-17-2020 09:59:42.968 INFO UPNP Discovery Listener running and ready.... com.bwssystems.HABridge.upnp.UpnpListener 12-17-2020 10:00:05.734 INFO Traceupnp: hue api user create requested for device type: test_ha_bridge#192.168.2.11 and username: e70392e3a02e46e993c2c0bb221101fa com.bwssystems.HABridge.hue.HueMulator 12-17-2020 10:00:16.126 WARN Could not find device: 50 for hue state change request: ImWQwpewvxiboa76JoLeqs9tNPzEPtVmegQwmoE from 192.168.2.58 body: {"on":false} com.bwssystems.HABridge.hue.HueMulator 12-17-2020 10:00:16.143 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener 12-17-2020 10:00:16.811 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener 12-17-2020 10:00:16.812 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener 12-17-2020 10:00:17.525 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener 12-17-2020 10:00:17.526 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener 12-17-2020 10:00:18.177 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener 12-17-2020 10:00:18.178 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener 12-17-2020 10:00:18.892 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener 12-17-2020 10:00:18.892 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener 12-17-2020 10:00:19.550 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener 12-17-2020 10:00:19.550 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener 12-17-2020 10:00:20.202 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener 12-17-2020 10:02:12.276 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.38:50000 com.bwssystems.HABridge.upnp.UpnpListener 12-17-2020 10:02:12.947 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.38:50000 com.bwssystems.HABridge.upnp.UpnpListener 12-17-2020 10:02:12.947 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.38:50000 com.bwssystems.HABridge.upnp.UpnpListener 12-17-2020 10:02:13.654 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.38:50000 com.bwssystems.HABridge.upnp.UpnpListener 12-17-2020 10:02:13.654 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.38:50000 com.bwssystems.HABridge.upnp.UpnpListener 12-17-2020 10:02:14.341 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.38:50000 com.bwssystems.HABridge.upnp.UpnpListener 12-17-2020 10:02:14.341 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.38:50000 com.bwssystems.HABridge.upnp.UpnpListener 12-17-2020 10:02:15.033 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.38:50000 com.bwssystems.HABridge.upnp.UpnpListener 12-17-2020 10:02:15.034 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.38:50000 com.bwssystems.HABridge.upnp.UpnpListener 12-17-2020 10:02:15.725 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.38:50000 com.bwssystems.HABridge.upnp.UpnpListener 12-17-2020 10:02:15.726 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.38:50000 com.bwssystems.HABridge.upnp.UpnpListener 12-17-2020 10:02:16.451 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.38:50000 com.bwssystems.HABridge.upnp.UpnpListener 12-17-2020 10:02:45.895 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener 12-17-2020 10:02:46.518 INFO Traceupnp: request of description.xml from: 192.168.1.30:80 filled in with address: 0.0.0.0:80 com.bwssystems.HABridge.upnp.UpnpSettingsResource 12-17-2020 10:02:46.569 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener 12-17-2020 10:02:46.570 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener 12-17-2020 10:02:47.265 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener 12-17-2020 10:02:47.266 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener 12-17-2020 10:02:47.987 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener 12-17-2020 10:02:47.987 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener 12-17-2020 10:02:48.641 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener 12-17-2020 10:02:48.641 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener 12-17-2020 10:02:49.366 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener 12-17-2020 10:02:49.367 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener 12-17-2020 10:02:50.076 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener 12-17-2020 10:02:50.077 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.70:50000 com.bwssystems.HABridge.upnp.UpnpListener 12-17-2020 10:02:50.785 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.70:50000 com.bwssystems.HABridge.upnp.UpnpListener 12-17-2020 10:02:50.786 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.70:50000 com.bwssystems.HABridge.upnp.UpnpListener 12-17-2020 10:02:51.503 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.70:50000 com.bwssystems.HABridge.upnp.UpnpListener 12-17-2020 10:02:51.503 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.70:50000 com.bwssystems.HABridge.upnp.UpnpListener 12-17-2020 10:02:52.228 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.70:50000 com.bwssystems.HABridge.upnp.UpnpListener 12-17-2020 10:02:52.228 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.70:50000 com.bwssystems.HABridge.upnp.UpnpListener 12-17-2020 10:02:52.941 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.70:50000 com.bwssystems.HABridge.upnp.UpnpListener 12-17-2020 10:02:52.942 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.70:50000 com.bwssystems.HABridge.upnp.UpnpListener 12-17-2020 10:02:53.639 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.70:50000 com.bwssystems.HABridge.upnp.UpnpListener 12-17-2020 10:02:53.639 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.70:50000 com.bwssystems.HABridge.upnp.UpnpListener 12-17-2020 10:02:54.291 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.70:50000 com.bwssystems.HABridge.upnp.UpnpListener 12-17-2020 10:02:54.292 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.98:50000 com.bwssystems.HABridge.upnp.UpnpListener 12-17-2020 10:02:54.996 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.98:50000 com.bwssystems.HABridge.upnp.UpnpListener 12-17-2020 10:02:54.996 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.98:50000 com.bwssystems.HABridge.upnp.UpnpListener 12-17-2020 10:02:55.673 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.98:50000 com.bwssystems.HABridge.upnp.UpnpListener 12-17-2020 10:02:55.674 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.98:50000 com.bwssystems.HABridge.upnp.UpnpListener 12-17-2020 10:02:56.397 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.98:50000 com.bwssystems.HABridge.upnp.UpnpListener 12-17-2020 10:02:56.398 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.98:50000 com.bwssystems.HABridge.upnp.UpnpListener 12-17-2020 10:02:57.112 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.98:50000 com.bwssystems.HABridge.upnp.UpnpListener 12-17-2020 10:02:57.112 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.98:50000 com.bwssystems.HABridge.upnp.UpnpListener 12-17-2020 10:02:57.822 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.98:50000 com.bwssystems.HABridge.upnp.UpnpListener 12-17-2020 10:02:57.822 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.98:50000 com.bwssystems.HABridge.upnp.UpnpListener 12-17-2020 10:02:58.219 INFO Traceupnp: hue api user create requested for device type: test_ha_bridge#192.168.2.11 and username: e70392e3a02e46e993c2c0bb221101fa com.bwssystems.HABridge.hue.HueMulator 12-17-2020 10:02:58.536 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.98:50000 com.bwssystems.HABridge.upnp.UpnpListener 12-17-2020 10:02:58.537 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.49:50000 com.bwssystems.HABridge.upnp.UpnpListener 12-17-2020 10:02:59.239 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.49:50000 com.bwssystems.HABridge.upnp.UpnpListener 12-17-2020 10:02:59.239 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.49:50000 com.bwssystems.HABridge.upnp.UpnpListener 12-17-2020 10:02:59.901 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.49:50000 com.bwssystems.HABridge.upnp.UpnpListener 12-17-2020 10:02:59.902 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.49:50000 com.bwssystems.HABridge.upnp.UpnpListener 12-17-2020 10:03:00.597 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.49:50000 com.bwssystems.HABridge.upnp.UpnpListener 12-17-2020 10:03:00.597 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.49:50000 com.bwssystems.HABridge.upnp.UpnpListener 12-17-2020 10:03:01.309 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.49:50000 com.bwssystems.HABridge.upnp.UpnpListener 12-17-2020 10:03:01.310 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.49:50000 com.bwssystems.HABridge.upnp.UpnpListener 12-17-2020 10:03:02.005 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.49:50000 com.bwssystems.HABridge.upnp.UpnpListener 12-17-2020 10:03:02.006 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.49:50000 com.bwssystems.HABridge.upnp.UpnpListener 12-17-2020 10:03:02.677 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.49:50000 com.bwssystems.HABridge.upnp.UpnpListener 12-17-2020 10:03:02.677 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.4:50000 com.bwssystems.HABridge.upnp.UpnpListener 12-17-2020 10:03:03.381 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.4:50000 com.bwssystems.HABridge.upnp.UpnpListener 12-17-2020 10:03:03.381 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.4:50000 com.bwssystems.HABridge.upnp.UpnpListener 12-17-2020 10:03:04.103 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.4:50000 com.bwssystems.HABridge.upnp.UpnpListener 12-17-2020 10:03:43.736 INFO Traceupnp: hue api user create requested for device type: test_ha_bridge#192.168.2.11 and username: e70392e3a02e46e993c2c0bb221101fa com.bwssystems.HABridge.hue.HueMulator Time Level Message Component
12-17-2020 09:59:35.790 INFO HA Bridge startup sequence... com.bwssystems.HABridge.HABridge
12-17-2020 09:59:36.110 INFO HA Bridge (v5.4.0) initializing.... com.bwssystems.HABridge.HABridge
12-17-2020 09:59:36.137 INFO reading from config file: data/habridge.config com.bwssystems.HABridge.BridgeSettings
12-17-2020 09:59:36.666 WARN The upnp config address, 192.168.1.203, does not match any known IP's on this host. Using default address: null com.bwssystems.HABridge.BridgeSettings
12-17-2020 09:59:42.201 INFO StaticResourceHandler configured with folder = /public spark.staticfiles.StaticFilesConfiguration
12-17-2020 09:59:42.295 INFO System control service started.... com.bwssystems.HABridge.SystemControl
12-17-2020 09:59:42.440 INFO Initializing UDP response Socket... com.bwssystems.HABridge.util.UDPDatagramSender
12-17-2020 09:59:42.446 INFO UDP response Socket initialized to: 50000 com.bwssystems.HABridge.util.UDPDatagramSender
12-17-2020 09:59:42.450 INFO HTTP Home created. com.bwssystems.HABridge.plugins.http.HTTPHome
12-17-2020 09:59:42.456 INFO Harmony Home created. No Harmony devices configured. com.bwssystems.HABridge.plugins.harmony.HarmonyHome
12-17-2020 09:59:42.458 INFO Nest Home created. No Nest configured. com.bwssystems.HABridge.plugins.NestBridge.NestHome
12-17-2020 09:59:42.459 INFO Hue passthru Home created. No Hue passtrhu systems configured. com.bwssystems.HABridge.plugins.hue.HueHome
12-17-2020 09:59:42.461 INFO HAL Home created. No HAL devices configured. com.bwssystems.HABridge.plugins.hal.HalHome
12-17-2020 09:59:42.462 INFO MQTT Home created. No MQTT Clients configured. com.bwssystems.HABridge.plugins.mqtt.MQTTHome
12-17-2020 09:59:42.464 INFO HomeAssistant Home created. No HomeAssistants configured. com.bwssystems.HABridge.plugins.hass.HassHome
12-17-2020 09:59:42.465 INFO HomeWizard Home created. No HomeWizard gateways configured. com.bwssystems.HABridge.plugins.homewizard.HomeWizardHome
12-17-2020 09:59:42.467 INFO Command Home for system program execution created. com.bwssystems.HABridge.plugins.exec.CommandHome
12-17-2020 09:59:42.468 INFO TCP Home created. com.bwssystems.HABridge.plugins.tcp.TCPHome
12-17-2020 09:59:42.471 INFO UDP Home created. com.bwssystems.HABridge.plugins.udp.UDPHome
12-17-2020 09:59:42.472 INFO Vera Home created. No Veras configured. com.bwssystems.HABridge.plugins.vera.VeraHome
12-17-2020 09:59:42.473 INFO Fibaro Home created. No Fibaros configured. com.bwssystems.HABridge.plugins.fibaro.FibaroHome
12-17-2020 09:59:42.475 INFO Domoticz Home created. No Domoticz devices configured. com.bwssystems.HABridge.plugins.domoticz.DomoticzHome
12-17-2020 09:59:42.476 INFO Somfy Home created. No Somfys configured. com.bwssystems.HABridge.plugins.somfy.SomfyHome
12-17-2020 09:59:42.479 INFO LifxDevice Home created. No LifxDevices configured. com.bwssystems.HABridge.plugins.lifx.LifxHome
12-17-2020 09:59:42.481 INFO OpenHAB Home created. No OpenHABs configured. com.bwssystems.HABridge.plugins.openhab.OpenHABHome
12-17-2020 09:59:42.483 INFO FHEM Home created. No FHEMs configured. com.bwssystems.HABridge.plugins.fhem.FHEMHome
12-17-2020 09:59:42.518 INFO Broadlink Home created. No Broadlinks configured. com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome
12-17-2020 09:59:42.520 INFO Mozilla IOT Home created. No Mozilla IOTs configured. com.bwssystems.HABridge.plugins.moziot.MozIotHome
12-17-2020 09:59:42.521 INFO == Spark has ignited ... spark.embeddedserver.jetty.EmbeddedJettyServer
12-17-2020 09:59:42.521 INFO >> Listening on 0.0.0.0:80 spark.embeddedserver.jetty.EmbeddedJettyServer
12-17-2020 09:59:42.522 INFO HomeGenie Home created. No HomeGenies configured. com.bwssystems.HABridge.plugins.homegenie.HomeGenieHome
12-17-2020 09:59:42.630 INFO HABridge device management service started.... com.bwssystems.HABridge.devicemanagmeent.DeviceResource
12-17-2020 09:59:42.732 INFO Hue emulator service started.... com.bwssystems.HABridge.hue.HueMulator
12-17-2020 09:59:42.810 INFO Traceupnp: upnp config address: 192.168.1.203 -useIface: false on web server: 0.0.0.0:80 com.bwssystems.HABridge.HABridge
12-17-2020 09:59:42.889 INFO Description xml service started.... com.bwssystems.HABridge.upnp.UpnpSettingsResource
12-17-2020 09:59:42.904 INFO UPNP Discovery Listener starting.... com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 09:59:42.905 INFO Traceupnp: Interface: en0 valid usable IP address: /192.168.1.203 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 09:59:42.906 INFO Traceupnp: Adding en0 to our upnp join interface set. com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 09:59:42.906 INFO Traceupnp: Interface: lo0 valid usable IP address: /127.0.0.1 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 09:59:42.906 INFO Traceupnp: Adding lo0 to our upnp join interface set. com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 09:59:42.906 INFO Create and run mDNS service. com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 09:59:42.968 INFO UPNP Discovery Listener running and ready.... com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:00:05.734 INFO Traceupnp: hue api user create requested for device type: test_ha_bridge#192.168.2.11 and username: e70392e3a02e46e993c2c0bb221101fa com.bwssystems.HABridge.hue.HueMulator
12-17-2020 10:00:16.126 WARN Could not find device: 50 for hue state change request: ImWQwpewvxiboa76JoLeqs9tNPzEPtVmegQwmoE from 192.168.2.58 body: {"on":false} com.bwssystems.HABridge.hue.HueMulator
12-17-2020 10:00:16.143 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:00:16.811 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:00:16.812 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:00:17.525 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:00:17.526 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:00:18.177 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:00:18.178 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:00:18.892 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:00:18.892 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:00:19.550 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:00:19.550 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:00:20.202 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:12.276 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.38:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:12.947 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.38:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:12.947 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.38:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:13.654 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.38:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:13.654 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.38:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:14.341 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.38:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:14.341 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.38:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:15.033 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.38:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:15.034 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.38:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:15.725 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.38:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:15.726 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.38:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:16.451 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.38:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:45.895 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:46.518 INFO Traceupnp: request of description.xml from: 192.168.1.30:80 filled in with address: 0.0.0.0:80 com.bwssystems.HABridge.upnp.UpnpSettingsResource
12-17-2020 10:02:46.569 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:46.570 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:47.265 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:47.266 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:47.987 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:47.987 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:48.641 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:48.641 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:49.366 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:49.367 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:50.076 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:50.077 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.70:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:50.785 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.70:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:50.786 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.70:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:51.503 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.70:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:51.503 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.70:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:52.228 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.70:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:52.228 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.70:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:52.941 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.70:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:52.942 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.70:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:53.639 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.70:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:53.639 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.70:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:54.291 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.70:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:54.292 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.98:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:54.996 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.98:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:54.996 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.98:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:55.673 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.98:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:55.674 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.98:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:56.397 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.98:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:56.398 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.98:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:57.112 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.98:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:57.112 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.98:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:57.822 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.98:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:57.822 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.98:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:58.219 INFO Traceupnp: hue api user create requested for device type: test_ha_bridge#192.168.2.11 and username: e70392e3a02e46e993c2c0bb221101fa com.bwssystems.HABridge.hue.HueMulator
12-17-2020 10:02:58.536 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.98:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:58.537 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.49:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:59.239 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.49:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:59.239 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.49:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:59.901 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.49:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:59.902 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.49:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:03:00.597 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.49:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:03:00.597 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.49:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:03:01.309 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.49:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:03:01.310 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.49:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:03:02.005 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.49:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:03:02.006 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.49:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:03:02.677 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.49:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:03:02.677 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.4:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:03:03.381 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.4:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:03:03.381 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.4:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:03:04.103 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.4:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:03:43.736 INFO Traceupnp: hue api user create requested for device type: test_ha_bridge#192.168.2.11 and username: e70392e3a02e46e993c2c0bb221101fa com.bwssystems.HABridge.hue.HueMulator
Time Level Message Component
12-17-2020 09:59:35.790 INFO HA Bridge startup sequence... com.bwssystems.HABridge.HABridge
12-17-2020 09:59:36.110 INFO HA Bridge (v5.4.0) initializing.... com.bwssystems.HABridge.HABridge
12-17-2020 09:59:36.137 INFO reading from config file: data/habridge.config com.bwssystems.HABridge.BridgeSettings
12-17-2020 09:59:36.666 WARN The upnp config address, 192.168.1.203, does not match any known IP's on this host. Using default address: null com.bwssystems.HABridge.BridgeSettings
12-17-2020 09:59:42.201 INFO StaticResourceHandler configured with folder = /public spark.staticfiles.StaticFilesConfiguration
12-17-2020 09:59:42.295 INFO System control service started.... com.bwssystems.HABridge.SystemControl
12-17-2020 09:59:42.440 INFO Initializing UDP response Socket... com.bwssystems.HABridge.util.UDPDatagramSender
12-17-2020 09:59:42.446 INFO UDP response Socket initialized to: 50000 com.bwssystems.HABridge.util.UDPDatagramSender
12-17-2020 09:59:42.450 INFO HTTP Home created. com.bwssystems.HABridge.plugins.http.HTTPHome
12-17-2020 09:59:42.456 INFO Harmony Home created. No Harmony devices configured. com.bwssystems.HABridge.plugins.harmony.HarmonyHome
12-17-2020 09:59:42.458 INFO Nest Home created. No Nest configured. com.bwssystems.HABridge.plugins.NestBridge.NestHome
12-17-2020 09:59:42.459 INFO Hue passthru Home created. No Hue passtrhu systems configured. com.bwssystems.HABridge.plugins.hue.HueHome
12-17-2020 09:59:42.461 INFO HAL Home created. No HAL devices configured. com.bwssystems.HABridge.plugins.hal.HalHome
12-17-2020 09:59:42.462 INFO MQTT Home created. No MQTT Clients configured. com.bwssystems.HABridge.plugins.mqtt.MQTTHome
12-17-2020 09:59:42.464 INFO HomeAssistant Home created. No HomeAssistants configured. com.bwssystems.HABridge.plugins.hass.HassHome
12-17-2020 09:59:42.465 INFO HomeWizard Home created. No HomeWizard gateways configured. com.bwssystems.HABridge.plugins.homewizard.HomeWizardHome
12-17-2020 09:59:42.467 INFO Command Home for system program execution created. com.bwssystems.HABridge.plugins.exec.CommandHome
12-17-2020 09:59:42.468 INFO TCP Home created. com.bwssystems.HABridge.plugins.tcp.TCPHome
12-17-2020 09:59:42.471 INFO UDP Home created. com.bwssystems.HABridge.plugins.udp.UDPHome
12-17-2020 09:59:42.472 INFO Vera Home created. No Veras configured. com.bwssystems.HABridge.plugins.vera.VeraHome
12-17-2020 09:59:42.473 INFO Fibaro Home created. No Fibaros configured. com.bwssystems.HABridge.plugins.fibaro.FibaroHome
12-17-2020 09:59:42.475 INFO Domoticz Home created. No Domoticz devices configured. com.bwssystems.HABridge.plugins.domoticz.DomoticzHome
12-17-2020 09:59:42.476 INFO Somfy Home created. No Somfys configured. com.bwssystems.HABridge.plugins.somfy.SomfyHome
12-17-2020 09:59:42.479 INFO LifxDevice Home created. No LifxDevices configured. com.bwssystems.HABridge.plugins.lifx.LifxHome
12-17-2020 09:59:42.481 INFO OpenHAB Home created. No OpenHABs configured. com.bwssystems.HABridge.plugins.openhab.OpenHABHome
12-17-2020 09:59:42.483 INFO FHEM Home created. No FHEMs configured. com.bwssystems.HABridge.plugins.fhem.FHEMHome
12-17-2020 09:59:42.518 INFO Broadlink Home created. No Broadlinks configured. com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome
12-17-2020 09:59:42.520 INFO Mozilla IOT Home created. No Mozilla IOTs configured. com.bwssystems.HABridge.plugins.moziot.MozIotHome
12-17-2020 09:59:42.521 INFO == Spark has ignited ... spark.embeddedserver.jetty.EmbeddedJettyServer
12-17-2020 09:59:42.521 INFO >> Listening on 0.0.0.0:80 spark.embeddedserver.jetty.EmbeddedJettyServer
12-17-2020 09:59:42.522 INFO HomeGenie Home created. No HomeGenies configured. com.bwssystems.HABridge.plugins.homegenie.HomeGenieHome
12-17-2020 09:59:42.630 INFO HABridge device management service started.... com.bwssystems.HABridge.devicemanagmeent.DeviceResource
12-17-2020 09:59:42.732 INFO Hue emulator service started.... com.bwssystems.HABridge.hue.HueMulator
12-17-2020 09:59:42.810 INFO Traceupnp: upnp config address: 192.168.1.203 -useIface: false on web server: 0.0.0.0:80 com.bwssystems.HABridge.HABridge
12-17-2020 09:59:42.889 INFO Description xml service started.... com.bwssystems.HABridge.upnp.UpnpSettingsResource
12-17-2020 09:59:42.904 INFO UPNP Discovery Listener starting.... com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 09:59:42.905 INFO Traceupnp: Interface: en0 valid usable IP address: /192.168.1.203 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 09:59:42.906 INFO Traceupnp: Adding en0 to our upnp join interface set. com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 09:59:42.906 INFO Traceupnp: Interface: lo0 valid usable IP address: /127.0.0.1 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 09:59:42.906 INFO Traceupnp: Adding lo0 to our upnp join interface set. com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 09:59:42.906 INFO Create and run mDNS service. com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 09:59:42.968 INFO UPNP Discovery Listener running and ready.... com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:00:05.734 INFO Traceupnp: hue api user create requested for device type: test_ha_bridge#192.168.2.11 and username: e70392e3a02e46e993c2c0bb221101fa com.bwssystems.HABridge.hue.HueMulator
12-17-2020 10:00:16.126 WARN Could not find device: 50 for hue state change request: ImWQwpewvxiboa76JoLeqs9tNPzEPtVmegQwmoE from 192.168.2.58 body: {"on":false} com.bwssystems.HABridge.hue.HueMulator
12-17-2020 10:00:16.143 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:00:16.811 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:00:16.812 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:00:17.525 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:00:17.526 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:00:18.177 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:00:18.178 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:00:18.892 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:00:18.892 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:00:19.550 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:00:19.550 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:00:20.202 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:12.276 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.38:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:12.947 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.38:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:12.947 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.38:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:13.654 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.38:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:13.654 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.38:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:14.341 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.38:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:14.341 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.38:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:15.033 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.38:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:15.034 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.38:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:15.725 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.38:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:15.726 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.38:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:16.451 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.38:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:45.895 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:46.518 INFO Traceupnp: request of description.xml from: 192.168.1.30:80 filled in with address: 0.0.0.0:80 com.bwssystems.HABridge.upnp.UpnpSettingsResource
12-17-2020 10:02:46.569 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:46.570 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:47.265 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:47.266 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:47.987 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:47.987 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:48.641 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:48.641 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:49.366 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:49.367 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:50.076 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:50.077 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.70:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:50.785 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.70:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:50.786 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.70:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:51.503 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.70:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:51.503 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.70:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:52.228 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.70:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:52.228 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.70:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:52.941 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.70:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:52.942 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.70:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:53.639 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.70:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:53.639 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.70:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:54.291 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.70:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:54.292 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.98:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:54.996 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.98:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:54.996 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.98:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:55.673 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.98:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:55.674 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.98:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:56.397 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.98:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:56.398 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.98:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:57.112 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.98:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:57.112 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.98:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:57.822 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.98:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:57.822 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.98:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:58.219 INFO Traceupnp: hue api user create requested for device type: test_ha_bridge#192.168.2.11 and username: e70392e3a02e46e993c2c0bb221101fa com.bwssystems.HABridge.hue.HueMulator
12-17-2020 10:02:58.536 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.98:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:58.537 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.49:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:59.239 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.49:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:59.239 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.49:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:59.901 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.49:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:59.902 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.49:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:03:00.597 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.49:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:03:00.597 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.49:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:03:01.309 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.49:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:03:01.310 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.49:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:03:02.005 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.49:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:03:02.006 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.49:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:03:02.677 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.49:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:03:02.677 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.4:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:03:03.381 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.4:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:03:03.381 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.4:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:03:04.103 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.4:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:03:43.736 INFO Traceupnp: hue api user create requested for device type: test_ha_bridge#192.168.2.11 and username: e70392e3a02e46e993c2c0bb221101fa com.bwssystems.HABridge.hue.HueMulator
Time Level Message Component
12-17-2020 09:59:35.790 INFO HA Bridge startup sequence... com.bwssystems.HABridge.HABridge
12-17-2020 09:59:36.110 INFO HA Bridge (v5.4.0) initializing.... com.bwssystems.HABridge.HABridge
12-17-2020 09:59:36.137 INFO reading from config file: data/habridge.config com.bwssystems.HABridge.BridgeSettings
12-17-2020 09:59:36.666 WARN The upnp config address, 192.168.1.203, does not match any known IP's on this host. Using default address: null com.bwssystems.HABridge.BridgeSettings
12-17-2020 09:59:42.201 INFO StaticResourceHandler configured with folder = /public spark.staticfiles.StaticFilesConfiguration
12-17-2020 09:59:42.295 INFO System control service started.... com.bwssystems.HABridge.SystemControl
12-17-2020 09:59:42.440 INFO Initializing UDP response Socket... com.bwssystems.HABridge.util.UDPDatagramSender
12-17-2020 09:59:42.446 INFO UDP response Socket initialized to: 50000 com.bwssystems.HABridge.util.UDPDatagramSender
12-17-2020 09:59:42.450 INFO HTTP Home created. com.bwssystems.HABridge.plugins.http.HTTPHome
12-17-2020 09:59:42.456 INFO Harmony Home created. No Harmony devices configured. com.bwssystems.HABridge.plugins.harmony.HarmonyHome
12-17-2020 09:59:42.458 INFO Nest Home created. No Nest configured. com.bwssystems.HABridge.plugins.NestBridge.NestHome
12-17-2020 09:59:42.459 INFO Hue passthru Home created. No Hue passtrhu systems configured. com.bwssystems.HABridge.plugins.hue.HueHome
12-17-2020 09:59:42.461 INFO HAL Home created. No HAL devices configured. com.bwssystems.HABridge.plugins.hal.HalHome
12-17-2020 09:59:42.462 INFO MQTT Home created. No MQTT Clients configured. com.bwssystems.HABridge.plugins.mqtt.MQTTHome
12-17-2020 09:59:42.464 INFO HomeAssistant Home created. No HomeAssistants configured. com.bwssystems.HABridge.plugins.hass.HassHome
12-17-2020 09:59:42.465 INFO HomeWizard Home created. No HomeWizard gateways configured. com.bwssystems.HABridge.plugins.homewizard.HomeWizardHome
12-17-2020 09:59:42.467 INFO Command Home for system program execution created. com.bwssystems.HABridge.plugins.exec.CommandHome
12-17-2020 09:59:42.468 INFO TCP Home created. com.bwssystems.HABridge.plugins.tcp.TCPHome
12-17-2020 09:59:42.471 INFO UDP Home created. com.bwssystems.HABridge.plugins.udp.UDPHome
12-17-2020 09:59:42.472 INFO Vera Home created. No Veras configured. com.bwssystems.HABridge.plugins.vera.VeraHome
12-17-2020 09:59:42.473 INFO Fibaro Home created. No Fibaros configured. com.bwssystems.HABridge.plugins.fibaro.FibaroHome
12-17-2020 09:59:42.475 INFO Domoticz Home created. No Domoticz devices configured. com.bwssystems.HABridge.plugins.domoticz.DomoticzHome
12-17-2020 09:59:42.476 INFO Somfy Home created. No Somfys configured. com.bwssystems.HABridge.plugins.somfy.SomfyHome
12-17-2020 09:59:42.479 INFO LifxDevice Home created. No LifxDevices configured. com.bwssystems.HABridge.plugins.lifx.LifxHome
12-17-2020 09:59:42.481 INFO OpenHAB Home created. No OpenHABs configured. com.bwssystems.HABridge.plugins.openhab.OpenHABHome
12-17-2020 09:59:42.483 INFO FHEM Home created. No FHEMs configured. com.bwssystems.HABridge.plugins.fhem.FHEMHome
12-17-2020 09:59:42.518 INFO Broadlink Home created. No Broadlinks configured. com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome
12-17-2020 09:59:42.520 INFO Mozilla IOT Home created. No Mozilla IOTs configured. com.bwssystems.HABridge.plugins.moziot.MozIotHome
12-17-2020 09:59:42.521 INFO == Spark has ignited ... spark.embeddedserver.jetty.EmbeddedJettyServer
12-17-2020 09:59:42.521 INFO >> Listening on 0.0.0.0:80 spark.embeddedserver.jetty.EmbeddedJettyServer
12-17-2020 09:59:42.522 INFO HomeGenie Home created. No HomeGenies configured. com.bwssystems.HABridge.plugins.homegenie.HomeGenieHome
12-17-2020 09:59:42.630 INFO HABridge device management service started.... com.bwssystems.HABridge.devicemanagmeent.DeviceResource
12-17-2020 09:59:42.732 INFO Hue emulator service started.... com.bwssystems.HABridge.hue.HueMulator
12-17-2020 09:59:42.810 INFO Traceupnp: upnp config address: 192.168.1.203 -useIface: false on web server: 0.0.0.0:80 com.bwssystems.HABridge.HABridge
12-17-2020 09:59:42.889 INFO Description xml service started.... com.bwssystems.HABridge.upnp.UpnpSettingsResource
12-17-2020 09:59:42.904 INFO UPNP Discovery Listener starting.... com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 09:59:42.905 INFO Traceupnp: Interface: en0 valid usable IP address: /192.168.1.203 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 09:59:42.906 INFO Traceupnp: Adding en0 to our upnp join interface set. com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 09:59:42.906 INFO Traceupnp: Interface: lo0 valid usable IP address: /127.0.0.1 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 09:59:42.906 INFO Traceupnp: Adding lo0 to our upnp join interface set. com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 09:59:42.906 INFO Create and run mDNS service. com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 09:59:42.968 INFO UPNP Discovery Listener running and ready.... com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:00:05.734 INFO Traceupnp: hue api user create requested for device type: test_ha_bridge#192.168.2.11 and username: e70392e3a02e46e993c2c0bb221101fa com.bwssystems.HABridge.hue.HueMulator
12-17-2020 10:00:16.126 WARN Could not find device: 50 for hue state change request: ImWQwpewvxiboa76JoLeqs9tNPzEPtVmegQwmoE from 192.168.2.58 body: {"on":false} com.bwssystems.HABridge.hue.HueMulator
12-17-2020 10:00:16.143 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:00:16.811 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:00:16.812 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:00:17.525 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:00:17.526 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:00:18.177 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:00:18.178 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:00:18.892 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:00:18.892 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:00:19.550 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:00:19.550 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:00:20.202 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:12.276 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.38:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:12.947 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.38:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:12.947 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.38:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:13.654 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.38:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:13.654 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.38:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:14.341 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.38:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:14.341 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.38:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:15.033 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.38:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:15.034 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.38:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:15.725 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.38:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:15.726 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.38:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:16.451 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.38:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:45.895 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:46.518 INFO Traceupnp: request of description.xml from: 192.168.1.30:80 filled in with address: 0.0.0.0:80 com.bwssystems.HABridge.upnp.UpnpSettingsResource
12-17-2020 10:02:46.569 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:46.570 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:47.265 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:47.266 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:47.987 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:47.987 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:48.641 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:48.641 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:49.366 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:49.367 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:50.076 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:50.077 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.70:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:50.785 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.70:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:50.786 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.70:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:51.503 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.70:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:51.503 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.70:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:52.228 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.70:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:52.228 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.70:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:52.941 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.70:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:52.942 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.70:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:53.639 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.70:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:53.639 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.70:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:54.291 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.70:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:54.292 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.98:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:54.996 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.98:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:54.996 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.98:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:55.673 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.98:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:55.674 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.98:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:56.397 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.98:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:56.398 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.98:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:57.112 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.98:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:57.112 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.98:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:57.822 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.98:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:57.822 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.98:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:58.219 INFO Traceupnp: hue api user create requested for device type: test_ha_bridge#192.168.2.11 and username: e70392e3a02e46e993c2c0bb221101fa com.bwssystems.HABridge.hue.HueMulator
12-17-2020 10:02:58.536 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.98:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:58.537 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.49:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:59.239 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.49:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:59.239 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.49:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:59.901 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.49:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:59.902 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.49:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:03:00.597 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.49:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:03:00.597 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.49:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:03:01.309 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.49:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:03:01.310 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.49:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:03:02.005 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.49:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:03:02.006 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.49:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:03:02.677 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.49:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:03:02.677 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.4:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:03:03.381 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.4:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:03:03.381 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.4:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:03:04.103 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.4:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:03:43.736 INFO Traceupnp: hue api user create requested for device type: test_ha_bridge#192.168.2.11 and username: e70392e3a02e46e993c2c0bb221101fa com.bwssystems.HABridge.hue.HueMulator
Time Level Message Component
12-17-2020 09:59:35.790 INFO HA Bridge startup sequence... com.bwssystems.HABridge.HABridge
12-17-2020 09:59:36.110 INFO HA Bridge (v5.4.0) initializing.... com.bwssystems.HABridge.HABridge
12-17-2020 09:59:36.137 INFO reading from config file: data/habridge.config com.bwssystems.HABridge.BridgeSettings
12-17-2020 09:59:36.666 WARN The upnp config address, 192.168.1.203, does not match any known IP's on this host. Using default address: null com.bwssystems.HABridge.BridgeSettings
12-17-2020 09:59:42.201 INFO StaticResourceHandler configured with folder = /public spark.staticfiles.StaticFilesConfiguration
12-17-2020 09:59:42.295 INFO System control service started.... com.bwssystems.HABridge.SystemControl
12-17-2020 09:59:42.440 INFO Initializing UDP response Socket... com.bwssystems.HABridge.util.UDPDatagramSender
12-17-2020 09:59:42.446 INFO UDP response Socket initialized to: 50000 com.bwssystems.HABridge.util.UDPDatagramSender
12-17-2020 09:59:42.450 INFO HTTP Home created. com.bwssystems.HABridge.plugins.http.HTTPHome
12-17-2020 09:59:42.456 INFO Harmony Home created. No Harmony devices configured. com.bwssystems.HABridge.plugins.harmony.HarmonyHome
12-17-2020 09:59:42.458 INFO Nest Home created. No Nest configured. com.bwssystems.HABridge.plugins.NestBridge.NestHome
12-17-2020 09:59:42.459 INFO Hue passthru Home created. No Hue passtrhu systems configured. com.bwssystems.HABridge.plugins.hue.HueHome
12-17-2020 09:59:42.461 INFO HAL Home created. No HAL devices configured. com.bwssystems.HABridge.plugins.hal.HalHome
12-17-2020 09:59:42.462 INFO MQTT Home created. No MQTT Clients configured. com.bwssystems.HABridge.plugins.mqtt.MQTTHome
12-17-2020 09:59:42.464 INFO HomeAssistant Home created. No HomeAssistants configured. com.bwssystems.HABridge.plugins.hass.HassHome
12-17-2020 09:59:42.465 INFO HomeWizard Home created. No HomeWizard gateways configured. com.bwssystems.HABridge.plugins.homewizard.HomeWizardHome
12-17-2020 09:59:42.467 INFO Command Home for system program execution created. com.bwssystems.HABridge.plugins.exec.CommandHome
12-17-2020 09:59:42.468 INFO TCP Home created. com.bwssystems.HABridge.plugins.tcp.TCPHome
12-17-2020 09:59:42.471 INFO UDP Home created. com.bwssystems.HABridge.plugins.udp.UDPHome
12-17-2020 09:59:42.472 INFO Vera Home created. No Veras configured. com.bwssystems.HABridge.plugins.vera.VeraHome
12-17-2020 09:59:42.473 INFO Fibaro Home created. No Fibaros configured. com.bwssystems.HABridge.plugins.fibaro.FibaroHome
12-17-2020 09:59:42.475 INFO Domoticz Home created. No Domoticz devices configured. com.bwssystems.HABridge.plugins.domoticz.DomoticzHome
12-17-2020 09:59:42.476 INFO Somfy Home created. No Somfys configured. com.bwssystems.HABridge.plugins.somfy.SomfyHome
12-17-2020 09:59:42.479 INFO LifxDevice Home created. No LifxDevices configured. com.bwssystems.HABridge.plugins.lifx.LifxHome
12-17-2020 09:59:42.481 INFO OpenHAB Home created. No OpenHABs configured. com.bwssystems.HABridge.plugins.openhab.OpenHABHome
12-17-2020 09:59:42.483 INFO FHEM Home created. No FHEMs configured. com.bwssystems.HABridge.plugins.fhem.FHEMHome
12-17-2020 09:59:42.518 INFO Broadlink Home created. No Broadlinks configured. com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome
12-17-2020 09:59:42.520 INFO Mozilla IOT Home created. No Mozilla IOTs configured. com.bwssystems.HABridge.plugins.moziot.MozIotHome
12-17-2020 09:59:42.521 INFO == Spark has ignited ... spark.embeddedserver.jetty.EmbeddedJettyServer
12-17-2020 09:59:42.521 INFO >> Listening on 0.0.0.0:80 spark.embeddedserver.jetty.EmbeddedJettyServer
12-17-2020 09:59:42.522 INFO HomeGenie Home created. No HomeGenies configured. com.bwssystems.HABridge.plugins.homegenie.HomeGenieHome
12-17-2020 09:59:42.630 INFO HABridge device management service started.... com.bwssystems.HABridge.devicemanagmeent.DeviceResource
12-17-2020 09:59:42.732 INFO Hue emulator service started.... com.bwssystems.HABridge.hue.HueMulator
12-17-2020 09:59:42.810 INFO Traceupnp: upnp config address: 192.168.1.203 -useIface: false on web server: 0.0.0.0:80 com.bwssystems.HABridge.HABridge
12-17-2020 09:59:42.889 INFO Description xml service started.... com.bwssystems.HABridge.upnp.UpnpSettingsResource
12-17-2020 09:59:42.904 INFO UPNP Discovery Listener starting.... com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 09:59:42.905 INFO Traceupnp: Interface: en0 valid usable IP address: /192.168.1.203 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 09:59:42.906 INFO Traceupnp: Adding en0 to our upnp join interface set. com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 09:59:42.906 INFO Traceupnp: Interface: lo0 valid usable IP address: /127.0.0.1 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 09:59:42.906 INFO Traceupnp: Adding lo0 to our upnp join interface set. com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 09:59:42.906 INFO Create and run mDNS service. com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 09:59:42.968 INFO UPNP Discovery Listener running and ready.... com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:00:05.734 INFO Traceupnp: hue api user create requested for device type: test_ha_bridge#192.168.2.11 and username: e70392e3a02e46e993c2c0bb221101fa com.bwssystems.HABridge.hue.HueMulator
12-17-2020 10:00:16.126 WARN Could not find device: 50 for hue state change request: ImWQwpewvxiboa76JoLeqs9tNPzEPtVmegQwmoE from 192.168.2.58 body: {"on":false} com.bwssystems.HABridge.hue.HueMulator
12-17-2020 10:00:16.143 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:00:16.811 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:00:16.812 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:00:17.525 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:00:17.526 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:00:18.177 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:00:18.178 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:00:18.892 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:00:18.892 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:00:19.550 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:00:19.550 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:00:20.202 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:12.276 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.38:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:12.947 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.38:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:12.947 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.38:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:13.654 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.38:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:13.654 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.38:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:14.341 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.38:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:14.341 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.38:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:15.033 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.38:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:15.034 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.38:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:15.725 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.38:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:15.726 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.38:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:16.451 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.38:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:45.895 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:46.518 INFO Traceupnp: request of description.xml from: 192.168.1.30:80 filled in with address: 0.0.0.0:80 com.bwssystems.HABridge.upnp.UpnpSettingsResource
12-17-2020 10:02:46.569 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:46.570 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:47.265 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:47.266 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:47.987 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:47.987 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:48.641 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:48.641 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:49.366 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:49.367 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:50.076 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.58:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:50.077 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.70:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:50.785 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.70:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:50.786 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.70:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:51.503 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.70:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:51.503 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.70:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:52.228 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.70:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:52.228 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.70:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:52.941 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.70:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:52.942 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.70:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:53.639 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.70:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:53.639 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.70:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:54.291 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.70:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:54.292 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.98:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:54.996 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.98:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:54.996 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.98:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:55.673 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.98:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:55.674 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.98:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:56.397 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.98:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:56.398 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.98:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:57.112 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.98:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:57.112 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.98:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:57.822 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.98:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:57.822 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.98:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:58.219 INFO Traceupnp: hue api user create requested for device type: test_ha_bridge#192.168.2.11 and username: e70392e3a02e46e993c2c0bb221101fa com.bwssystems.HABridge.hue.HueMulator
12-17-2020 10:02:58.536 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.98:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:58.537 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.49:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:59.239 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.49:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:59.239 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.49:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:59.901 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.49:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:02:59.902 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.49:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:03:00.597 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.49:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:03:00.597 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.49:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:03:01.309 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.49:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:03:01.310 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.49:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:03:02.005 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.49:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:03:02.006 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.49:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:03:02.677 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.49:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:03:02.677 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.4:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:03:03.381 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.4:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:03:03.381 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.2.4:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:03:04.103 INFO Traceupnp: send upnp discovery template 1 with response address: 0.0.0.0:80 to address: 192.168.2.4:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-17-2020 10:03:43.736 INFO Traceupnp: hue api user create requested for device type: test_ha_bridge#192.168.2.11 and username: e70392e3a02e46e993c2c0bb221101fa com.bwssystems.HABridge.hue.HueMulator
bwssytems commented 3 years ago

what's the ip addresses of your echos?

heffneil commented 3 years ago

No idea I have a bunch and they’re all dhcp so it’s a 192.168.2.x address. All of them are.

Jean-Mercier commented 3 years ago

Turn off the link button in the security settings. Turn the trace upnp calls on in the bridge control. Post the output of the log after you do a discover from alexa

Hello @bwssytems here my log

My alexa echo is 10.0.0.20 ip address and echo dot : 10.0.0.31

HA-bridge on 10.0.0.21 `

12-21-2020 13:34:50.903 INFO Traceupnp: SSDP M-SEARCH packet from 10.0.0.21:53784 com.bwssystems.HABridge.upnp.UpnpListener
12-21-2020 13:34:51.554 INFO Traceupnp: send upnp discovery template 1 with response address: 10.0.0.21:8080 to address: 10.0.0.21:53784 com.bwssystems.HABridge.upnp.UpnpListener
12-21-2020 13:35:00.903 INFO Traceupnp: SSDP M-SEARCH packet from 10.0.0.21:53784 com.bwssystems.HABridge.upnp.UpnpListener
12-21-2020 13:35:01.554 INFO Traceupnp: send upnp discovery template 1 with response address: 10.0.0.21:8080 to address: 10.0.0.21:53784 com.bwssystems.HABridge.upnp.UpnpListener
12-21-2020 13:35:10.903 INFO Traceupnp: SSDP M-SEARCH packet from 10.0.0.21:53784 com.bwssystems.HABridge.upnp.UpnpListener
12-21-2020 13:35:11.554 INFO Traceupnp: send upnp discovery template 1 with response address: 10.0.0.21:8080 to address: 10.0.0.21:53784 com.bwssystems.HABridge.upnp.UpnpListener
12-21-2020 13:35:11.554 INFO Traceupnp: SSDP M-SEARCH packet from 10.0.0.21:58022 com.bwssystems.HABridge.upnp.UpnpListener
12-21-2020 13:35:12.205 INFO Traceupnp: send upnp discovery template 1 with response address: 10.0.0.21:8080 to address: 10.0.0.21:58022 com.bwssystems.HABridge.upnp.UpnpListener
12-21-2020 13:35:12.206 INFO Traceupnp: SSDP M-SEARCH packet from 10.0.0.21:58022 com.bwssystems.HABridge.upnp.UpnpListener
12-21-2020 13:35:12.856 INFO Traceupnp: send upnp discovery template 1 with response address: 10.0.0.21:8080 to address: 10.0.0.21:58022 com.bwssystems.HABridge.upnp.UpnpListener
12-21-2020 13:35:20.904 INFO Traceupnp: SSDP M-SEARCH packet from 10.0.0.21:53784 com.bwssystems.HABridge.upnp.UpnpListener
12-21-2020 13:35:21.554 INFO Traceupnp: send upnp discovery template 1 with response address: 10.0.0.21:8080 to address: 10.0.0.21:53784 com.bwssystems.HABridge.upnp.UpnpListener
12-21-2020 13:35:24.393 INFO Traceupnp: SSDP M-SEARCH packet from 10.0.0.31:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-21-2020 13:35:25.043 INFO Traceupnp: send upnp discovery template 1 with response address: 10.0.0.21:8080 to address: 10.0.0.31:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-21-2020 13:35:25.044 INFO Traceupnp: SSDP M-SEARCH packet from 10.0.0.31:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-21-2020 13:35:25.064 INFO Traceupnp: request of description.xml from: 10.0.0.31:8080 filled in with address: 10.0.0.21:8080 com.bwssystems.HABridge.upnp.UpnpSettingsResource
12-21-2020 13:35:25.694 INFO Traceupnp: send upnp discovery template 1 with response address: 10.0.0.21:8080 to address: 10.0.0.31:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-21-2020 13:35:25.694 INFO Traceupnp: SSDP M-SEARCH packet from 10.0.0.31:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-21-2020 13:35:26.345 INFO Traceupnp: send upnp discovery template 1 with response address: 10.0.0.21:8080 to address: 10.0.0.31:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-21-2020 13:35:26.345 INFO Traceupnp: SSDP M-SEARCH packet from 10.0.0.31:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-21-2020 13:35:26.996 INFO Traceupnp: send upnp discovery template 1 with response address: 10.0.0.21:8080 to address: 10.0.0.31:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-21-2020 13:35:26.996 INFO Traceupnp: SSDP M-SEARCH packet from 10.0.0.31:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-21-2020 13:35:27.646 INFO Traceupnp: send upnp discovery template 1 with response address: 10.0.0.21:8080 to address: 10.0.0.31:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-21-2020 13:35:27.647 INFO Traceupnp: SSDP M-SEARCH packet from 10.0.0.31:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-21-2020 13:35:28.297 INFO Traceupnp: send upnp discovery template 1 with response address: 10.0.0.21:8080 to address: 10.0.0.31:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-21-2020 13:35:28.297 INFO Traceupnp: SSDP M-SEARCH packet from 10.0.0.20:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-21-2020 13:35:28.950 INFO Traceupnp: send upnp discovery template 1 with response address: 10.0.0.21:8080 to address: 10.0.0.20:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-21-2020 13:35:28.950 INFO Traceupnp: SSDP M-SEARCH packet from 10.0.0.20:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-21-2020 13:35:29.057 INFO Traceupnp: request of description.xml from: 10.0.0.20:8080 filled in with address: 10.0.0.21:8080 com.bwssystems.HABridge.upnp.UpnpSettingsResource
12-21-2020 13:35:29.600 INFO Traceupnp: send upnp discovery template 1 with response address: 10.0.0.21:8080 to address: 10.0.0.20:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-21-2020 13:35:29.600 INFO Traceupnp: SSDP M-SEARCH packet from 10.0.0.20:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-21-2020 13:35:30.251 INFO Traceupnp: send upnp discovery template 1 with response address: 10.0.0.21:8080 to address: 10.0.0.20:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-21-2020 13:35:30.251 INFO Traceupnp: SSDP M-SEARCH packet from 10.0.0.20:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-21-2020 13:35:30.901 INFO Traceupnp: send upnp discovery template 1 with response address: 10.0.0.21:8080 to address: 10.0.0.20:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-21-2020 13:35:30.901 INFO Traceupnp: SSDP M-SEARCH packet from 10.0.0.20:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-21-2020 13:35:31.551 INFO Traceupnp: send upnp discovery template 1 with response address: 10.0.0.21:8080 to address: 10.0.0.20:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-21-2020 13:35:31.552 INFO Traceupnp: SSDP M-SEARCH packet from 10.0.0.20:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-21-2020 13:35:32.202 INFO Traceupnp: send upnp discovery template 1 with response address: 10.0.0.21:8080 to address: 10.0.0.20:50000 com.bwssystems.HABridge.upnp.UpnpListener
12-21-2020 13:35:32.202 INFO Traceupnp: SSDP M-SEARCH packet from 10.0.0.21:4282 com.bwssystems.HABridge.upnp.UpnpListener
12-21-2020 13:35:32.853 INFO Traceupnp: send upnp discovery template 1 with response address: 10.0.0.21:8080 to address: 10.0.0.21:4282 com.bwssystems.HABridge.upnp.UpnpListener
12-21-2020 13:35:32.853 INFO Traceupnp: SSDP M-SEARCH packet from 10.0.0.21:4282 com.bwssystems.HABridge.upnp.UpnpListener
12-21-2020 13:35:33.503 INFO Traceupnp: send upnp discovery template 1 with response address: 10.0.0.21:8080 to address: 10.0.0.21:4282 com.bwssystems.HABridge.upnp.UpnpListener
12-21-2020 13:35:33.503 INFO Traceupnp: SSDP M-SEARCH packet from 10.0.0.21:60370 com.bwssystems.HABridge.upnp.UpnpListener
12-21-2020 13:35:34.154 INFO Traceupnp: send upnp discovery template 1 with response address: 10.0.0.21:8080 to address: 10.0.0.21:60370 com.bwssystems.HABridge.upnp.UpnpListener
12-21-2020 13:35:34.154 INFO Traceupnp: SSDP M-SEARCH packet from 10.0.0.21:60370 com.bwssystems.HABridge.upnp.UpnpListener
12-21-2020 13:35:34.804 INFO Traceupnp: send upnp discovery template 1 with response address: 10.0.0.21:8080 to address: 10.0.0.21:60370 com.bwssystems.HABridge.upnp.UpnpListener
12-21-2020 13:35:34.805 INFO Traceupnp: SSDP M-SEARCH packet from 10.0.0.21:53784 com.bwssystems.HABridge.upnp.UpnpListener
12-21-2020 13:35:35.455 INFO Traceupnp: send upnp discovery template 1 with response address: 10.0.0.21:8080 to address: 10.0.0.21:53784 com.bwssystems.HABridge.upnp.UpnpListener
12-21-2020 13:35:40.904 INFO Traceupnp: SSDP M-SEARCH packet from 10.0.0.21:53784 com.bwssystems.HABridge.upnp.UpnpListener
12-21-2020 13:35:41.555 INFO Traceupnp: send upnp discovery template 1 with response address: 10.0.0.21:8080 to address: 10.0.0.21:53784 com.bwssystems.HABridge.upnp.UpnpListener
12-21-2020 13:35:50.904 INFO Traceupnp: SSDP M-SEARCH packet from 10.0.0.21:53784 com.bwssystems.HABridge.upnp.UpnpListener
12-21-2020 13:35:51.555 INFO Traceupnp: send upnp discovery template 1 with response address: 10.0.0.21:8080 to address: 10.0.0.21:53784 com.bwssystems.HABridge.upnp.UpnpListener
12-21-2020 13:36:00.904 INFO Traceupnp: SSDP M-SEARCH packet from 10.0.0.21:32870 com.bwssystems.HABridge.upnp.UpnpListener
12-21-2020 13:36:01.555 INFO Traceupnp: send upnp discovery template 1 with response address: 10.0.0.21:8080 to address: 10.0.0.21:32870 com.bwssystems.HABridge.upnp.UpnpListener
12-21-2020 13:36:10.906 INFO Traceupnp: SSDP M-SEARCH packet from 10.0.0.21:49438 com.bwssystems.HABridge.upnp.UpnpListener
12-21-2020 13:36:11.557 INFO Traceupnp: send upnp discovery template 1 with response address: 10.0.0.21:8080 to address: 10.0.0.21:49438 com.bwssystems.HABridge.upnp.UpnpListener
12-21-2020 13:36:12.947 INFO Traceupnp: SSDP M-SEARCH packet from 10.0.0.21:58022 com.bwssystems.HABridge.upnp.UpnpListener
12-21-2020 13:36:13.598 INFO Traceupnp: send upnp discovery template 1 with response address: 10.0.0.21:8080 to address: 10.0.0.21:58022 com.bwssystems.HABridge.upnp.UpnpListener
12-21-2020 13:36:13.598 INFO Traceupnp: SSDP M-SEARCH packet from 10.0.0.21:58022 com.bwssystems.HABridge.upnp.UpnpListener
12-21-2020 13:36:14.248 INFO Traceupnp: send upnp discovery template 1 with response address: 10.0.0.21:8080 to address: 10.0.0.21:58022 com.bwssystems.HABridge.upnp.UpnpListener
12-21-2020 13:36:20.905 INFO Traceupnp: SSDP M-SEARCH packet from 10.0.0.21:49438 com.bwssystems.HABridge.upnp.UpnpListener
12-21-2020 13:36:21.555 INFO Traceupnp: send upnp discovery template 1 with response address: 10.0.0.21:8080 to address: 10.0.0.21:49438 com.bwssystems.HABridge.upnp.UpnpListener
12-21-2020 13:36:23.552 INFO Traceupnp: SSDP M-SEARCH packet from 10.0.0.21:4282 com.bwssystems.HABridge.upnp.UpnpListener
12-21-2020 13:36:24.202 INFO Traceupnp: send upnp discovery template 1 with response address: 10.0.0.21:8080 to address: 10.0.0.21:4282 com.bwssystems.HABridge.upnp.UpnpListener
12-21-2020 13:36:24.203 INFO Traceupnp: SSDP M-SEARCH packet from 10.0.0.21:4282 com.bwssystems.HABridge.upnp.UpnpListener
12-21-2020 13:36:24.853 INFO Traceupnp: send upnp discovery template 1 with response address: 10.0.0.21:8080 to address: 10.0.0.21:4282 com.bwssystems.HABridge.upnp.UpnpListener
12-21-2020 13:36:30.905 INFO Traceupnp: SSDP M-SEARCH packet from 10.0.0.21:49438 com.bwssystems.HABridge.upnp.UpnpListener
12-21-2020 13:36:31.555 INFO Traceupnp: send upnp discovery template 1 with response address: 10.0.0.21:8080 to address: 10.0.0.21:49438 com.bwssystems.HABridge.upnp.UpnpListener
12-21-2020 13:36:34.865 INFO Traceupnp: SSDP M-SEARCH packet from 10.0.0.21:60370 com.bwssystems.HABridge.upnp.UpnpListener
12-21-2020 13:36:35.515 INFO Traceupnp: send upnp discovery template 1 with response address: 10.0.0.21:8080 to address: 10.0.0.21:60370 com.bwssystems.HABridge.upnp.UpnpListener
12-21-2020 13:36:35.515 INFO Traceupnp: SSDP M-SEARCH packet from 10.0.0.21:60370 com.bwssystems.HABridge.upnp.UpnpListener
12-21-2020 13:36:36.166 INFO Traceupnp: send upnp discovery template 1 with response address: 10.0.0.21:8080 to address: 10.0.0.21:60370 com.bwssystems.HABridge.upnp.UpnpListener
12-21-2020 13:36:40.905 INFO Traceupnp: SSDP M-SEARCH packet from 10.0.0.21:49438 com.bwssystems.HABridge.upnp.UpnpListener
12-21-2020 13:36:41.556 INFO Traceupnp: send upnp discovery template 1 with response address: 10.0.0.21:8080 to address: 10.0.0.21:49438 com.bwssystems.HABridge.upnp.UpnpListener
12-21-2020 13:36:50.905 INFO Traceupnp: SSDP M-SEARCH packet from 10.0.0.21:49438 com.bwssystems.HABridge.upnp.UpnpListener
12-21-2020 13:36:51.556 INFO Traceupnp: send upnp discovery template 1 with response address: 10.0.0.21:8080 to address: 10.0.0.21:49438 com.bwssystems.HABridge.upnp.UpnpListener
12-21-2020 13:37:00.905 INFO Traceupnp: SSDP M-SEARCH packet from 10.0.0.21:49438 com.bwssystems.HABridge.upnp.UpnpListener
12-21-2020 13:37:01.556 INFO Traceupnp: send upnp discovery template 1 with response address: 10.0.0.21:8080 to address: 10.0.0.21:49438 com.bwssystems.HABridge.upnp.UpnpListener
12-21-2020 13:37:10.906 INFO Traceupnp: SSDP M-SEARCH packet from 10.0.0.21:49438 com.bwssystems.HABridge.upnp.UpnpListener
12-21-2020 13:37:11.556 INFO Traceupnp: send upnp discovery template 1 with response address: 10.0.0.21:8080 to address: 10.0.0.21:49438 com.bwssystems.HABridge.upnp.UpnpListener
12-21-2020 13:37:14.313 INFO Traceupnp: SSDP M-SEARCH packet from 10.0.0.21:58022 com.bwssystems.HABridge.upnp.UpnpListener

`

Jean-Mercier commented 3 years ago

It s i thinks same problèm as #1272

It generate are with - and not :

audiofreak9 commented 3 years ago

@bwssytems It seems 5.4.0 is still generating uniqueid's with the dash followed by two digits prefix, that was found to be the discovery issue in this thread, also see this thread

Git-ChrisSc commented 3 years ago

Hello Jean-Mercier: First Things first: This IP-Adress-Range are unusual, can you provide your subnet?

My alexa echo is 10.0.0.20 ip address and echo dot : 10.0.0.31 HA-bridge on 10.0.0.21

The Second One: Please Change the listen Port for HA-Bridge to :80 - maybe you have to redirect. Some Generation of Alexas have to use only :80. The same Problem has occured by "Node Red" - the Highports coudn't use anymore. So the machine have to redirect from :80 to highport to solve this problem . Please Check it out :-) I use the 5.3.1 RC3 without big problems in in my Netzwork.

@bwssytems I have written a new Install-Guide for 5.31 R3 and Java 11 - can i provide it here? It's in german and bad english.

sonypsx commented 3 years ago

@bwssytems. Maybe i can contribute here a bit ... I used now habridge quite a while. Still running on a Raspi 1! Just upgraded to 5.4.0... I recently wanted to add some devices and run in the very same situation. In first place, because i didn't know that IP SEED Param, i try to renumber my devices via a small own script -> this did the trick in the frist place. Now i tried again to add some devices, runned again into the same issue. Yes, i deleted all devices via alexa.amazon.com, yes security link is OFF, i do not have any IP issues (running also in a 10.0.0.0/24 iprange), NTP is running fine, ha-bridge is still running on Port 80. For me it looks like Amazon is caching somehow deviceids, and as soon as you are using the same ID again, you run into the well known problems. Rebooting Alexas do not help (i do have dot Generation1,2 and 4). The only thing which seems to help is to increase this IP SEED number. However the good question is: how high can we go with this number until amazon will say thats too high?

audiofreak9 commented 3 years ago

Have a look at my post here https://github.com/bwssytems/ha-bridge/issues/1272#issuecomment-749246189 to edit your deviceid uniqueid to something Alexa will discover. The posts above the linked one above describe the issue.

sonypsx commented 3 years ago

Thanks for pointing this out, however i had this issue also with non 0 leading dev IDs. so my dev IDs were just straight from 1 - 24. Sample: { "id": "3", "uniqueid": "4c:56:ff:4c:e4:aa:f9-57", "name": "Verstärker Kino", "mapId": "undefined-copy", "mapType": "httpDevice", "deviceType": "custom", "offUrl": "[{\"item\":\"[]\"}]", "onUrl": "[{\"item\":\"http://10.0.0.52/YamahaRemoteControl/ctrl\",\"type\":\"httpDevice\",\"httpVerb\":\"POST\",\"httpBody\":\"<YAMAHA_AV cmd=\\\"PUT\\\"><Main_Zone><Input><Input_Sel>AV1</Input_Sel></Input></Main_Zone></YAMAHA_AV>\",\"contentType\":\"text/xml\"}]", "inactive": false, "noState": false, "offState": false, "deviceState": {}, "onFirstDim": false, "onWhenDimPresent": false, "lockDeviceId": false, "dimNoOn": false, "dimOnColor": false }

audiofreak9 commented 3 years ago

@sonypsx Sorry I miss-typed, I should have typed "uniqueid" not "deviceid". Your uniqueid has a dash followed by two digits: 4c:56:ff:4c:e4:aa:f9-57. Get rid of the "-57" and Alexa will find your device.

audiofreak9 commented 3 years ago

Code below stops the bridge, makes a copy of your device.db file, then removes all "dash,digit,digit" combinations, then restarts the bridge.

# systemctl stop ha-bridge.service
# cp device.db device.copy
# sed -i 's/-[0-9][0-9]"/"/g' device.db
# systemctl start ha-bridge.service
sonypsx commented 3 years ago

@audiofreak9: OK interesting! so maybe its a combination of the device-id and uniqueid, because currently alexa finds my devices with the dash! To get it working i just did change the IP SEED to 400 and it starts working again, even adding a single device in addition afterwards. grep uniqueid device.db "uniqueid": "da:4f:b5:c6:e9:3e:74-d3", "uniqueid": "5f:93:f9:83:52:4d:ef-3d", "uniqueid": "4c:56:ff:4c:e4:aa:f9-57", "uniqueid": "f8:99:13:9d:f5:e1:05-93", "uniqueid": "69:8d:51:a1:9d:8a:12-1c", "uniqueid": "a0:a0:80:f4:2e:6f:13-b3", "uniqueid": "38:b3:ef:f8:ba:f5:66-27", "uniqueid": "7f:6f:fa:a6:bb:0b:40-80", "uniqueid": "ec:89:56:63:7a:99:78-7b", "uniqueid": "73:27:8a:4a:86:96:0e-eb", "uniqueid": "69:74:ce:5a:c6:60:61-0b", "uniqueid": "5f:d0:b3:7c:d7:db:bb-00", "uniqueid": "c9:e1:07:4f:5b:3f:9f-c8", "uniqueid": "2b:44:92:8a:e1:1f:b9-38", "uniqueid": "65:b9:ee:a6:e1:cc:6b-b9", "uniqueid": "c4:51:47:de:e7:29:31-1e", "uniqueid": "f0:93:5e:4c:d5:92:0a-a6", "uniqueid": "eb:16:0d:e1:de:89:d9-05", "uniqueid": "a9:7d:a6:29:b0:98:b7-5c", "uniqueid": "5e:f0:59:93:8b:a7:99-aa", "uniqueid": "a3:c6:5c:29:74:27:0f-d0", "uniqueid": "07:e1:cd:7d:ca:89:a1-67", "uniqueid": "27:23:d0:92:b6:38:85-e0",

Jean-Mercier commented 3 years ago

Thanks i can t try it now but i will in two week After holidays ;) Merry Christmas ;)

audiofreak9 commented 3 years ago

I was able to get discovery of new devices to work by just changing the uniqueid as stated above without SEED change. You were able to get discovery by changing the SEED number in settings. So this tells me that it is indeed an Alexa cache issue using a combination of the id and uniqueid. If one or the other (or both) is changed the device(s) are discovered. This may also explain the return of previously deleted devices during discovery. Merry Christmas to you too!

@bwssytems: The above leads me to believe this is why some folks are seeing previously deleted devices reappear when they try to discover new devices. The device id may still be the same as the previously deleted device(s), Alexa has cached that id and recreates the device in the list. Then the new device, with a new uniqueid is not discovered unless the uniqueid is altered. HA-Bridge may need to never reuse id or uniqueid to avoid the above? Just thinking out loud...

bwssytems commented 3 years ago

I ran into this as well. Once I renumbered and rediscovered with duplicates, I started deleting the duplicate devices then did a rediscover. Had to do this multiple times but it resolved that cache issue. Alexa wants the devices deleted while the ha-bridge is up and running as it seems to try to validate them. The old numbers cause a problem, but as you mention are cached. The perfect way to do this is to delete devices while the ha-bridge is up before any renumbering, then do the renumber and rediscover.

trpster commented 3 years ago

I could find no way to directly clear the Alexa device cache, so following the advice from the bwssytem post above,
here's the procedure that worked for me: 1) backup Bridge Devices, then delete all of them 2) use Alexa app to delete all devices (or forget all) 3) discover devices 4) use Alexa app to again delete all devices 5) discover devices (if any reappear then repeat; delete all devices, discover devices again) 6) Once Alexa finds no devices, restore Bridge Devices for HA Bridge 7) discover devices, and for me, all were properly discovered and worked But BEWARE, if you then renumber and re-discover, you'll end up with doubles for any devices whose ID changed. To prevent this from occurring, I locked all the devices after they were properly discovered. Hope this helps.

Jean-Mercier commented 3 years ago

Hello happy new years to you !!

this not work for me alexa don't discover any device

i try to edit unique id to replace - by : but same problem

alexa don't found habridge device

audiofreak9 commented 3 years ago

@Jean-Mercier Did you reseed the device IDs? From the Bridge Control page, scroll to the bottom, find the "ID Seed" input and change it to something like 400. Then click Save at the top. When it reboots, from the Bridge Devices page click Renumber Devices. Then re-run discovery.

If discovery is successful, from the Bridge Devices page click the ID number for your devices to "lock" them, they will turn bold when locked.

sonypsx commented 3 years ago

Another help discovering devices and avoid the dupes:

I have played now around a couple of hours. With rebooting Alexas, clearing devices restore, and renumbering. However every time i did a discover i got 6 dupes of every device which is created in habridge. (V5.4.0) I was wondering why i did have 6 dupes. The answer is easy: .) 1x Alexa dot 1. Gen .) 1x Alexa dot 2. Gen .) 2x Alexa dot 4. Gen .) 1x Alexa app on a PC .) 1x Alexa on my mobile

Total 6 pieces of Alexa

However it does not make a difference by unplug them from power. The only way to avoid the dupes: you have to logoff them in the App on your mobile every single alexa. The alexa App on the mobile can stay online. After logging off all of them, you have the reset ONE Alexa to factory settings and add them as you would normally do if you got a new one. To be 100% sure you can renumber your devices on your habridge with a higher seed ID. Now say the magic words and voila you have all your devices back online and only one at a time.

What i also found out: I do have several TASMOTA Plugs running in "Belkin WeMo" Emulation mode. I have not added them to habridge, they got discovered on their own by alexa and it doesn't matter how many alexas are online, they always discovered correctly by one at a time. Maybe this is a hint for @bwssytems to sort some things out.

Good luck for all those having dupe devices!

trpster commented 3 years ago

sonypsx, I think your 6 dupes and 6 Alexas is a coincidence, but I wouldn't bet a lot of money on it. I've spent more time on this than I'm willing to admit, but I think the dupes are a result of the same devices having separate unique ID's and Alexa having a cache of devices. When I backed up and deleted all the HA Bridge devices and then discovered devices, all the devices I had deleted still showed up on the Alexa app. I had to delete them and discover devices twice before they were all deleted on the Alexa app.
Once they were all gone from the Alexa app, I restored the devices I had saved, re-seeded, then renumbered, and finally all were discovered and worked. I also have lots of Echo's strewn about, and it doesn't seem to matter which I use to turn something on or off; it works from any of them.
Everything is working right now, but I'm afraid to change anything. When I entered one device I gave it the name "Craft Room," and when my wife says, "Alexa turn on the craft room light," Alexa keeps saying "Do you mean Craft Room," and when my wife says "yes" the light turns on. I suppose I could change the name to "Craft room light," but I'm afraid it would screw things up. It's easier to train my wife to say "craft room."

sonypsx commented 3 years ago

@trpster: Your fear by changing something is correct. I just ran into it. One device on habridge did respond with a 404 error even with the Testbutton. Reboot habridge, test again -> works fine - delete just that one device and add it again -> headbang! Dupes did appear again - delete all of them readd -> dupes! Delete everything, Logoff all alexas, just reonline one Alexa -> device discover -> everything is correct. Even without renumbering! Maybe this is the only way to somehow delete that cache?!

Jean-Mercier commented 3 years ago

@Jean-Mercier Did you reseed the device IDs? From the Bridge Control page, scroll to the bottom, find the "ID Seed" input and change it to something like 400. Then click Save at the top. When it reboots, from the Bridge Devices page click Renumber Devices. Then re-run discovery.

yes i try it still no device

npaisnel commented 3 years ago

Audiofreak

you comment about starting and stopping the ha-bridge service

I tried to do that ..but it seems mine is not setup as a service.

but bridge discovery WAS working ..the system was workmen find.

If i try to Stop the service I get this

Would the fact that ha-bridge i not running as a device in any way to do with this?

I am having the same issues.

pi@192.168.1.49's password: Linux x10 4.14.98-v7+ #1200 SMP Tue Feb 12 20:27:48 GMT 2019 armv7l

The programs included with the Debian GNU/Linux system are free software; the exact distribution terms for each program are described in the individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law. Last login: Mon Jan 4 10:06:14 2021 from 192.168.1.74

Wi-Fi is disabled because the country is not set. Use raspi-config to set the country before use.

pi@x10:~ $ systemctl stop ha-bridge.service ==== AUTHENTICATING FOR org.freedesktop.systemd1.manage-units === Authentication is required to stop 'ha-bridge.service'. Authenticating as: root Password: ==== AUTHENTICATION COMPLETE === Failed to stop ha-bridge.service: Unit ha-bridge.service not loaded. pi@x10:~ $ systemctl start ha-bridge.service ==== AUTHENTICATING FOR org.freedesktop.systemd1.manage-units === Authentication is required to start 'ha-bridge.service'. Authenticating as: root Password: ==== AUTHENTICATION COMPLETE === Failed to start ha-bridge.service: Unit ha-bridge.service not found. pi@x10:~ $ cp device.db device.copy cp: cannot stat 'device.db': No such file or directory pi@x10:~ $ sudo reboot now Connection to 192.168.1.49 closed by remote host. Connection to 192.168.1.49 closed.

[Process completed]

trpster commented 3 years ago

npaisnel, I'm assuming that your wifi is working; the log above says it isn't, and ha-bridge is dead without it.

I know that this has been frustrating for everyone who is having problems getting Alexa to properly find and control devices, but I remain convinced that the problem lies with Alexa and not with ha-bridge. I finally got it working and probably did more than I needed to to get everything working. I decided I needed to start fresh, so I completely deleted ha-bridge from the r-pi where it was running, and used the latest procedure from the bwssytem readme to install it on a different r-pi. At the time, the Alexa app showed 4 separate instances of most of the devices, and once I had ha-bridge installed and running on a new r-pi with no defined devices, I deleted all the devices on the Alexa app and kept doing the "discover devices" followed by deleting them until Alexa finally said it could find no new devices and the app showed no devices. I think as bwssytem has mentioned that ha-bridge MUST BE RUNNING in order for this to clear out the Alexa cache. Once I got to the stage where the Alexa app was no longer showing any devices, I restored the ha-bridge devices that I had previously backed up, reseeded (although I'm not positive this step it necessary), renumbered, and asked for another "discover devices." Finally Alexa found all the devices, and they all work. Then I locked all the ha-bridge devices. I think that if you don't lock the devices before you renumber, you may end up with Alexa adding the renumbered devices to the already existing devices, because even though they have the same name, they have different device ID's. I think I proved this theory; I had everything working, then added a new ha-bridge device and renumbered. All the devices worked, but the names were wrong. That is what caused me to delete everything and start fresh.

I believe that for all this to work properly, you can't renumber without first clearing devices that will be renumbered from the Alexa cache, and the only way I know to do this is to backup the ha-bridge devices and go through the "discover devices," clear all devices on the Alexa app, and repeat until all devices are gone. Then restore the saved devices, and discover devices.

One thing I don't yet understand, but I'm unwilling to experiment further (I've already spent too much time on this). But does anyone know what happens if I just change the name of an existing ha-bridge device? Do I need to "discover devices" before Alexa will recognize the new name? Right now I'm at the "Don't poke the bear" stage, but I'll give it a shot if someone thinks it'll work. Thanks.

npaisnel commented 3 years ago

WiFi

Well every thing else is working fine on wifi, but the HA-bridge RPi is hardwired to the network

Last time I looked at construction the HA-bridge form scratch was whenI bought the RPi a few years go ..and it has worked perfectly ever since.

If i had to start from scratch again and learn about how to do the complete RPI install again from the start.. I would only unearth a whole host of new problems. I made a few notes of what I did back then .. but most of it will probably be out of date now.

It used to just work..then suddenly trying to add one device, fully working devices stopped too.

trpster commented 3 years ago

npaisnel, believe me, I know how you feel. I'm probably the last person who should be advising anyone, but here's a suggestion that won't require reinstalling (which I now believe was overkill in my case). 1) Backup your current devices on ha-bridge 2) Delete all the ha-bridge devices and delete all the devices on the Alexa app 3) do the "discover devices" then delete all devices again on the Alexa app, repeat until no devices show up on the Alexa app. 4) Restore your saved ha-bridge devices and then "discover devices." (I think reseeding and renumbering is superfluous) A lot of us would like to know if this resolves your problem, and shouldn't take too long to accomplish. Since things aren't working correctly right now, what have you got to lose?

npaisnel commented 3 years ago

Will try later

Was about to tell you about the day I have had in front of 4 screens since 0730..now 1815... still not got any further than I was as I finished the config at 0930..then some one walked past and snapped the USB stick off.......

so with all other things..i am now just getting back to where I was at 0830 this morning ...and then maybe I can start looking at this Alexa again!

npaisnel commented 3 years ago

And just when you think you are getting there...ELF -Interpreter error...WTF is that ..when i plug a new HDD in ....not the RPI and ha-bridge box...but another systemm...grr computers!

Fitz2380 commented 3 years ago

I have dealt with this issue off and on for several months and prior to 5.4.0. I have been running5.3.1.R1 and ran into this in November: see post: https://github.com/bwssytems/ha-bridge/issues/1233. At that time I was assuming there was some kind of Amazon cache of devices.

I ran into this problem again a few days ago. I am not sure what changed as I did not add any devices to the ha-bridge in the past couple of weeks. However, Amazon started showing 6 new devices and 3 of these were duplicates. I know this post was started due to feeling it was a 5.4.0 issue, but as someone noted above I believe it is an Amazon issue and I wanted to supply my experience thus far.

As noted I now have 6 new devices to which 3 seemed to be duplicates and 3 seemed to be old devices no longer defined in ha-bridge.

I followed the process defined above by trpster.

1> Backed up current devices on ha-bridge. 2> Deleted all the devices in ha-bridge and then deleted duplicates and old devices in Amazon (did not delete the rest of devicies). 3> Rediscoverd devices in Alexa. It did not rediscover the duplicate/old devices this time (it had done this all other times before after deleting from Alexa). 3b> I did then deleted all ha-bridge devices out of Alexa and rediscovered devices. Alexa did not discover any devices. 4> I restored the backed up database from #1. and then 'discover devices' through Alexa. No devices were found. My Alexa app now has no ha-bridge devices defined (oh oh my wife is not happy now). My next step will be to reindex through ha-bridge as this has worked in the past, but I would be willing to try other things for debug purposes if anyone has suggestions. I thought about editing the unique ha-bridge Id but I am not sure if I should do that.

I can try the new 5.4.0 code but again I don't think this has created the issue.

trpster commented 3 years ago

It sounds like I'm wrong about not needing to renumber, since you (Fitz2380 ) didn't renumber and it isn't working.
I'd suggest doing both; reseed and renumber and see if the devices are found.

I'm using 5.4.0 and have everything working fine, and have relegated any more experimenting to my prison file (i.e., the list of things I plan to do if I'm incarcerated; read War and Peace, learn to play the piano, etc.).

Fitz2380 commented 3 years ago

Ok.. Update: I decided to download and run 5.4.0 as a test. I did not change anything else. I did a discovery from Alexa and she now found my 23 devices with no duplicates. They appear to be functioning as expected.... hmmm. I did not renumber.

npaisnel commented 3 years ago

I too do not have any devices nay more.

I tried the delete form HA-bridge delete form Alexa . discover..re install form backup etc..but not joy.

Tried the link button both on and roof Increased the On time to 90 seconds

No suggestions see to work ..seeem totally random.

But this is not a new issue. I remember it form a year or more back. well before 5.3 even

sonypsx commented 3 years ago

@Fitz2380: Because i ran into the exact same troubles for me, i have a bulletproof tasklist for avoid dupes: .) delete all devices via https://alexa.amazon.de/spa/index.html#appliances .) if you have more then one alexa, logoff aal of them except ONE (the App on the mobile does not count as a full alexa) .) if you have just one, log it off and back on .) Optional you can do a renumber even with a Seed ID of 1, but thats not needed .) Do a discover with that one Alexa Online .) Devices are added without any dupes .) If you are satisfied with the results , logon the rest of your alexas if there are any. .) Done!

Before i figured out that order i had everytime the dupes, i have now followed this order several times and it is working every time.

Br sonypsx

audiofreak9 commented 3 years ago

@npaisnel you asked about running the ha-bridge as a service:

you comment about starting and stopping the ha-bridge service

I tried to do that ..but it seems mine is not setup as a service.

Try this $ sudo systemctl status habridge.service -l and tell me what you get?

Fitz2380 commented 3 years ago

I agree that this issue has been going on for awhile. I chased down this Alexa post which was linked in another ha-bridge post and it is not just ha-bridge that has the issue but it appears that Amazon does not want to fix the issue. I agree there needs to be a forget devices in my Amazon account so I can reset periodically...

https://www.amazonforum.com/s/question/0D54P00006zSyeDSAS/alexa-discovering-smart-devices-from-cache

npaisnel commented 3 years ago

@audiofreak

● habridge.service - HA Bridge Loaded: loaded (/etc/systemd/system/habridge.service; enabled; vendor preset: enabled) Active: active (running) since Mon 2021-01-04 19:25:22 GMT; 1h 6min ago Main PID: 499 (java) CGroup: /system.slice/habridge.service └─499 /usr/bin/java -jar -Dconfig.file=/home/pi/habridge/data/habridge.config /home/pi/habridge/

Jan 04 20:30:11 x10 java[499]: 2021-01-04 20:30:11,729 [main] INFO com.bwssystems.HABridge.upnp.UpnpListen Jan 04 20:30:34 x10 java[499]: 2021-01-04 20:30:34,000 [main] INFO com.bwssystems.HABridge.upnp.UpnpListen Jan 04 20:30:35 x10 java[499]: 2021-01-04 20:30:35,303 [main] INFO com.bwssystems.HABridge.upnp.UpnpListen Jan 04 20:30:48 x10 java[499]: 2021-01-04 20:30:48,046 [main] INFO com.bwssystems.HABridge.upnp.UpnpListen Jan 04 20:30:49 x10 java[499]: 2021-01-04 20:30:49,350 [main] INFO com.bwssystems.HABridge.upnp.UpnpListen Jan 04 20:31:16 x10 java[499]: 2021-01-04 20:31:16,283 [main] INFO com.bwssystems.HABridge.upnp.UpnpListen Jan 04 20:31:17 x10 java[499]: 2021-01-04 20:31:17,584 [main] INFO com.bwssystems.HABridge.upnp.UpnpListen Jan 04 20:31:17 x10 java[499]: 2021-01-04 20:31:17,585 [main] INFO com.bwssystems.HABridge.upnp.UpnpListen Jan 04 20:31:18 x10 java[499]: 2021-01-04 20:31:18,890 [main] INFO com.bwssystems.HABridge.upnp.UpnpListen Jan 04 20:31:23 x10 java[499]: 2021-01-04 20:31:23,475 [main] INFO com.bwssystems.HABridge.upnp.UpnpListen ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~

audiofreak9 commented 3 years ago

@sonypsx HA_Bridge is running as a service on your machine. How did you try to stop/start the service? I use $ sudo systemctl stop habridge and $ sudo systemctl start habridge respectively.

What I do find odd is that your script does not point to a ha-bridge.jar file.

Here is what my RPi returns, note the bold portion showing "ha-bridge.jar":

● habridge.service - HA Bridge Loaded: loaded (/etc/systemd/system/habridge.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2020-12-30 13:22:17 EST; 5 days ago Main PID: 606 (java) Tasks: 99 (limit: 2065) CGroup: /system.slice/habridge.service └─606 /usr/bin/java -jar -Dconfig.file=/home/pi/habridge/data/habridge.config /home/pi/habridge/ha-bridge.jar

Enter this $ sudo nano /etc/systemd/system/habridge.service and post the contents of this file.

@Fitz2380 I have a sinking feeling that Amazon (as Google already did) may drop local discovery of Philips Hue in the near future as those Gen 1 devices reach end-of-life cycle in the Philips Hue ecosystem.

npaisnel commented 3 years ago

Linux x10 4.14.98-v7+ #1200 SMP Tue Feb 12 20:27:48 GMT 2019 armv7l

The programs included with the Debian GNU/Linux system are free software; the exact distribution terms for each program are described in the ...systemd/system/habridge.service [Unit] Description=HA Bridge Wants=network.target After=network.target

[Service] Type=simple WorkingDirectory=/home/pi/habridgeExecStart=/usr/bin/java -jar -Dco$ [ Read 13 lines ] ^G Get Help^O Write Ou^W Where Is ^X Exit ^R Read Fil^\ Replace ...systemd/system/habridge.service [Unit] Description=HA Bridge Wants=network.target After=network.target

[Service] Type=simple WorkingDirectory=/home/pi/habridgeExecStart=/usr/bin/java -jar -Dco$ [Install] WantedBy=multi-user.target

^G Get Help^O Write Ou^W Where Is ^X Exit ^R Read Fil^\ Replace

sonypsx commented 3 years ago

@audiofreak9 and @npaisnel Do a ls -la /etc/systemd/system/bridge should look like this:

root@raspberrypi:~# ls -la /etc/systemd/system/*bridge* -rw-r--r-- 1 root root 291 Dez 22 19:10 /etc/systemd/system/ha-bridge.service root@raspberrypi:~#

After that do... the following command on your pi: cat /etc/systemd/system/ha-bridge.service (use exactly the name of the file which was printed on the ls before)

should look like this: `root@raspberrypi:~# cat /etc/systemd/system/bridge [Unit] Description=HA Bridge Wants=network.target After=network.target

[Service] Type=simple

WorkingDirectory=/home/pi/ha-bridge ExecStart=/usr/bin/java -jar -Dconfig.file=/home/pi/ha-bridge/data/habridge.config /home/pi/ha-bridge/ha-bridge-5.4.0.jar

[Install] WantedBy=multi-user.target root@raspberrypi:~# ` Afterwards please do the following: ls -la /home/pi/ha-bridge/ha-bridge-5.4.0.jar (please use copy paste the path to the jarfile which is printed in the service file) should look like this:

root@raspberrypi:~# ls -la /home/pi/ha-bridge/ha-bridge-5.4.0.jar -rw-r--r-- 1 pi pi 9670679 Dez 14 19:26 /home/pi/ha-bridge/ha-bridge-5.4.0.jar root@raspberrypi:~#

@audiofreak9: Yes i use systemctl status/start/stop ha-bridge.service. Sample:

` root@raspberrypi:~# systemctl status ha-bridge.service ● ha-bridge.service - HA Bridge Loaded: loaded (/etc/systemd/system/ha-bridge.service; enabled; vendor preset: enabled) Active: active (running) since Sat 2021-01-02 22:20:40 CET; 2 days ago Main PID: 333 (java) Tasks: 30 (limit: 881) CGroup: /system.slice/ha-bridge.service └─333 /usr/bin/java -jar -Dconfig.file=/home/pi/ha-bridge/data/habridge.config /home/pi/ha-bridge/ha-bridge-5.4.0.jar

Jän 05 13:47:01 raspberrypi java[333]: 2021-01-05 13:47:01,102 [SocketListener(Philips-hue)] DEBUG javax.jmdns.impl.JmDNSImpl - Phil Jän 05 13:47:01 raspberrypi java[333]: 2021-01-05 13:47:01,103 [SocketListener(Philips-hue)] DEBUG javax.jmdns.impl.JmDNSImpl - Phil Jän 05 13:47:01 raspberrypi java[333]: 2021-01-05 13:47:01,104 [SocketListener(Philips-hue)] DEBUG javax.jmdns.impl.DNSIncoming - DN Jän 05 13:47:01 raspberrypi java[333]: 2021-01-05 13:47:01,105 [SocketListener(Philips-hue)] DEBUG javax.jmdns.impl.JmDNSImpl - Phil Jän 05 13:47:01 raspberrypi java[333]: 2021-01-05 13:47:01,115 [SocketListener(Philips-hue)] DEBUG javax.jmdns.impl.JmDNSImpl - Phil Jän 05 13:47:01 raspberrypi java[333]: 2021-01-05 13:47:01,117 [SocketListener(Philips-hue)] DEBUG javax.jmdns.impl.DNSIncoming - DN Jän 05 13:47:01 raspberrypi java[333]: 2021-01-05 13:47:01,118 [SocketListener(Philips-hue)] DEBUG javax.jmdns.impl.JmDNSImpl - Phil Jän 05 13:47:01 raspberrypi java[333]: 2021-01-05 13:47:01,119 [SocketListener(Philips-hue)] DEBUG javax.jmdns.impl.JmDNSImpl - Phil Jän 05 13:47:01 raspberrypi java[333]: 2021-01-05 13:47:01,139 [SocketListener(Philips-hue)] DEBUG javax.jmdns.impl.JmDNSImpl - Phil Jän 05 13:47:02 raspberrypi java[333]: 2021-01-05 13:47:02,726 [Thread-13] DEBUG com.bwssystems.HABridge.plugins.http.HttpClientPool root@raspberrypi:~# `

Maybe you did forgot a "systemctl daemon-reload" after the installation of ha-bridge?

root@raspberrypi:~# systemctl daemon-reload root@raspberrypi:~#

@npaisnel: Please post the results of the issued cmds here ...

Br sonypsx

npaisnel commented 3 years ago

I have been called in to work, and it seems my NO-IP address at home has not updated.. so can’t access it at the moment from work/phone Will get back on it later today if I don’t get another emergency Callout... I am on 24 hour -6 day standby at moment

npaisnel commented 3 years ago

pi@x10:/etc/systemd/system $ ls -la habridge.service -rw-rw-r-- 1 root root 284 Aug 4 2018 habridge.service pi@x10:/etc/systemd/system $

pi@x10:/etc/systemd/system $ cat /etc/systemd/system/habridge.service [Unit] Description=HA Bridge Wants=network.target After=network.target

[Service] Type=simple WorkingDirectory=/home/pi/habridge ExecStart=/usr/bin/java -jar -Dconfig.file=/home/pi/habridge/data/habridge.config /home/pi/habridge/ha-bridge.jar

[Install] WantedBy=multi-user.target

npaisnel commented 3 years ago

As per the above it has alway worked perfectly before. not ben changed . the service has been started from that / like that since I built the system in 2018...

Discovery has alway worked fine. It failed once before then 'magically ' started working again. for no adequately explored reasons.

I am wondering about just creating a new Amazon account and see if that makes it work again...isolating the problem at least.

sonypsx commented 3 years ago

@npaisnel Did you try to logoff your Alexa(s)?

npaisnel commented 3 years ago

I’ll look up how I do that later Thanks. Nothing to loose now as NOTHING works any way 😩

npaisnel commented 3 years ago

Oh... no maybe I won’t. Took me weeks of fiddling to get the Yamaha MusicCast Skill working... That and Harmony TV Control still works. The thought of trying to get all that working again just makes me want to slit my wrists !