Alexa not discovering

Posted on
Wed Jan 04, 2017 7:07 am
kcossabo offline
Posts: 38
Joined: Dec 02, 2007

Alexa not discovering

I am having issues with Alexa not discovering the plugin. I worked through a few issues, and think I am in a networking one now, but would appreciate input.

Setup/Background

    OS = 10.10.5
    plugin version =2.0.9
    Indigo Version = 7.0.2
    Platform = Mac Mini
    Network has a trunk with native VLAN being 192.168.11.x
    Secondary VLAN to 192.168.12.x (shutdown at this point)
    Wireless off
    Amazon Echo in network 192.168.11.x
    Mac Mini also running OS X Server (10.10.5) with DHCP/DNS/Open Directory running
    Indigo plugin 'Hue Light' working to Hue Hub (real version2)
    Amazon Echo controlling Hue Hub (in network 192.168.11.x) fine
    Mac Mini reports wrong IP when doing socket.gethostbyname(socket.gethostname())
    Set ip Address in the 'Alexa-Hue Bridge' to the IP address of the ethernet (native VLAN)
    Turned on all Debug in 'Alexa-Hue Bridge'
    Virtual Device for the Alexa-Hue Bridge configured and is showing discoverable

Log when reseting the 'Alexa-Hue Bridge'
Code: Select all
Jan 4, 2017, 7:58:37 AM
   Reloading plugin "Alexa-Hue Bridge 2.0.9"
   Stopping plugin "Alexa-Hue Bridge 2.0.9" (pid 1146)
   Alexa-Hue Bridge                HTTP server stopped...
   Stopped plugin "Alexa-Hue Bridge 2.0.9"
   Starting plugin "Alexa-Hue Bridge 2.0.9" (pid 38226)
   Alexa-Hue Bridge                Alexa-Hue Bridge initialising . . .
   Alexa-Hue Bridge                Host IP Address overridden and specified as: '192.168.11.2'
   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 2.0.9"
   Alexa-Hue Bridge                Alexa-Hue Bridge initialization complete
   Alexa-Hue Bridge                Hue Bridge 'Alexa-Bridge-1' Host: 192.168.11.2
   Alexa-Hue Bridge                'Alexa-Bridge-1' has one device published
   Alexa-Hue Bridge                Starting Hue Bridge 'Alexa-Bridge-1' web server thread
   Alexa-Hue Bridge                Starting Hue Bridge 'Alexa-Bridge-1' discovery thread as 'Auto Start Discovery' requested


When asking the Amazon Echo to discover my devices, there is NO LOG in Indigo

From a Mac on the network if I go to http://192.168.11.2:8178

Code: Select all
<head>
<title>Alexa Hue Bridge</title>
</head>
<body>
This is the Alexa Hue Bridge plugin for Indigo. It allows some devices in Indigo to present on the local network as Hue
bulbs and makes them discoverable in a way that allows any Alexa device (Echo, FireTV, etc.) to find and control them.
</body>


Thoughts

I am assuming that the Amazon Echo is broadcasting something on the VLAN 192.168.11.x and for some reason the plugin is not seeing the broadcast. Since DHCP is also a broadcast, and Indigo could discover the real HUE HUB, I assume the Mac Mini can see broadcasts on the 192.168.11.x segment, but not the Amazon Echo.

I can not find how to discover the IP or MAC of the Amazon Echo. I have a few suspects but not sure.

Assuming that the discovery protocol is something like a UPNP broadcast, I assume that there is a process blocking it to Indigo?

I thought it might be the OS X Server app, but can not see a way to 'shutdown' it to let the discovery occur

Any Help is appreciated at this point.

Posted on
Wed Jan 04, 2017 7:31 am
autolog offline
Posts: 3243
Joined: Sep 10, 2013
Location: West Sussex, UK [GMT+1 aka UTC+1]

Re: Alexa not discovering

I have just posted separately how to check for debug logs and check port 1900. :)

Posted on
Wed Jan 04, 2017 7:51 am
kcossabo offline
Posts: 38
Joined: Dec 02, 2007

Re: Alexa not discovering

