Discovery no longer working after upgrade to 3.0.20

Posted on
Thu Mar 15, 2018 12:58 pm
ottoppp offline
Posts: 12
Joined: Oct 21, 2013

Discovery no longer working after upgrade to 3.0.20

I've been very thankful to have the Alexa-Hue-Bridge, but now my wife depends upon it, and I broke it. Hopefully someone can help me with this suddenly dire problem.

I was using version 2.0.11 and upgraded to version 3.0.20. My devices stopped responding (wrong ID), so I removed and re-added them, and now I cannot get discovery to work at all. I have read through the troubleshooting and steps in the Discover Failure topic, and have not had any luck. I've gone through disabling and clearing out all settings and verified that port 1900 is working. I have tried discovery from all of my Echo devices (two Echo v1, Echo Dot v1, Echo Show, Echo Spot). I've upgraded to 3.0.27 and setup Echo devices in Indigo for all of my Echos. I've attached screen shots of the settings.

The log with all the debugging options looks like this repeating:

2018-03-15 11:47:24.900 DEBUG Plugin.responder.respond Responder.respond for Alexa-Hue-Bridge-3.0, called from address ('192.168.10.2', 55039)
HTTP/1.1 200 OK
CACHE-CONTROL: max-age=100
EXT:
LOCATION: http://192.168.10.2:8178/description.xml
SERVER: FreeRTOS/7.4.2, UPnP/1.0, IpBridge/1.7.0
ST: urn:schemas-upnp-org:device:basic:1
USN: uuid:50e26666-27d7-11e8-9d77-b8f6b115595b


2018-03-15 11:47:24.900 DEBUG Plugin.responder.respond Responder.respond: for Alexa-Hue-Bridge-3.0, creating output_socket
2018-03-15 11:47:24.900 DEBUG Plugin.responder.respond Responder.respond: for Alexa-Hue-Bridge-3.0, calling output_socket.sendto
2018-03-15 11:47:24.900 DEBUG Plugin.responder.respond Responder.respond: for Alexa-Hue-Bridge-3.0, closing output_socket
2018-03-15 11:47:24.900 DEBUG Plugin.responder.respond Responder.respond: for Alexa-Hue-Bridge-3.0, UDP Response sent to ('192.168.10.2', 55039)
2018-03-15 11:47:34.899 DEBUG Plugin.responder.run Responder.respond called from SKIPPED address '192.168.10.92'
2018-03-15 11:47:34.899 DEBUG Plugin.responder.run Responder.respond called from SKIPPED address '192.168.10.93'
2018-03-15 11:47:34.899 DEBUG Plugin.responder.run Responder.run: received from ('192.168.10.2', 55039): M-SEARCH * HTTP/1.1
Host: 239.255.255.250:1900
Man: "ssdp:discover"
ST: ssdp:all
MX: 5


2018-03-15 11:47:34.899 DEBUG Plugin.responder.respond Responder.respond for Alexa-Hue-Bridge-3.0, called from address ('192.168.10.2', 55039)
HTTP/1.1 200 OK
CACHE-CONTROL: max-age=100
EXT:
LOCATION: http://192.168.10.2:8178/description.xml
SERVER: FreeRTOS/7.4.2, UPnP/1.0, IpBridge/1.7.0
ST: urn:schemas-upnp-org:device:basic:1
USN: uuid:50e26666-27d7-11e8-9d77-b8f6b115595b


2018-03-15 11:47:34.899 DEBUG Plugin.responder.respond Responder.respond: for Alexa-Hue-Bridge-3.0, creating output_socket
2018-03-15 11:47:34.899 DEBUG Plugin.responder.respond Responder.respond: for Alexa-Hue-Bridge-3.0, calling output_socket.sendto
2018-03-15 11:47:34.900 DEBUG Plugin.responder.respond Responder.respond: for Alexa-Hue-Bridge-3.0, closing output_socket
2018-03-15 11:47:34.900 DEBUG Plugin.responder.respond Responder.respond: for Alexa-Hue-Bridge-3.0, UDP Response sent to ('192.168.10.2', 55039)
2018-03-15 11:47:44.895 DEBUG Plugin.responder.run Responder.respond called from SKIPPED address '192.168.10.92'
2018-03-15 11:47:44.895 DEBUG Plugin.responder.run Responder.respond called from SKIPPED address '192.168.10.93'
2018-03-15 11:47:44.896 DEBUG Plugin.responder.run Responder.run: received from ('192.168.10.2', 55039): M-SEARCH * HTTP/1.1
Host: 239.255.255.250:1900
Man: "ssdp:discover"
ST: ssdp:all
MX: 5


2018-03-15 11:47:44.896 DEBUG Plugin.responder.respond Responder.respond for Alexa-Hue-Bridge-3.0, called from address ('192.168.10.2', 55039)
HTTP/1.1 200 OK
CACHE-CONTROL: max-age=100
EXT:
LOCATION: http://192.168.10.2:8178/description.xml
SERVER: FreeRTOS/7.4.2, UPnP/1.0, IpBridge/1.7.0
ST: urn:schemas-upnp-org:device:basic:1
USN: uuid:50e26666-27d7-11e8-9d77-b8f6b115595b


