You must be getting to hate these posts, but here I am, failing to get my Alexa to discover my Alexa/Hue bridge device. I have followed the instructions for the latest plugin, have the latest Indigo update and run discovery on the Echo, but Alexa never finds my device (a Zwave power socket which Indigo is very happy to control successfully)
Despite having enabled debugging in the plugin I dont see any relevant messages there either at discovery time. Here is the only part of the event log that ever mentions the plugin:
Alexa-Hue Bridge Alexa-Hue Bridge initialising . . .
Alexa-Hue Bridge Alexa discovery request logging enabled
Alexa-Hue Bridge Warning Debugging enabled for Alexa-Hue Bridge: General, Server, Broadcaster, Responder, Method Trace
Started plugin "Alexa-Hue Bridge 3.0.11"
Alexa-Hue Bridge Alexa-Hue Bridge checking network access by attempting to access 'www.google.com'
Alexa-Hue Bridge Alexa-Hue Bridge network access check to http://www.google.com successfully completed.
Alexa-Hue Bridge Alexa-Hue Bridge initialization complete
Alexa-Hue Bridge Hue Bridge 'EchoEMU' Host: 192.168.1.64
Alexa-Hue Bridge Hue Bridge 'EchoEMU' Host: 192.168.1.64
Alexa-Hue Bridge 'EchoEMU' has one Alexa Device published
Alexa-Hue Bridge Starting Hue Bridge 'EchoEMU' web server thread
Alexa-Hue Bridge Starting Hue Bridge 'EchoEMU' discovery thread as 'Auto Start Discovery' requested
What I see in the Alexa-hue-bridge debug folder is
2017-09-10 09:16:21.864 DEBUG Plugin.responder.respond Responder.respond called from address ('192.168.1.64', 4455)
HTTP/1.1 200 OK
CACHE-CONTROL: max-age=100
EXT:
LOCATION: http://192.168.1.64: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:9b0af985-95a6-11e7-8122-0c4de9cc78e1
2017-09-10 09:16:21.864 DEBUG Plugin.responder.respond Responder.respond: creating output_socket
2017-09-10 09:16:21.864 DEBUG Plugin.responder.respond Responder.respond: calling output_socket.sendto
2017-09-10 09:16:21.864 DEBUG Plugin.responder.respond Responder.respond: closing output_socket
2017-09-10 09:16:21.864 DEBUG Plugin.responder.respond Responder.respond: UDP Response sent to ('192.168.1.64', 4455)
2017-09-10 09:16:21.864 DEBUG Plugin.responder.run Responder.run: received: M-SEARCH * HTTP/1.1
MX: 5
ST: upnp:rootdevice
MAN: "ssdp:discover"
User-Agent: UPnP/1.0 DLNADOC/1.50 Platinum/1.0.5.13
Connection: close
Host: 239.255.255.250:1900
2017-09-10 09:16:21.864 DEBUG Plugin.responder.respond Responder.respond called from address ('192.168.1.64', 4455)
HTTP/1.1 200 OK
CACHE-CONTROL: max-age=100
EXT:
LOCATION: http://192.168.1.64: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:9b0af985-95a6-11e7-8122-0c4de9cc78e1
2017-09-10 09:16:21.864 DEBUG Plugin.responder.respond Responder.respond: creating output_socket
2017-09-10 09:16:21.864 DEBUG Plugin.responder.respond Responder.respond: calling output_socket.sendto
2017-09-10 09:16:21.864 DEBUG Plugin.responder.respond Responder.respond: closing output_socket
2017-09-10 09:16:21.864 DEBUG Plugin.responder.respond Responder.respond: UDP Response sent to ('192.168.1.64', 4455)
2017-09-10 09:16:29.477 DEBUG Plugin.responder.run Responder.run: received: M-SEARCH * HTTP/1.1
Host: 239.255.255.250:1900
Man: "ssdp:discover"
ST: ssdp:all
MX: 5
2017-09-10 09:16:29.478 DEBUG Plugin.responder.respond Responder.respond called from address ('192.168.1.64', 58688)
HTTP/1.1 200 OK
CACHE-CONTROL: max-age=100
EXT:
LOCATION: http://192.168.1.64: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:9b0af985-95a6-11e7-8122-0c4de9cc78e1
2017-09-10 09:16:29.478 DEBUG Plugin.responder.respond Responder.respond: creating output_socket
2017-09-10 09:16:29.478 DEBUG Plugin.responder.respond Responder.respond: calling output_socket.sendto
2017-09-10 09:16:29.478 DEBUG Plugin.responder.respond Responder.respond: closing output_socket
2017-09-10 09:16:29.478 DEBUG Plugin.responder.respond Responder.respond: UDP Response sent to ('192.168.1.64', 58688)
over and over again.
I have tried restarting the software, the plugin and the Echo. Where do I go from here? I know it must be so hard for you to second-guess what I have done wrong (which is almost certainly true!) but some guidance as to how to investigate the issue would be very welcome.