From 31af901a4899efb951fdde50f94b1299e50e92e0 Mon Sep 17 00:00:00 2001 From: keeperofdakeys Date: Mon, 18 May 2020 18:52:42 +1000 Subject: [PATCH] Mention mDNS behaviour change in cast docs (#13380) Explicitly mention that mDNS discovery is now mandatory as of version 109 of Home Assistant. This ensures users who are upgrading with an unsupported configuration are aware that this behaviour has changed, so they must make the appropriate changes to their infrastructure. --- source/_integrations/cast.markdown | 2 ++ 1 file changed, 2 insertions(+) diff --git a/source/_integrations/cast.markdown b/source/_integrations/cast.markdown index b29197893dc..725fdfee5ce 100644 --- a/source/_integrations/cast.markdown +++ b/source/_integrations/cast.markdown @@ -76,3 +76,5 @@ If this is not possible, it's necessary to: - Enable mDNS forwarding between the subnets. - Enable source NAT to make requests from Home Assistant to the Chromecast appear to come from the same subnet as the Chromecast. + +Note that this functionality was changed in [release 109](https://www.home-assistant.io/blog/2020/04/29/release-109/) of Home Assistant, making mDNS discovery mandatory.