Closed davidnewhall closed 6 years ago
No problem but it is better for me if you post a new thread in the Indigo Alexa-Hue Bridge forum. :)
Anyway, thanks for reporting and it is a bug which I have now discovered (via testing) that happens on a new install. :(
I am looking at it now and will post an announcement in the Indigo Alexa-Hue Bridge forum when I have fixed it. I will also update this report. :)
Should now be fixed in Release 3.0.19 :)
Okay thanks! I'm in Vegas for AWS; will try again when I return home!
Seems to work just fine now. I have another request/issue, but I'll hit up the forums for that. Thanks so much!!
Hello,
I hope you find this an appropriate place to reach out for support. I've been using the Alexa Hue Bridge just fine for quite a long time. I really appreciate what you've provided here; thank you!
Recently, I moved. It took me a while to get Indigo reconfigured, but I'm there now and trying to get Alexa to control my lights once more. I upgraded to the latest plugin, but immediately had errors when it loaded. I've tried many different things to make it function, but I've had no success. If me describing the "check boxes" and "ip address boxes" I went to tinkering with will help diagnose the issue, then I can be far more descriptive. I'll say: I wiped all the published devices out, disabled the plugin, re-installed, re-enabled, and in a "virgin" state it throws errors as shown below.
I hope the errors I get in the Indigo log provides some insight you can share with me. If there is a preferences file somewhere I should be nuking, please provide enlightenment.
Thank you for your time! -david
PS. Yes, the server's IP is really 192.168.3.1, that's not the router's address.