From 690a74ebfc5cea18411559d343365dfad0c34853 Mon Sep 17 00:00:00 2001 From: Darren Foo Date: Wed, 19 Jul 2023 00:29:53 -0700 Subject: [PATCH] update russound rnet for mutiple controllers (#28244) --- source/_integrations/russound_rnet.markdown | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/source/_integrations/russound_rnet.markdown b/source/_integrations/russound_rnet.markdown index 71ba849a4cc..85031cab5ae 100644 --- a/source/_integrations/russound_rnet.markdown +++ b/source/_integrations/russound_rnet.markdown @@ -13,7 +13,7 @@ ha_integration_type: integration 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. +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. If you have mutiple controllers connected via the RNET link ports, every increment of 6 zones maps to the corresponding controller ID. 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) @@ -39,6 +39,9 @@ media_player: name: Dining Room 6: name: Guest Bedroom + # controller 2 - zone 1 (connected via RNET link ports) + 7: + name: Basement Recroom sources: - name: Sonos - name: Sky+