From 8a442f17ff43f75adc936f0bcf7662c9582d7e51 Mon Sep 17 00:00:00 2001 From: Erik Montnemery Date: Sun, 12 Apr 2020 19:02:51 +0200 Subject: [PATCH] Update Google Cast documentation (#12859) * Update cast.markdown * Update cast.markdown * :pencil2: Tweaks Co-authored-by: Franck Nijhof --- source/_integrations/cast.markdown | 14 ++++++++++++-- 1 file changed, 12 insertions(+), 2 deletions(-) diff --git a/source/_integrations/cast.markdown b/source/_integrations/cast.markdown index 8a326f576ac..7c5abfd6bbb 100644 --- a/source/_integrations/cast.markdown +++ b/source/_integrations/cast.markdown @@ -27,7 +27,8 @@ Note that Home Assistant Cast requires your Home Assistant installation to be ac ## Advanced use -Cast devices can only be discovered if they are on the same subnet as Home Assistant. If this is not the case, you need to configure the IP address of the Cast device directly: +### Manual configuration +By default, any discovered Cast device is added to Home Assistant. This can be restricted by supplying a white list of wanted chrome casts. ```yaml # Example configuration.yaml entry @@ -43,7 +44,7 @@ media_player: type: list keys: host: - description: Use only if you don't want to scan for devices. + description: IP-address of a Cast device to add to Home Assistant. Use only if you don't want to add all available devices. The device won't be added until discovered through mDNS. required: false type: string ignore_cec: @@ -53,3 +54,12 @@ media_player: required: false type: list {% endconfiguration %} + +### Cast devices and Home Assistant on different subnets + +Cast devices can only be discovered and connected to if they are on the same subnet as Home Assistant. If this is not the case, 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. + +Setups with cast devices on a different subnet than Home Assistant are not recommended and not supported.