Indigo Domotics

I see the release notes for .20 and .23, but what does this mean? All of sudden this happened today. I have had an Echo Show since Christmas and Echo Gen 2 devices since then as well without a problem. All of the devices are unresponsive and no dot or show responds to voice commands for Indigo devices.

Could this have something to do with changing the wifi all my echo devices use to my guest rather than main network?

tried setting the port to 'auto' as well as rebooting the iMac but no luck.

I have been following Wheeler's post, but nothing has worked for me, all devices are Unresponsive. Here is the plugin reload log

Feb 3, 2018 at 5:26:09 PM
Reloading plugin "Alexa-Hue Bridge 3.0.23"
Stopping plugin "Alexa-Hue Bridge 3.0.23" (pid 503)
Alexa-Hue Bridge Alexa-Hue Bridge shutdown requested
Alexa-Hue Bridge HTTP server stopping...
Alexa-Hue Bridge HTTP server stopped
Alexa-Hue Bridge HTTP server stopped
Alexa-Hue Bridge HTTP server stopping...
Alexa-Hue Bridge HTTP server stopped
Alexa-Hue Bridge HTTP server stopping...
Stopped plugin "Alexa-Hue Bridge 3.0.23"
Starting plugin "Alexa-Hue Bridge 3.0.23" (pid 647)
Alexa-Hue Bridge Alexa-Hue Bridge initialising . . .
Alexa-Hue Bridge Plugin Host IP Address is discovered as: '10.0.1.100'
Alexa-Hue Bridge Alexa discovery request logging enabled
Alexa-Hue Bridge No debugging requested
Started plugin "Alexa-Hue Bridge 3.0.23"
Alexa-Hue Bridge Alexa-Hue Bridge initialization complete
Alexa-Hue Bridge 'Alexa Devices 1' has 19 Alexa Devices published
Alexa-Hue Bridge Starting Hue Bridge 'Alexa Devices 1' web server thread
Alexa-Hue Bridge Starting Hue Bridge 'Alexa Devices 1' discovery thread as 'Auto Start Discovery' requested
Alexa-Hue Bridge Error 'Alexa Devices 1' unable to access HTTP port 8178 as already in use - waiting 15 seconds to try again (will retry 3 more times)
Alexa-Hue Bridge Alexa-Hue Bridge 'Alexa Devices 1' started: Host: 10.0.1.100 Port: 8178
Alexa-Hue Bridge 'Alexa Devices 2' has 17 Alexa Devices published
Alexa-Hue Bridge Starting Hue Bridge 'Alexa Devices 2' web server thread
Alexa-Hue Bridge Starting Hue Bridge 'Alexa Devices 2' discovery thread as 'Auto Start Discovery' requested
Alexa-Hue Bridge Error 'Alexa Devices 2' unable to access HTTP port 8182 as already in use - waiting 15 seconds to try again (will retry 3 more times)
Alexa-Hue Bridge Alexa-Hue Bridge 'Alexa Devices 2' started: Host: 10.0.1.100 Port: 8182
Alexa-Hue Bridge 'Alexa Groups' has 3 Alexa Devices published
Alexa-Hue Bridge Starting Hue Bridge 'Alexa Groups' web server thread
Alexa-Hue Bridge Error 'Alexa Groups' unable to access HTTP port 8183 as already in use - waiting 15 seconds to try again (will retry 3 more times)
Alexa-Hue Bridge Starting Hue Bridge 'Alexa Groups' discovery thread as 'Auto Start Discovery' requested
Alexa-Hue Bridge Alexa-Hue Bridge 'Alexa Groups' started: Host: 10.0.1.100 Port: 8183
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 checking for Plugin update
Alexa-Hue Bridge Checking for updates...
Alexa-Hue Bridge No updates are available
Alexa-Hue Bridge Alexa-Hue Bridge next update check scheduled for: Sunday, 2018-Feb-04 at 17:26
Alexa-Hue Bridge Error 'Alexa Devices 1' trying again to access HTTP port 8178 [attempt 1]
Alexa-Hue Bridge Error 'Alexa Devices 1' unable to access HTTP port 8178 as already in use - waiting 15 seconds to try again (will retry 2 more times)
Alexa-Hue Bridge Error 'Alexa Devices 2' trying again to access HTTP port 8182 [attempt 1]
Alexa-Hue Bridge Error 'Alexa Devices 2' unable to access HTTP port 8182 as already in use - waiting 15 seconds to try again (will retry 2 more times)
Alexa-Hue Bridge Error 'Alexa Groups' trying again to access HTTP port 8183 [attempt 1]
Alexa-Hue Bridge Error 'Alexa Groups' unable to access HTTP port 8183 as already in use - waiting 15 seconds to try again (will retry 2 more times)


I then manually put in new ports:

Feb 3, 2018 at 5:27:36 PM
Alexa-Hue Bridge 'Alexa Devices 1' updated and now has 19 Alexa Devices published
Alexa-Hue Bridge HTTP server stopping...
Alexa-Hue Bridge HTTP server stopped
Alexa-Hue Bridge 'Alexa Devices 1' has 19 Alexa Devices published
Alexa-Hue Bridge Starting Hue Bridge 'Alexa Devices 1' web server thread
Alexa-Hue Bridge HTTP server stopping...
Alexa-Hue Bridge Starting Hue Bridge 'Alexa Devices 1' discovery thread as 'Auto Start Discovery' requested
Alexa-Hue Bridge Alexa-Hue Bridge 'Alexa Devices 1' started: Host: 10.0.1.100 Port: 8184

