Alexa no longer discovering Indigo installed/managed devices

Posted on
Wed Aug 28, 2019 3:38 pm
PETStech offline
User avatar
Posts: 50
Joined: Jul 03, 2015

Alexa no longer discovering Indigo installed/managed devices

What am I missing?

Situation: Alexa discovery and voice command of Indigo devices have been working for more than six months without any problems. Failure to discover or control individual or grouped Indigo-managed devices occurred a little over a week ago. I can still manage and control Indigo devices via the Indigo app on MBA and with Indigo Touch on iOS devices.

Discover: (via Alexa App on MBA) Shows 12 devices; before current failure, Discover would also show these and more than 60 Indigo devices)

Recent Log:

2019-08-28 15:09:45.785 WebServer Indigo Touch client connected from 192.168.10.115
2019-08-28 15:10:06.151 Alexa-Hue Bridge sent "Alexa-Hue Bridge #1" Discovery off
2019-08-28 15:10:06.188 Alexa-Hue Bridge Stop Discovery . . . . . . . . . .
2019-08-28 15:10:06.194 Alexa-Hue Bridge Stopping Hue Bridge 'Alexa-Hue Bridge #1' discovery threads as 'Turn Off Discovery' requested
2019-08-28 15:10:21.841 Alexa-Hue Bridge sent "Alexa-Hue Bridge #1" Discovery on
2019-08-28 15:10:21.849 Alexa-Hue Bridge Starting Hue Bridge 'Alexa-Hue Bridge #1' discovery threads as 'Turn On Discovery' requested
2019-08-28 15:23:41.456 Alexa-Hue Bridge sent "Alexa-Hue Bridge #1" Discovery on
2019-08-28 15:23:41.510 Alexa-Hue Bridge Starting Hue Bridge 'Alexa-Hue Bridge #1' discovery threads as 'Turn On Discovery' requested

Indigo Installation:
Indigo 7.2.0
Plugins [reloaded]
Alexa-Hue Bridge v3.0.29  Address: 8178
Utilities
Virtual Devices [reloaded]

Amazon Devices:
Echo Dot [Gen 1]
Echo [Gen 2]
Echo Show 5
Blink XT2 Camera

Alexa iOS app On iPad [2019], iPad Air 2, iPhone SE

Alexa 2.2.290163.0 - August 20, 2019
App update and Alexa failure to discover Indigo devices and inability to control via voice any Indigo actions using either an Echo device or the Alexa app occurred about the same time.

Alexa 2.2.291375.0 - August 27, 2019
Alexa app updated, but still no discovery of Indigo devices; meanwhile, devices installed with Magic Home, Magic Light WF can be voice controlled via Echo 2 and Alexa app on MBA [2019]

Am I alone on this?
Last edited by PETStech on Thu Aug 29, 2019 9:31 am, edited 1 time in total.

Posted on
Wed Aug 28, 2019 4:36 pm
jay (support) offline
Site Admin
User avatar
Posts: 16211
Joined: Mar 19, 2008
Location: Austin, Texas

Re: Alexa longer discovering Indigo installed/managed device

I'm not the expert on this plugin (any more), but did you by chance enable both WiFi and Ethernet interfaces on your Mac? That can cause issues like this.

Jay (Indigo Support)
Twitter | Facebook | LinkedIn

Posted on
Thu Aug 29, 2019 4:21 am
kwijibo007 offline
Posts: 299
Joined: Sep 27, 2013
Location: Melbourne, Australia

Re: Alexa longer discovering Indigo installed/managed device

I think I’m having the same issue. It hit within the past 12 hours.

Alexa says [device name] ‘isn’t responding. Please Check it’s network connection and power supply’.

I’ve rebooted every Alexa, restarted the plugin and then the Mac (running Indigo).

4 x Dot 2nd Gen and 1 x Spot.

In the past I’ve had issues and restarting everything as above fixed it.

Wifi is disabled on my Mac.

It’s late where I am. I’ll pick up troubleshooting tomorrow.

Pete

Posted on
Thu Aug 29, 2019 4:32 am
autolog offline
Posts: 3235
Joined: Sep 10, 2013
Location: West Sussex, UK [GMT+1 aka UTC+1]

Re: Alexa longer discovering Indigo installed/managed device

PETStech wrote:
What am I missing? ...


I'm not sure I am an expert either. :wink:

Check out Jay's suggestion first.

Then, if that doesn't fix it, I would suggest accessing your Alexa account from your Apple Mac and select the tab SmartHome > Devices. Find the Indigo devices and click Forget.
Once all forgotten, reload the plugin and then try a discovery again.