2018-03-15 11:47:44.896 DEBUG Plugin.responder.respond Responder.respond: for Alexa-Hue-Bridge-3.0, creating output_socket
2018-03-15 11:47:44.896 DEBUG Plugin.responder.respond Responder.respond: for Alexa-Hue-Bridge-3.0, calling output_socket.sendto
2018-03-15 11:47:44.896 DEBUG Plugin.responder.respond Responder.respond: for Alexa-Hue-Bridge-3.0, closing output_socket
2018-03-15 11:47:44.896 DEBUG Plugin.responder.respond Responder.respond: for Alexa-Hue-Bridge-3.0, UDP Response sent to ('192.168.10.2', 55039)
2018-03-15 11:47:54.895 DEBUG Plugin.responder.run Responder.respond called from SKIPPED address '192.168.10.92'
2018-03-15 11:47:54.895 DEBUG Plugin.responder.run Responder.respond called from SKIPPED address '192.168.10.93'
2018-03-15 11:47:54.896 DEBUG Plugin.responder.run Responder.run: received from ('192.168.10.2', 55039): M-SEARCH * HTTP/1.1
Host: 239.255.255.250:1900
Man: "ssdp:discover"
ST: ssdp:all
MX: 5
Attachments
Screen Shot 2018-03-15 at 11.46.38 AM.png
Screen Shot 2018-03-15 at 11.46.38 AM.png (198.66 KiB) Viewed 1651 times
Screen Shot 2018-03-15 at 11.46.25 AM.png
Screen Shot 2018-03-15 at 11.46.25 AM.png (338.47 KiB) Viewed 1651 times
Screen Shot 2018-03-15 at 11.45.59 AM.png
Screen Shot 2018-03-15 at 11.45.59 AM.png (372.82 KiB) Viewed 1651 times
Screen Shot 2018-03-15 at 11.45.33 AM.png
Screen Shot 2018-03-15 at 11.45.33 AM.png (431.51 KiB) Viewed 1651 times
Screen Shot 2018-03-15 at 11.45.06 AM.png
Bridge and Echo devices
Screen Shot 2018-03-15 at 11.45.06 AM.png (108.95 KiB) Viewed 1651 times

Posted on
Fri Mar 16, 2018 3:26 pm
autolog offline
Posts: 3988
Joined: Sep 10, 2013
Location: West Sussex, UK [GMT aka UTC]

Re: Discovery no longer working after upgrade to 3.0.20

What type of Echo is 192.168.10.2 (Echo Hue Bridge) as that is where the traffic is coming from.

You could try deleting the Alexa devices by logging into Alexa so that all devices need re-discovering and then do a discovery. This may help?

Posted on
Fri Mar 16, 2018 3:42 pm
ottoppp offline
Posts: 12
Joined: Oct 21, 2013

Re: Discovery no longer working after upgrade to 3.0.20

Happy to try this, but not sure why it might be relevant. Discovery doesn't seem to be working at all for Indigo. Do you know of a way to delete ALL of the devices in the Alexa app? I recall there was a reset or something similar, but I don't see that, and no answer via Google. Manually deleting each item now.

Posted on
Fri Mar 16, 2018 5:01 pm
ottoppp offline
Posts: 12
Joined: Oct 21, 2013

Re: Discovery no longer working after upgrade to 3.0.20

OK, deleted all 60 remaining non-Alexa-Hue-Bridge devices (the only ones left after deleting the others previously) individually and ran discovery. It found all 60 non-indigo-Alexa-Hue-Bridge devices (Nest, Hue, Ring, Sonos). No indication in the Alexa-Hue-Bridge debug log that anything happened.

Posted on
Sat Mar 17, 2018 1:02 pm
autolog offline
Posts: 3988
Joined: Sep 10, 2013
Location: West Sussex, UK [GMT aka UTC]

Re: Discovery no longer working after upgrade to 3.0.20

You can delete the devices via the Amazon Alexa website - it has a delete all.

I am at a bit of a loss as to why it isn't working. :|

Unfortunately, at the moment, I have run out of available time to probe this deeper.
Hopefully, I can look at it in more detail in a week or two if the problem hasn't been resolved - sorry. :|

Posted on
Sun Apr 15, 2018 11:22 am
ottoppp offline
Posts: 12
Joined: Oct 21, 2013

Re: Discovery no longer working after upgrade to 3.0.20

I have been working on this for quite some time, and have not found a solution. I think I have discovered why it's happening, but not why there is a change between 2.0.11 and 3.0.2X.

I was running Indigo 7.1.1 on a computer running macOS 10.12.6 with macOS Server 5.4 installed. I think it is macOS Server that is the cause. Running Indigo in a VMWare Fusion virtual machine without macOS Server on the same computer allows discovery to work. This is my workaround.

As to what is causing discovery to fail on the machine running macOS server, my investigations haven't been successful. The 8178 server port is open and responding. The uPnP port is open by the plugin and responding. I have altered the Apache proxy server configuration to not respond on all IP addresses and created a separate IP address for Indigo. It might be the presence of multiple network interfaces, but I cannot remove the multiple interfaces from this configuration to test. There may be a time when I can try that, and will report back if that is successful or not.

Posted on
Sun Apr 15, 2018 3:56 pm
jay (support) offline
Site Admin
User avatar
Posts: 18200
Joined: Mar 19, 2008
Location: Austin, Texas

Re: Discovery no longer working after upgrade to 3.0.20

Multiple active interfaces will often times cause UPnP/Bonjour related failures because macOS doesn't to a particularly good job of prioritizing one interface over the other. So the Bonjour discovery will bind to one interface, but when the plugin creates the actual connection it binds to the other one. I don't know of any way to work around it (other than only having a single interface enabled).

Jay (Indigo Support)
Twitter | Facebook | LinkedIn

Posted on
Sun Apr 15, 2018 3:58 pm
ottoppp offline
Posts: 12
Joined: Oct 21, 2013

Re: Discovery no longer working after upgrade to 3.0.20

I figured out a way to temporarily eliminate the other active interfaces. I restarted the app, still no luck. I restarted the computer, still no luck. That doesn't appear to be the issue.

Page 1 of 1

Who is online

Users browsing this forum: No registered users and 1 guest