
I have a Russound CAA66. This component also works to control it. Important note: While the CAV6.6 uses a straight through cable, the CAA66 uses a null-modem cable!
1.8 KiB
layout, title, description, date, sidebar, comments, sharing, footer, logo, ha_category, ha_release, ha_iot_class
layout | title | description | date | sidebar | comments | sharing | footer | logo | ha_category | ha_release | ha_iot_class |
---|---|---|---|---|---|---|---|---|---|---|---|
page | Russound RNET | Instructions on how to integrate Russound RNET devices into Home Assistant. | 2016-07-21 22:00 | true | false | true | true | russound.png | Media Player | 0.25 | Local Polling |
The russound_rnet
platform allows you to control Russound devices that make use of the RNET protocol.
This has initially been tested against a Russound CAV6.6 unit with six zones and six sources. It will also work with a Russound CAA66, but be sure to use a null-modem cable.
Connecting to the Russound device is only possible by TCP, you can make use of a TCP to Serial gateway such as tcp_serial_redirect
To add a device to your installation, add the following to your configuration.yaml
file:
# Example configuration.yaml entry
media_player:
- platform: russound_rnet
host: 192.168.1.10
port: 1337
name: Russound
zones:
1:
name: Main Bedroom
2:
name: Living Room
3:
name: Kitchen
4:
name: Bathroom
5:
name: Dining Room
6:
name: Guest Bedroom
sources:
- name: Sonos
- name: Sky+
{% configuration %} host: description: The IP of the TCP gateway. required: true type: string port: description: The port of the TCP gateway. required: true type: integer name: description: The name of the device. required: true type: string zones: description: This is the list of zones available. required: true type: integer sources: description: The list of sources available, these must be in order as they are connected to the device. required: true type: list {% endconfiguration %}