jeans/home-assistant.io
jeans/home-assistant.io
1
0
Fork 0
mirror of https://github.com/home-assistant/home-assistant.io.git synced 2025-07-19 15:26:59 +00:00
Code Issues Packages Projects Releases Wiki Activity

[snips] Adding warning about mismatching intent names (#5582)

Browse Source 
* 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

* ✏️ Small tweak
This commit is contained in:
hcooper 2018-06-24 05:21:19 -07:00 committed by Franck Nijhof
parent bd1b69f400
commit 4b71bd301f
1 changed files with 2 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
source/_components/snips.markdown
View File

@ -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: