Alexa not finding Indigo

Posted on
Tue Dec 27, 2016 5:32 pm
kbwidener offline
Posts: 2
Joined: Dec 27, 2016

Alexa not finding Indigo

I have an Echo and when I ask Alexa to find devices, the only one it finds is my Nest thermostat. I have the Indigo 7 log turned on and I'm not seeing any queries from Alexa. I do show the 6 devices that I've added as published devices. Both Alexa and my computer are on the same WiFi network. Discovery is turned ON.

Don't know if this is a hint or something totally different but when I try "Open Scripting Shell", the terminal window has "ImportError: No module named site"

Any help is appreciated, thanks!

Kevin

Posted on
Wed Dec 28, 2016 9:23 am
Brady offline
Posts: 57
Joined: May 25, 2016

Re: Alexa not finding Indigo

Not to hijack your thread, but I think we may be experiencing the same issue. The Alexa-Hue plugin is enabled and discovery is ON. My Alexa finds nothing but my Nest Thermostat.

Looking in my logs (they are buried in Application Support, doesn't write to Indigo log window) I see the following...

Code: Select all
2016-12-28 09:18:35.414   INFO           Plugin.general.__init__                  Alexa-Hue Bridge initilizing . . .
2016-12-28 09:18:35.417   WARNING        Plugin.general.setDebuggingLevels        Debugging enabled for Alexa-Hue Bridge: General, Server, Broadcaster, Responder, Method Trace
2016-12-28 09:18:35.422   THREADDEBUG    Plugin.method.startup                   CLASS: Plugin
2016-12-28 09:18:35.423   INFO           Plugin.general.startup                   Alexa-Hue Bridge initialization complete
2016-12-28 09:18:35.426   THREADDEBUG    Plugin.method.deviceStartComm           CLASS: Plugin
2016-12-28 09:18:35.426   DEBUG          Plugin.general.deviceStartComm           DEVICE START: Utility - Alexa Bridge - Lights
2016-12-28 09:18:35.426   THREADDEBUG    Plugin.method.deviceStartComm           CLASS: Plugin
2016-12-28 09:18:35.429   THREADDEBUG    Plugin.method.refreshDeviceList         CLASS: Plugin
2016-12-28 09:18:35.440   DEBUG          Plugin.general.refreshDeviceList         found published device: 956872863 - Family Room - Light - Couch
2016-12-28 09:18:35.455   DEBUG          Plugin.general.refreshDeviceList         found published device: 1125957587 - Kitchen - Light - Island
2016-12-28 09:18:35.464   INFO           Plugin.general.refreshDeviceList         'Utility - Alexa Bridge - Lights' has 2 devices published
2016-12-28 09:18:35.465   INFO           Plugin.general.deviceStartComm           Starting Hue Bridge 'Utility - Alexa Bridge - Lights' web server thread
2016-12-28 09:18:35.465   DEBUG          Plugin.server.run                       Httpd.run called
2016-12-28 09:18:35.465   INFO           Plugin.general.deviceStartComm           Starting Hue Bridge 'Utility - Alexa Bridge - Lights' discovery threads as 'Auto Start Discovery' requested
2016-12-28 09:18:35.466   DEBUG          Plugin.server.run                       Httpd.run SocketServer.ThreadingTCPServer
2016-12-28 09:18:35.466   DEBUG          Plugin.broadcaster.__init__                  Broadcaster.__init__ for 'Utility - Alexa Bridge - Lights' is running
2016-12-28 09:18:35.467   DEBUG          Plugin.broadcaster.__init__                  Broadcaster.__init__ for 'Utility - Alexa Bridge - Lights' is running
2016-12-28 09:18:35.467   DEBUG          Plugin.broadcaster.run                       Broadcaster.run called
2016-12-28 09:18:35.467   DEBUG          Plugin.responder.run                       Responder.run called
2016-12-28 09:18:35.467   DEBUG          Plugin.general.setDeviceDiscoveryState   SET DEVICE DISCOVERY STATE = True
2016-12-28 09:18:35.467   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://0.0.0.192:8178/description.xml
SERVER: FreeRTOS/7.4.2, UPnP/1.0, IpBridge/1.7.0
NTS: ssdp:alive
NT: uuid:dee596e1-cc7b-11e6-a2f3-a8206637971e
USN: uuid:dee596e1-cc7b-11e6-a2f3-a8206637971e


2016-12-28 09:18:35.474   THREADDEBUG    Plugin.method.didDeviceCommPropertyChange CLASS: Plugin
2016-12-28 09:18:35.474   DEBUG          Plugin.general.setDeviceDiscoveryState   SET DEVICE DISCOVERY STATE = False
2016-12-28 09:18:35.475   DEBUG          Plugin.general.didDeviceCommPropertyChange DID-DEVICE-COMM-PROPERTY-CHANGE: Old [Utility - Alexa Bridge - Lights] vs New [Utility - Alexa Bridge - Lights]
2016-12-28 09:18:35.479   THREADDEBUG    Plugin.method.didDeviceCommPropertyChange CLASS: Plugin
2016-12-28 09:18:35.480   DEBUG          Plugin.general.didDeviceCommPropertyChange DID-DEVICE-COMM-PROPERTY-CHANGE: Old [Utility - Alexa Bridge - Lights] vs New [Utility - Alexa Bridge - Lights]
2016-12-28 09:18:35.480   THREADDEBUG    Plugin.method.didDeviceCommPropertyChange CLASS: Plugin
2016-12-28 09:18:35.481   DEBUG          Plugin.general.didDeviceCommPropertyChange DID-DEVICE-COMM-PROPERTY-CHANGE: Old [Utility - Alexa Bridge - Lights] vs New [Utility - Alexa Bridge - Lights]
2016-12-28 09:18:35.481   THREADDEBUG    Plugin.method.didDeviceCommPropertyChange CLASS: Plugin
2016-12-28 09:18:35.481   DEBUG          Plugin.general.didDeviceCommPropertyChange DID-DEVICE-COMM-PROPERTY-CHANGE: Old [Utility - Alexa Bridge - Lights] vs New [Utility - Alexa Bridge - Lights]
2016-12-28 09:18:35.482   THREADDEBUG    Plugin.method.didDeviceCommPropertyChange CLASS: Plugin
2016-12-28 09:18:35.482   DEBUG          Plugin.general.didDeviceCommPropertyChange DID-DEVICE-COMM-PROPERTY-CHANGE: Old [Utility - Alexa Bridge - Lights] vs New [Utility - Alexa Bridge - Lights]



After the plugin is running, if I check to see what upnp is active by running "sue lsof -i :1900"... nothing shows. If I do enable the Sonos Plugin, I will see it listed. While troubleshooting the Alexa issue, I have the Sonos plugin completely disabled just to make sure there are no upnp conflicts.

One interesting thing in the log... The location IP address of 0.0.0.192 looks very wrong to me... My actual local IP address is 192.168.1.125. I can not get the description.xml to show at all.

Any help would be greatly appreciated. I've tried the newest plugin & also the latest marked 'pre release'.

If this isn't exactly matching kbwidener's issue - Apologies!

Posted on
Wed Dec 28, 2016 10:40 am
Brady offline
Posts: 57
Joined: May 25, 2016

Re: Alexa not finding Indigo

I upgraded again to 2.0.8 and noticed that this version adds the following log item.

Code: Select all
2016-12-28 11:37:43.012   DEBUG          Plugin.general.setDeviceDiscoveryState   SET DEVICE DISCOVERY STATE = True
2016-12-28 11:37:43.017   DEBUG          Plugin.responder.run                       Responder.run: socket error: 49 - Can't assign requested address

Posted on
Wed Dec 28, 2016 3:45 pm
clawmd offline
Posts: 87
Joined: Jan 01, 2007

Re: Alexa not finding Indigo

My log also was showing this same error. Unfortunately, we were never able to figure it out. My knowledge is limited in this area. I spent some time searching and didn't find any obvious answers. In my case I checked that my Linksys router has Upnp checked and the firewall is turned off on my iMac. I also ran sudo lsof -1 :1900 in terminal and got no response. Reloading the plugin, restarting computer, resetting Echo dot, etc had no effect.

Posted on
Wed Dec 28, 2016 8:27 pm
Brady offline
Posts: 57
Joined: May 25, 2016

Re: Alexa not finding Indigo

I am actually in the middle of moving my Indigo install to a new Mac which is how I discovered this... Comparing the old Mac (plugin works) to the new Mac (plugin doesn't work), it seems that the new Mac is trying to start the plugin on the wrong IP address.

Old is using the correct IP address. It lists the actual IP the Mac is using on my LAN.
LOCATION: http://192.168.1.199:8179/description.xml

The new Mac is using something that makes no sense... Not sure if it is using the wrong network interface?
LOCATION: http://0.0.0.192:8178/description.xml

The actual IP is 192.168.1.225 for the newer Mac.

Posted on
Wed Dec 28, 2016 9:33 pm
Brady offline
Posts: 57
Joined: May 25, 2016

Re: Alexa not finding Indigo

Didn't have a ton of time, but I spent some time trying to troubleshoot this...

In discovery.py, if I change

self._host = PLUGIN.globals['hueBridge'][self.ahbDevId]['host']

to

self._host = "192.168.1.125"

it will stop the socket errors. Discovery starts fine and I can see the Alexa talking to the plugin in the logs. I also finally see the plugin listed by checking the port with lsof -I :1900. It is closer, but not all the way there. I still can't access http://192.168.1.125:8178/description.xml (and I don't think Alexa can either, because it isn't actually finding devices in discovery).

Posted on
Thu Dec 29, 2016 11:01 am
jay (support) offline
Site Admin
User avatar
Posts: 18199
Joined: Mar 19, 2008
Location: Austin, Texas

Re: Alexa not finding Indigo

Code: Select all
self._host = PLUGIN.globals['hueBridge'][self.ahbDevId]['host']


I wonder if it's possible that that host value is not getting set correctly somehow - which would explain the odd IP address. autolog?

Jay (Indigo Support)
Twitter | Facebook | LinkedIn

Posted on
Thu Dec 29, 2016 12:09 pm
clawmd offline
Posts: 87
Joined: Jan 01, 2007

Re: Alexa not finding Indigo

It seems like it would be very useful to identify what is different with a new mac that prevents the plugin from working since this could cause problems with other solutions.

Posted on
Thu Dec 29, 2016 5:33 pm
autolog offline
Posts: 3988
Joined: Sep 10, 2013
Location: West Sussex, UK [GMT aka UTC]

Re: Alexa not finding Indigo

jay (support) wrote:
Code: Select all
self._host = PLUGIN.globals['hueBridge'][self.ahbDevId]['host']


I wonder if it's possible that that host value is not getting set correctly somehow - which would explain the odd IP address. autolog?

Christmas, family and friends have meant I haven't been able to spend as much time as usual on Indigo related matters. :wink:

I will hopefully be able to look at this (and a few PMs I have received with log info) tomorrow when it begins to quieten down. :)

Posted on
Fri Dec 30, 2016 7:59 am
autolog offline
Posts: 3988
Joined: Sep 10, 2013
Location: West Sussex, UK [GMT aka UTC]

Re: Alexa not finding Indigo

Brady wrote:
I am actually in the middle of moving my Indigo install to a new Mac which is how I discovered this... Comparing the old Mac (plugin works) to the new Mac (plugin doesn't work), it seems that the new Mac is trying to start the plugin on the wrong IP address.

Old is using the correct IP address. It lists the actual IP the Mac is using on my LAN.
LOCATION: http://192.168.1.199:8179/description.xml

The new Mac is using something that makes no sense... Not sure if it is using the wrong network interface?
LOCATION: http://0.0.0.192:8178/description.xml

The actual IP is 192.168.1.225 for the newer Mac.

As a first step to trying to debug this, could you try the following in terminal window?:
Code: Select all
python
import socket
socket.gethostbyname(socket.gethostname())
and post back the results (for both the old Mac and the new Mac).

Thanks :)

EDIT: Also what versions of OS X / macOS are you running on your Macs?

Posted on
Fri Dec 30, 2016 8:40 am
RogueProeliator offline
User avatar
Posts: 2501
Joined: Nov 13, 2012
Location: Baton Rouge, LA

Re: Alexa not finding Indigo

Jon, just a suggestion, but you might ought to add that hostname check to the plugin - maybe spit that out on startup of discovery or something? Not sure you could do too much with it inside the plugin, but putting it in the logs for when users post them here could be beneficial.

Just a thought...

Adam

Posted on
Fri Dec 30, 2016 8:43 am
Brady offline
Posts: 57
Joined: May 25, 2016

Re: Alexa not finding Indigo

Working Mac - El Capitan 10.11.6
Python outputs - '192.168.1.199'

Broken Mac - Sierra 10.12.3 Beta (D'Oh!!!! I had no idea this Mac was flagged for beta installs. I've removed the Mac from getting future betas... My bad.)
Python outputs -' 0.0.0.192'


Obviously a beta release of Sierra could be the culprit... I'll be curious to see if others with the issue are also running a beta.

Posted on
Fri Dec 30, 2016 8:48 am
autolog offline
Posts: 3988
Joined: Sep 10, 2013
Location: West Sussex, UK [GMT aka UTC]

Re: Alexa not finding Indigo

RogueProeliator wrote:
Jon, just a suggestion, but you might ought to add that hostname check to the plugin - maybe spit that out on startup of discovery or something? Not sure you could do too much with it inside the plugin, but putting it in the logs for when users post them here could be beneficial.

Just a thought...

Adam

A good one - I will do that :)

Posted on
Fri Dec 30, 2016 10:21 am
autolog offline
Posts: 3988
Joined: Sep 10, 2013
Location: West Sussex, UK [GMT aka UTC]

Re: Alexa not finding Indigo

Brady wrote:
Working Mac - El Capitan 10.11.6
Python outputs - '192.168.1.199'

Broken Mac - Sierra 10.12.3 Beta (D'Oh!!!! I had no idea this Mac was flagged for beta installs. I've removed the Mac from getting future betas... My bad.)
Python outputs -' 0.0.0.192'


Obviously a beta release of Sierra could be the culprit... I'll be curious to see if others with the issue are also running a beta.


Can you also try:
Code: Select all
python
import socket
socket.gethostname()
I am just wondering if something is adrift with host name?

Feel free to PM me the output, if that's a problem :)

Thanks :)

Posted on
Fri Dec 30, 2016 11:00 am
clawmd offline
Posts: 87
Joined: Jan 01, 2007

Re: Alexa not finding Indigo

My iMac, that does not work with the plugin is running El Capitan 10.11.6. This seems to indicate that the issue is not related to Sierra.

Who is online

Users browsing this forum: No registered users and 2 guests

cron