Skip to content

Commit e221eac

Browse files
committed
Update
1 parent 77441ba commit e221eac

File tree

1 file changed

+13
-10
lines changed

1 file changed

+13
-10
lines changed

source/_components/ifttt.markdown

Lines changed: 13 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -12,30 +12,30 @@ ha_category: Automation
1212
featured: true
1313
---
1414

15-
[IFTTT](https://ifttt.com) is a web service that allows users to create chains of simple conditional statements, so called "recipes". With the IFTTT component you can trigger recipes through the "maker" channel. See the [announcement blog post](/blog/2015/09/13/home-assistant-meets-ifttt/) for examples how to use it.
15+
[IFTTT](https://ifttt.com) is a web service that allows users to create chains of simple conditional statements, so called "Applets". With the IFTTT component you can trigger applets through the **"Maker"** channel. See the [announcement blog post](/blog/2015/09/13/home-assistant-meets-ifttt/) for examples how to use it.
1616

1717
```yaml
1818
# Example configuration.yaml entry
1919
ifttt:
2020
key: xxxxx-x-xxxxxxxxxxxxx
2121
```
2222
23-
Key is your API key which can be obtained by viewing the properties of the [Maker Channel](https://ifttt.com/maker).
23+
`key` is your API key which can be obtained by viewing the **Settings** of the [Maker Channel](https://ifttt.com/maker). It's the last part of the URL.
2424

2525
<p class='img'>
2626
<img src='/images/components/ifttt/finding_key.png' />
2727
Property screen of the Maker Channel
2828
</p>
2929

30-
Once you have added your key to `configuration.yaml`, restart your Home Assistant server. This will load up the IFTTT component and make a service available to trigger events in IFTTT.
30+
Once you have added your key to your `configuration.yaml` file, restart your Home Assistant server. This will load up the IFTTT component and make a service available to trigger events in IFTTT.
3131

3232
<p class='note'>
3333
After restarting the server, be sure to watch the console for any logging errors that show up in red, white or yellow.
3434
</p>
3535

3636
### {% linkable_title Testing your trigger %}
3737

38-
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:
38+
You can use the **Developer tools** to test your [Maker Channel](https://ifttt.com/maker) trigger. To do this, open the Home Assistant frontend, 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:
3939

4040
Field | Value
4141
----- | -----
@@ -50,6 +50,13 @@ When your screen looks like this, click the 'call service' button.
5050

5151
### {% linkable_title Setting up a recipe %}
5252

53+
Press the *New applet* button and search for *Maker* .
54+
55+
<p class='img'>
56+
<img src='/images/components/ifttt/setup_service.png' />
57+
Choose "Maker" as service.
58+
</p>
59+
5360
<p class='img'>
5461
<img src='/images/components/ifttt/setup_trigger.png' />
5562
You need to setup a unique trigger for each event you sent to IFTTT.
@@ -69,13 +76,9 @@ automation:
6976

7077
### {% linkable_title Sending events from IFTTT to Home Assistant %}
7178

72-
To be able to receive events from IFTTT, your Home Assistant instance needs to be accessible from the web. This can be achieved by forwarding port 8123 from your router to the device running Home Assistant. If your ISP is giving you a new IP address from time to time, consider using [DuckDNS][duck-dns].
73-
74-
In the URL field, you can then put an [API URL][rest-api]. You probably want to use a POST action, so select `POST` as method. After your request line, you need to add your Home Assistant password, which you defined in the [http section of your config][http-configuration], in the form off `?api_password=<your_password>`. For the message body, refer to the API page linked above.
79+
To be able to receive events from IFTTT, your Home Assistant instance needs to be accessible from the web. This can be achieved by forwarding port 8123 from your router to the device running Home Assistant. If your ISP is giving you a new IP address from time to time, consider using [DuckDNS](https://duckdns.org).
7580

76-
[duck-dns]: https://duckdns.org
77-
[rest-api]: https://home-assistant.io/developers/rest_api/
78-
[http-configuration]: https://home-assistant.io/getting-started/basic/#password-protecting-the-web-interface
81+
In the URL field, you can then put an [API URL](/developers/rest_api/). You probably want to use a POST action, so select `POST` as method. After your request line, you need to add your Home Assistant password, which you defined in the [http section of your config](/getting-started/basic/#password-protecting-the-web-interface), in the form of `?api_password=YOUR_PASSWORD`. For the message body, refer to the API page linked above.
7982

8083
<p class='img'>
8184
<img src='/images/components/ifttt/IFTTT_to_HA.png' />

0 commit comments

Comments
 (0)