Amazon Developer

as

Settings
Sign out
Notifications
Alexa
Amazon Appstore
Ring
AWS
Documentation
Support
Contact Us
My Cases
Get started
Connect with Matter
Alexa Connect Kit
Add-ons
Certify
Resources
Skip to main content
Implement the Alexa.Cooking.PresetController interface in your Alexa add-on so that users can control cooking appliances that cook with custom settings, called presets. For example, a microwave with a popcorn button or an oven with a custom way to cook “Herb Roasted Chicken” for a specific brand. When you set up presets, a user can cook foods without manually having to select time, temperature, or power level, and without having to read directions. You must use the PresetController interface with the Alexa.Cooking interface. For more details about cooking add-ons, see Build Smart Home Add-ons for Cooking Appliances. For the list of languages that the PresetController interface supports, see List of Alexa Interfaces and Supported Languages. For the definitions of the message properties, see Alexa Interface Message and Property Reference.

Utterances

The Alexa.Cooking.PresetController interface uses the pre-built voice interaction model. The following examples show some customer utterances:


After the user says one of these utterances, Alexa sends a corresponding directive to your add-on.

Preset catalogs

Preset cooking relies on a catalog of custom cooking settings that you provide to Amazon. Alexa can use this catalog to tailor the speech recognition to better understand the user’s utterances and intentions. A preset catalog includes the preset item name and cooking mode, along with some optional fields, such as whether the preset requires the food quantity. Together, the preset item name and cooking mode must be unique. Consider the following when you build your catalog:
  • Include commonly used recipes and packaged food in your catalog.
  • Avoid using the full name of items.
  • Avoid repeating the same words in more than one item.
  • Group items that share the same cooking mode and time settings under a common name, such as roasted chicken.
  • Use item names that reflect the most common way people identify or describe the cooked item, not necessarily the actual name on the box.
  • Catalogs can vary by brand, appliance type, and model.
The following table shows an example of information to provide in your preset catalog.
Preset item nameCooking modeFood quantity (optional)
ChickenDEFROSTWeight
ChickenROAST—
CoffeeREHEATVolume
PopcornPRESET—
PotatoesPRESETCount
You identify the catalog that your device uses in your discover response. When the user includes a preset in the utterance, Alexa sends the item from the catalog to your add-on in the CookByPreset directive.

Prepare your preset catalog for submission

You must send an email request to Amazon to receive your catalog ID and instructions about uploading your catalog. To prepare to submit a preset cooking catalog for Alexa to use
  1. Draft an email that includes in the subject line, the appliance brand, the appliance type, the appliance model, and your AWS Account ID. For example, your email could look like the following.
  2. Send the email to alexa-kitchen-presets@amazon.com.
Within two weeks, you receive a response that includes the following information:
  • Instructions for uploading your catalog.
    • How to format your catalog in Excel.
    • Where to upload the Excel file that contains your catalog.
  • Your preset catalog ID.
    • The ID is from 3 through 63 characters long, and contains numbers, lower case letters, and hyphens.
    • You specify the catalog ID in your discover response for devices that use the catalog.

Reportable properties

The Alexa.Cooking.PresetController interface uses the presetName and the requestedFoodDoneness properties as the primary properties. The presetName property represents the name of the preset from the preset catalog. The requestedFoodDoneness property, expressed as a FoodDoneness string, represents how cooked a user wants their food, such as a hard egg or a well-done steak.

FoodDoneness values

FoodDoneness represents how cooked a user wants their food, such as a rare steak, crispy bacon, or al dente pasta. You can use the following values for FoodDoneness. The values are strings.
Doneness valueSupported food types
AL_DENTEPasta, vegetables
CREAMYEggs
CRISPYVegetables
DRY—
FIRMFish, poultry
FLAKYFish
HARDEggs
JUICYPoultry
MEDIUMEggs, fish, meat, pasta
MEDIUM_RAREFish, meat
MEDIUM_WELLEggs, fish, meat, pasta
MOIST—
OPAQUE—
OVERCOOKEDFish, meat, pasta
RAREFish, meat
RUNNYEggs
SMOOTHEggs
SOFTEggs, vegetables
SPRINGY—
SUCCULENT—
TENDERPoultry
UNDERCOOKEDPasta, vegetables
VELVETYEggs
WELL_DONEFish, meat, pasta

Discovery

You describe endpoints that support Alexa.Cooking.PresetController by using the standard discovery mechanism described in Alexa.Discovery. Set retrievable to true for the properties that you report when Alexa sends your add-on a state report request. Set proactivelyReported to true for the properties that you proactively report to Alexa in a change report. For the full list of display categories, see display categories. To let Alexa know the health of your device, also implement the Alexa.EndpointHealth interface.

Configuration object

In addition to the usual discovery response fields, for PresetController, include a configuration object that contains the following fields.
FieldDescriptionTypeRequired
presetCatalogIdID for the preset catalog. For details, see preset catalogs.StringYes
supportsRemoteStartTrue if Alexa can start the device after a voice command. When false, Alexa sends the CookByPreset directive to set the parameters for the cook session, and Alexa prompts the user to push Start on the device. The default is false.BooleanNo
supportedCookingModesCooking modes that the device supports through this interface. Specify the default cooking mode as the first item in the array. Use other interfaces to specify cooking modes for the same appliance.Array of CookingMode valuesYes

Discover response example

The following example shows a Discover.Response message for a microwave that supports the PresetController and Cooking interfaces.

Directives

Alexa sends the following Alexa.Cooking.PresetController interface directives to your add-on.

CookByPreset directive

Support the CookByPreset directive so that customers can start a cooking session and specify a preset option. The following examples show customer utterances:

CookByPreset directive example

The following example shows a CookByPreset directive that Alexa sends to your add-on.

CookByPreset directive with requested food doneness example

The following example shows a CookByPreset directive that Alexa sends to your add-on to request a specific food doneness.

CookByPreset directive payload

The following table shows the payload details for the CookByPreset directive.
PropertyDescriptionTypeRequired
presetNameName of the preset option to use for the cooking session. For details, see preset catalogs.StringYes
cookingModeCooking mode for the cooking session, such as PRESET mode. If the user doesn’t specify the cookingMode, Alexa chooses the first supported mode that you specified in your discovery response.CookingMode objectYes
requestedFoodDonenessHow cooked a user wants their food, such as a rare steak. The directive includes this field only if the user specifies it.FoodDoneness stringNo
foodItemFood to cook. The directive includes this field only if the user specifies it.FoodItem objectNo

CookByPreset response

If you handle a CookByPreset directive successfully, respond with an Alexa.Response event. In the context object, include the values of all relevant properties. The following example shows a response to a CookByPreset directive. The context object contains the values of all properties relevant to the current cooking action, even those properties defined by other interfaces.

CookByPreset directive error handling

If you can’t handle a CookByPreset directive successfully, respond with an Alexa.Cooking.ErrorResponse event. You can also respond with a generic Alexa.ErrorResponse event if your error is generic, and not specific to cooking.

State reporting

Alexa sends a ReportState directive to request information about the state of an endpoint. When Alexa sends a ReportState directive, you send a StateReport event in response. The response contains the current state of all retrievable properties in the context object. You identify your retrievable properties in your discovery response. For more details about state reports, see Understand State and Change Reporting.

StateReport response example

Change reporting

You send a ChangeReport event to report changes proactively in the state of an endpoint. You identify the properties that you proactively report in your discovery response. For more details about change reports, see Understand State and Change Reporting.

ChangeReport event example

Last modified on December 22, 2025