I updated to 2.3.9.193. Began having frequent Telnet connection failures. Reverted back to 2.3.8.139. Now no obvious issues and Telnet stays connected as expected.
Telnet to what?
1 Like
It's jacked, but I use the IP2IR telnet (Bryan Turcotte (@bptworld)) device driver to my Russound AV so that I can control the Russound with telnet commands.
Reboot everything?????
I did that yesterday. I have a webcore piston that monitors the telnet connection and reboots the Russound if re-initializing the telnet connection fails x 3. My system was in a reboot cycle yesterday and I had to shut it down. Powered back up this morning with the same problem. I reverted back to 2.3.8.139. No looping now. Not sure what the cause is. Just thought I would mention that this problem began after the most recent HE platform update.
3 Likes
I'm confused, you're using a global cache IP2IR device with hubitat connected over telnet to the Global Cache device, and the Global Cache IP2IR controls the Russound device over IR?
And you're saying you need to reboot the Russound unit?
Sorry, a little more info may be helpful. My Russound can be controlled by the iTach IP2IR Hubitat driver. I figured out that HE/webcore can use that driver to directly send telnet commands to my Russound and control it. No IR is involved. I use webcore to send those telnet commands. For some reason, the telnet connection would only stay active if commands were being sent. If that connection sat "idle" for > 1 hour, it would disconnect from my Russound. So, I have been sending a "mute" command to the Russound every hour. That has worked well to keep the telnet active. On occasion, I would have to reboot the Russound, maybe once a week or so, when the telnet connection became "disconnected." I have a webcore piston that monitors that connection. And when it becomes "disconnected", it reboots the Russound and checks the connection again. That has been working relatively well. But after the Update to 2.3.9.193 or maybe a little earlier, rebooting the Russound would not reconnect the telnet, forcing me to reboot HE. And that worked. But lately I have to reboot HE every day, sometimes more than once a day, because the telnet becomes "disconnected." I'm not sure if this problem is from the update, my ancient, failing Russound, my coding, or some combination all all of that. But the WAF has greatly decayed. I hope this helps.
So the Russound has an ethernet port and supports Telnet directly?, if so what's the point of the iTach connecting to Hubitat via telnet, and the iTach connecting via telnet to the Russound?
Yes. Networking and communication protocols are not my strong point. I struggled for quite some time to get Hubitat to communicate with my Russound. I could not figure it out. A few years ago, a user here recommended the IP2IR. And with lots of trial and error, I was able to get Hubitat to communicate with the Russound. This is from the my Russound MCA-C5 manual....
This document provides a description of a new protocol intended to ease integration of 3rd party devices and software with Russound C-Series and E-Series systems. We refer to this new feature as Russound I/O, or RIO. RIO is a new text-based command set that improves upon our 3rd Party Integration Support, making it easier to develop UI devices and applications that require Russound system integration and control.
Here is a summary of the services provided by this new command set:
• Serves as a superset of the existing RNet protocol capability
• Full 2-way communication capability
• The RIO Command Set is available as ASCII text via IP (using port 9621) and RS232
interfaces. Up to 8 simultaneous IP connections is supported for C-Series and E-Series
systems.
• Adjustable RS232 baud rates (choose between 19200, 38400, 57600 and 115200) and
protocol (choose between RNet and RIO), configured via SCS-C5
If it is possible to control my Russound without the IP2IR, then I would welcome it. That driver may be a source of the difficulties that I am having. The IP2IR allowed me to send text commands (RIO) via ethernet to my Russound. Can that be accomplished without IP2IR?
Do you have a link to the actual documentation file?, if so I might be able to write a dedicated built in driver for this device
1 Like
I just wanted to chime in on this topic. I have two Russound MCA-88s and an MBX-PRE. I've been revisiting the forums hoping for some activity around a Russound driver for a few years.
I'd be willing to donate to the developer of this driver and offer any other support I could.
In case you didn't find it, the link to the documentation is:
https://www.russound.com/component/edocman/rio-protocol-version-1-16-01/download
Just be a little patient it’s coming…
2 Likes
Ha. I came across this after my post. Good luck, @mike.maxwell !
I have been writing Russound RIO code for my MCA-C5 for years. However, I do not know how to write drivers. @mike.maxwell has been gracious enough to write the Russound driver for me. He and I have been working on it for weeks now. Initial testing on the Rusound MCA-C5 has been fantastic. My C5 has since died and I should get the MCA-66 tomorrow and will start testing the driver. I suspect Mike's driver will need a little adjustment to work with the MCA-66. But if my intuition is correct, the driver will work with the MCA-66 and your MCA-88 with little or no modification since all of them use RIO. I will post more info over the next few weeks after testing. One thing that we have noticed is that the serial connection to the Russound appears to function better than the ethernet connection for control. So you may want to look at the following. I have been using this setup with good results.
Global Caché iTach Flex IP
Instantly Enables IP Control For Any Electronic DeviceThe Global Caché iTach Flex IP instantly enables IP control for electronic devices, allowing you to automate almost any device, system, or protocol. Remotely control the connected device using an...
PRICE: $98.96 USD
and
Global Caché Flex Link Serial Cable (RS232)
DetailsFor Use With The iTach FlexThe Global Caché Flex Link Serial Cable (RS232) connects to your iTach Flex Module via the 3.5mm jack to enable IP/WiFi control for RS232 serial components. Designed as a total RS232 solution, the cable automatically...
PRICE: $24.95 USD
3 Likes
The driver for the Russound units is included in platform 2.4.0
We are nearing release for this, however if you can’t wait you could join the beta and play around with prior to that if you like.
3 Likes
Thank you for the reply and for giving some insight into all of the movement that is happening behind the scenes. I’m excited to see a first iteration of a driver and would be happy to participate and provide feedback in the testing on MCA-88(s) and/or the MBX-PRE.
As for the serial control versus IP control, I wish I could give better news but I’m not completely surprised by your findings. I have several IPK-1 keypads scattered across my house. I will say that, over the years, Russound has pushed out updates that have seemed to make them more reliable. However, even to this day, about half the time I go to use the keypads, I get frustrated by the slow/lack of response and end up pulling out my phone and using the Russound App. In the app, I can at least see what’s going – navigate directly to a source rather than cycle through several sources, directly input a volume increase from 20 to 60 rather than push the Volume Up button 40 times, etc.
…As I’ve been typing this @mike.maxwell has replied. I will take a look and go from there.
1 Like
