-
IFTTT 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 for examples how to use it.
+IFTTT 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 for examples how to use it.
# Example configuration.yaml entry
ifttt:
@@ -98,14 +98,14 @@
Key is your API key which can be obtained by viewing the properties of the Maker Channel.
+key is your API key which can be obtained by viewing the Settings of the Maker Channel. It’s the last part of the URL.
Property screen of the Maker Channel
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.
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.
After restarting the server, be sure to watch the console for any logging errors that show up in red, white or yellow. @@ -113,7 +113,7 @@ After restarting the server, be sure to watch the console for any logging errors
Testing your trigger
-You can use the developer tools to test your Maker Channel 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 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:
+Choose “Maker” as service.
+
You need to setup a unique trigger for each event you sent to IFTTT.
@@ -166,7 +173,7 @@ You need to setup a unique trigger for each event you sent to IFTTT.
diff --git a/images/components/ifttt/IFTTT_to_HA.png b/images/components/ifttt/IFTTT_to_HA.png
index 1bd2df9cf3..1005004b06 100644
Binary files a/images/components/ifttt/IFTTT_to_HA.png and b/images/components/ifttt/IFTTT_to_HA.png differ
diff --git a/images/components/ifttt/finding_key.png b/images/components/ifttt/finding_key.png
index 5502f2a68a..0a4ea0a11d 100644
Binary files a/images/components/ifttt/finding_key.png and b/images/components/ifttt/finding_key.png differ
diff --git a/images/components/ifttt/setup_service.png b/images/components/ifttt/setup_service.png
new file mode 100644
index 0000000000..ab9685921b
Binary files /dev/null and b/images/components/ifttt/setup_service.png differ
diff --git a/images/components/ifttt/setup_trigger.png b/images/components/ifttt/setup_trigger.png
index 6e93b14ea3..77ae362663 100644
Binary files a/images/components/ifttt/setup_trigger.png and b/images/components/ifttt/setup_trigger.png differ
diff --git a/images/components/ifttt/testing_service.png b/images/components/ifttt/testing_service.png
index 27a53a5ff2..bb31479729 100644
Binary files a/images/components/ifttt/testing_service.png and b/images/components/ifttt/testing_service.png differ
diff --git a/sitemap.xml b/sitemap.xml
index 457ef096fb..f7bc3fe2f9 100644
--- a/sitemap.xml
+++ b/sitemap.xml
@@ -2309,62 +2309,62 @@