Thank you. Now to understand what I am seeing in the log and the command.

Code: Select all
homeserver:~ Dad$ sudo lsof -i :1900
Password:
COMMAND   PID USER   FD   TYPE            DEVICE SIZE/OFF NODE NAME
IndigoPlu 685  Dad   21u  IPv4 0x34f252ca6f40bab      0t0  UDP *:ssdp
homeserver:~ Dad$


I assume that is not blocked

For the log, I reset the plugin, and then did a discovery from Amazon Echo

Code: Select all
2017-01-04 08:47:31.132   THREADDEBUG    Plugin.method.deviceStopComm            CLASS: Plugin
2017-01-04 08:47:31.132   DEBUG          Plugin.server.stop                      Httpd.stop called
2017-01-04 08:47:31.516   INFO           Plugin.server.stop                      HTTP server stopped...
2017-01-04 08:47:31.516   THREADDEBUG    Plugin.method.setDeviceDiscoveryState   CLASS: Plugin
2017-01-04 08:47:31.516   DEBUG          Plugin.general.setDeviceDiscoveryState   SET DEVICE DISCOVERY STATE = False
2017-01-04 08:47:31.521   DEBUG          Plugin.broadcaster.stop                      Broadcaster thread stopped
2017-01-04 08:47:31.521   THREADDEBUG    Plugin.method.setDeviceDiscoveryState   CLASS: Plugin
2017-01-04 08:47:31.521   DEBUG          Plugin.general.setDeviceDiscoveryState   SET DEVICE DISCOVERY STATE = False
2017-01-04 08:47:31.525   DEBUG          Plugin.responder.stop                      Responder thread stopped
2017-01-04 08:47:31.525   THREADDEBUG    Plugin.method.shutdown                  CLASS: Plugin
2017-01-04 08:47:31.525   DEBUG          Plugin.general.shutdown                  shutdown called
2017-01-04 08:47:32.201   DEBUG          Plugin.responder.run                       Responder.run: self.interrupted: True
2017-01-04 08:47:32.201   THREADDEBUG    Plugin.method.setDeviceDiscoveryState   CLASS: Plugin
2017-01-04 08:47:32.201   DEBUG          Plugin.general.setDeviceDiscoveryState   SET DEVICE DISCOVERY STATE = False
2017-01-04 08:47:32.202   THREADDEBUG    Plugin.method.setDeviceDiscoveryState   CLASS: Plugin
2017-01-04 08:47:32.202   DEBUG          Plugin.general.setDeviceDiscoveryState   SET DEVICE DISCOVERY STATE = False
2017-01-04 08:47:35.208   INFO           Plugin.general.__init__                  Alexa-Hue Bridge initialising . . .
2017-01-04 08:47:35.210   INFO           Plugin.general.closedPrefsConfigUi       Host IP Address overridden and specified as: '192.168.11.2'
2017-01-04 08:47:35.210   INFO           Plugin.general.closedPrefsConfigUi       Alexa discovery request logging enabled
2017-01-04 08:47:35.211   WARNING        Plugin.general.setDebuggingLevels        Debugging enabled for Alexa-Hue Bridge: General, Server, Broadcaster, Responder, Method Trace
2017-01-04 08:47:35.219   THREADDEBUG    Plugin.method.startup                   CLASS: Plugin
2017-01-04 08:47:35.219   INFO           Plugin.general.startup                   Alexa-Hue Bridge initialization complete
2017-01-04 08:47:35.223   THREADDEBUG    Plugin.method.deviceStartComm           CLASS: Plugin
2017-01-04 08:47:35.223   DEBUG          Plugin.general.deviceStartComm           DEVICE START: Alexa-Bridge-1
2017-01-04 08:47:35.220   DEBUG          Plugin.server.run                       Discovery Logging thread initialised.
2017-01-04 08:47:35.223   THREADDEBUG    Plugin.method.deviceStartComm           CLASS: Plugin
2017-01-04 08:47:35.223   INFO           Plugin.general.deviceStartComm           Hue Bridge 'Alexa-Bridge-1' Host: 192.168.11.2
2017-01-04 08:47:35.226   THREADDEBUG    Plugin.method.refreshDeviceList         CLASS: Plugin
2017-01-04 08:47:35.264   DEBUG          Plugin.general.refreshDeviceList         found published device: 1863492555 - house
2017-01-04 08:47:35.291   INFO           Plugin.general.refreshDeviceList         'Alexa-Bridge-1' has one device published
2017-01-04 08:47:35.291   INFO           Plugin.general.deviceStartComm           Starting Hue Bridge 'Alexa-Bridge-1' web server thread
2017-01-04 08:47:35.291   INFO           Plugin.general.deviceStartComm           Starting Hue Bridge 'Alexa-Bridge-1' discovery thread as 'Auto Start Discovery' requested
2017-01-04 08:47:35.292   DEBUG          Plugin.server.run                       Httpd.run called
2017-01-04 08:47:35.292   DEBUG          Plugin.broadcaster.__init__                  Broadcaster.__init__ for 'Alexa-Bridge-1' is running
2017-01-04 08:47:35.292   DEBUG          Plugin.server.run                       Httpd.run SocketServer.ThreadingTCPServer
2017-01-04 08:47:35.292   DEBUG          Plugin.responder.__init__                  Responder.__init__ for 'Alexa-Bridge-1' is running
2017-01-04 08:47:35.447   DEBUG          Plugin.responder.run                       Responder.run called
2017-01-04 08:47:35.447   DEBUG          Plugin.broadcaster.run                       Broadcaster.run called
2017-01-04 08:47:35.447   DEBUG          Plugin.server.run                       Httpd.run calling server.serve_forever()
2017-01-04 08:47:35.447   THREADDEBUG    Plugin.method.setDeviceDiscoveryState   CLASS: Plugin
2017-01-04 08:47:35.447   DEBUG          Plugin.broadcaster.run                       Broadcaster.run: sending first broadcast:
NOTIFY * HTTP/1.1
HOST: 239.255.255.250:1900
CACHE-CONTROL: max-age=100
LOCATION: http://192.168.11.2:8178/description.xml
SERVER: FreeRTOS/7.4.2, UPnP/1.0, IpBridge/1.7.0
NTS: ssdp:alive
NT: uuid:86f660d4-d209-11e6-a266-a82066319edb
USN: uuid:86f660d4-d209-11e6-a266-a82066319edb


