From 9c465abc77d4930a6bc735e69dd6918502be2655 Mon Sep 17 00:00:00 2001 From: xelprep Date: Thu, 17 Oct 2019 09:30:31 -0700 Subject: [PATCH] Snips Doc - Fix link (#10772) * Snips Doc - Fix link The original author intended to link to a specific `if` statement that strips a username from an intent. * :pencil2: Removed the link --- source/_integrations/snips.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_integrations/snips.markdown b/source/_integrations/snips.markdown index ebcc67f9548..1937ef70490 100644 --- a/source/_integrations/snips.markdown +++ b/source/_integrations/snips.markdown @@ -135,7 +135,7 @@ Alternatively, MQTT can be configured to bridge messages between servers if usin In Home Assistant, we trigger actions based on intents produced by Snips using the [`intent_script`](/integrations/intent_script) component. For instance, the following block handles a `ActivateLightColor` intent to change light colors: -Note: If your Snips action is prefixed with a username (e.g., `john:playmusic` or `john__playmusic`), the Snips integration in Home Assistant [will try and strip off the username](https://github.com/home-assistant/home-assistant/blob/c664c20165ebeb248b98716cf61e865f274a2dac/homeassistant/integrations/snips.py#L126-L129). Bear this in mind if you get the error `Received unknown intent` even when what you see on the MQTT bus looks correct. Internally the Snips integration is trying to match the non-username version of the intent (i.e., just `playmusic`). +Note: If your Snips action is prefixed with a username (e.g., `john:playmusic` or `john__playmusic`), the Snips integration in Home Assistant will try and strip off the username. Bear this in mind if you get the error `Received unknown intent` even when what you see on the MQTT bus looks correct. Internally the Snips integration is trying to match the non-username version of the intent (i.e., just `playmusic`). {% raw %} ```yaml