Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
| indigo_2022.1_documentation:plugins:alexa [2022/03/11 20:28] – external edit 127.0.0.1 | indigo_2022.1_documentation:plugins:alexa [2025/04/14 20:10] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== Alexa ====== | ||
| + | |||
| + | [[https:// | ||
| + | |||
| + | Amazon has enabled integration with third parties like Indigo to integrate smart home devices so that you can use voice commands to control them (aka a //Smart Home Skill//). **In English speaking regions**, we've also created a way to execute action groups and have the value of variables read to you (aka a //Custom Skill//). | ||
| + | |||
| + | <color blue> | ||
| + | |||
| + | ===== Smart Home Skill ===== | ||
| + | |||
| + | <color red> | ||
| + | |||
| + | We have implemented a skill which you can enable that will provide standard smart home device control. This enables an Alexa user to control devices in the exact same way regardless of how that device is connected to Alexa. This section will give you an overview of the device types in Indigo that you can publish to Alexa for control. We don't automatically publish your Indigo devices for a variety of reasons, but primarily as a security measure. You must make an explicit decision to enable voice control of a device. | ||
| + | |||
| + | You must have your Indigo Reflector activated in order to proceed. | ||
| + | |||
| + | You enable the Indigo Skill in the Alexa app (this is the iOS App as of June 2021, it may change): | ||
| + | |||
| + | - Open the Alexa App. | ||
| + | - Go to the Devices list and click the link to Your Smart Home Skills. | ||
| + | - Click Enable Smart Home Skills. | ||
| + | - Tap the Search icon. | ||
| + | - Search for " | ||
| + | - Add the skill. | ||
| + | - Link the skill to your Indigo Account & license (currently by clicking/ | ||
| + | - Log in using your Indigo Account username and password. | ||
| + | - On the next page (the authorization page), if you have multiple Indigo Licenses, make sure you have the correct one selected (you must have an active Indigo Up-to-Date subscription); | ||
| + | |||
| + | ==== Alexa Store Links ==== | ||
| + | |||
| + | Here are direct links to the skills in their respective Alexa stores: | ||
| + | |||
| + | * [[https:// | ||
| + | * [[https:// | ||
| + | * [[https:// | ||
| + | * [[https:// | ||
| + | * [[https:// | ||
| + | * [[https:// | ||
| + | * [[https:// | ||
| + | * [[https:// | ||
| + | ==== Making a Device Available in Alexa ==== | ||
| + | |||
| + | To make a device available to Alexa, you must explicitly publish it. Use the'' | ||
| + | |||
| + | {{: | ||
| + | |||
| + | In this dialog, you will select a device from the popup. Note that the popup is divided into two sections: | ||
| + | |||
| + | {{: | ||
| + | |||
| + | The top part of the list are Indigo devices that can be published to Alexa, but haven' | ||
| + | |||
| + | Some devices will also show a Type popup: | ||
| + | |||
| + | {{: | ||
| + | |||
| + | You will use this popup to tell Alexa more specifically what kind of device it is. We will attempt to look at various other characteristics of the device to select what we believe is the appropriate type, but you may select any from the list and we will relay that information to Alexa so you can control it using appropriate terminology (see below for specifics). | ||
| + | |||
| + | The bottom part of the list are devices that you have already published to Alexa. If you select one of these devices, you can edit or unpublish the device. | ||
| + | |||
| + | <color orange> | ||
| + | ==== Device Types Supported ==== | ||
| + | |||
| + | In this release, the following device types are supported: | ||
| + | |||
| + | * On/Off devices (sometimes referred to as relay) - simple appliance control plug-in modules, outlets, and switches are the most common type. This also includes Locks and Garage Doors. | ||
| + | * Dimmer devices - dimmer switches and plug-in modules are the most common, though in Indigo there are a variety of other device types that Indigo sees as dimmers: Blinds/ | ||
| + | * Thermostats | ||
| + | * Fans - Indigo natively only supports the Insteon FanLinc fan as a proper fan device (with the right controls) - Z-Wave fan controllers are currently implemented as dimmers, but they will work as fans in Alexa if configured correctly. | ||
| + | |||
| + | === On/Off Devices === | ||
| + | |||
| + | This type of device has a boolean value, most often on/off or open/ | ||
| + | |||
| + | * //Alexa, turn on office lamp// | ||
| + | * //Alexa, turn off bedroom fan// | ||
| + | * //Alexa, open garage door// | ||
| + | |||
| + | When you select an Indigo device that is a standard On/Off device to publish, you will get a popup that will help us tell Alexa how to control your device: | ||
| + | |||
| + | {{: | ||
| + | |||
| + | We will take a guess at what the specific type of the device is, but we won't always guess correctly. For instance, if there isn't anything about your device that Indigo can determine, it will just automatically select '' | ||
| + | |||
| + | The options are: | ||
| + | * Door Bell - as of this release, this will only allow you to turn on/off the doorbell, not accept ring events. We will look at adding that in a future release. | ||
| + | * Door Controller - if you have a device that physically operates a door (but not a garage door), you can use this device type. You can then say things like: | ||
| + | * //Alexa, open the front door// | ||
| + | * //Alexa, what's the status of the front door// | ||
| + | * Garage Controller - this is exactly what you think it is. You will be able to open/close (raise/ | ||
| + | * //Alexa, open the garage door// | ||
| + | * //Alexa, is the garage door open// | ||
| + | * Lock - similar to a garage door, a lock device will need to have a PIN assigned for it in the Alexa app. Once that's done, when you attempt to unlock the door (//Alexa, unlock the back door//), it will prompt you for the PIN. You can say things like: | ||
| + | * //Alexa, lock the back door// | ||
| + | * //Alexa, is the back door locked// | ||
| + | * All the rest of the types will simply respond to standard on/off commands. There is currently no distinction other than the icon that shows up in the Alexa app. You can say things like: | ||
| + | * //Alexa, turn on bathroom exhaust fan// | ||
| + | * //Alexa turn off desk lamp// | ||
| + | === Dimmer Devices === | ||
| + | |||
| + | This type of device is most often a dimmable load, though there are some other options. Most of these device types will also respond to on/off commands like Relay Devices above. To control from Alexa, you use phrases like: | ||
| + | |||
| + | * //Alexa, brighten office lamp to 35%// | ||
| + | * //Alexa, dim office lamp by 15%// | ||
| + | |||
| + | If the devices supports color and/or white temperature, | ||
| + | |||
| + | * //Alexa, set color of office bulb to red// (color devices) | ||
| + | * //Alexa, set office bulb to daylight// (white color temperature) | ||
| + | * //Alexa, make office bulb warmer// (white color temperature) | ||
| + | |||
| + | For white temperatures, | ||
| + | |||
| + | | **Shades of White** | **Temperature in Kelvin** | | ||
| + | | warm, warm white | 2200 | | ||
| + | | incandescent, | ||
| + | | white | 4000 | | ||
| + | | daylight, daylight white | 5500 | | ||
| + | | cool, cool white | 7000 | | ||
| + | |||
| + | When you select an Indigo device that is a dimmer device to publish, you will get a popup that will help us tell Alexa how to control your device: | ||
| + | |||
| + | {{: | ||
| + | |||
| + | We will take a guess at what the specific type of the device is, but we won't always guess correctly. For instance, if there isn't anything about your device that Indigo can determine, it will just automatically select '' | ||
| + | |||
| + | The options are: | ||
| + | |||
| + | * '' | ||
| + | * //Alexa, raise the blinds to twenty-five percent// | ||
| + | * //Alexa, set the drapes to fifty percent// | ||
| + | * //Alexa, close the shades// | ||
| + | * //Alexa, what is the status of the shades// | ||
| + | * '' | ||
| + | * //Alexa, set ceiling fan to medium// | ||
| + | * //Alexa, set ceiling fan to highest// | ||
| + | * //Alexa, ceiling fan speed// | ||
| + | * //Alexa, turn off ceiling fan// | ||
| + | * '' | ||
| + | * //Alexa, set set the valve to thirty percent// | ||
| + | * //Alexa, increase valve by ten percent// | ||
| + | * //Alexa, turn off the valve// | ||
| + | * All the rest will support standard on/off and dim/ | ||
| + | |||
| + | === Indigo Fan Devices === | ||
| + | |||
| + | Indigo has a native fan device type. Currently, the only built-in device using this type is the Insteon FanLinc. There are some other plugins which also support this device type. If you select a device of this type the only option will be the Alternative name as there are no other options. You can say things like: | ||
| + | * //Alexa, set ceiling fan to medium// | ||
| + | * //Alexa, set ceiling fan to highest// | ||
| + | * //Alexa, increase ceiling fan speed// | ||
| + | * //Alexa, turn off ceiling fan// | ||
| + | |||
| + | === Indigo Thermostat Devices === | ||
| + | |||
| + | Any Indigo thermostat device can be added to Alexa. Schedule/ | ||
| + | |||
| + | <color red> | ||
| + | |||
| + | |||
| + | So, with that warning aside, you can say things like: | ||
| + | * //Alexa, set the thermostat to cool// | ||
| + | * //Alexa, what is my thermostat set to// | ||
| + | * //Alexa, turn off the heat// | ||
| + | * //Alexa, set the AC to seventy-five// | ||
| + | * //Alexa, make it warmer in here// | ||
| + | |||
| + | |||
| + | ===== Custom Indigo Skill ===== | ||
| + | |||
| + | **<color red> | ||
| + | |||
| + | When you enable the **Indigo Smart Home Skill** in the Alexa app, you also gain access to some custom functionality that's specific to Indigo. In this release, we enable you to hear the value of a variable (complete with speech markup), hear a list of all of your variables, and run Action Groups. | ||
| + | |||
| + | Custom skill requests require that you preface your requests by saying //Alexa, tell Indigo// or //Alexa, ask Indigo//. These are called **invocations** and are needed so that Alexa can know where to direct the request. It's not needed for Smart Home Skills (ones that deal with Indigo devices as described above as well as devices from other skills) because Alexa knows details about each individual device and where to send the request based on that information. | ||
| + | |||
| + | **<color red> | ||
| + | |||
| + | * US, UK - " | ||
| + | * CA, AU - " | ||
| + | |||
| + | We are attempting to get Amazon to help us correct this, but we are unsure if it's going to be possible or not at this time. | ||
| + | |||
| + | === Speaking the Value of a Variable === | ||
| + | |||
| + | **<color blue> | ||
| + | |||
| + | To hear the value of a variable, just ask Indigo for it. There are a variety of ways to ask, here are a few (variable names are in quotes, underscores are treated as spaces): | ||
| + | |||
| + | * //Alexa, ask Indigo to get " | ||
| + | * //Alexa, ask Indigo to look up " | ||
| + | * //Alexa, ask Indigo to read " | ||
| + | * //Alexa, ask Indigo to say " | ||
| + | * //Alexa, ask Indigo to speak " | ||
| + | * //Alexa, ask Indigo to tell me " | ||
| + | * //Alexa, ask Indigo for the value of variable " | ||
| + | * //Alexa, ask Indigo the value of " | ||
| + | * //Alexa, ask Indigo the current value of " | ||
| + | |||
| + | You can also use //tell Indigo// interchangeably with //ask Indigo//. | ||
| + | |||
| + | The default response (in the default voice) will be: | ||
| + | |||
| + | //The value of variable " | ||
| + | |||
| + | You can adjust how Alexa responds in a couple of ways: | ||
| + | |||
| + | * You can use [[https:// | ||
| + | * Variable values that contain the device (%%d: | ||
| + | * You may also specify in the plugin' | ||
| + | |||
| + | |||
| + | === Get a List of Variables === | ||
| + | |||
| + | You can hear a list of your variables as well. Here are a variety of ways to ask: | ||
| + | |||
| + | * //Alexa, ask Indigo to get my variable list// | ||
| + | * //Alexa, ask Indigo to list my variables// | ||
| + | * //Alexa, ask Indigo to list all variables// | ||
| + | * //Alexa, ask Indigo what variables are available// | ||
| + | |||
| + | You can also use //tell Indigo// interchangeably with //ask Indigo//. | ||
| + | |||
| + | === Execute an Action Group === | ||
| + | |||
| + | You can tell Indigo to execute an action group. Here are a variety of ways to ask (action group names are in quotes): | ||
| + | |||
| + | * //Alexa, tell Indigo to arm "the kitchen zone"// | ||
| + | * //Alexa, tell Indigo to do "my favorite thing"// | ||
| + | * //Alexa, tell Indigo to execute " | ||
| + | * //Alexa, tell Indigo to launch " | ||
| + | * //Alexa, tell Indigo to make "the house secure"// | ||
| + | * //Alexa, tell Indigo to perform " | ||
| + | * //Alexa, tell Indigo to play "my favorite playlist"// | ||
| + | * //Alexa, tell Indigo to reset "the alarm"// | ||
| + | * //Alexa, tell Indigo to restart "the laundry timer"// | ||
| + | * //Alexa, tell Indigo to restore "the standard speaker set"// | ||
| + | * //Alexa, tell Indigo to run " | ||
| + | * //Alexa, tell Indigo to start "the laundry timer"// | ||
| + | * //Alexa, tell Indigo to set "the playlist to classic rock"// | ||
| + | |||
| + | Action group names can contain letters, numbers, and spaces only. If you say " | ||
| + | |||
| + | ''< | ||
| + | </ | ||
| + | |||
| + | That will tell you the text that Alexa sent to the plugin, so you can name your action group exactly what's in single quotes and the next time it will work. | ||
| + | |||
| + | <color blue> | ||
| + | |||
| + | ===== Alexa Plugin operations ===== | ||
| + | |||
| + | === Plugin Startup === | ||
| + | |||
| + | When the plugin starts up, you will see a list of what's published to Alexa in the Event log. It will look something like this: | ||
| + | |||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | Alexa Warning | ||
| + | |||
| + | === Showing Publications === | ||
| + | |||
| + | You can also select the '' | ||
| + | |||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | |||
| + | === Discovery Requests from Alexa === | ||
| + | |||
| + | When the plugin receives a discover request from the Alexa servers, you will see something similar to this in the Event Log: | ||
| + | |||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | |||
| + | === Command Requests from Alexa === | ||
| + | |||
| + | When an Alexa command is received, you will see something similar to this in the Event Log: | ||
| + | |||
| + | | ||
| + | Sent Hue Lights | ||
| + | |||
| + | This will allow you to easily see that the change was the result of an Alexa request. This will show for every change that the Alexa plugin makes. | ||
| + | |||
| + | ===== Migrating from the Alexa Hue Bridge plugin ===== | ||
| + | |||
| + | If you are using the Alexa-Hue Bridge plugin, you will definitely want to read through this section. | ||
| + | |||
| + | We know there are users that have relied on the Alexa-Hue Bridge plugin even though it requires Echo hardware that is no longer available. It was a great stop-gap and we really appreciate everyone who contributed to maintaining it through the years, particularly forum user @Autolog. | ||
| + | |||
| + | If you are migrating, we highly recommend that you do a full switch rather than try to use both while switching. While it's possible to use both, doing a full switch will help you avoid a variety of issues, including Alexa caching, device name conflicts, etc. | ||
| + | |||
| + | === Full Switch === | ||
| + | |||
| + | Doing a full switch is pretty simple, just follow these steps: | ||
| + | |||
| + | - Disable the Alexa-Hue Bridge plugin. | ||
| + | - In the [[https:// | ||
| + | - In Indigo, follow the directions above in the [[indigo_2022.1_documentation: | ||
| + | - Once you have all your devices published, you can confirm that they are all published by selecting the '' | ||
| + | - In the Alexa app, website, or using an Alexa enabled device, click/touch the Discover button or say " | ||
| + | |||
| + | This should make all of your devices available in Alexa. Whenever you ask an Alexa device to discover, you will see the following Event Log line followed by a summary of publications: | ||
| + | |||
| + | < | ||
| + | |||
| + | === Partial Switch === | ||
| + | |||
| + | If you want to attempt to switch one at a time, the process is more complicated and somewhat error-prone. The general process is: | ||
| + | |||
| + | - Disable the device from the Alexa-Hue Bridge plugin (see [[https:// | ||
| + | - In the [[https:// | ||
| + | - In Indigo, follow the directions above in the [[indigo_2022.1_documentation: | ||
| + | - In the Alexa app, website, or using an Alexa enabled device, click/touch the Discover button or say " | ||
| + | |||
| + | Hopefully, Alexa will find your device and it will work properly. Unfortunately, | ||
| + | |||
| + | |||
| + | ===== Alexa Troubleshooting ===== | ||
| + | |||
| + | Because this integration is made up of a variety of parts, and because Alexa itself can talk to multiple smart home skills as well as allow the definition of custom " | ||
| + | |||
| + | If you don't find an answer to your problem in this section, post a detailed description of your issue and the steps you have taken (and any relevant Event Log entries) to the [[https:// | ||
| + | |||
| + | ==== Device Caching ==== | ||
| + | |||
| + | The first and foremost issue that users experience with Alexa, device discovery and device changes, is that Amazon caches device definitions, | ||
| + | |||
| + | So, when making any changes, it's always a good idea to wait for maybe 10 minutes between any changes that you make. For instance, if you change the name of a device, run discovery as advised below, but wait for 10 minutes before looking for the change in the Alexa app or trying to control the device using the new name. | ||
| + | |||
| + | Usually, when adding a new device, it happens pretty quickly. However, not always, and especially if it's combined with a change in another device. This seems not only to slowly propagate the change, but also slow the addition of a new device. | ||
| + | |||
| + | If you want to delete a device (or all devices to start over), this seems to be the most problematic scenario for their caching scheme. You will want to wait 10 minutes to make sure that the deletion actually occurs before doing anything else. Users have reported that doing a Remove All from the Alexa website will continually fail and that the way to accomplish it is to delete a few at a time. While we haven' | ||
| + | ==== Account Linking Issues ==== | ||
| + | |||
| + | When you enable the Indigo Smart Home Skill in the Alexa app, you're required to link it to a [[https:// | ||
| + | |||
| + | If you see an error page saying that you don't have any available licenses, this could be a result of a couple of things: | ||
| + | |||
| + | - You have previously linked your license to Alexa but haven' | ||
| + | - Your Indigo Up-to-Date subscription has expired. To use Alexa (and similar types of integrations), | ||
| + | - Your Indigo License doesn' | ||
| + | |||
| + | ==== Changing a Published Device in Indigo ==== | ||
| + | === Changing the Indigo Name === | ||
| + | |||
| + | If you specified an alternate name for a device when publishing it, then changing the Indigo name won't make any difference and you won't need to do anything. | ||
| + | |||
| + | If, however, you didn't specify an alternate name, then Indigo will use the Indigo device name. If you change it, then you will need to rerun discovery in the Alexa app or on an Alexa-enabled device. If discovering by voice command, Alexa will say that it couldn' | ||
| + | |||
| + | If it doesn' | ||
| + | |||
| + | Also, remember our discussion of device caches above: give Alexa at least 10 minutes for changes to propagate throughout their device caches. | ||
| + | |||
| + | If you've made a change and waited and it's still not responding, one other possibility is that you have a routine defined in Alexa with the name or a similar name - that may cause conflicts when Alexa attempts to determine what it is you're asking. | ||
| + | === Changing the Alternate (Alexa) Name === | ||
| + | |||
| + | If you change the alternate name, you will need to rerun discovery. If the new name doesn' | ||
| + | === Changing the Device Type === | ||
| + | |||
| + | If you edit a device and change the type, protocol, or anything that changes the nature of the device, you will most likely want to follow this procedure: | ||
| + | |||
| + | - In the Alexa app, remove the device. | ||
| + | - Go back to the [[indigo_2022.1_documentation: | ||
| + | - Save any changes. | ||
| + | - Rerun discovery in Alexa. | ||
| + | |||
| + | It should say that it has found a new device (since you deleted it first) and you should now be able to control it based on the new type. Note that changing protocol might not require the process above (an Indigo dimmer device works the same no matter the protocol), but we have found that Alexa caches information about devices and just doing a discover after changing may not be enough to force Alexa to reset the device cache. | ||
| + | |||
| + | ==== General Issues ==== | ||
| + | |||
| + | Alexa uses some sophisticated caching mechanisms throughout their hosted systems in order to optimize performance/ | ||
| + | |||
| + | The very first thing you want to check when troubleshooting any Alexa issues is the Event Log window. You will see various warnings and errors that will help you determine if there are issues. Those errors may help you to determine where to go next. First, ensure the following: | ||
| + | |||
| + | - Make sure that you have [[indigo_2022.1_documentation: | ||
| + | - Make sure that your [[https:// | ||
| + | - Ensure that your Indigo Reflector is configured and connected. Check this by hitting your reflector URL in a browser: https:// | ||
| + | |||
| + | Here are a few things to help you diagnose issues. | ||
| + | |||
| + | === Alexa can't find a device === | ||
| + | |||
| + | - Make sure that you have [[indigo_2022.1_documentation: | ||
| + | - Watch the Event Log window for [[indigo_2022.1_documentation: | ||
| + | * If you don't see any discovery requests: | ||
| + | * Make sure that your reflector is up and running | ||
| + | * Make sure your Indigo Up-to-Date subscription hasn't lapsed | ||
| + | * Make sure you have OAuth enabled in the [[indigo_2022.1_documentation: | ||
| + | |||
| + | * If you see a discovery request: | ||
| + | * Make sure that the device you are publishing is in the list. Take note of the names of your published devices to ensure that they are unique - if you publish two devices with the same name Alexa will ignore or both of them. | ||
| + | * If the above step is fine, then make sure that you aren't using a name that's used by a device in some other smart home skill (some users use the Hue skill to directly control Hue lights, if you have the Alexa-Hue Bridge plugin enabled that may also be publishing a device with the same name). | ||
| + | * Make sure that you are giving Alexa enough time to update its caches - 10 minutes after a discovery is the recommended wait time. | ||
| + | * If you have a slow or unreliable internet connection, Alexa can timeout a request rather quickly and will speak some error message. If you see inconsistent behavior, this may be a hint that there is some kind of internet connection issue between the Alexa hosted servers and your Indigo Server (see below for more details). | ||
| + | |||
| + | === Alexa can't control a device === | ||
| + | |||
| + | Some steps to try when Alexa says it can't find a device: | ||
| + | |||
| + | - Make sure you are clearly saying the device name. Alexa can sometimes hear something slightly different than what you're saying. | ||
| + | - Make sure you have the device published in the plugin. You can do this by selecting the '' | ||
| + | - Rerun discovery from the Alexa app for an Alexa device. | ||
| + | - Look in the Event Log window for errors when trying to control the device. | ||
| + | |||
| + | === Alexa can't speak a variable value === | ||
| + | |||
| + | Some steps to try when Alexa has a problem speaking the value of a variable: | ||
| + | |||
| + | - Make sure that the value doesn' | ||
| + | - Make sure that the value of the variable is less than 8000 characters - that's the speech output limit for Alexa. | ||
| + | |||
| + | === Alexa can't speak the variable list === | ||
| + | |||
| + | Some steps to try when Alexa has a problem speaking the variable list: | ||
| + | |||
| + | - If you have too many variables, you may get the error //“There is a problem with the requested skill response”// | ||
| + | |||
| + | === Alexa can't speak the variable of a variable === | ||
| + | |||
| + | If the value of your variable contains an ampersand (&) or perhaps other special characters, you should replace them with the actual english word (and). Alternately, | ||
| + | |||
| + | === Alexa says there are issues when you try various things === | ||
| + | |||
| + | Alexa skills are hosted on their servers, and must communicate with your Indigo server through your reflector. If you have a poor internet connection, you may see some odd issues: not being able to discover, errors when you ask Indigo for things even though it appears on the Indigo side that they have happened, etc. Their API is very picky about response times, as slow response times is a poor user experience. This does mean, however, that anyone with slow connections (Satellite) or unreliable internet connections will experience various error messages from Alexa. Unfortunately, | ||
| + | |||
| + | === If All Else Fails ==== | ||
| + | If every other troubleshooting step has been taken and you have multiple Indigo licenses, contact support (mentioning that you have multiple licenses) so we can more quickly determine if this is related to your problem. | ||