From bf653ac333e1a42ebd919564f7646ee1dd48d537 Mon Sep 17 00:00:00 2001 From: Flo Date: Thu, 11 May 2023 08:54:02 +0200 Subject: [PATCH] Update alexa.intent.markdown (#27326) --- source/_integrations/alexa.intent.markdown | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/source/_integrations/alexa.intent.markdown b/source/_integrations/alexa.intent.markdown index 3fa8b049d11..06a160ff05f 100644 --- a/source/_integrations/alexa.intent.markdown +++ b/source/_integrations/alexa.intent.markdown @@ -195,6 +195,8 @@ The names must exactly match the scene names (minus underscores - Amazon discard In the new Alexa Skills Kit, you can also create synonyms for slot type values, which can be used in place of the base value in utterances. Synonyms will be replaced with their associated slot value in the intent request sent to the Alexa API endpoint, but only if there are not multiple synonym matches. Otherwise, the value of the synonym that was spoken will be used. +If you want to use the `Optional ID` field next to or instead of the Synonym value, you can simply append "_Id" at the end of the template variable e.g. `Scene_Id`. +

Custom slot values with synonyms. @@ -217,6 +219,8 @@ intent_script: service: scene.turn_on target: entity_id: scene.{{ Scene | replace(" ", "_") }} + data: + id: {{ Scene_Id }} speech: type: plain text: OK