From 4b71bd301f03e7395a6829bc7cb8c9cf48165c49 Mon Sep 17 00:00:00 2001 From: hcooper Date: Sun, 24 Jun 2018 05:21:19 -0700 Subject: [PATCH] [snips] Adding warning about mismatching intent names (#5582) * Adding warning about mismatching intent names Took me a while to realize snips.py is editing the intent name, causing it to mismatch intent configs. * [snips] warning about intent names * :pencil2: Small tweak --- source/_components/snips.markdown | 2 ++ 1 file changed, 2 insertions(+) diff --git a/source/_components/snips.markdown b/source/_components/snips.markdown index 6dece0c5743..fd125970615 100644 --- a/source/_components/snips.markdown +++ b/source/_components/snips.markdown @@ -141,6 +141,8 @@ 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`](/components/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 component in Home Assistant [will try and strip off the username](https://github.com/home-assistant/home-assistant/blob/c664c20165ebeb248b98716cf61e865f274a2dac/homeassistant/components/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 component is trying to match the non-username version of the intent (i.e., just `playmusic`). + {% raw %} ```yaml snips: