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-10 10:56:49 +00:00
Code Issues Packages Projects Releases Wiki Activity

Changed the Flow

Browse Source 
Moved 'Testing your trigger' to the end of the page.
This commit is contained in:
Carlo Costanzo 2015-09-28 01:42:13 -04:00
parent fb6df63661
commit 1c97229c84
1 changed files with 8 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
source/components/ifttt.manything.markdown
View File

@ -55,6 +55,14 @@ automation:
data: {"event":"manything_off"} data: {"event":"manything_off"}
``` ```
### {% linkable_title Setting up a recipe %}
<p class='img'>
<img src='/images/components/ifttt/IFTTT_manything_trigger.png' />
You need to setup a unique trigger for each event you sent to IFTTT.
For ManyThing support, you need to set up an <code>on</code> and <code>off</code> event.
</p>
### {% linkable_title Testing your trigger %} ### {% linkable_title Testing your trigger %}
You can use the developer tools to test your [Maker Channel](https://ifttt.com/maker) trigger. To do this, open the Home Assistant UI, open the sidebar, click on the first icon in the developer tools. This should get you to the 'Call Service' screen. Fill in the following values: You can use the developer tools to test your [Maker Channel](https://ifttt.com/maker) trigger. To do this, open the Home Assistant UI, open the sidebar, click on the first icon in the developer tools. This should get you to the 'Call Service' screen. Fill in the following values:
@ -65,11 +73,4 @@ domain | `ifttt`
service | `trigger` service | `trigger`
Service Data | `{"event": "manything_on"}` Service Data | `{"event": "manything_on"}`
### {% linkable_title Setting up a recipe %}
<p class='img'>
<img src='/images/components/ifttt/IFTTT_manything_trigger.png' />
You need to setup a unique trigger for each event you sent to IFTTT.
For ManyThing support, you need to set up an <code>on</code> and <code>off</code> event.
</p>