Update Google Cast docs (#17549)

Co-authored-by: Franck Nijhof <git@frenck.dev>
This commit is contained in:
Erik Montnemery 2021-04-22 15:35:22 +02:00 committed by GitHub
parent e2d58e3dae
commit 346ab81569
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -182,11 +182,19 @@ data:
- url: "https://tilos.hu/images/kockalogo.png"
```
## Cast devices and Home Assistant on different subnets
## Troubleshooting automatic discovery
Cast devices can only be automatically discovered if they are on the same subnet as Home Assistant.
Setups with cast devices on a different subnet than Home Assistant are not recommended and not supported.
If this is not possible, it's necessary to either enable mDNS forwarding between the subnets or to provide a list of known hosts.
mDNS relies on UDP multicast, which may fail for various reasons. If none of the tips in this section helps, the recommended solution is to ensure all cast devices have static IPs assigned to them and configure a list of known hosts.
### Zeroconf configuration
The Google Cast integration relies on the [Zeroconf integration](/integrations/zeroconf) for mDNS discovery. The Zeroconf integration has some configuration options which impact mDNS routing.
### Cast devices and Home Assistant on different subnets
Cast devices can only be automatically discovered if they are on the same subnet as Home Assistant because mDNS packets are not routed across subnets.
Automatic discovery in setups with cast devices on a different subnet than Home Assistant is not recommended and not supported.
If it is not possible, it's necessary to either enable mDNS forwarding between the subnets or to configure a list of known hosts.
### Home Assistant Container