Alexa won't discover new devices since Indigo 2021.1

[jay (support)]

Excellent.

As a test I added some temporary code to berkinet's plugin:

Code: Select all

   def addressCheck(self):
      for dev in indigo.devices.iter("self"):
         if dev.address == "":
            dProps = dev.pluginProps
               dProps["address"] = "None"
               dev.replacePluginPropsOnServer(dProps)

The devices can now be added. Thanks Jay!

Could you share where you added the code?


Sent from my iPhone using Tapatalk Pro

I put it at the end of the main code, then call it in startup with:

Code: Select all

self.addressCheck()

Still no result on my end. I tried a series of different devices (z-wave & insteon) one at a time. In each instance I deleted all devices in the alexa app and then re-ran discovery mode. The only devices found are my alexa devices and my brother printer. The event log showed the communication between indigo and alexa. This was at 09:16:08am PST. When checking my server access authorizations on my indigo account I noticed it kept track of my prior revocations. Not sure if that's significant or not.

Oddly enough..... I can tell Alexa "tell indigo to run XXX action group". She will reply that she is having trouble with my smart home skill, yet the action group will execute and is seen in the event log. All of this while no indigo devices have been discovered.

[jay (support)]

Did you revoke those prior authorizations yourself?

Did you revoke those prior authorizations yourself?

Yes, those are from my revocations.

[jay (support)]

Yes, those are from my revocations.

Ok, something very strange indeed is going on. A couple more questions:

1) What kind of internet connection do you have?
2) Do you have the alexa hue bridge enabled?
3) What other smart home skills do you have enabled and are you sure there are no overlaps in terms of device names between other skills and what you're publishing in Indigo?

Yes, those are from my revocations.

Ok, something very strange indeed is going on. A couple more questions:

1) What kind of internet connection do you have?
2) Do you have the alexa hue bridge enabled?
3) What other smart home skills do you have enabled and are you sure there are no overlaps in terms of device names between other skills and what you're publishing in Indigo?

1) My internet is the most horrible one you can buy, Hughsnet satellite (at least until Skylink is available!). My internal wireless is via eero pro 6 mesh network and indigo runs on a dedicated stand-a-lone mac mini 2018 (Big Sur 11.2.2.).
2) The alexa hue bridge is not enabled.
3) I deleted all skills except Indigo.

Butch

[jay (support)]

Ok, I'm pretty positive that it's your Internet that's the issue. Alexa expects responses to all requests within a few seconds or you get errors like the ones you're getting. They are pretty bad about just failing if even the slightest thing is wrong with the API calls, be it a slight formatting issue or a response time. This would explain why you're getting the action group execution but she's responding with an error: the reply from the plugin isn't getting back to her fast enough for her liking so she says there's an issue.

Note, the Alexa-Hue Bridge plugin doesn't rely on direct communication with Amazon's Alexa servers - rather, it communicates directly with the old Echo device on your local network. This would likely explain why that was working for you. I'd recommend continuing to use the AHB plugin until such time that your Internet connection improves.

Ok, I'm pretty positive that it's your Internet that's the issue. Alexa expects responses to all requests within a few seconds or you get errors like the ones you're getting. They are pretty bad about just failing if even the slightest thing is wrong with the API calls, be it a slight formatting issue or a response time. This would explain why you're getting the action group execution but she's responding with an error: the reply from the plugin isn't getting back to her fast enough for her liking so she says there's an issue.

Note, the Alexa-Hue Bridge plugin doesn't rely on direct communication with Amazon's Alexa servers - rather, it communicates directly with the old Echo device on your local network. This would likely explain why that was working for you. I'd recommend continuing to use the AHB plugin until such time that your Internet connection improves.

Well that is a bummer, but reaffirms my dislike for Hughsnet. I'm of the waitlist for Starlink, hopefully in September. Thanks for the efforts.

Butch

SOLVED! After waiting a year and a half, I've finally received my starlink dish. I asked Alexa to find new devices and, whammo! She found them on the first try. The delay of my old hughnet satellite dish was the problem. Many thanks to those who researched this matter.

[matt (support)]

Score one for satellites at a much lower orbit altitude.