Set the lights to green in the living room
We should see the transcribed phrase in the logs, as well as a properly parsed intent. The intent is published on MQTT, on the hermes/nlu/intentParsed topic. The Snips Home Assistant component subscribes to this topic, and handles the intent according to the rules defined in configuration.yaml, as explained below.
By default, Snips runs its own MQTT broker. But we can also tell Snips to use an external broker by specifying this when launching Snips. In this case, instead of running the snips command above (which assumes we are using the internal MQTT broker), we use the full launch command with explicitly specified parameters (replace MQTT_BROKER_IP and MQTT_BROKER_PORT with appropriate values):
$ docker run -t --rm --name snips --log-driver none -v /home/pi/.asoundrc:/root/.asoundrc -v /opt/snips/config:/opt/snips/config --privileged -v /dev/snd:/dev/snd snipsdocker/platform --mqtt MQTT_BROKER_IP:MQTT_BROKER_PORT
+For more details on launch options, check the documentation on Snips Platform Commands.
By default, the Snips MQTT broker runs on port 9898. We should tell Home Assistant to use this as a broker, rather than its own, by adding the following section to configuration.yaml:
Messages between Snips and Home Assistant are passed via MQTT. We must tell Home Assistant which MQTT broker to use by adding the following entry to configuration.yaml:
mqtt:
+ broker: MQTT_BROKER_IP
+ port: MQTT_BROKER_PORT
+As explained above, Snips by default runs an MQTT broker on port 9898. So if we wish to use this broker, the entry will look as follows:
mqtt:
broker: 127.0.0.1
port: 9898
In Home Assistant, we trigger actions based on intents produced by Snips. This is done in configuration.yaml. For instance, the following block handles ActivateLightColors intents (included in the Snips IoT intent bundle) to change light colors:
snips:
intents:
diff --git a/docs/scripts/index.html b/docs/scripts/index.html
index 96064a227f..d3141021a0 100644
--- a/docs/scripts/index.html
+++ b/docs/scripts/index.html
@@ -127,7 +127,7 @@
Wait until some things are complete. We support at the moment wait_template for waiting until a condition is true, see also on Template-Trigger. It is possible to set a timeout after that will the script abort his execution. Timeout have same syntax as delay.
Wait until some things are complete. We support at the moment wait_template for waiting until a condition is true, see also on Template-Trigger. The Timeout has same syntax as delay. If you set a Timeout for 1 minute and the condition is not satified within that minute, the script will continue.
# wait until media player have stop the playing
wait_template: "{{ states.media_player.floor.states == 'stop' }}"