From 9683029ff59e7145c555f81bc0bc77b627d93050 Mon Sep 17 00:00:00 2001
From: inputd <38230664+inputd@users.noreply.github.com>
Date: Sat, 24 Nov 2018 13:02:41 -0700
Subject: [PATCH] Update media_player.russound_rnet_markdown (#7626)

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!
---
 source/_components/media_player.russound_rnet.markdown | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/source/_components/media_player.russound_rnet.markdown b/source/_components/media_player.russound_rnet.markdown
index bd5a7ff68c0..c8bd43a1739 100644
--- a/source/_components/media_player.russound_rnet.markdown
+++ b/source/_components/media_player.russound_rnet.markdown
@@ -15,7 +15,7 @@ ha_iot_class: "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.
+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](https://github.com/pyserial/pyserial/blob/master/examples/tcp_serial_redirect.py)