Who can develop smart home add-ons for Alexa?
Anyone with cloud-connected devices can develop a smart home add-on. The Smart Home API uses the pre-built voice interaction model, which defines the utterances that customers say to interact with your add-on. Each interface defines a set of pre-built utterances to control the device. Alexa knows how to interpret the customer’s speech and what directives to send to your add-on. Smart home add-on development falls into two categories:- Device manufacturers who want to enable customers to interact with their cloud-connected devices by using voice, the Alexa app, and Alexa-enabled devices with a screen
- Independent developers who want to create an Alexa add-on for cloud-connected devices, either for their own private use or general public use
What kinds of devices does the Smart Home API support?
You can connect almost any type of device to Alexa by using the Smart Home API. You decide how you want the customer to interact with your device, and then you implement the capability interfaces that support those interactions. For example, your device might be a lamp that customers want to turn on and off. To support this functionality, you implement theAlexa.PowerController interface in your add-on.
Most devices implement multiple smart home interfaces to support multiple device features, such as dimming the light and turning the light off and on. For the full list of smart home interfaces, see List of Alexa Interfaces and Supported Languages.
Some Alexa interfaces support specific device types, but other interfaces support many kinds of devices. For example, implement the Alexa.ThermostatController interface only for thermostats, but implement interfaces like Alexa.PowerLevelController for many kinds of devices.
How your cloud connects to Alexa
Your smart home add-on uses the smart home model. The add-on code runs in an Amazon Web Services (AWS) Lambda function and handles communication between Alexa and your device. When a customer enables your add-on, Alexa starts device discovery. During discovery, your add-on describes your device and the properties and interfaces that it supports, and reports the device details to Alexa. Then, when a customer asks Alexa to control the device, Alexa sends your add-on a directive. Your add-on reacts to the message by changing the state of the device through your cloud infrastructure. Your add-on uses account linking to connect the customer’s account in your system with their Amazon account. Account linking lets your add-on identify the customer and their devices, and it requires an OAuth 2.0 authorization server. For details, see Account Linking for Smart Home and Other Domains.Capability interfaces
The Smart Home API provides capability interfaces that you use to describe your devices and the properties, events, and directives that they support. After you receive aDiscover directive from Alexa, send a Discover.Response event to describe your device. For details, see About Alexa Discovery.
Alexa uses this description of your device and its capabilities to automatically enable certain functionality, such as:
- Contextual targeting, which uses clues, such as device groups, to target the device when the customer doesn’t name the device explicitly
- Controlling devices through Alexa Routines
- Viewing and controlling devices with the Alexa app and on Alexa-enabled devices with a screen
Device updates
The Smart Home API also supports device updates when the state of a device changes. Customers can ask Alexa about the state of a device and view the up-to-date status in the Alexa app and on Alexa-enabled devices with a screen. For example, a customer can check the temperature of their home or see if a light is on. In addition, your add-on or device can proactively notify Alexa when the customer manually changes the device state, such as turning on the light switch. For details, see Understand State and Change Reporting. To support these customer scenarios, the Smart Home API has the following features:- Synchronous and asynchronous messaging – When Alexa sends a directive, your smart home add-on responds either synchronously or asynchronously. You’re free to choose asynchronous or synchronous responses or a combination of the two, whichever works best for your device and cloud architecture.
- Device state change notifications – When you provide proactive state updates to Alexa, Alexa shows accurate, up-to-date device status in the Alexa app and on Alexa-enabled devices with a screen. Proactive updates enable customers to take action, if needed. For example, if someone manually unlocks the door, you can send this change to Alexa to speak or display to the customer.
- Querying state – Capability interfaces define properties that Alexa can query. Customers can ask Alexa for the current state of a device or view it in the Alexa app.
Example: Control a kitchen light
A customer enables your smart home add-on and links it to their account in your device cloud. Alexa then discovers the devices associated with that account. Later, the customer says, for example, or makes a change to a device setting in the Alexa app. Alexa uses information from the customer’s utterance or the app to compose a message that identifies the endpoint and the operation to perform. Alexa sends this message, called a directive, to your add-on to control the kitchen light. The directive includes:- The directive name and interface, for example,
BrightnessController.SetBrightness, and the new setting value - The endpoint ID, in this example, the ID for the device that the customer named “kitchen light”
- Information that authenticates the customer
ChangeReport event to Alexa to indicate that the light is now off. Alexa displays the updated status in the Alexa app and on Alexa-enabled devices with a screen.

