jeans/home-assistant.io
jeans/home-assistant.io
1
0
Fork 0
mirror of https://github.com/home-assistant/home-assistant.io.git synced 2025-07-19 07:17:14 +00:00
Code Issues Packages Projects Releases Wiki Activity

added option example (#4326)

Browse Source 
* added option example

it wasn't clear to me.

* Add example
This commit is contained in:
Carlo Costanzo 2018-01-11 15:09:09 -05:00 committed by Franck Nijhof
parent cff420f074
commit 5da39427c5
1 changed files with 13 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
source/_components/media_player.cast.markdown
View File

@ -17,7 +17,7 @@ ha_iot_class: "Local Polling"
Google Cast devices like Android TVs and Chromecasts will be automatically discovered if you enable [the discovery component]({{site_root}}/components/discovery/). There is a issue where Chromecasts can only be discovered if your device is connected to the same subnet as your Chromecast.
Chromecast platform can also be forced to load by adding the following lines to your `configuration.yaml`:
The Chromecast platform can also be forced to load by adding the following lines to your `configuration.yaml`:
```yaml
# Example configuration.yaml entry
@ -28,4 +28,15 @@ media_player:
Configuration variables:
- **host** (*Optional*): Use only if you don't want to scan for devices.
- **ignore_cec** (*Optional*) A list of chromecasts that should ignore CEC data for determining the active input. [See the upstream documentation for more information.](https://github.com/balloob/pychromecast#ignoring-cec-data)
- **ignore_cec** (*Optional*) A list of Chromecasts that should ignore CEC data for determining the active input. [See the upstream documentation for more information.](https://github.com/balloob/pychromecast#ignoring-cec-data)
## {% linkable_title Example %}
By setting `host:` you can specify the Chromecast to use.
```yaml
# Example configuration.yaml entry
media_player:
- platform: cast
host: 192.168.1.10
```