2017-01-04 08:47:35.448   DEBUG          Plugin.general.setDeviceDiscoveryState   SET DEVICE DISCOVERY STATE = True
2017-01-04 08:47:35.453   THREADDEBUG    Plugin.method.didDeviceCommPropertyChange CLASS: Plugin
2017-01-04 08:47:35.454   DEBUG          Plugin.general.didDeviceCommPropertyChange DID-DEVICE-COMM-PROPERTY-CHANGE: Old [Alexa-Bridge-1] vs New [Alexa-Bridge-1]
2017-01-04 08:47:35.454   THREADDEBUG    Plugin.method.didDeviceCommPropertyChange CLASS: Plugin
2017-01-04 08:47:35.454   DEBUG          Plugin.general.didDeviceCommPropertyChange DID-DEVICE-COMM-PROPERTY-CHANGE: Old [Alexa-Bridge-1] vs New [Alexa-Bridge-1]
2017-01-04 08:47:35.454   THREADDEBUG    Plugin.method.didDeviceCommPropertyChange CLASS: Plugin
2017-01-04 08:47:35.454   DEBUG          Plugin.general.didDeviceCommPropertyChange DID-DEVICE-COMM-PROPERTY-CHANGE: Old [Alexa-Bridge-1] vs New [Alexa-Bridge-1]
2017-01-04 08:48:19.566   DEBUG          Plugin.responder.run                       Responder.run: received: M-SEARCH * HTTP/1.1
Host:239.255.255.250:1900
ST:urn:schemas-upnp-org:service:WANPPPConnection:1
Man:"ssdp:discover"
MX:3


