Skip to content

Minimizing of the configuration sample (Media player) #1033

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Oct 2, 2016
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions source/_components/media_player.braviatv.markdown
Original file line number Diff line number Diff line change
Expand Up @@ -10,6 +10,7 @@ footer: true
logo: bravia.png
ha_category: Media Player
ha_release: 0.23
ha_iot_class: "Local Polling"
---

The `braviatv` platform allows you to control a [Sony Bravia TV](http://www.sony.com).
Expand All @@ -23,9 +24,8 @@ To add a TV to your installation, add the following to your `configuration.yaml`
```yaml
# Example configuration.yaml entry
media_player:
platform: braviatv
host: 192.168.0.10
name: Living Room TV
- platform: braviatv
host: 192.168.0.10
```

Configuration variables:
Expand Down
5 changes: 3 additions & 2 deletions source/_components/media_player.cast.markdown
Original file line number Diff line number Diff line change
Expand Up @@ -10,6 +10,8 @@ footer: true
logo: google_cast.png
ha_category: Media Player
featured: true
ha_release: pre 0.7
ha_iot_class: "Local Polling"
---


Expand All @@ -20,8 +22,7 @@ Chromecast platform can also be forced to load by adding the following lines to
```yaml
# Example configuration.yaml entry
media_player:
platform: cast
host: 192.168.1.9
- platform: cast
```

Configuration variables:
Expand Down
20 changes: 9 additions & 11 deletions source/_components/media_player.cmus.markdown
Original file line number Diff line number Diff line change
Expand Up @@ -9,35 +9,33 @@ comments: false
sharing: true
footer: true
ha_category: Media Player
ha_iot_class: "Local Polling"
---


The `cmus` platform allows you to control a [cmus](https://cmus.github.io/) music player on a remote or local machine from Home Assistant.

To add cmus to your installation, add the following to your `configuration.yaml` file if cmus is running on a remote server:
To add cmus to your installation, add the following to your `configuration.yaml` file if running locally it will look like:

```yaml
# Example configuration.yaml entry
media_player:
platform: cmus
host: IP_ADDRESS
port: 3000
password: PASSWORD
name: Desktop Computer Music Player
- platform: cmus
```

if running locally it will look like:
if cmus is running on a remote server:

```yaml
# Example configuration.yaml entry
media_player:
platform: cmus
name: Local Music Player
- platform: cmus
host: IP_ADDRESS
password: PASSWORD
```

Configuration variables:

- **host** Hostname or IP address of the machine running cmus. Note if a remote
cmus is configured that instance must be configured to listen to remote connections, which also requires a password to be set.
- **host** (*Optional*): Hostname or IP address of the machine running cmus. Note if a remote cmus is configured that instance must be configured to listen to remote connections, which also requires a password to be set.
- **password** (*Required if host is set*): Password for your cmus player.
- **port** (*Optional*): Port of the cmus socket, defaults to 3000.
- **name** (*Optional*): The name you'd like to give the cmus player in Home Assistant
6 changes: 3 additions & 3 deletions source/_components/media_player.denon.markdown
Original file line number Diff line number Diff line change
Expand Up @@ -9,6 +9,7 @@ sharing: true
footer: true
logo: denon.png
ha_category: Media Player
ha_iot_class: "Local Polling"
---


Expand All @@ -26,9 +27,8 @@ To add a Denon Network Receiver to your installation, add the following to your
```yaml
# Example configuration.yaml entry
media_player:
platform: denon
host: IP_ADDRESS
name: Music station
- platform: denon
host: IP_ADDRESS
```
Configuration variables:

Expand Down
5 changes: 1 addition & 4 deletions source/_components/media_player.directv.markdown
Original file line number Diff line number Diff line change
Expand Up @@ -20,10 +20,7 @@ The `directv` media player platform can also be forced to load by adding the fol
```yaml
# Example configuration.yaml entry
media_player:
platform: directv
host: 192.168.1.10
port: 8080
name: DirecTV Living Room
- platform: directv
```

Configuration variables:
Expand Down
6 changes: 1 addition & 5 deletions source/_components/media_player.firetv.markdown
Original file line number Diff line number Diff line change
Expand Up @@ -38,11 +38,7 @@ To add FireTV to your installation, add the following to your `configuration.yam
```yaml
# Example configuration.yaml entry
media_player:
platform: firetv
host: localhost
port: 5556
device: livingroom-firetv
name: My Amazon Fire TV
- platform: firetv
```

Configuration variables:
Expand Down
12 changes: 6 additions & 6 deletions source/_components/media_player.gpmdp.markdown
Original file line number Diff line number Diff line change
Expand Up @@ -11,9 +11,10 @@ logo: gpmdp.png
ha_category: Media Player
ha_iot_class: "Local Polling"
ha_release: "0.20"

ha_iot_class: "Local Polling"
---


The `gpmdp` media player platform allows you to control a [GPMDP](http://www.googleplaymusicdesktopplayer.com/) instance running on a computer from Home Assistant.

You will have first have to check "Enable playback API" in GPMDP's settings and then add an inbound rule to the firewall to allow access to port 5672 on the computer running GPMDP.
Expand All @@ -23,13 +24,12 @@ Then just add the following to your `configuration.yaml` file:
```yaml
# Example configuration.yaml entry
media_player:
platform: gpmdp
host: IP_ADDRESS
name: NAME
- platform: gpmdp
host: IP_ADDRESS
```

Configuration variables:

- **host** (*Required*): IP address of the computer running GPMDP
- **name** (*Optional*): Name of the player
- **host** (*Required*): IP address of the computer running GPMDP.
- **name** (*Optional*): Name of the player.

7 changes: 3 additions & 4 deletions source/_components/media_player.itunes.markdown
Original file line number Diff line number Diff line change
Expand Up @@ -10,6 +10,7 @@ footer: true
logo: itunes.png
ha_category: Media Player
ha_release: 0.7.3
ha_iot_class: "Local Polling"
---


Expand All @@ -22,10 +23,8 @@ To add iTunes to your installation, add the following to your `configuration.yam
```yaml
# Example configuration.yaml entry
media_player:
platform: itunes
name: iTunes
host: http://192.168.1.50
port: 8181
- platform: itunes
host: http://192.168.1.50
```

Configuration variables:
Expand Down
10 changes: 3 additions & 7 deletions source/_components/media_player.kodi.markdown
Original file line number Diff line number Diff line change
Expand Up @@ -11,6 +11,7 @@ logo: kodi.png
ha_category: Media Player
featured: true
ha_release: pre 0.7
ha_iot_class: "Local Polling"
---


Expand All @@ -21,13 +22,8 @@ To add Kodi to your installation, add the following to your `configuration.yaml`
```yaml
# Example configuration.yaml entry
media_player:
platform: kodi
host: http://192.168.0.123
port: 8080
name: Kodi
username: USERNAME
password: PASSWORD
turn_off_action: shutdown
- platform: kodi
host: http://192.168.0.123
```

Configuration variables:
Expand Down
7 changes: 3 additions & 4 deletions source/_components/media_player.lg_netcast.markdown
Original file line number Diff line number Diff line change
Expand Up @@ -11,6 +11,7 @@ logo: lg.png
ha_category: Media Player
ha_iot_class: "Local Poll"
ha_release: "0.20"
ha_iot_class: "Local Polling"
---

The `lg_netcast` platform allows you to control a LG Smart TV running NetCast 3.0 (LG Smart TV models released in 2012) and NetCast 4.0 (LG Smart TV models released in 2013). For the new LG WebOS TV's use the [webostv](/components/media_player.webostv) platform.
Expand All @@ -20,10 +21,8 @@ To add a LG TV to your installation, add the following to your `configuration.ya
```yaml
# Example configuration.yaml entry
media_player:
platform: lg_netcast
host: 192.168.0.20
access_token: 889955
name: Living Room TV
- platform: lg_netcast
host: 192.168.0.20
```

Configuration variables:
Expand Down
7 changes: 3 additions & 4 deletions source/_components/media_player.mpchc.markdown
Original file line number Diff line number Diff line change
Expand Up @@ -11,6 +11,7 @@ logo: mpchc.png
ha_category: Media Player
featured: false
ha_release: 0.25
ha_iot_class: "Local Polling"
---


Expand All @@ -33,10 +34,8 @@ To add MPC-HC to your installation, add the following to your `configuration.yam
```yaml
# Example configuration.yaml entry
media_player:
platform: mpchc
host: http://192.168.0.123
port: 13579
name: MPC-HC
- platform: mpchc
host: http://192.168.0.123
```

Configuration variables:
Expand Down
8 changes: 3 additions & 5 deletions source/_components/media_player.mpd.markdown
Original file line number Diff line number Diff line change
Expand Up @@ -10,6 +10,7 @@ footer: true
logo: mpd.png
ha_category: Media Player
ha_release: pre 0.7
ha_iot_class: "Local Polling"
---


Expand All @@ -20,11 +21,8 @@ To add MPD to your installation, add the following to your `configuration.yaml`
```yaml
# Example configuration.yaml entry
media_player:
platform: mpd
host: IP_ADDRESS
port: 6600
location: bedroom
password: PASSWORD
- platform: mpd
host: IP_ADDRESS
```

Configuration variables:
Expand Down
21 changes: 11 additions & 10 deletions source/_components/media_player.onkyo.markdown
Original file line number Diff line number Diff line change
Expand Up @@ -10,6 +10,7 @@ footer: true
logo: onkyo.png
ha_category: Media Player
ha_release: 0.17
ha_iot_class: "Local Polling"
---


Expand All @@ -20,21 +21,21 @@ To add an Onkyo receiver to your installation, add the following to your `config
```yaml
# Example configuration.yaml entry
media_player:
platform: onkyo
host: 192.168.1.2
name: receiver
sources:
pc: 'HTPC'
aux1: 'Chromecast'
bd: 'Bluray'
game: 'Wii U'
- platform: onkyo
host: 192.168.1.2
name: receiver
sources:
pc: 'HTPC'
```

Configuration variables:
- **host** (*Optional*): IP address of the device. Example:`192.168.1.2` If not specified, the platform will load any discovered receivers.
- **name** (*Required if host is specified*): Name of the device

- **host** (*Optional*): IP address of the device. Example:`192.168.1.2`. If not specified, the platform will load any discovered receivers.
- **name** (*Required if host is specified*): Name of the device.
- **sources** (*Optional*): A list of mappings from source to source name. Valid sources can be found below. A default list will be used if no source mapping is specified.

List of source names:

- video1
- video2
- video3
Expand Down
11 changes: 5 additions & 6 deletions source/_components/media_player.panasonic_viera.markdown
Original file line number Diff line number Diff line change
Expand Up @@ -11,6 +11,7 @@ logo: panasonic.png
ha_category: Media Player
featured: false
ha_release: 0.17
ha_iot_class: "Local Polling"
---

The `panasonic_viera` platform allows you to control a Panasonic Viera TV.
Expand All @@ -27,14 +28,12 @@ To add a TV to your installation, add the following to your `configuration.yaml`
```yaml
# Example configuration.yaml entry
media_player:
platform: panasonic_viera
host: 192.168.0.10
port: 55000
name: Living Room TV
- platform: panasonic_viera
host: 192.168.0.10
```

Configuration variables:

- **host** (*Required*): The IP of the Panasonic Viera TV, e.g. `192.168.0.10`
- **port** (*Optional*): The port of your Panasonic Viera TV. Defaults to `55000`
- **host** (*Required*): The IP of the Panasonic Viera TV, e.g. `192.168.0.10`.
- **port** (*Optional*): The port of your Panasonic Viera TV. Defaults to `55000`.
- **name** (*Optional*): The name you would like to give to the Panasonic Viera TV.
3 changes: 2 additions & 1 deletion source/_components/media_player.pandora.markdown
Original file line number Diff line number Diff line change
Expand Up @@ -11,6 +11,7 @@ logo: pandora.png
ha_category: Media Player
featured: false
ha_release: 0.22
ha_iot_class: "Local Polling"
---

If you have a Pandora account, you can control it from Home Assistant with this media player.
Expand Down Expand Up @@ -51,7 +52,7 @@ The Pandora player can be loaded by adding the following lines to your `configur
```yaml
# Example configuration.yaml entry
media_player:
platform: pandora
- platform: pandora
```

That's it! Now you will find a media player. If you click it you will find all your stations listed as different sources. If you switch to one, the station will begin playing.
Expand Down
6 changes: 3 additions & 3 deletions source/_components/media_player.pioneer.markdown
Original file line number Diff line number Diff line change
Expand Up @@ -11,6 +11,7 @@ logo: pioneer.png
ha_category: Media Player
featured: false
ha_release: 0.19
ha_iot_class: "Local Polling"
---

The `pioneer` platform allows you to control Pioneer Network Receivers.
Expand All @@ -20,9 +21,8 @@ To add a Pioneer receiver to your installation, add the following to your `confi
```yaml
# Example configuration.yaml entry
media_player:
platform: pioneer
host: 192.168.0.10
name: Living receiver
- platform: pioneer
host: 192.168.0.10
```

Configuration variables:
Expand Down
3 changes: 2 additions & 1 deletion source/_components/media_player.plex.markdown
Original file line number Diff line number Diff line change
Expand Up @@ -11,6 +11,7 @@ logo: plex.png
ha_category: Media Player
featured: true
ha_release: 0.7.4
ha_iot_class: "Local Polling"
---


Expand All @@ -33,7 +34,7 @@ If you want to enable the plex platform directly, add the following lines to you
```yaml
# Example configuration.yaml entry
media_player:
platform: plex
- platform: plex
```

In case [discovery](/components/discovery/) does not work (GDM disabled or non-local plex server), you can create `~/.homeassistant/plex.conf` manually.
Expand Down
Loading