Which protocol you used for the connection? Which adapter you use? I try to connect the same way and I don´t get any connection. I tried everything. I use a Moxa N5210
I am using the RIO protocol. It has a much better feature-set then RNET. As such, I’m using the Russound RIO integration in HA.
I’m using an Global Cache IPSL adapter.
What protocol / integration are you using?
I tried several, but nothing seems working:
Serial seetings I tried also to adapt, right now I use that:
Probably you can help to find the right direction. I use the HA internal Russound RIO integration, with IP from the IP to RS232 device and a given port number
In SCS-C5 (for the Russound device), make sure the RS232 port is set to Protocol: RIO and Baud Rate is 19200.
Looking at the manual for your converter, I think TCP Server Mode is correct for this use case. I’d change the TCP alive check time to 99 minutes, and set the “max connection” field to the highest number. Make sure you are using the local TCP port number in the config for the Home Assistant integration.
Hmmm, strange, your recommandation is exactly what I tried…I will check again all values and try again.
Thanks a lot for your help!
1 Like
I made it 
Finally I checked everything and tried it with several settings. But I think the best idea was to remove the network cable completely from the device (MCA C5) and test different settings. Was not aware that there is an issue because of that
@heidle78 Nice! Which mode on your unit ended up being correct? Just in case others run into the same issue.
Hi @noahhusby did something changed recently in HA regarding russound ? I was getting multiple days of uptime now every couple of hours my mca5 crashes
Hi @mshrem,
Nothing has changed in the Russound integration in a few months.
I assume you are using the ethernet port directly on the Russound unit, and not an ethernet to serial adapter? For some reason, the ethernet implementation on the MCA-C3 and C5 is very unreliable.
Yeah i am using a normal ethernet cable should i change to ethernet to serial ? Which one do you recommend me to get , i can also emulate the rs232 with some docker or a raspberry if i recall i have no real knlowledge with rs232 @noahhusby thanks for your reply
Yeah, I strongly recommend a physical ethernet to serial device.
USB to RS232 with a docker container is another option, but I’d recommend having a physical converter over using Ser2Net or something like that.
iTach TCP/IP to Serial Converter is what I’m currently using and have no issues. Although I’m sure there are cheaper alternatives that can accomplish the same thing.
Only thing to note, is you will have to change the setting for the serial port on the MCA-C5 from RNET to RIO mode if it’s not set like that already.
Thanks i have ordered a USB to RS232 cable since i have the server relatevily close to the amplifier .
Can the change on the port be made via the webui ??? I do not have any russound programing software
I’m pretty sure the port can only be changed in the SCS-C5 software. It can be found online for download.
So i pulled an all nighter yesterday trying to get ser2net to work i think it reads for a few seconds then throws out an error , is your ip to serial converter dificult to set up or is it just plug and play ??? @noahhusby
My converter is pretty much plug and play.
Did you attempt to change the port type from RNET to RIO on the controller? I think they all come shipped with RNET by default so it definitely won’t work unless that is changed.
Yeah i changed to RIO however it seems that the unit is not responding to anything i throw over serial , maybe my serial cable is bad but i doubt that since i already tried 2 different cables i guess i can use your solution and see if that works or not
Did you also unplug the existing ethernet plug before using serial? If not, unplug and restart the unit.
Also obviously make sure you’ve got the baudrate correct. It is 19200 by default but can be changed for RIO.
Yeah no dice , i found someone selling a unit like yours locally for not that much , i have ordered and i expect it to be here in the end of the week , hopefully that solves it , btw i need a null modem cable or something special ??
I bought a straight-through cable for mine.