2017-01-04 08:48:19.566   DEBUG          Plugin.responder.respond                   Responder.respond called from address ('192.168.11.2', 51911)
HTTP/1.1 200 OK
CACHE-CONTROL: max-age=100
EXT:
LOCATION: http://192.168.11.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:86f660d4-d209-11e6-a266-a82066319edb


2017-01-04 08:48:19.566   DEBUG          Plugin.responder.respond                   Responder.respond: creating output_socket
2017-01-04 08:48:19.566   DEBUG          Plugin.responder.respond                   Responder.respond: calling output_socket.sendto
2017-01-04 08:48:19.566   DEBUG          Plugin.responder.respond                   Responder.respond: closing output_socket
2017-01-04 08:48:19.566   DEBUG          Plugin.responder.respond                   Responder.respond: UDP Response sent to ('192.168.11.2', 51911)
2017-01-04 08:48:19.567   DEBUG          Plugin.responder.run                       Responder.run: received: M-SEARCH * HTTP/1.1
Host:239.255.255.250:1900
ST:urn:schemas-upnp-org:service:WANIPConnection:1
Man:"ssdp:discover"
MX:3


2017-01-04 08:48:19.567   DEBUG          Plugin.responder.respond                   Responder.respond called from address ('192.168.11.2', 51911)
HTTP/1.1 200 OK
CACHE-CONTROL: max-age=100
EXT:
LOCATION: http://192.168.11.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:86f660d4-d209-11e6-a266-a82066319edb


2017-01-04 08:48:19.567   DEBUG          Plugin.responder.respond                   Responder.respond: creating output_socket
2017-01-04 08:48:19.567   DEBUG          Plugin.responder.respond                   Responder.respond: calling output_socket.sendto
2017-01-04 08:48:19.567   DEBUG          Plugin.responder.respond                   Responder.respond: closing output_socket
2017-01-04 08:48:19.567   DEBUG          Plugin.responder.respond                   Responder.respond: UDP Response sent to ('192.168.11.2', 51911)
2017-01-04 08:48:19.568   DEBUG          Plugin.responder.run                       Responder.run: received: M-SEARCH * HTTP/1.1
Host:239.255.255.250:1900
ST:urn:schemas-upnp-org:service:WANPPPConnection:1
Man:"ssdp:discover"
MX:3


2017-01-04 08:48:19.568   DEBUG          Plugin.responder.respond                   Responder.respond called from address ('192.168.11.2', 51911)
HTTP/1.1 200 OK
CACHE-CONTROL: max-age=100
EXT:
LOCATION: http://192.168.11.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:86f660d4-d209-11e6-a266-a82066319edb


2017-01-04 08:48:19.568   DEBUG          Plugin.responder.respond                   Responder.respond: creating output_socket
2017-01-04 08:48:19.568   DEBUG          Plugin.responder.respond                   Responder.respond: calling output_socket.sendto
2017-01-04 08:48:19.568   DEBUG          Plugin.responder.respond                   Responder.respond: closing output_socket
2017-01-04 08:48:19.568   DEBUG          Plugin.responder.respond                   Responder.respond: UDP Response sent to ('192.168.11.2', 51911)


I will read through this to see if I can tell if I am getting a request from the Amazon Echo, or not.

Thank you for the info on the log!

Posted on
Thu Jan 05, 2017 6:42 am
mattggarland offline
Posts: 49
Joined: Jan 06, 2013

Re: Alexa not discovering

Hi Guys,
Having a problem with alexa plugin in indigo 6. I can't create a virtual hue bridge, it's not an option in the new device type dropdown. Any thoughts?
Thanks,
Matt

Posted on
Thu Jan 05, 2017 7:37 am
autolog offline
Posts: 3243
Joined: Sep 10, 2013
Location: West Sussex, UK [GMT+1 aka UTC+1]

Re: Alexa not discovering

The new version of the plugin (V2.x.x) supports Alexa-Hue Bridge devices and enables you to exceed the Alexa limit of 27 devices by configuring multiple devices.
It is an Indigo 7+ plugin i.e. doesn't run on Indigo 6.

