Indigo Skill not working anymore

[matt (support)]

We had a problem with how a new SSL certificate was installed on our server which caused problems for the Indigo Server.

It is fixed now, but may take 15 minutes for your reflector to re-establish itself. Appreciate everyone's patience with this not working earlier.

Thank you, as always, Matt. When things are working fine you don't generally hear from us, but when there's a hiccup, we crawl out of the woodwork screaming.

Truth be told, we appreciate your efforts both with software maintenance and development. You guys have a big job and it gets more and more complex with each Amazon, Apple, (etc) software update.

Thanks for the quick resolution to today's issue --- especially on a Friday evening.

Thank You! Working again here at our site.

It works again.

Thanks a lot

Morning all,

I have been battling this for months now. After a few days, I will get a message that my skill is not enabled. I have to go in and revoke the authorization, then enable the skill, thus restoring the authorization. I just counted and I've done this 9 times this year. It would be more, but I have gotten used to turning lights on and off the old-fashioned way, until I am frustrated and then go through the process above. I've tried everything I can think of.

I replaced my ISP.
Installed a new, top-of-the-line wireless network
I have experimented with nightly restarts of my automation computer.
I have the latest version of Indigo installed and running.
I am upgrading my automation computer so it is the latest and greatest.

When I look at the logs, the Alexa Hue Bridge seems to be working, but all the individual switches are not enabled individually unless I go through the process above.

It looks like only a few folks are having this problem otherwise I would expect more traffic on the topic. Is there any way to have someone look at my server and settings to see if I've set something up incorrectly? Thanks in advance for the help.

Kind Regards,
Brennan

.

[jay (support)]

The Alexa Hue bridge plugin is NOT the plugin that we include, they operate completely differently. We recommend that you remove that plugin as it may cause duplicate devices in Alexa. If you haven't configured our included Alexa plugin correctly, then maybe that's the problem?

Some users are experiencing what appears to be a bug in macOS, but I don't know if it's the problem you're seeing because you don't really post any Event Log details (if there are any).

Note that the last few posts were specifically because of an SSL cert issue that we experienced in June, so your issue isn't related.

Please start a new topic in this forum (rather than try to recycle this old one) with the specifics:

1) Where did it say the skill wasn't enabled? Screenshot and/or log entries?
2) Were you experiencing any other errors in the Event Log at the time?
3) What was the exact behavior you were seeing?
4) Have you tried all of the steps in the Troubleshooting section of the Alexa Plugin docs?

Jay,
I have tried and checked all of the items in the Alexa Trouble Shooting page multiple times.

Reflector is working
have reenabled and re-linked Alexa multiple times (revoking authorization each time)
Created new API key for the reflector name shown in the local server startup window
Examined the list of published devices in the plugin. they are all there.
Looked at the list of devices in Alexa app. They are all there but listed as non-responsive
Reloaded the plugin. No error messages in the event log and the list of devices in the log is correct.
Plugin debug is enabled and periodically produces a list of errors that look like this. The debug dump does not seem to relate to an asking Alexa to do something.

Alexalib Debug EndpointHealth.__init__ called...
Alexalib Debug CapabilityInterface.__init__ called...
Alexalib Debug created the default Alexa interface
Alexalib Debug BrightnessController.__init__ called...
Alexalib Debug CapabilityInterface.__init__ called...
Alexalib Debug created the default Alexa interface
Alexalib Debug PowerController.__init__ called...
Alexalib Debug CapabilityInterface.__init__ called...
Alexalib Debug created the default Alexa interface
Alexalib Debug CapabilityInterface.__init__ called...
Alexalib Debug created the default Alexa interface
Alexalib Debug EndpointHealth.__init__ called...
Alexalib Debug CapabilityInterface.__init__ called...
Alexalib Debug created the default Alexa interface
Alexalib Debug BrightnessController.__init__ called...
Alexalib Debug CapabilityInterface.__init__ called...
Alexalib Debug created the default Alexa interface
Alexalib Debug PowerController.__init__ called...
Alexalib Debug CapabilityInterface.__init__ called...
Alexalib Debug created the default Alexa interface
Alexalib Debug CapabilityInterface.__init__ called...
Alexalib Debug created the default Alexa interface
Alexalib Debug EndpointHealth.__init__ called...
Alexalib Debug CapabilityInterface.__init__ called...
Alexalib Debug created the default Alexa interface
Alexalib Debug BrightnessController.__init__ called...
Alexalib Debug CapabilityInterface.__init__ called...
Alexalib Debug created the default Alexa interface
Alexalib Debug PowerController.__init__ called...
Alexalib Debug CapabilityInterface.__init__ called...
Alexalib Debug created the default Alexa interface
Alexalib Debug CapabilityInterface.__init__ called...
Alexalib Debug created the default Alexa interface
Alexalib Debug EndpointHealth.__init__ called...
Alexalib Debug CapabilityInterface.__init__ called...
Alexalib Debug created the default Alexa interface
When I ask Alexa to turn on a device she says:

Sorry the hub that the device xxxx is connected to is not responding

I deleted a device from the publications list
The republished it with a modified name.
I showed up with the new name on both the plugin's list of published devices and on the alexa app but was still shown as unresponsive in the app's list of devices

I no longer now what to try.

[jay (support)]

The log lines you posted are fine - they are debug information only and do not represent errors.

Created new API key for the reflector name shown in the local server startup window

What do you mean by this? If you're talking about an API Key, that will not work. In the Alexa app, unlink the Indigo skill, then relink it. That's how the authorization is created. API Keys are used for something completely different.

Hi Jay,

Well I ;noticed that the name of the AOI key showing was the name of an old reflexor so I added a key for the new one.
If that doesn't relate to the issue at hand, well... Im trying everything I can think of to get Alexa working again.

Is there someway I can do a clean install of the plugin other than just reloading it?

API key not Api

[jay (support)]

As I said above, you don't use API Keys for Alexa, so creating them will not help you.

You must go into the Alexa app on your iPhone and unlink the Indigo Skill. Then relink it as you did when you first enabled it.

I understand that the API key is not the issue.

I have disabled the skill and reenabled and linked it at least a dozen time. Nothing changes

I'm having the same issue. Relinking isn't helping.

I had similar issues starting Thursday (9th) evening. The Indigo-Alexa Skill would go in and out of service. All other home automation related skills were running fine. The Indigo log also showed issues with connecting to the reflector throughout the evening. Things appear to be working now...

[jay (support)]

Reflector issues would definitely cause Alexa issues since the Alexa skill has to talk to Indigo over the reflector.