From e3ab5eea073c6c122e97de8d176260a28253db3a Mon Sep 17 00:00:00 2001
From: Paulus Schoutsen <paulus@paulusschoutsen.nl>
Date: Sat, 14 Oct 2017 00:18:27 -0700
Subject: [PATCH] Update lets_encrypt.markdown

---
 source/_docs/ecosystem/certificates/lets_encrypt.markdown | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/source/_docs/ecosystem/certificates/lets_encrypt.markdown b/source/_docs/ecosystem/certificates/lets_encrypt.markdown
index c248bec61d7..ad7963fae69 100644
--- a/source/_docs/ecosystem/certificates/lets_encrypt.markdown
+++ b/source/_docs/ecosystem/certificates/lets_encrypt.markdown
@@ -9,6 +9,10 @@ sharing: true
 footer: true
 ---
 
+<p class='note'>
+If you are using Hass.io, do not use this guide. Instead, use the [DuckDNS add-on](/addons/duckdns/) to automatically maintain a subdomain including HTTPS certificates via Let's Encrypt.
+</p>
+
 <p class=' note warning'>
 Before exposing your Home Assistant instance to the outside world it is ESSENTIAL that you have set a password following the advice on the [http](https://home-assistant.io/docs/configuration/basic/) page.
 </p>