Repository navigation
Amazon Echo still not recognize 5.4.0 #1270
Description
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
thanks
Activity
devel6236 commentedon Dec 16, 2020
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 commentedon Dec 17, 2020
Thanks i already test to renumber and change the ID SEED
i use the link button
bwssytems commentedon Dec 17, 2020
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 commentedon Dec 17, 2020
I have link button off. I found 55 devices - and they still don't respond.
heffneil commentedon Dec 17, 2020
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
bwssytems commentedon Dec 18, 2020
what's the ip addresses of your echos?
heffneil commentedon Dec 18, 2020
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 commentedon Dec 21, 2020
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
`
`
Jean-Mercier commentedon Dec 21, 2020
It s i thinks same problèm as #1272
It generate are with - and not :
audiofreak9 commentedon Dec 21, 2020
@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 commentedon Dec 22, 2020
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 commentedon Dec 22, 2020
@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 commentedon Dec 22, 2020
Have a look at my post here #1272 (comment) to edit your
deviceiduniqueid to something Alexa will discover. The posts above the linked one above describe the issue.sonypsx commentedon Dec 22, 2020
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 }64 remaining items
trpster commentedon Jan 15, 2021
My link time is set for 45 seconds; I suppose it's the default because I never set it.
One thing to check; when you go through the process of discover/delete, ha-bridge must be running.
I can post my "Bridge Control" setup if anyone thinks it will help (and can tell me the easiest way to post it).
I've also backed up the ha-bridge.config file in case it will help if things turn to shit, but I've been afraid
to make any changes since I got everything working.
All of my devices are controlled by MQTT.
npaisnel commentedon Jan 15, 2021
I do not need to use the Link button
I just tried it
I created a new device and Alexa found ti immediately ...no need to Press the Link button.
Try without using Link
kllngtme commentedon Jan 16, 2021
I finally got this. Enabling the trace upnp helped me understand what was going on better. All my devices were being seen, just not connecting really. I switched the web server port from 8080 to port 80 and that was the fix. All my devices are connecting now. Phew.
audiofreak9 commentedon Jan 16, 2021
@kllngtme Yes Amazon has changed discovery to only work with port 80. This occurred more than a year ago.
npaisnel commentedon Jan 21, 2021
Well
I can say one thing about the 'fix' of deleting the data folder...is that is a one time fix...I have tried it again when Alexa some how came up with a new error
"Can't find device or group named X in Y's profile"
So I tried a Discover devices..no go
Deleted all the devices form HA-Bridge Gui
No go
So went back both fix that worked last week.
Backup the /habridge/Data folder to a different name..and re boot the server so it created a new data folder
This time.
on re creating new devices..I does not find them.
So the Fix of deleting Data and start gin a fresh 'system" was merely a fluke.
Maybe it is just a matter of leaving Alexa alone for a week or so ...so it flushes old data out of a cache some where....
dunno..but the fix is not a real fix..it was just a lucky coincidence!
npaisnel commentedon Jan 22, 2021
Another update.
MY Alexa stopped responding and seeing any devices that were already found when I Accidentally Hit the Setup Remote button on the iPhone App.
After hitting that and quitting out of the app...Alexa did not see the devices..
No amount of re booting or other tricks would see them again.
Just got a messages from Alexa saying ..
"No such device or Group in Neils profile."
Last night before I went to bed I de-registered both Alexa devices.
This morning I plugged them back in to power and just walked away .
Give them 10 minutes and they start flashing orange and you can set them up again.
I also Deleted the data file from habridge directory
Rebooted and then copied the devices.db file back to data.
Diaan "Alexa Find new devices...and all 26 were found again.
Maybe the trick is to deregister the Echo devices and leave it all for a few hours..over night,,,
Dunno ...
But if you get stuck, worth a try .
sonypsx commentedon Jan 22, 2021
@npaisnel:
Thats exactly the way i was able to avoid my dupe finding of devices. Deregister Alexa will help instantly - you don't have to wait overnight or even hours. I am pretty sure this deregistering is triggering "something" back at Jeffs playground ;)
heffneil commentedon Jan 22, 2021
I deactivated all my echos like you guys suggested and finally found no new devices.
Then I had to get everything working again and my installation of HA-Bridge is / was a mess. It still is. The problem is almost no one here is using Mac OSX to run this so I don't have a good reference on HOW it should be configured. I finally was able to get OLD files to reload by rebooting EVERY time. I don't know why I have to reboot but the devices and config files will not stick unless I reboot.
My files were PRE moving to port 80 for the webserver.
I am at the point where Amazon can not find any of my devices. Nothing gets discovered. Don't know why and kinda don't care anymore. I gave it the good try - but frustration and lack of being able to control this stuff - it just isn't worth the trouble anymore folks.
npaisnel commentedon Jan 22, 2021
How long did you leave them de-registered for before you re-registered them and tried a discovery.
I had to de register, leave it over night
, re-register them, before trying a discovery
Do you have a link to setting habridge up on Mac?
I have a spare Mac Mini here I could try on
npaisnel commentedon Jan 22, 2021
heffneil commentedon Jan 22, 2021
Just long enough to get them all offline. I didn't register them again until I had the bridge sorta working.
npaisnel commentedon Jan 22, 2021
I found you did have to leave them unregistered for a time.
if I re registered straight away i found no devices
Jean-Mercier commentedon Feb 7, 2021
Thanks so i can close this issue because i'm running ha-bridge on synology docker and port 80 is reserved for synology system
it's was a long time i didn't discover device
jayjupdhig commentedon Mar 18, 2021
Now it's completely finish with that kind of devices - indepdendently from the "virtual" link button - "ON" vs. "OFF":
#1295
beandi commentedon Apr 3, 2021
So after not discovering any new devices for the last two weeks i decided to try and edit the unique ids in the device.db-file:
My findings after some try and error: Replacing the last "-"-separator with a ":"-separator (and nine octets) did the job, every device was recognized again.