jay (support) wrote:Did you read through the Troubleshooting section of the Alexa Plugin docs? There are several tips there that might help.
jay (support) wrote:Also, did you remove all your devices from the Alexa Hue Bridge before discovering from the plugin as mentioned in the Migrating section?
jay (support) wrote:Executing actions is different than controlling devices.
Indigo is successfully returning device discoveries. Do you see the devices in the Alexa app? What happens when you try to control them? You should see Event Log entries when the plugin receives a control message from Alexa.
jay (support) wrote:Interesting. The plugin is responding to the discovery request, so for some reason Alexa isn't doing the right thing with the response.
Time for a full reset:
- Disable the Indigo Smart Home Skill in the Alexa app/web site
- On the Authorizations page of your Indigo Account, revoke the Alexa Service Authorization
- Remove all devices in the Alexa app - it's most easily done on the Alexa web page since you can just click the Remove All button
- Wait for a few minutes (Alexa seems to have some caching issues, so waiting for a while seems to allow the device removals to propagate)
- Confirm that the Alexa Hue Bridge isn't running; also confirm that you don't have any other native Alexa smart home skills enabled (like for instance the Hue Skill) - name conflicts between skills can kill a discovery request
- In the Alexa Plugin's Manage Publications dialog. unpublish all but one device (make it a very simple on/off switch if possible)
- In the Alexa app, enable the Indigo Smart Home skill and link it
- Run a discovery - verify that the one device that you've published appears
What we're going for here is to determine if cleaning everything out and just publishing one device will get us back on track. If this works, then add the devices back one at a time, discovering between each one. I've seen Alexa freak out over one specific device and reject the entire discovery payload, so adding one at a time will help us determine if there is one specific device which Alexa doesn't like (and we can then troubleshoot that one directly).
jay (support) wrote:One other thing to try: disable any other Smart Home skills (including the Wyze skill since you mentioned it). Maybe one of those skills is doing something weird...
jay (support) wrote:Yep, it's now showing removed in their console.
Users browsing this forum: No registered users and 1 guest