Feb 3, 2018 at 5:27:56 PM
Alexa-Hue Bridge 'Alexa Devices 2' updated and now has 17 Alexa Devices published
Alexa-Hue Bridge HTTP server stopping...
Alexa-Hue Bridge HTTP server stopped
Alexa-Hue Bridge 'Alexa Devices 2' has 17 Alexa Devices published
Alexa-Hue Bridge Starting Hue Bridge 'Alexa Devices 2' web server thread
Alexa-Hue Bridge HTTP server stopping...
Alexa-Hue Bridge Starting Hue Bridge 'Alexa Devices 2' discovery thread as 'Auto Start Discovery' requested
Alexa-Hue Bridge Alexa-Hue Bridge 'Alexa Devices 2' started: Host: 10.0.1.100 Port: 8185
Received INSTEON "Garage Indoor Flood" on
Trigger Auto Off - Garage Indoor Flood
Alexa-Hue Bridge 'Alexa Groups' updated and now has 3 Alexa Devices published
Alexa-Hue Bridge HTTP server stopping...
Alexa-Hue Bridge 'Alexa Groups' has 3 Alexa Devices published
Alexa-Hue Bridge HTTP server stopped
Alexa-Hue Bridge Starting Hue Bridge 'Alexa Groups' web server thread
Alexa-Hue Bridge HTTP server stopping...
Alexa-Hue Bridge Starting Hue Bridge 'Alexa Groups' discovery thread as 'Auto Start Discovery' requested
Alexa-Hue Bridge Alexa-Hue Bridge 'Alexa Groups' started: Host: 10.0.1.100 Port: 8186

But still devices are unresponsive

Last thing to note, when i ask an echo device to 'turn on [device]" the response is: " [device] doesn't support that"

went to alexa.amazon.com and all the indigo devices are indicated as 'offline', however within Indigo, Discover for the two bridges that contain 19 and 17 devices respectively show discovery on, and I am not getting any port errors. Any help here appreciated.

I also tried manually, individually, forgetting a couple of the devices on alexa.amazon.com and tried to discover devices but the iOS app didn't discover any devices....

wormhole wrote:

... Could this have something to do with changing the wifi all my echo devices use to my guest rather than main network?

Most likely.

Have you tried changing it back to see if it fixes the problem?

So I tried changing the Show back, but still everything shows as offline.

Just to reiterate

1. Using the iOS app Alexa won't discover any devices and
2. Going to alexa.amazon.com, all my indigo devices show as 'offline', other skills work fine.

So apologies for all the posts....i changed ALL the Echo Dots back to the main wifi network and everything works...just for my understanding, why would this have impacted the discoverability/Availability?

You need to move an Echo Dot back as the Show can't discover devices.

The devices will often show as offline (or unresponsive) in the App but as soon as you issue a command it will respond.

You need to be able to say directly to Alexa on your Echo Dot 'Alexa discover devices' - the App is not always successful in discovering for the plugin devices..

Skills don't have anything to do with the plugin. They will most likely work regardless whether the plugin works or not.

wormhole wrote:

So apologies for all the posts....i changed ALL the Echo Dots back to the main wifi network and everything works...just for my understanding, why would this have impacted the discoverability/Availability?

Discovery only works on Echo (Gen 1) or Echo Dot (Gen 1 and 2).

Glad you got it working

But the devices were already 'discovered', i just changed the wifi after the fact. Does this mean only one of my Dots needs to be on the main wifi network? Sorry for the questions.

wormhole wrote:

But the devices were already 'discovered', i just changed the wifi after the fact. Does this mean only one of my Dots needs to be on the main wifi network? Sorry for the questions.

I can't answer this question directly as I don't know but assuming you are running the pre-release version (3.0.23), when you ask Alexa to turn on / off any of your devices, the Indigo Event Log will show you which device (hopefully an Echo Dot) issued the command to Indigo (either by name if you have added in Indigo Echo devices which is a new 3.0.23 feature or IP address if you haven't). Try leaving this device on your main network and move the others to your guest network. You can then test if it works or not.

Thanks, I'll play around with it. What is the purpose/benefit of adding Echo devices to the plugin?

It just gives you better visibility of which Echo device is communicating with Indigo. When you ask an Echo device to do something, it isn't always the one you have asked that sends the request to Indigo.

wormhole wrote:

But the devices were already 'discovered', i just changed the wifi after the fact. Does this mean only one of my Dots needs to be on the main wifi network? Sorry for the questions.

It appears that the Echo's relatively frequently attempt to do SDP (service discovery protocol) requests to the Hue hub (in our case, the bridge device). SDP only works on the same network subnet so if your echo's aren't on the same subnet as your Indigo Server those will fail. Since it appears that only one echo is, in fact, doing the talking, then you may be able to have all the other echos on the different subnet and just leave the "main" echo on the same subnet as the Indigo Server. But that's just speculation on my part.