It might also be worth powering off all echo devices other than your Gen 1 and talking to that one to do the discovery. :)

Posted on
Thu Aug 29, 2019 2:32 pm
PETStech offline
User avatar
Posts: 50
Joined: Jul 03, 2015

Re: Alexa no longer discovering Indigo installed/managed dev

Thanks,

Tried Jay's and your suggestions, but no luck. I'm going to uninstall/reinstall/reconfigure the Alexa-Hue Bridge and see if I can get it working, again.

More, later.

- Tom

Posted on
Thu Aug 29, 2019 3:49 pm
kwijibo007 offline
Posts: 299
Joined: Sep 27, 2013
Location: Melbourne, Australia

Re: Alexa no longer discovering Indigo installed/managed dev

I’m back up and running this morning. I Rebooted all the Echos and ran discovery again.

I think all my devices did an update from Amazon (I know 3 did). Guessing that this was the cause.

Pete

Posted on
Fri Aug 30, 2019 8:29 pm
wormhole offline
Posts: 121
Joined: Feb 21, 2017

Re: Alexa no longer discovering Indigo installed/managed dev

I'm having the same issue...rebooting Echo's doesn't seem to work

Alexa-Hue Bridge Error Start Discovery action failed for 'Alexa Bridge 1': broadcaster thread couldn't start. Try restarting the plugin.'
Alexa-Hue Bridge Error Traceback (most recent call last):
Alexa-Hue Bridge Error File "plugin.py", line 1771, in startDiscovery
Alexa-Hue Bridge Error self.globals['alexaHueBridge'][ahbDev.id]['broadcaster'].start()
Alexa-Hue Bridge Error File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/threading.py", line 739, in start
Alexa-Hue Bridge Error raise RuntimeError("threads can only be started once")
Alexa-Hue Bridge Error RuntimeError: threads can only be started once

Posted on
Sat Aug 31, 2019 5:04 am
wormhole offline
Posts: 121
Joined: Feb 21, 2017

Re: Alexa no longer discovering Indigo installed/managed dev

Tried adding a new test bridge,

Alexa-Hue Bridge Error getHueDeviceJSON exception:
Traceback (most recent call last):
File "/Library/Application Support/Perceptive Automation/Indigo 7.3/Plugins/Alexa-Hue Bridge.indigoPlugin/Contents/Server Plugin/hue_listener.py", line 331, in getHueDeviceJSON
self.alexaDeviceNameKey = PLUGIN.globals['alexaHueBridge'][p1_ahbDevId]['hashKeys'][p3_alexaDeviceHashedKey]
KeyError: '2f6c1024b59c87954b51fc92419f55e99592f3bcc565063bffac1e274e4d9803'

Alexa-Hue Bridge Error StandardError detected in HttpdRequestHandler for 'self.ahbDev.name'. Line '185' has error='must be string or buffer, not None'
Alexa-Hue Bridge Error StandardError detected in HttpdRequestHandler for 'Alexa Test'. Line '185' has error='must be string or buffer, not None'

Posted on
Sat Aug 31, 2019 8:27 am
ar26pt2 offline
Posts: 23
Joined: Jan 23, 2014

Re: Alexa no longer discovering Indigo installed/managed dev

Going to Alexa.amazon.con and forgetting all devices, then searching for devices again worked for me. :D before this I updated my indigo and updated plugin. Thanks!

Posted on
Sat Aug 31, 2019 2:02 pm
autolog offline
Posts: 3235
Joined: Sep 10, 2013
Location: West Sussex, UK [GMT+1 aka UTC+1]

Re: Alexa no longer discovering Indigo installed/managed dev

ar26pt2 wrote:
Going to Alexa.amazon.con and forgetting all devices, then searching for devices again worked for me. :D before this I updated my indigo and updated plugin. Thanks!


I concur with this approach. :)

I think the hash keys might be mismatched which is how the plugin ties up the Alexa devices with the Indigo devices.
Not sure what would cause this to happen though. :?

Posted on
Sat Aug 31, 2019 4:08 pm
wormhole offline
Posts: 121
Joined: Feb 21, 2017

Re: Alexa no longer discovering Indigo installed/managed dev

Did that, still getting these errors

