Skip to content

Commit

Permalink
Update Google Cast docs (home-assistant#17549)
Browse files Browse the repository at this point in the history
Co-authored-by: Franck Nijhof <[email protected]>
  • Loading branch information
emontnemery and frenck authored Apr 22, 2021
1 parent e2d58e3 commit 346ab81
Showing 1 changed file with 12 additions and 4 deletions.
16 changes: 12 additions & 4 deletions source/_integrations/cast.markdown
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down

0 comments on commit 346ab81

Please sign in to comment.