home-assistant.github.io/source/_components/media_player.directv.markdown
Florian Klien dd51ad0df5 fixed double 'the' (#3447)
* fixed double 'the'

mostly 's/the the /the /', little style changes where 'is' or 'to' was missing

* removed duplicate words

removed duplicate words like 'to to', 'you you' or 'account account' etc.

a batch of pizza-toasts burnt for this.
2017-09-26 20:30:04 +02:00

75 lines
2.1 KiB
Markdown
Raw Blame History

This file contains invisible Unicode characters

This file contains invisible Unicode characters that are indistinguishable to humans but may be processed differently by a computer. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

---
layout: page
title: "DirecTV"
description: "Instructions how to integrate DirecTV receivers into Home Assistant."
date: 2016-07-19 01:0+0000
sidebar: true
comments: false
sharing: true
footer: true
logo: directv.png
ha_category: Media Player
ha_release: 0.25
ha_iot_class: "Local Polling"
---
Master [DirecTV](http://www.directv.com/) receivers (ie: those that have tuners) will be automatically discovered if you enable the [discovery component](/components/discovery/) and the receiver is powered-on. Slave/RVU client/Genie boxes will also be discovered, but only if they are also online at the time of discovery.
To ensure that your DirecTV boxes are always found and configured, they should be added into your `configuration.yaml`.
```yaml
# Example configuration.yaml entry
media_player:
- platform: directv
```
Configuration variables:
- **host** (*Optional*): Use only if you don't want to scan for devices.
- **port** (*Optional*): The port your receiver is using. Defaults to `8080`.
- **name** (*Optional*): Use to give a specific name to the device.
- **device** (*Optional*): Use to specify a particular receiver in a Genie setup.
To find valid device IDs, open `http://<IP Address of Genie Server>:8080/info/getLocations` in a web browser. For each Genie slave, you will find a variable `clientAddr` in the response, and this should be used for `device` in `configuration.yaml`
For example, a response such as:
```json
{
"locations": [
{
"clientAddr": "0",
"locationName": "MASTER GENIE SERVER",
"tunerBond": true
},
{
"clientAddr": "5009591D6969",
"locationName": "SOME SLAVE GENIE"
}
],
"status": {
"code": 200,
"commandResult": 0,
"msg": "OK.",
"query": "/info/getLocations"
}
}
```
Could be formatted into `configuration.yaml` like so:
```yaml
media_player:
 - platform: directv
host: 192.168.1.10
port: 8080
name: Main DirecTV Box
device: 0
- platform: directv
host: 192.168.1.10
port: 8080
name: Bedroom DirecTV
device: 5009591D6969
```
It is important to notice that the host and port variables for slave/Genie receivers are the same as the master receiver.