Error cannot update device state for key clientConnectionStatus to value error (invalid enumeration value)
Error cannot update device state for key clientConnectionStatus to value error (invalid enumeration value)
Error cannot update device state for key clientConnectionStatus to value error (invalid enumeration value)
Error cannot update device state for key clientConnectionStatus to value error (invalid enumeration value)
Error cannot update device state for key clientConnectionStatus to value error (invalid enumeration value)
Error cannot update device state for key clientConnectionStatus to value error (invalid enumeration value)
Error cannot update device state for key clientConnectionStatus to value error (invalid enumeration value)
Error cannot update device state for key clientConnectionStatus to value error (invalid enumeration value)
Error cannot update device state for key clientConnectionStatus to value error (invalid enumeration value)
Error cannot update device state for key clientConnectionStatus to value error (invalid enumeration value)
Error cannot update device state for key clientConnectionStatus to value error (invalid enumeration value)
Error cannot update device state for key clientConnectionStatus to value error (invalid enumeration value)
Error cannot update device state for key clientConnectionStatus to value error (invalid enumeration value)
Error cannot update device state for key clientConnectionStatus to value error (invalid enumeration value)
Alexa-Hue Bridge Request received from 10.0.1.43:53978: Setting on state of Alexa device "Study Lights" ["Study Lights"] to ON
Sent INSTEON "Study Lights" on
Trigger Study Lights On
Sent INSTEON "Study Lights 2" on
Error cannot update device state for key clientConnectionStatus to value error (invalid enumeration value)
Error cannot update device state for key clientConnectionStatus to value error (invalid enumeration value)
Error cannot update device state for key clientConnectionStatus to value error (invalid enumeration value)
Alexa-Hue Bridge Request received from 10.0.1.43:53982: Setting on state of Alexa device "Master Bedroom Light" ["Master Bed Main Light"] to ON
Sent INSTEON "Master Bed Main Light" on to 100
Error cannot update device state for key clientConnectionStatus to value error (invalid enumeration value)
Error cannot update device state for key clientConnectionStatus to value error (invalid enumeration value)
Error cannot update device state for key clientConnectionStatus to value error (invalid enumeration value)
Error cannot update device state for key clientConnectionStatus to value error (invalid enumeration value)
Error cannot update device state for key clientConnectionS

Posted on
Sat Aug 31, 2019 4:11 pm
wormhole offline
Posts: 121
Joined: Feb 21, 2017

Re: Alexa no longer discovering Indigo installed/managed dev

forget everything a second time, then rediscovered, then it seems to work....

Posted on
Sat Aug 31, 2019 4:42 pm
wormhole offline
Posts: 121
Joined: Feb 21, 2017

Re: Alexa no longer discovering Indigo installed/managed dev

still getting these errors constantly in the log window

Error cannot update device state for key clientConnectionStatus to value error (invalid enumeration value)
Error cannot update device state for key clientConnectionStatus to value error (invalid enumeration value)
Error cannot update device state for key clientConnectionStatus to value error (invalid enumeration value)
Error cannot update device state for key clientConnectionStatus to value error (invalid enumeration value)
Error cannot update device state for key clientConnectionStatus to value error (invalid enumeration value)
Error cannot update device state for key clientConnectionStatus to value error (invalid enumeration value)

Posted on
Sun Sep 01, 2019 5:39 am
autolog offline
Posts: 3235
Joined: Sep 10, 2013
Location: West Sussex, UK [GMT+1 aka UTC+1]

Re: Alexa no longer discovering Indigo installed/managed dev

wormhole wrote:
forget everything a second time, then rediscovered, then it seems to work....


As you have been replying to two threads, I am a bit confused as to whether you are up and running again? :?

Posted on
Sun Sep 01, 2019 5:41 am
autolog offline
Posts: 3235
Joined: Sep 10, 2013
Location: West Sussex, UK [GMT+1 aka UTC+1]

Re: Alexa no longer discovering Indigo installed/managed dev

wormhole wrote:
still getting these errors constantly in the log window

Error cannot update device state for key clientConnectionStatus to value error (invalid enumeration value)
Error cannot update device state for key clientConnectionStatus to value error (invalid enumeration value)
Error cannot update device state for key clientConnectionStatus to value error (invalid enumeration value)
Error cannot update device state for key clientConnectionStatus to value error (invalid enumeration value)
Error cannot update device state for key clientConnectionStatus to value error (invalid enumeration value)
Error cannot update device state for key clientConnectionStatus to value error (invalid enumeration value)


Are these caused by the Alexa-Hue Bridge plugin? If so I would expect a bit more detail in the log.

Is there any obvious thing that is triggering the messages? :)

Who is online

Users browsing this forum: No registered users and 1 guest