Alexa Only Discovering Some of My Devices

Good question. Both on same network.

Well I think that there is something odd about your system that is preventing communication with the plugin.

I would double check that you haven't got a firewall in place that is preventing access.

Have you checked that nothing else is conflicting with port 1900 as described under Discovery in the documentation.
You can run the specified command to double check. There is a list of things that are know to use port 1900 at the end of the document.

If after you have checked all this and it still doesn't work, you can PM me the debug log as described next:.

Best to make sure all debug logging is turned on, reload the plugin, let the plugin complete its start up and initialisation of its discovery processing and then ask Alexa to discover devices. Ask her rather than use the App. When she tells you discovery is finished you can PM me the log. If your are able to edit the log and delete entries prior to the plugin reload, it should make the log smaller but don't worry if you can't.

All debug logging info from the plugin gets written to its own plugin.log file in the opensource.alexa-hue-bridge folder contained in the Indigo Logs folder (accessible by clicking on the Show Event Logs Folder in the Indigo Event Log window.

Not sure I will get anything from the logs but it is worth a try.

I won't be able to look at any logs you send me until tomorrow now as it is ~23:30 in the UK and I am off to bed.

[jay (support)]

One other thing: if you have your firewall enabled, make sure that under the options you don't have Stealth Mode enabled - that might block UPnP.

Checked upnp, reset Echo Dot, restarted server, checked that Echo connects to Internet and gets an appropriate IP address. I checked to see if there is some issue with Linksys routers and Echo; nothing. Maybe the Echo Dot is the problem. I getting another Echo Dot anyway so I can test it.

So here is what I get from the log after asking "discover devices"

2016-12-20 18:11:19.263 INFO Plugin.general.__init__ Alexa-Hue Bridge initialising . . .
2016-12-20 18:11:19.265 INFO Plugin.general.validatePrefsConfigUi Alexa discovery request logging enabled
2016-12-20 18:11:19.265 WARNING Plugin.general.setDebuggingLevels Debugging enabled for Alexa-Hue Bridge: General, Server, Broadcaster, Responder, Method Trace
2016-12-20 18:11:19.270 THREADDEBUG Plugin.method.startup CLASS: Plugin
2016-12-20 18:11:19.270 INFO Plugin.general.startup Alexa-Hue Bridge initialization complete
2016-12-20 18:11:19.270 DEBUG Plugin.server.run Discovery Logging thread initialised.
2016-12-20 18:11:19.272 THREADDEBUG Plugin.method.deviceStartComm CLASS: Plugin
2016-12-20 18:11:19.273 DEBUG Plugin.general.deviceStartComm DEVICE START: new device
2016-12-20 18:11:19.273 THREADDEBUG Plugin.method.deviceStartComm CLASS: Plugin
2016-12-20 18:11:19.276 THREADDEBUG Plugin.method.refreshDeviceList CLASS: Plugin
2016-12-20 18:11:19.282 DEBUG Plugin.general.refreshDeviceList found published device: 632251534 - Theater back lights
2016-12-20 18:11:19.288 INFO Plugin.general.refreshDeviceList 'new device' has one device published
2016-12-20 18:11:19.288 INFO Plugin.general.deviceStartComm Starting Hue Bridge 'new device' web server thread
2016-12-20 18:11:19.289 INFO Plugin.general.deviceStartComm Starting Hue Bridge 'new device' discovery thread as 'Auto Start Discovery' requested
2016-12-20 18:11:19.289 DEBUG Plugin.server.run Httpd.run called
2016-12-20 18:11:19.289 DEBUG Plugin.broadcaster.__init__ Broadcaster.__init__ for 'new device' is running
2016-12-20 18:11:19.289 DEBUG Plugin.server.run Httpd.run SocketServer.ThreadingTCPServer
2016-12-20 18:11:19.290 DEBUG Plugin.broadcaster.run Broadcaster.run called
2016-12-20 18:11:19.290 DEBUG Plugin.responder.__init__ Responder.__init__ for 'new device' is running
2016-12-20 18:11:19.290 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://50.199.162.25:8178/description.xml
SERVER: FreeRTOS/7.4.2, UPnP/1.0, IpBridge/1.7.0
NTS: ssdp:alive
NT: uuid:0e97fa1e-c708-11e6-8dfd-685b35b6a083
USN: uuid:0e97fa1e-c708-11e6-8dfd-685b35b6a083


2016-12-20 18:11:19.291 DEBUG Plugin.responder.run Responder.run called
2016-12-20 18:11:19.291 THREADDEBUG Plugin.method.setDeviceDiscoveryState CLASS: Plugin
2016-12-20 18:11:19.291 DEBUG Plugin.general.setDeviceDiscoveryState SET DEVICE DISCOVERY STATE = True
2016-12-20 18:11:19.291 THREADDEBUG Plugin.method.setDeviceDiscoveryState CLASS: Plugin
2016-12-20 18:11:19.296 THREADDEBUG Plugin.method.didDeviceCommPropertyChange CLASS: Plugin
2016-12-20 18:11:19.296 DEBUG Plugin.general.setDeviceDiscoveryState SET DEVICE DISCOVERY STATE = False
2016-12-20 18:11:19.296 DEBUG Plugin.general.didDeviceCommPropertyChange DID-DEVICE-COMM-PROPERTY-CHANGE: Old [new device] vs New [new device]
2016-12-20 18:11:19.300 THREADDEBUG Plugin.method.didDeviceCommPropertyChange CLASS: Plugin
2016-12-20 18:11:19.300 DEBUG Plugin.general.didDeviceCommPropertyChange DID-DEVICE-COMM-PROPERTY-CHANGE: Old [new device] vs New [new device]
2016-12-20 18:11:19.300 THREADDEBUG Plugin.method.didDeviceCommPropertyChange CLASS: Plugin
2016-12-20 18:11:19.301 DEBUG Plugin.general.didDeviceCommPropertyChange DID-DEVICE-COMM-PROPERTY-CHANGE: Old [new device] vs New [new device]
2016-12-20 18:11:19.301 THREADDEBUG Plugin.method.didDeviceCommPropertyChange CLASS: Plugin
2016-12-20 18:11:19.301 DEBUG Plugin.general.didDeviceCommPropertyChange DID-DEVICE-COMM-PROPERTY-CHANGE: Old [new device] vs New [new device]
2016-12-20 18:11:19.301 THREADDEBUG Plugin.method.didDeviceCommPropertyChange CLASS: Plugin
2016-12-20 18:11:19.301 DEBUG Plugin.general.didDeviceCommPropertyChange DID-DEVICE-COMM-PROPERTY-CHANGE: Old [new device] vs New [new device]

I entered sudo lsof -i :81900 and did not get any resulting app

I entered sudo lsof -i :81900 and did not get any resulting app

Not sure if it is a typo, but the command is:

Code: Select all

sudo lsof -i :1900

Looking at the log and the plugin code I can see where an error might be occurring and not being output to the user log.
The log shows an entry:

Code: Select all

2016-12-20 18:11:19.291   DEBUG Plugin.general.setDeviceDiscoveryState SET DEVICE DISCOVERY STATE = True

and then

Code: Select all

2016-12-20 18:11:19.296   DEBUG Plugin.general.setDeviceDiscoveryState SET DEVICE DISCOVERY STATE = False

So it seems to be turning on discovery and then turning it off straight away.

I think an error is being detected (so there is a problem) but it isn't being reported.

Am I correct that after you start the plugin, the Indigo Alexa_Hue device shows a status of 'Discovery: off'?

I just need to dig a bit deeper on this.

Yes to typo. Yes to Discovery:off.

I have uploaded version 2.0.8 (beta) to Github for you to try.

When you get the problem, please post the log or PM it to me.

Hopefully there may be additional debugging info in the log.

Restarted computer, restarted Indigo, reloaded 2.0.8. Aha! Looks like the old "socket error 49" problem. Whatever that is. Sill have same issue. Maybe this provides a clue.

2016-12-21 19:17:11.629 INFO Plugin.general.__init__ Alexa-Hue Bridge initialising . . .
2016-12-21 19:17:11.630 INFO Plugin.general.validatePrefsConfigUi Alexa discovery request logging enabled
2016-12-21 19:17:11.630 WARNING Plugin.general.setDebuggingLevels Debugging enabled for Alexa-Hue Bridge: General, Server, Broadcaster, Responder, Method Trace
2016-12-21 19:17:11.635 THREADDEBUG Plugin.method.startup CLASS: Plugin
2016-12-21 19:17:11.635 INFO Plugin.general.startup Alexa-Hue Bridge initialization complete
2016-12-21 19:17:11.636 DEBUG Plugin.server.run Discovery Logging thread initialised.
2016-12-21 19:17:11.638 THREADDEBUG Plugin.method.deviceStartComm CLASS: Plugin
2016-12-21 19:17:11.638 DEBUG Plugin.general.deviceStartComm DEVICE START: new device
2016-12-21 19:17:11.638 THREADDEBUG Plugin.method.deviceStartComm CLASS: Plugin
2016-12-21 19:17:11.641 THREADDEBUG Plugin.method.refreshDeviceList CLASS: Plugin
2016-12-21 19:17:11.648 DEBUG Plugin.general.refreshDeviceList found published device: 632251534 - Theater back lights
2016-12-21 19:17:11.657 INFO Plugin.general.refreshDeviceList 'new device' has one device published
2016-12-21 19:17:11.657 INFO Plugin.general.deviceStartComm Starting Hue Bridge 'new device' web server thread
2016-12-21 19:17:11.657 INFO Plugin.general.deviceStartComm Starting Hue Bridge 'new device' discovery thread as 'Auto Start Discovery' requested
2016-12-21 19:17:11.658 DEBUG Plugin.broadcaster.__init__ Broadcaster.__init__ for 'new device' is running
2016-12-21 19:17:11.658 DEBUG Plugin.server.run Httpd.run called
2016-12-21 19:17:11.658 DEBUG Plugin.responder.__init__ Responder.__init__ for 'new device' is running
2016-12-21 19:17:11.658 DEBUG Plugin.broadcaster.run Broadcaster.run called
2016-12-21 19:17:11.659 DEBUG Plugin.server.run Httpd.run SocketServer.ThreadingTCPServer
2016-12-21 19:17:11.659 THREADDEBUG Plugin.method.setDeviceDiscoveryState CLASS: Plugin
2016-12-21 19:17:11.659 DEBUG Plugin.responder.run Responder.run called
2016-12-21 19:17:11.659 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://50.199.162.25:8178/description.xml
SERVER: FreeRTOS/7.4.2, UPnP/1.0, IpBridge/1.7.0
NTS: ssdp:alive
NT: uuid:a256f166-c7db-11e6-a2a4-685b35b6a083
USN: uuid:a256f166-c7db-11e6-a2a4-685b35b6a083


2016-12-21 19:17:11.660 DEBUG Plugin.general.setDeviceDiscoveryState SET DEVICE DISCOVERY STATE = True
2016-12-21 19:17:11.666 DEBUG Plugin.responder.run Responder.run: socket error: 49 - Can't assign requested address
2016-12-21 19:17:11.666 THREADDEBUG Plugin.method.didDeviceCommPropertyChange CLASS: Plugin
2016-12-21 19:17:11.666 THREADDEBUG Plugin.method.setDeviceDiscoveryState CLASS: Plugin
2016-12-21 19:17:11.666 DEBUG Plugin.general.didDeviceCommPropertyChange DID-DEVICE-COMM-PROPERTY-CHANGE: Old [new device] vs New [new device]
2016-12-21 19:17:11.667 DEBUG Plugin.general.setDeviceDiscoveryState SET DEVICE DISCOVERY STATE = False
2016-12-21 19:17:11.669 THREADDEBUG Plugin.method.didDeviceCommPropertyChange CLASS: Plugin
2016-12-21 19:17:11.670 DEBUG Plugin.general.didDeviceCommPropertyChange DID-DEVICE-COMM-PROPERTY-CHANGE: Old [new device] vs New [new device]
2016-12-21 19:17:11.670 THREADDEBUG Plugin.method.didDeviceCommPropertyChange CLASS: Plugin
2016-12-21 19:17:11.670 DEBUG Plugin.general.didDeviceCommPropertyChange DID-DEVICE-COMM-PROPERTY-CHANGE: Old [new device] vs New [new device]
2016-12-21 19:17:11.671 THREADDEBUG Plugin.method.didDeviceCommPropertyChange CLASS: Plugin
2016-12-21 19:17:11.671 DEBUG Plugin.general.didDeviceCommPropertyChange DID-DEVICE-COMM-PROPERTY-CHANGE: Old [new device] vs New [new device]
2016-12-21 19:17:11.671 THREADDEBUG Plugin.method.didDeviceCommPropertyChange CLASS: Plugin
2016-12-21 19:17:11.671 DEBUG Plugin.general.didDeviceCommPropertyChange DID-DEVICE-COMM-PROPERTY-CHANGE: Old [new device] vs New [new device]

...
DEBUG Plugin.responder.run Responder.run: socket error: 49 - Can't assign requested address

OK - at least we now know you are getting an error and what it is - just need to work out why.

Might need some help on this one as I am not an expert on UPNP - so I am not sure whether the error is referring to the address of you Indigo Alexa-Hue bridge device or the general broadcast address.

I will continue to investigate further.

I have no idea what the issue is. I tried to do some research on socket error:49, but I couldn't really identify a specific issue.

So has this issue been resolved with V2.0.9? Just trying to establish what issues are outstanding and remain to be looked at?

Did you resolve this - I'm getting the same error.

Alexa-Hue Bridge Error Responder.run: socket error: 49 - Can't assign requested address