Assuming you are running the earlier version of the plugin, this doesn't support Alexa-Hue Bridge devices (so limits you to 27 devices) and you configure it via the plugin menu.

Hope this helps. :)

Posted on
Sat Jan 14, 2017 9:47 am
kcossabo offline
Posts: 38
Joined: Dec 02, 2007

Re: Alexa not discovering

Giving up.

I rebuilt the Mac, Format the HDD, install OS X, instal Indigo, restore back up of devices, Alexa can not find Indigo. :(

I did some wershark captures of the ethernet and I do see the broadcasts from the server on the wire, and attempted to do a wireshark capture of the wifi, where I saw no broadcast from the server. Not sure if the Wireless adaptor was in a promiscuous mode or not, so I might have missed it?

Anyway, with a fresh build and not working, time to move on for a bit.

Posted on
Sat Jan 14, 2017 5:11 pm
jay (support) offline
Site Admin
User avatar
Posts: 16264
Joined: Mar 19, 2008
Location: Austin, Texas

Re: Alexa not discovering

kcossabo wrote:
I did some wershark captures of the ethernet and I do see the broadcasts from the server on the wire, and attempted to do a wireshark capture of the wifi, where I saw no broadcast from the server.


BTW - if you have both WiFi and Ethernet enabled on a single Mac on the same network at the same time that might be the problem. It's not really a recommended configuration, but more importantly multicast/upnp/bonjour doesn't like it at all.

Jay (Indigo Support)
Twitter | Facebook | LinkedIn

Posted on
Mon Jan 16, 2017 9:47 am
kcossabo offline
Posts: 38
Joined: Dec 02, 2007

Re: Alexa not discovering

@Jay

I assumed that, most apps do not like multi homed hosts. In my testing I had JUST the Ethernet enabled, the Amazon Echo, needs to be on WiFi, so I was trying to see what it saw on the air.

My Hue Hub is on the same Ethernet Subnet as the Mac Mini, and Indigo sees it fine (devices added) and the Amazon Echo sees the Hue Hub fine as well (devices added to it).

Posted on
Tue Jan 24, 2017 7:50 am
kcossabo offline
Posts: 38
Joined: Dec 02, 2007

Re: Alexa not discovering

:D

Today, after doing nothing to fix this, I see in the log;

Code: Select all
 Alexa-Hue Bridge                Alexa-Hue Bridge 'new device 4' responding to Alexa discovery [request id: 1117] ...
   Alexa-Hue Bridge                + Publishing device 'jacob' to Alexa
   Alexa-Hue Bridge                ... One device discovered by Alexa on Alexa-Hue Bridge 'new device 4'.
   Alexa-Hue Bridge                Alexa-Hue Bridge 'Alexa-Bridge-1' responding to Alexa discovery [request id: 1118] ...
   Alexa-Hue Bridge                + Publishing device 'Backyard - Deck' to Alexa
   Alexa-Hue Bridge                + Publishing device 'home' to Alexa
   Alexa-Hue Bridge                ... 2 devices discovered by Alexa on Alexa-Hue Bridge 'Alexa-Bridge-1'.
   Alexa-Hue Bridge                Alexa-Hue Bridge 'new device 4' responding to Alexa discovery [request id: 1119] ...
   Alexa-Hue Bridge                + Publishing device 'jacob' to Alexa
   Alexa-Hue Bridge                ... One device discovered by Alexa on Alexa-Hue Bridge 'new device 4'.
   Alexa-Hue Bridge                Alexa-Hue Bridge 'Alexa-Bridge-1' responding to Alexa discovery [request id: 1120] ...
   Alexa-Hue Bridge                + Publishing device 'Backyard - Deck' to Alexa
   Alexa-Hue Bridge                + Publishing device 'home' to Alexa
   Alexa-Hue Bridge                ... 2 devices discovered by Alexa on Alexa-Hue Bridge 'Alexa-Bridge-1'.


And yes it :) works :)

"Alexa, turn on Home"
[*] iTunes on the Mac Mini starts to play over whole house Audio!!!

Wish I knew what changed :?

Page 1 of 1

Who is online

Users browsing this forum: No registered users and 2 guests