diff --git a/_deploy b/_deploy
index 8c6ee3c712f..9a3bd15c402 160000
--- a/_deploy
+++ b/_deploy
@@ -1 +1 @@
-Subproject commit 8c6ee3c712fedd76d9d21cd41ea479443743bc49
+Subproject commit 9a3bd15c4023fa258c30dff51e5bd971664c96b2
diff --git a/source/components/ifttt.markdown b/source/components/ifttt.markdown
index 5376bded7b7..8cffcb173b9 100644
--- a/source/components/ifttt.markdown
+++ b/source/components/ifttt.markdown
@@ -9,7 +9,10 @@ sharing: true
 footer: true
 ---
 <img src='/images/supported_brands/ifttt.png' class='brand pull-right' />
-[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.
+[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.
 
 ```yaml
 # Example configuration.yaml entry
@@ -51,3 +54,12 @@ When your screen looks like this, click the 'call service' button.
 <img src='/images/components/ifttt/setup_trigger.png' />
 You need to setup a unique trigger for each event you sent to IFTTT.
 </p>
+
+### {% linkable_title Sending events from IFTTT to Home Assistant %}
+
+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].
+
+[duck-dns]: https://duckdns.org