From f7e5b556ff4615298399731e6c8826b03ccdb2ed Mon Sep 17 00:00:00 2001 From: Brandon Corry <17894275+brandoncorry@users.noreply.github.com> Date: Tue, 5 Nov 2019 03:12:58 -0800 Subject: [PATCH] Adding a small tip about DNS propagation. (#11101) I recently had to redo the setup for Google Assistant. Everything was correct (URLs in Google, ports, port forwarding, certs, etc.) but the process was failing when trying to connect with Google Assistant via the app to add the devices. While doing many troubleshooting steps, after some time, it would randomly work once, then not again for some time. More troubleshooting with failures, then randomly work. I had updated my DNS about 12-15 hours prior, which I thought was enough time, but it looks like it needed longer. Simply waiting was sufficient. I am hoping that this tip might save others some time pulling their hair out. :) --- source/_integrations/google_assistant.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_integrations/google_assistant.markdown b/source/_integrations/google_assistant.markdown index f49c2e84a0c..a96ea5a33f6 100644 --- a/source/_integrations/google_assistant.markdown +++ b/source/_integrations/google_assistant.markdown @@ -22,7 +22,7 @@ The Google Assistant integration requires a bit more setup than most due to the
-To use Google Assistant, your Home Assistant configuration has to be [externally accessible with a hostname and SSL certificate](/docs/configuration/remote/). If you haven't already configured that, you should do so before continuing. +To use Google Assistant, your Home Assistant configuration has to be [externally accessible with a hostname and SSL certificate](/docs/configuration/remote/). If you haven't already configured that, you should do so before continuing. If you make DNS changes to accomplish this, please ensure you have allowed up to the full 48 hours for DNS changes to propogate, otherwise Google may not be able to reach your server.