The Vera Community forums have moved!

General => AV Control => Topic started by: kabdalla on July 27, 2013, 01:25:48 pm

Title: Russound RNET Plugin v1.4
Post by: kabdalla on July 27, 2013, 01:25:48 pm
v1.4
Changes in this version:

1) Changed implementation to utilize more standard SwitchPower and RenderingControl services.

I've attached the relevant files here to be used until the plugin is approved in the App Store.  The only things missing are the icon images which are unchanged from the previous version.



v1.2
Changes in this version:

1) Support for C-series controllers (MCA-C5, MCA-C3)*.

2) Changed incoming message parsing to allow for variable lengths.


* A known issue with "grouped" zones on C-series controllers exists that will lock up the controller if sources are changes rapidly.  Russound is working on this issue.



v1.1
Changes in this version:

1) RNET commands have been updated to the latest version.  Per Russound, these should work with all CA-series and C-series controllers, as long as they are on the latest firmware.  There has been a report of issues with the "Source" buttons on a C-series controller but I'm unsure of the version of firmware that controller was running.  Any feedback from C-series controller users would be appreciated.

2) Mute toggle button added.

3) Additional controller messages parsed for "Display" window.

4) Status feedback parsing revamped with explicit status requests no longer being needed.

5) New icon for audio zones.



v1.0
Intro
This plugin was created for personal use but I wanted to share with the community as I know this has been requested a number of times.  I'm not a developer but with the help of a few people on this forum, I was able to put this together.  Below are some key bits of information for installation and use.


Devices
The only controller that I can say with certainty that this will work with is the CAM6.6(T) as that is what I have.  The "set" and "get" codes were retrieved from a Russound RNET protocol document that states support for the CAM, CAV, CAA, and CAS series controllers, so my assumption is it will work with those, as well.  As for any other controller, my fingers are crossed but I can't promise anything.  I've asked big517 to do some testing on an MCA controller and it doesn't appear to work properly.  If I can get a complete protocol document for the MCA implementation of RNET, I'll happily put together an I_RNET.xml file for those controllers.


Connectivity
This plugin only works with serially-connected Russound controllers.  I am personally using a FTDI-chipped serial/USB adapter on the back of the Russound controller with a USB extension cable connected to the Vera and it worked right out of the box.  Search for "Serial Device Compatibility" and you'll find a page that talks about these devices.  In UI5, the serial port configuration is set in "Apps" > "Develop Apps" > "Serial Port configuration".  The settings you will need for communication to the Russound controller are:

Baud: 19200
Parity: none
Data bits: 8
Stop bits: 1


Installation
During the plugin installation process, you'll see a message scrolling in the message window asking you to choose the serial port.  In a new window you need to go to the same "Serial Port configuration" page and in the "Used by device" drop-down menu, select the RNET Controller.  It will complete the process by installing the parent "Controller" device, as well as two child "Zone" devices by default.  To add (or remove) zones, go to the parent device's "Advanced" tab, scroll down to the "ZoneIds" variable, and enter or remove the Russound zones you want to control through Vera.  Zones are separated by commas with no spaces.


Use
This should be relatively straight forward as it should mimic the use of a keypad.  A few potential issues here:

1) I was hoping to use a slider for the volume control but the Vera slider will only allow changes in 10% increments.  This isn't granular enough for me so I went with volume up/down buttons.  If the granularity of this changes in the future, I'll likely change this to a slider.

2) In the "Control" tab of each zone is a Source Display.  This will display a broadcast from an RNET-compatible source to each zone that is set to that source.  The protocol document I used stated this would be a 42 byte long status but I found this to actually be 39 bytes long on the tuner module of my CAM6.6.  I don't currently have any other RNET-compatible sources so I can't test if this changes by source.  If anyone out there has an iPod dock and/or SMS3 and it's not displaying the information you get on your keypad, let me know and I'll have you run a couple of tests to figure out the byte length.

3) This may be specific to the tuner module I have but both the "Play" and "Pause" buttons also function as mute...independently.  If you mute with one and unmute with the other, the Source Display will still show Muted/Unmuted.  I can't think of a way to address this so just know that if you do this, you'll have to click each of "Play" and "Pause" again to clear the display.  This must have been an old issue from an old build, the uploaded version does not have this problem.  "Play" changes band, "Pause" mutes/unmutes, "Stop" seeks.

4) I have not figured out how I want to deploy Party Mode on this yet.  Once I figure it out, I'll upload a new version of the plugin.


Well that is all I have for now.  Please feel free to share any feedback and I'll do my best to address issues with the limited resources/knowledge that I have in plugin development.
Title: Re: Russound RNET Plugin
Post by: S-F on July 27, 2013, 06:46:25 pm
I can't thank you enough for this! My CAA66 is on its way. I still need to get a serial to USB adapter.  I'll tackle that one this weekend. Hopefully by next weekend I'll be able to give you some input!

BTW, where is this plugin?

For future reference here's the MCV wiki page on serial devices: http://wiki.micasaverde.com/index.php/Serial_Supported_Hardware

Here's the one I ordered from Amazon: http://www.amazon.com/gp/product/B006PIU2KO/ref=ox_sc_act_title_1?ie=UTF8&psc=1&smid=A96BHCEI0V7QU

Hope it works.
Title: Re: Russound RNET Plugin
Post by: kabdalla on July 27, 2013, 08:08:26 pm
The plugin has been Pending Approval all day.  Not sure if they don't review on the weekends or what the holdup is.  It should appear as soon as it is approved.
Title: Re: Russound RNET Plugin
Post by: garrettwp on July 27, 2013, 10:05:22 pm
They are not open on the weekends. You'll have to wait until some time this week.

- Garrett

Title: Re: Russound RNET Plugin
Post by: big517 on July 28, 2013, 08:17:12 am
Can you post the plugin files in the meantime?

Thanks!
Title: Re: Russound RNET Plugin
Post by: kabdalla on July 28, 2013, 09:19:20 am
Sure, here are the files.  D_RNET is the parent device file.
Title: Re: Russound RNET Plugin
Post by: S-F on July 30, 2013, 09:38:12 am
@ big517

How's it working for you?
Title: Re: Russound RNET Plugin
Post by: big517 on July 30, 2013, 12:24:44 pm
It works, but not 100% because I have the newer units and some RNET functionality has changed.  I found this out when using my ELK to control the unit.
What works for MCA-C5:
I have communications with the zones, seems to work with Volume up and down.  I did have a strange issue when I chose a Source for one of the zones, it turned all the linked zones on and off every few seconds This is probably an incompatibility with my MCA-C5 system as there are other features on this such as zone source sharing and linking that are causing the problem.  I don't believe this will be an issue w/ your system.

I've disabled it in the meantime because of the traffic it produces, but it looks clean, child devices were created as expected and is pretty impressive.
Title: Re: Russound RNET Plugin
Post by: kabdalla on July 30, 2013, 02:05:42 pm
That's disappointing.  I actually added zones 7 and 8 for you and others with the MCA-C5.  I haven't been able to find the RNET protocol document for the MCA devices, as generating different commands based on the model wouldn't be that big of a task.  If you find it, let me know.

Also found out that the new RIO protocol operates over IP or RS232.  If you find that command structure, I'd be curious to look at it.  If it's not completely different, I might be able to adapt the plugin and create a new one for RIO and have you do the testing.  Let me know.  Wow, just found the RIO protocol document and it is completely different.  Would take a fresh rewrite and debugging/testing.  My offer still stands on the MCA RNET command inclusion if you can find that document, though.
Title: Re: Russound RNET Plugin
Post by: DanielMason on July 30, 2013, 04:18:08 pm
This is amazing! Thank You.

Any way to make it run with a serial to ip? Like the wiznet.

Cheers
Title: Re: Russound RNET Plugin
Post by: kabdalla on July 30, 2013, 04:44:43 pm
Unfortunately I know nothing about how those devices receive commands and I don't have one to test with.  Someone else on here may be able to help modify my plugin to support that.
Title: Re: Russound RNET Plugin
Post by: big517 on July 30, 2013, 06:06:35 pm
I think the most updated RNET info is in that Box link I posted above, can you cross reference the "all on" and "all off" codes?

Out of curiousity does that RIO protocol make sense?  So the plugin can "listen" and russound reports changes and keypad presses...  Is there even capability to support that?
Title: Re: Russound RNET Plugin
Post by: kabdalla on July 30, 2013, 07:14:09 pm
It may be my advancing age but I don't see a link anywhere above.

I didn't delve much into the RIO protocol, I'm sure it would make sense if I took the time to understand it.  The problem is the syntax, structure, everything about it is different.  I wouldn't think adapting this plugin would be the way to go for RIO, instead I would think it would be easier for someone to start from scratch on it.  If someone wants to donate an MCA box, I'm happy to do it!! :-)

With RNET, the controller doesn't send out status (other than connectivity) unless it is queried.  I could have saved a lot of lines of code if RNET replied to a change of state/source/volume or periodically broadcast status.  Does it broadcast this information on its own with RIO?

And if you're asking if I could include a RIO "listener" in this plugin, I'm not sure it would help you as I believe you have to choose between RNET or RIO protocol on your controller.  So if you set it to send RIO, you wouldn't be able to control with RNET.
Title: Re: Russound RNET Plugin
Post by: big517 on July 30, 2013, 08:26:51 pm
Yes,
Rio broadcasts everything, I watched it with a TCP socket program on my Android phone, pretty cool actually.  The syntax is pretty easy, and I get how it works, I lack the ability to write the plugins however.
Here is the Box link that I posted in the other thread
https://app.box.com/s/eoujz8t4d230ocwt4zzd (https://app.box.com/s/eoujz8t4d230ocwt4zzd)

Regarding RIO;
I've wrtten 1-liners to manipulate the system with my ELK.
For Every MCA system you have they will be assigned a controller number.  I only have 1 MCA-C5, i'm sure most folks are the same, but it's like this;

If I wanted to tell my 1st MCA system to turn Zone 4 on, this is the text I send;
"EVENT C[1].Z[4]!ZoneOn"
i'm sure you can see the variables and how that works.
For anyone referencing ELK M1 Gold, the "text" is; "00AP4EVENT C[1].Z[4]!ZoneOn^M^J" ; see my sticky in the ELK Plugin forum for setting up TCP

other examples, you can probably guess at what they do
EVENT C[1].Z[3]!ZoneOn
EVENT C[1].Z[3]!ZoneOff
EVENT C[1].Z[5]!KeyPress Mute
EVENT C[1].Z[5]!KeyPress VolumeDown

You see how it works?  Almost plain text control.

Now i've brought that BOX link I uploaded with all the RS232 and RIO docs that was given to me by Russound rep, it may help.
Title: Re: Russound RNET Plugin
Post by: kabdalla on July 30, 2013, 09:06:48 pm
Well RIO is much more straight forward but I'm going to leave that to someone else to play around with.

Looking at the latest RNET document in that batch, I'm surprised that my plugin works with the MCA at all.  If you're interested, I can put together a new I_RNET file for you using this syntax and send it to you sometime this week to test.  What the updated doc doesn't detail, though, is the structure of the responses when queried for status.  If you're not getting correct status back on the Vera tiles or Control tab, I'll need to you provide a copy of your log for each command so I can see what is being returned.
Title: Re: Russound RNET Plugin
Post by: kabdalla on July 30, 2013, 11:57:33 pm
Give this I_RNET.xml file a shot for the MCA devices.  I essentially guessed at the structure for the request status command and left the parsing of the reply from the controller as is since neither of those commands are listed in the MCA doc.
Title: Re: Russound RNET Plugin
Post by: big517 on July 31, 2013, 08:52:04 am
Sure, i'll gladly give it another run! 
Are you noticing a lot of differences from the RNET doc I sent?  Were you working off an older doc originally?


UPDATE:

All Off worked.
Specific Zone ON did not seem to work, but making a volume adjust does, and will turn the zone on.

Too early to test extensively without waking up the baby ;)

Noticed this FULL BUFFER message in the log;
Code: [Select]
luup_log:596: Received full buffer from controller via serial F0 01 00 70 00 00 7F 00 00 04 02 00 00 07 00 00 01 00 0C 00 00 02 11 0A 0E 01 0A 00 01 00 00 00 51 F7 <0x2faa4680>
50 07/31/13 9:08:19.389 luup_log:596: Received full buffer from controller via serial F0 01 00 70 00 00 7F 00 00 04 02 00 00 07 00 00 01 00 0C 00 00 02 11 0A 0E 01 0A 00 01 00 00 00 51 F7 <0x2faa4680>
50 07/31/13 9:08:20.440 luup_log:596: Received full buffer from controller via serial F0 01 00 70 00 00 7F 00 00 04 02 00 00 07 00 00 01 00 0C 00 00 02 11 0A 0E 01 0A 00 01 00 00 00 51 F7 <0x2faa4680>
50 07/31/13 9:08:21.598 luup_log:596: Received full buffer from controller via serial F0 02 00 70 00 00 7F 00 00 04 02 00 00 07 00 00 01 00 0C 00 00 02 11 0A 0E 01 0A 00 01 00 00 00 52 F7 <0x2faa4680>
50 07/31/13 9:08:22.597 luup_log:596: Received full buffer from controller via serial F0 02 00 70 00 00 7F 00 00 04 02 00 00 07 00 00 01 00 0C 00 00 02 11 0A 0E 01 0A 00 01 00 00 00 52 F7 <0x2faa4680>
50 07/31/13 9:08:23.101 luup_log:596: Request returned in 0ms <0x2e663680>
50 07/31/13 9:08:23.102 luup_log:596: Request returned in 0ms <0x2e663680>
50 07/31/13 9:08:23.103 luup_log:596: Request returned in 0ms <0x2e663680>
50 07/31/13 9:08:23.192 luup_log:596: Received full buffer from controller via serial F0 00 01 71 00 00 7F 00 00 04 02 00 00 06 00 00 01 00 01 00 00 04 F7 <0x2faa4680>

Title: Re: Russound RNET Plugin
Post by: big517 on July 31, 2013, 09:39:39 am
Pause Play Stop work as well.

Source Selection does NOT work with the exception of Source1 (RADIO). 
Title: Re: Russound RNET Plugin
Post by: kabdalla on July 31, 2013, 10:09:13 am
That's what I get for trying this so late last night.  This should fix zone power and source.  Let me know how it handles the status (is the correct power on/off button staying lit? does the correct zone button stay lit?)

And to answer your questions, there are two sets of the RNET implementation for controllers apparently, one for CA-series (CAM, CAV, CAA, CAS) which is what my plugin supports, and another set for C-Series (MCA).  The biggest difference is the location of the byte which specifies which zone you're sending the command for.  And what I missed in the first MCA-specific file I sent you yesterday, is for zone power and source there are two bytes in the string that specify it, I only caught one (which is what the CA-series implementation uses).

The gaps in the MCA RNET protocol document is there is no description of what string to send for status request, and no description of what the controller should return.  On the files I'm sending you, I'm just guessing on those based on the structure of the commands they do detail.
Title: Re: Russound RNET Plugin
Post by: S-F on July 31, 2013, 10:27:37 am
The suspense is killing me! My CAA66 came yesterday and it's DOA! 
Title: Re: Russound RNET Plugin
Post by: big517 on July 31, 2013, 10:33:14 am
Trying Now.

@S-F  that sucks!!!   Did you buy it off eBay, or new?
Title: Re: Russound RNET Plugin
Post by: big517 on July 31, 2013, 10:52:14 am
POWER ON/OFF Works from within the device, but not on the front page for some reason.

Still a problem with Source Selection.  Can only choose Radio, and then everything locks up.  Have to delete plugin again.

Also want to note it's constantly polling the device, and choking the system.  Take a look at system log.
Maybe reduce the polling to every 2 minutes, or have an option to not poll automatically

Code: [Select]
Mem Available85912kilo bytes
CPU Load (1 minute)1.34
CPU Load (5 minute)1.09
CPU Load (15 minute)0.82
Title: Re: Russound RNET Plugin
Post by: kabdalla on July 31, 2013, 11:14:57 am
@S-F: That does suck, sorry to hear that.

@big517:
That is really strange since those two power buttons map to the exact same action...there should be no difference between them at all.

As for the CPU issues, my guess is what the plugin is sending to the controller requesting status is what is causing the CPU issue as my CPU doesn't get below 80% idle (0.11 0.20 0.22).  It's probably completely wrong for that implementation of RNET and it's processing a bunch of junk coming back.  You can likely alleviate that issue by commenting out all the status request commands but then, obviously, you'll get no status.  If you can find the proper commands and responses for that implementation of RNET (or ask Russound for them), I'm happy to make the change.

I'm baffled by the source issues.  Only thing I can think of here is that this implementation now has two controller bytes, one for "controller" and one for "source controller".  This isn't the case in the CA-series implementation (only one controller byte) and there is no description I can find for what "source controller" is.  If you ping Russound support, ask for these descriptions, too.
Title: Re: Russound RNET Plugin
Post by: big517 on July 31, 2013, 11:28:49 am
Was that information not contained in one of the documents I posted?  Maybe in the Zip file?
Title: Re: Russound RNET Plugin
Post by: kabdalla on July 31, 2013, 11:40:40 am
It isn't included for the C-series implementation of RNET.  The two documents that reference it are:

Russound_Controllers_Protocol_v1_00_04.pdf
Reading RNET V1_00_03.pdf

Both of which apply to the CA-series implementation (and what I used to develop my plugin).  The C-series implementation appears to be RNET V1_00_07 based on that command document provided here (Russound RS232 hex codes v1_00_7.pdf).

If you can get a Russound_Controllers_Protocol_v1_00_07.pdf document, that is what I need.
Title: Re: Russound RNET Plugin
Post by: big517 on July 31, 2013, 12:35:08 pm
Reaching out to Russound now.
Title: Re: Russound RNET Plugin
Post by: legend99 on July 31, 2013, 03:51:38 pm
Thanks Kabdalla!   ;D
Title: Re: Russound RNET Plugin
Post by: big517 on July 31, 2013, 04:18:10 pm
UPDATED DOCS!

https://app.box.com/s/eoujz8t4d230ocwt4zzd

Title: Re: Russound RNET Plugin
Post by: kabdalla on July 31, 2013, 04:27:26 pm
I wish I had good news but it looks like the only thing added/updated is the RIO command string list.
Title: Re: Russound RNET Plugin
Post by: big517 on July 31, 2013, 04:42:40 pm
Quote
If you can get a Russound_Controllers_Protocol_v1_00_07.pdf document, that is what I need.

So that RNET Serial Hex 1_00_07.pdf is NOT helpful then?
Title: Re: Russound RNET Plugin
Post by: kabdalla on July 31, 2013, 04:55:47 pm
It provides the "set" codes, which is what I used for my modified I_RNET file for you, but doesn't offer any "get" codes.  It also doesn't provide the structure for controller responses to "get" codes.  Look at the "Russound_Controllers_Protocol_v1_00_04.pdf" document for examples.

I've put in my own request to Russound so we'll see what they respond with.
Title: Re: Russound RNET Plugin
Post by: kabdalla on July 31, 2013, 05:35:24 pm
Just got off the phone with a Russound integration engineer who was extremely helpful.  I think I can write a single I_RNET document that will work with all controllers.  Once I confirm it's working on my, I'll upload it here for testing on an MCA controller.
Title: Re: Russound RNET Plugin
Post by: big517 on July 31, 2013, 06:34:07 pm
Awesome!  I've been impressed with Russound's support.  the ONE thing that still bothers me is the lack of "MUTE ON, and MUTE OFF" for RIO protocol.  Someone I spoke with said they added it to their list to implement, but I didn't see it in this last update....
Title: Re: Russound RNET Plugin
Post by: kabdalla on July 31, 2013, 06:40:12 pm
What I found out is the legacy "70" version (my plugin) only works on CA-series but this new "71" version works on all controllers.  The issues you were seeing are that it's a much more "chatty" version.  I sent one volume status request and got 5 responses of what the level is.  That's why your CPU was spiking and why buttons were sometimes working and sometimes not, the serial interface was busy.

Working on getting the status part working, though don't know how long it will take.  Hopefully have something up today.
Title: Re: Russound RNET Plugin
Post by: big517 on July 31, 2013, 06:50:14 pm
Take your time... your efforts are appreciated.  Interesting to know there is a less chatty version.  Hopefully you don't have to re-work the entire plugin.
Title: Re: Russound RNET Plugin
Post by: kabdalla on July 31, 2013, 08:33:19 pm
Ok, I've got a file for you to test @big517.  I have to say, understanding this new version of RNET is making this much easier.  I've got status coming back based on any change in state, volume, or source, whether its from Vera, keypad, or remote, without having to explicitly request.

The one gotcha I have is that I don't have the exact structure for these responses.  I built the updates based on my logs and analysis so I hope they hold true on the C-series.

Please test out all the buttons, I'm particularly interested in the "All On" command.  Good luck!
Title: Re: Russound RNET Plugin
Post by: big517 on July 31, 2013, 09:25:20 pm
That is interesting... so it "listens" instead of queries?
Title: Re: Russound RNET Plugin
Post by: S-F on July 31, 2013, 09:37:41 pm
This rapid development is stupendous. This is shaping up to be a grade A plugin.

Yeah eBay. New though and from a Russound dealer so I can RMA it through Russound. Looks like it will be a while until I can play with you guys.
Title: Re: Russound RNET Plugin
Post by: kabdalla on July 31, 2013, 10:33:27 pm
@big517: That is what's confusing me.  I understand the new "set" commands can also prompt the controller to respond with a status but that doesn't explain how the controller also sends this status when controlled by keypad or remote.  I could have swore during my initial plugin development that when I changed volume or state from the keypad, the log showed nothing.  It could just be that I overlooked something.  It's not that there is "listening" going on, it's the controller is sending status whenever something is changed, regardless of what is changing it.

Title: Re: Russound RNET Plugin
Post by: big517 on August 01, 2013, 06:02:38 am
I remember in RIO you had to initialize the zone to broadcast that info. 
Not sure about RNET, but the "Reading RNET" documents leads me to beleive this as well.
Maybe you should call to that Russound person again?

Code: [Select]
Tech Tip
Reading Real-Time RNET Display and Status Messages:
This document is a supplement to the Russound_Controllers_Protocol_V1_00_03.doc. While the
RNET protocol document describes methods of controlling and polling the CAV 6.6, this
document concentrates on processing real-time RNET display and status messages. You will
need to read the standard protocol document to understand some of the concepts used.
1) How To Determine That A Message Should be Read
2) Handling Locally Rendered Display Messages
3) Handling Pre-formatted Display Messages
4) Handling Special Status / Display Element Messages
5) Handling Event Messages
6) String ID Tables
There are four types of display/status messages used by RNET controllers and peripherals. These messages are
used to update text displays, display icons, and to other system states such as zone power state, etc.
1) Locally rendered display messages (Rendered by the display device).
2) Pre-formatted display messages (Rendered by the CAV 6.6 or other peripheral RNET device).
3) Status messages to update special values such as source sharing, party mode, etc.
4) Event messages to change states of certain parameters such as zone power state
Title: Re: Russound RNET Plugin
Post by: kabdalla on August 01, 2013, 08:20:54 am
I may do that if people are having problems with this but I did nothing to initialize....except maybe use the "71" codes from Vera which may have triggered something.

Did you get a chance to try out the new I_RNET file?  Eager for some feedback.
Title: Re: Russound RNET Plugin
Post by: kabdalla on August 01, 2013, 12:41:59 pm
Once I get confirmation that this works on the C-series controllers I'll upload version 1.1 of the plugin.  It will include:

1) New I_RNET file with C-series support
2) Mute toggle button
3) Support for additional messages to display (including Mute)
4) New icon for zones
5) Incoming status parsing cleanup

Title: Re: Russound RNET Plugin
Post by: big517 on August 01, 2013, 03:26:24 pm
ALL ON and ALL OFF Working...  Still major bug with Source Selection.  volume and conrol work as well.  Seem like the only issue are the Source buttons.  Only Source 1 does anything and it switches to Tuner and crashes the unit completely!  I have to turn the MCA off to regain control.
Title: Re: Russound RNET Plugin
Post by: kabdalla on August 01, 2013, 03:38:30 pm
Ok.  Can you do the following for:

1) On the Vera under Setup > Logs, turn on verbose logging.  It will reboot the Vera.

2) In a terminal window, ssh into the Vera, chdir to /var/log/cmh

3) Type   tail -f LuaUPnP.log | grep '^5' > log.txt

4) Back on the Vera web interface, click a couple of Source buttons that are causing the crash.

5) Back in the terminal window, control-c to kill the last command.

6) Attach the log.txt file here.


Hopefully that all made sense.  I also have an email in to Russound.
Title: Re: Russound RNET Plugin
Post by: kabdalla on August 02, 2013, 04:20:22 pm
Also, if anyone else has a Russound MCA controller and is interested in helping troubleshoot, please let me know.  I'm trying to get this hammered out pretty quick.
Title: Re: Russound RNET Plugin v1.1
Post by: big517 on August 06, 2013, 08:30:06 am
Where exactly is the Log.txt file located?  Should I can WinSCP in but I would like to know the location so i'm sending the right file.

Thanks
Title: Re: Russound RNET Plugin v1.1
Post by: kabdalla on August 06, 2013, 09:17:00 am
It should be located in /var/log/cmh.
Title: Re: Russound RNET Plugin v1.1
Post by: big517 on August 06, 2013, 09:26:46 am
Hope this has the info you need... 
Title: Re: Russound RNET Plugin v1.1
Post by: kabdalla on August 06, 2013, 11:45:24 am
Thanks for the upload, big517.  One question for you, were you using keypads or remotes in any way while you were capturing this?

This will be very helpful, it looks like the C-series devices offer a lot more (and possibly different) feedback.  I'll look at it more closely this afternoon/evening.
Title: Re: Russound RNET Plugin v1.1
Post by: big517 on August 06, 2013, 12:00:22 pm
No keypads or remotes in use there, just clicked the buttons on the UI5 GUI.
Title: Re: Russound RNET Plugin v1.1
Post by: kabdalla on August 06, 2013, 10:47:02 pm
Ok, new I_RNET file for you to test.
Title: Re: Russound RNET Plugin v1.1
Post by: big517 on August 07, 2013, 09:11:26 am
ALL ON/OFF button received "NO IMPLEMENTATION" error in the GUI...   Volume Keys work, On/Off works.  Still too early to test source as it will wake up the baby  :-[
Title: Re: Russound RNET Plugin v1.1
Post by: kabdalla on August 07, 2013, 10:19:56 am
The All On/Off issue is because there's a version 1.1 of the plugin that has changes to the json file.  If you're on the original version of the plugin (plus the new uploaded I_RNET file), that error is expected.  If you do decide to upgrade to the 1.1 version of the plugin, this I_RNET file will still need to be installed on top of it.
Title: Re: Russound RNET Plugin v1.1
Post by: big517 on August 07, 2013, 11:44:17 am
Re-installing everything using plugin on the app site.  Uploading I_RNET.xml.

Will report back asap.
Title: Re: Russound RNET Plugin v1.1
Post by: big517 on August 07, 2013, 12:00:39 pm
ALL OFF works.   When Turning individual zone ON the power button remains lit.
When the zone is OFF and I press ALL ON, the power button lights up on the controller, but the display does not change (still clock with no backlight).

Zone INPUT change does not work. 
When I change inputs to anything other than Input 1, nothing happens.

WHen I change to INPUT 1 (Internal TUNER)  The Zones change, but I lose complete control of the hardware and it requires me to toggle power on the unit manually.

I'll post a log shortly.
Title: Re: Russound RNET Plugin v1.1
Post by: big517 on August 07, 2013, 12:25:55 pm
This time it looks like I was able to alternate inputs, and showing in corner of Controller while in standby mode, but it froze shortly afterward.

Log attached;
Title: Re: Russound RNET Plugin v1.1
Post by: big517 on August 07, 2013, 03:08:46 pm
OK, so I noticed I had an I/O error in my dashboard to my IP to RS232 adapter (failed to open port).  I have been running it through the switch on my SONOS Connect and i'm wondering if the extra switch in there couldnt keep up with the traffic so I plugged the IP232 directly into the router and tested again.

EVERYTHING SEEMS TO WORK  :o


I clicked every button and LOG is too big to attached so it's linked here
https://app.box.com/s/onaiyur2jfqcohfudwos
 (https://app.box.com/s/onaiyur2jfqcohfudwos)

I think we're in business!  Still getting Buffer Full errors though, what is that from?
Can polling time be reduced, or added as an option in the GUI?

Title: Re: Russound RNET Plugin v1.1
Post by: kabdalla on August 07, 2013, 03:24:39 pm
Fantastic!  I do have a new I_RNET file here that should give you some source/keypad displays.  It accounts for variable length messages as yours were different lengths than mine and should be flexible enough for all other RNET sources, too.  Are you getting the volume level changes correctly displayed?

The buffer full isn't an error, I have it reporting when the buffer receives a complete string and resets.  The buffer receives one byte at a time so I do it to make it easier to read (and parse), when it gets the "finish" byte of a string, it reports the whole string it received.

If this gives you displays, I'll include and publish version 1.2 with this file.
Title: Re: Russound RNET Plugin v1.1
Post by: big517 on August 07, 2013, 04:32:30 pm
Checking now...

In the meantime is it possible to display a message on the keypads?
Title: Re: Russound RNET Plugin v1.1
Post by: big517 on August 07, 2013, 04:44:00 pm
I had the error again with the Input 1 locking everything up...   I'm going to try to the previous file that worked just to rule that out.

EDIT:

Previous file works, the most recent has the lock-up issue with Zone1.
Title: Re: Russound RNET Plugin v1.1
Post by: kabdalla on August 07, 2013, 05:04:58 pm
Hmmm, I'm wondering if this isn't related to the plugin.  The only thing different between the two files is how the Vera parses incoming messages (none of which are queried).  All outgoing commands to the Russound are exactly the same.

In verbose logging mode and same log directory as before, can you run the following command then try to get it to crash again:

tail -f LuaUPnP.log | grep '^01\|^02'

This will show errors and warnings on the Vera and may catch a serial communications issue.
Title: Re: Russound RNET Plugin v1.1
Post by: big517 on August 07, 2013, 05:16:47 pm
You're right, it crashed on the old one when I try this from a specific zone that is in a "GROUP" setting.  It's like a loop is created.  I can re-create it now.  Stand by.
Title: Re: Russound RNET Plugin v1.1
Post by: big517 on August 07, 2013, 05:51:39 pm
That command didn't save anything to the log...  I think you might want to call me if possible.

Check your PM

Title: Re: Russound RNET Plugin v1.1
Post by: big517 on August 07, 2013, 06:19:50 pm
NEW LOG
https://app.box.com/s/onaiyur2jfqcohfudwos (https://app.box.com/s/onaiyur2jfqcohfudwos)

The error is re-created when I quickly click between 2 sources on a grouped zone.  (2 zone changes in < 1 sec)
Title: Re: Russound RNET Plugin v1.1
Post by: kabdalla on August 07, 2013, 06:39:27 pm
Relevant portion of the log file is on its way to Russound.  Glad we narrowed down the issue for them.  I'll let you know what they come back with and if they don't have anything, I'll work in a delay after a source command is sent.
Title: Re: Russound RNET Plugin v1.1
Post by: kabdalla on August 08, 2013, 05:08:32 pm
Heard back from Russound and they think it's an issue on the MCA with the buffer getting full and crashing.  He recommended what I thought he would (implementing a delay) as a temporary fix until their engineers have an opportunity to dig into it and fix it.  I've attached an I_RNET file that has a 1.5 second delay after each source button push.  I've tested rapid selections on my box with no issues, @big517 can you test on the MCA?
Title: Re: Russound RNET Plugin v1.1
Post by: big517 on August 09, 2013, 11:21:53 am
I will do my best to crash it again ;)

Title: Re: Russound RNET Plugin v1.1
Post by: big517 on August 09, 2013, 04:34:40 pm
I haven't had a chance to run with it yet, but I do recall only being able to show 6 zones.  The MCA-C5 has 8 zones.
Can you add support for the 2 missing zones?

Thank you,
Title: Re: Russound RNET Plugin v1.1
Post by: kabdalla on August 09, 2013, 04:38:36 pm
Done.  Here is the updated I_RNET file.
Title: Re: Russound RNET Plugin v1.1
Post by: big517 on August 09, 2013, 05:12:50 pm
Ok, still falls into that "loop" and crashes (ONLY ON LINKED ZONES)...  Try doubling the delay.

One slight irritation... in the madness of clicking back and forth between zones on a single unlinked zone, the commands were executing in the order I clicked, but not in real time.  so I click a string of buttons within a few seconds, but it takes 10 seconds before the last click is played out.  Is it queuing the command on the Vera Side, or do you think that is the Russound controller?
Title: Re: Russound RNET Plugin v1.1
Post by: kabdalla on August 09, 2013, 06:50:08 pm
I think it's the Vera that queues up the commands and I doubt I can do anything about that.  Doubling the delay won't do anything as the queued up commands seem to execute faster than the delay states.  It's just going to have to be a known bug until Russound fixes it.

In my effort to publish v1.2 with the latest I_RNET file, I accidentally unpublished 1.1.  Not sure how long 1.2 will take for approval (possibly until Monday) but my apologies for 1.1 disappearing until then.
Title: Re: Russound RNET Plugin v1.1
Post by: big517 on August 11, 2013, 10:13:43 am
Sounds like there is a bug on the Vera side as well.   
Can you attach some sort of wait variable to the source command that Vera has to wait for, or require confirmation of status change the command?
Seems logical that it would avoid the issue if it was required to confirm status change before sending the next command.
Title: Re: Russound RNET Plugin v1.1
Post by: kabdalla on August 12, 2013, 10:04:11 am
I thought about that but I don't know how to implement.  There is no way to know which zones are part of the group so I wouldn't know which zones to wait for.  Like I said, I think it's just something we're going to have to wait for Russound to address.  I also don't see people rapidly selecting different sources (in grouped zones) being that common of an issue.
Title: Re: Russound RNET Plugin v1.1
Post by: big517 on August 12, 2013, 12:40:38 pm
I agree, it's not a major issue.
Title: Re: Russound RNET Plugin v1.2
Post by: kabdalla on August 21, 2013, 08:04:26 am
Version 1.2 has been approved and is available from the app store.  Change log at the top of this thread.
Title: Re: Russound RNET Plugin v1.2
Post by: S-F on August 21, 2013, 09:01:52 am
@ kabdalla

Thank you for you persistent development of this plugin! My replacement unit arrived yesterday and so far I have three zones running. Hopefully I'll get a chance to plug it into Vera tonight and start really using this weekend.
Title: Re: Russound RNET Plugin v1.2
Post by: S-F on August 21, 2013, 07:38:12 pm
All On doesn't work for me. All Off does though.


Need logs?
Title: Re: Russound RNET Plugin v1.2
Post by: kabdalla on August 22, 2013, 11:11:55 am
Yes, logs would definitely be helpful.  Does everything else behave correctly?
Title: Re: Russound RNET Plugin v1.2
Post by: S-F on August 22, 2013, 11:20:03 am
I haven't explored to extensively yet so I can't say for sure. I'll get a log to you tonight.

By the way, would it be possible for you to implement the ability to set specific volume levels during scene creation? Also is it possible to poll for the volume level? So, for example, one could have a PLEG scene not the level, change sources and volume and then go back?
Title: Re: Russound RNET Plugin v1.2
Post by: kabdalla on August 22, 2013, 11:57:17 am
If you don't mind testing everything before sending the log, that will allow me to patch everything at once.

There shouldn't be a need to poll the volume, it should update regardless of what is changing the volume...same with source and state.

Regarding a place to set the volume, that is actually why I wanted to implement the slider but I'm not a fan of the MCV slider only allowing 10% increments for changes.  I can try to have the "Volume" variable watched and if it is set to a new value, issue the command to change the volume in that zone to that level.  Not sure how exactly that is done so it will likely take some time.
Title: Re: Russound RNET Plugin v1.2
Post by: S-F on August 22, 2013, 05:13:24 pm
Yeah maybe poll wasn't the right word. I meant show the level to PLEG.

The lack of volume control in scenes is turning out to be an issue for me. The default volume appears to be too low to hear TTS from Vera Alerts. I just quickly tried placing two successive UP commands before the Vera Alerts message and the volume didn't go up. So it's looking pike that doesn't work either.  I'll have more time to tinker with it this weekend. Maybe Sunday.
Title: Re: Russound RNET Plugin v1.2
Post by: kabdalla on August 22, 2013, 06:17:44 pm
Keep in mind the default volume (at least on my CAM) is configurable in each zone.  Don't know if that helps.

As for reporting to PLEG, the current volume is shown as a variable in the Advanced tab at the bottom.
Title: Re: Russound RNET Plugin v1.2
Post by: S-F on August 22, 2013, 06:19:50 pm
Hmmmmmm. Not sure that it is on the CAA66 but I will look into it. Thanks for the tip.
Title: Re: Russound RNET Plugin v1.2
Post by: kabdalla on August 22, 2013, 10:18:37 pm
I couldn't get it to properly monitor the variable so I've implemented a text box in the Control tab that allows you to enter a volume value.  Let me know when you're able to test the rest of the functions and I'll put together the new version.
Title: Re: Russound RNET Plugin v1.2
Post by: S-F on August 23, 2013, 05:44:05 am
Crazy!  Having you as an active member on the forum is like having a second Christmas.  I'll get back to you Sunday evening on the errors.
Title: Re: Russound RNET Plugin v1.2
Post by: S-F on August 25, 2013, 03:56:48 pm
I can't seem to get the log process to work. I'm using winscp and when I execute tail -f LuaUPnP.log | grep '^5' > log.txt I get a "host is not communicating for more than 15 seconds etc. etc. message. Could this be due to logging to a USB drive? Can I just reboot Vera, run the functions which do not work and then attach the log file gleaned manually?

EDIT:

Also, I've been tinkering with this all afternoon and... SO FAR... all that I can see which is failing is All On.
Title: Re: Russound RNET Plugin v1.2
Post by: kabdalla on August 26, 2013, 11:11:30 am
EDIT:  Just re-read your post.  You'll need to    "cd"    into whatever directory on the USB stick has your LuaUPnP.log file if it is not in /var/log/cmh/....




Are you changing into the correct directory first?  Before you run that command you need to:

cd /var/log/cmh

Also make sure you've checked the box for Verbose Logging in the Logs section of the Vera.
Title: Re: Russound RNET Plugin v1.2
Post by: S-F on August 26, 2013, 11:13:04 am
Yep. Did all that for sure. Could it be that I'm using winscp?

EDIT

OK. If I still have issues could I just get the entire log the old fashioned way?
Title: Re: Russound RNET Plugin v1.2
Post by: kabdalla on August 26, 2013, 11:24:02 am
That's fine.
Title: Re: Russound RNET Plugin v1.2
Post by: kabdalla on August 29, 2013, 12:04:49 pm
@S-F, let me know when you're able to upload a log file showing the error for All On.
Title: Re: Russound RNET Plugin v1.2
Post by: S-F on August 29, 2013, 12:16:25 pm
I haven't forgotten.  Just really busy.  I may be able to get to it tonight or tomorrow but by the end of th3 weekend definitely.
Title: Re: Russound RNET Plugin v1.2
Post by: S-F on August 29, 2013, 04:17:16 pm
@ kabdalla

Check your PM inbox.
Title: Re: Russound RNET Plugin v1.2
Post by: S-F on September 06, 2013, 05:49:37 pm
I have been using this all the time and I can say that the only thing that doesn't seem to be working is the Al On command.the rest is fantastic! I have two questions. 1, how can the state of the devices be used as inputs in PLEG? They aren't available under triggers or device properties. 2, how's work coming on the plugin?

Thanks again!
Title: Re: Russound RNET Plugin v1.2
Post by: S-F on September 07, 2013, 08:59:29 am
Under Advanced what do the variables Input and Status represent? I'd imagine they are for power and source but they don't seem to reflect these states in the devices.
Title: Re: Russound RNET Plugin v1.2
Post by: S-F on September 23, 2013, 08:21:30 am
Any word on the new version?
Title: Re: Russound RNET Plugin v1.2
Post by: kabdalla on September 23, 2013, 11:35:16 am
It's still pending approval from last week.  I don't know how long it's going to take this time around.
Title: Re: Russound RNET Plugin v1.2
Post by: S-F on September 23, 2013, 08:10:59 pm
Well. The forum will probably be defunct as well as Vera and MCV as a whole before it gets approved at this rate. Would you mind posting the new plugin here for us, me, to benefit from while we salute a sinking ship?
Title: Re: Russound RNET Plugin v1.4
Post by: kabdalla on September 24, 2013, 03:31:16 pm
I've attached it to the first post.  The icon images are not included but if you have a previous version installed, it'll use the image files already on the Vera from that installation.

Kal
Title: Re: Russound RNET Plugin v1.4
Post by: S-F on September 27, 2013, 09:00:21 am
There is no longer any options to turn a zone on or off from the advanced tab of the scene creation interface. The previously created off commands in scenes don't work but the on commands do. I have yet to try setting a zone to off from the main gui portion on the scene editor.
Title: Re: Russound RNET Plugin v1.4
Post by: kabdalla on September 27, 2013, 10:46:39 am
It uses SwitchPower now.  Trying setting that target to 0 for off and 1 for on.
Title: Re: Russound RNET Plugin v1.4
Post by: chilump on October 16, 2013, 09:23:30 am
Thanks for all your hard work!

I am trying to decide between C-Series and CA Series controllers.

Questions:

I understand you can select sources via RNET plugin for Vera. Has anyone integrated selecting music (Network or Streaming) within Vera then jumping to select zones etc within the same interface

Also if I go with a CA series do I need to also purchase the RNET Touch Point device?

Thanks!
Title: Re: Russound RNET Plugin v1.4
Post by: kabdalla on October 17, 2013, 05:44:56 pm
For the second question, you do not need the RNET Touch Point (in fact it won't work at all with it) but you do need a USB-Serial adapter for the Vera and a serial cable to connect the Vera to the Russound Controller.

For the first question, I'm not sure I understand.  I'm assuming by this question that your audio source is not RNET-enabled (Russound SMS3, DMS3, or iPod dock).  If that is the case then the only way I can think of for selecting a source and playing music is if your music player has a Vera plugin.  You can then create a scene that selects the music on the player plugin and zone/source on the RNET plugin.
Title: Re: Russound RNET Plugin v1.4
Post by: big517 on October 17, 2013, 06:05:30 pm
I suggest Sonos connect and C series.
Title: Re: Russound RNET Plugin v1.4
Post by: big517 on October 17, 2013, 07:35:13 pm
I just ordered a Myro bridge for enhanced control over Sonos from the c series keypad
Title: Re: Russound RNET Plugin v1.4
Post by: chilump on October 18, 2013, 08:08:27 am
For the first question, I'm not sure I understand.  I'm assuming by this question that your audio source is not RNET-enabled (Russound SMS3, DMS3, or iPod dock).  If that is the case then the only way I can think of for selecting a source and playing music is if your music player has a Vera plugin.  You can then create a scene that selects the music on the player plugin and zone/source on the RNET plugin.
[/quote]

I just ordered a Myro bridge for enhanced control over Sonos from the c series keypad [/quote]

Thanks for your response. I think your solution makes sense. I'm really aiming to have a sonos type interface where from a single interface I first select the source which then lets me select music (pandora or specific mp3 album) then select the zone you want to play it in.

Is this feasible within Vera or is it keypads only using a Sonos and C Series Keypad?
Title: Re: Russound RNET Plugin v1.4
Post by: big517 on October 18, 2013, 08:11:14 am
Both.   Check out the Sonos plugin.  You'll use that for what your are trying to accomplish.   The Myro just delivers metadata so you can see what's playing and control the sonos from your keypad.
Title: Re: Russound RNET Plugin v1.4
Post by: chilump on October 18, 2013, 08:13:11 am
Both.   Check out the Sonos plugin.  You'll use that for what your are trying to accomplish.   The Myro just delivers metadata so you can see what's playing and control the sonos from your keypad.

Thanks big517!
Title: Re: Russound RNET Plugin v1.4
Post by: sgruby on October 19, 2013, 08:51:56 am
Any chance your plugin is easily modified to talk to Russound controllers over a TCP to serial port server? I have 3 Russound CA4 units with the serial ports connected to a 4 port serial to TCP converter http://www.digi.com/products/serialservers/portserverts Instead of talking to it directly over over serial code, you send socket commands like this:

socket=require('socket')
local client = socket.connect('10.0.1.108', 2001) -- The IP address is the port server. The port is 2001 for unit 1, 2002 for unit 2, 2003 for unit 3
command = setPower(0,0)
client:send(command)
client:close()


(setPower is my own Lua routine that formats the Russound command given the zone and a value).

Also, can your plugin handle multiple Russound units? As I mentioned above, I have 3 separate units (12 zones total...the CA4 units can only be chained for a total of 8 zones so I left them all separate).

Thanks!
Title: Re: Russound RNET Plugin v1.4
Post by: big517 on October 19, 2013, 09:50:42 am
Have you tried the IP2Serial plugin?  I believe that is exactly what you are looking for.   Search the forum and you'll find it.
Title: Re: Russound RNET Plugin v1.4
Post by: sgruby on October 19, 2013, 11:30:10 am
Searching the forums shows that the plugin was a hack and is no longer available. The notes also indicate that it is straightforward (I won?t say easy) to add the functionality to a plugin that already does serial. When I get some time, I?ll poke at the plugin source and see if I can add the IP stuff to it.
Title: Re: Russound RNET Plugin v1.4
Post by: DanielMason on November 13, 2013, 01:28:31 pm
Not being a programmer at all. I thought that the transition from serial to IP was straight forward.

Yes you are correct the plugin is no longer available.


Searching the forums shows that the plugin was a hack and is no longer available. The notes also indicate that it is straightforward (I won?t say easy) to add the functionality to a plugin that already does serial. When I get some time, I?ll poke at the plugin source and see if I can add the IP stuff to it.
Title: Re: Russound RNET Plugin v1.4
Post by: sgruby on November 13, 2013, 11:17:54 pm
I ended up using the plugin as a shell and modified it significantly to meet my needs with 3 CA4 devices and a PortServer box. Unfortunately the plugin will have no use to anyone else Lua and plugins aren't too hard to write, but they take a bit of time to figure out.
Title: Re: Russound RNET Plugin v1.4
Post by: garrettwp on December 03, 2013, 02:59:31 am
Here is a modified version of the Russound plugin version 1.4 that fixes issues with the wrong service id's being used for the On / Off functions and the Volume function.

- Garrett
Title: Re: Russound RNET Plugin v1.4
Post by: DanielMason on December 04, 2013, 04:07:40 pm
Garrett----> Any chance you could make it so we can use a wiznet, instead of having to use the usb port on Vera? :)

Please


Here is a modified version of the Russound plugin version 1.4 that fixes issues with the wrong service id's being used for the On / Off functions and the Volume function.

- Garrett
Title: Re: Russound RNET Plugin v1.4
Post by: S-F on December 04, 2013, 04:54:15 pm
I don't think he has any intention of taking up development of this plugin as he himself doesn't have any Russound gear. He merely copied and pasted some small amount of information to make the plugin consistent with others of similar ilk.
Title: Re: Russound RNET Plugin v1.4
Post by: garrettwp on December 04, 2013, 11:23:32 pm
Correct, I have no intention of supporting this plug in. I am just making some small fixes so that it will work with 3rd party apps.

- Garrett

Title: Re: Russound RNET Plugin v1.4
Post by: S-F on December 05, 2013, 11:25:03 am
@ Garret

I have a bunch of scenes which turn various zones on and off. Since I uploaded your modified files none of the Off commands are firing any longer. Is this a coincidence or could it be related to the changes you made?
Title: Re: Russound RNET Plugin v1.4
Post by: garrettwp on December 05, 2013, 11:32:18 am
It is most likely related to the change since the original plugin used the wrong service type and your scenes are referencing that wrong service type. You'll have to modify the scenes to use the correct service type.

- Garrett
Title: Re: Russound RNET Plugin v1.4
Post by: DanielMason on December 05, 2013, 11:44:15 am
Oh well maybe someone else will pick it up.

Anyone know where someone could contract a programmer to create a plugin for Vera?
Title: Re: Russound RNET Plugin v1.4
Post by: S-F on December 05, 2013, 11:46:15 am
Oh Man! Thanks something on the order of 30+ scenes! And the ridiculous way UI5 shuffles scenes around when editing them makes keeping track of which I've already fixed a nightmare. What's up with that any way?

Thanks Garret.

@ DanielMason,

If you gave the developer of the plugin a wiznet he may be willing to modify his code.
Title: Re: Russound RNET Plugin v1.4
Post by: garrettwp on December 05, 2013, 11:52:47 am
Sorry for the extra work!

- Garrett
Title: Re: Russound RNET Plugin v1.4
Post by: DanielMason on December 05, 2013, 12:11:44 pm
@kabdalla I am willing to ship you a Wiznet if you could try making the plugin work with it.

Cheers
Title: Re: Russound RNET Plugin v1.4
Post by: S-F on December 11, 2013, 04:16:32 pm
@kabdalla

Minor bug: The plugin doesn't report mute status. This is shown in the plugin when muting and then unmuting, a field marked "Display" still reads *Muted* and the Mute icon doesn't change colors like the other buttons to indicate it's status. So you have to go by your ears alone and hope that your source is still playing.

Also is there a reason that the volume stays in position when turning off a zone? It's a little odd looking at a zone in AutHomation which is turned off and seeing the volume slider set to some % greater than 0. When a light, for example, is turned off the slider is pegged at 0%.
Title: Re: Russound RNET Plugin v1.4
Post by: kabdalla on January 11, 2014, 09:33:03 pm
Sorry all, I had some things going on that pulled me away from continuing support on this.  I plan on getting back at it tomorrow and I'll go through the various posts to see what's going on.
Title: Re: Russound RNET Plugin v1.4
Post by: S-F on January 11, 2014, 10:20:05 pm
Glad to see you here again kabdalla. I hope all of your duty time was at least pleasant and productive. The plugin is working like a charm for me! I assume it's working for everyone else too because no one is complaining.
Title: Re: Russound RNET Plugin v1.4
Post by: lolodomo on January 12, 2014, 01:49:05 pm
Sorry all, I had some things going on that pulled me away from continuing support on this.  I plan on getting back at it tomorrow and I'll go through the various posts to see what's going on.

Please read this topic: http://forum.micasaverde.com/index.php/topic,17991.0.html
That would be a good thing if you could include the "reference" file in your plugin. Tell me if something is missing in this file. Any change can be discussed of course.

Doing that, we have a chance to make your plugin and for example the Sonos plugin working well on the same Vera.
Title: Re: Russound RNET Plugin v1.4
Post by: AgileHumor on January 23, 2014, 05:51:57 pm
@kabdalla

Have you ever thought about introducing a "Paging" functionality.

They key logic would be:

Page On:
* Determine Volume and SwitchPower status of all zones
* Turn on All Zones for whole home paging or announcements

Page Off:
* Return Volume and SwitchPower status of all zones to previous (pre-page) values.
Title: Re: Russound RNET Plugin v1.4
Post by: rgtwng on January 29, 2014, 05:03:41 pm
@kabdalla

Have you ever thought about introducing a "Paging" functionality.

They key logic would be:

Page On:
* Determine Volume and SwitchPower status of all zones
* Turn on All Zones for whole home paging or announcements

Page Off:
* Return Volume and SwitchPower status of all zones to previous (pre-page) values.

Now that would be useful
Title: Re: Russound RNET Plugin v1.4
Post by: signal15 on February 09, 2014, 02:53:15 pm
I'm looking at modifying your plugin to support the Monoprice/McLelland/Factor 6-zone system (expandable to 18 zones with 3 units).  The serial port control protocol is at the end of this manual:
http://www.mclellandmusic.com/upfiles/down/MAP-1200HD%20User%20Manual.rar

Sorry for the RAR link, Monoprice doesn't have the manual available for download anymore for some reason. 

In any case, do you foresee this to be a difficult endeavor?  From the looks of it, it shouldn't be terribly hard.  I will need to add a control for each zone to turn on/off Do Not Disturb, it doesn't appear that Russound has this capability.

Any pointers on what I should look at changing?  I've only glanced over the code so far.
Title: Re: Russound RNET Plugin v1.4
Post by: therealabdo on February 26, 2014, 05:24:54 am
Can you add some photos or maybe video
You know before buying the Russound i just want to make a look

I heard it works with Authomation andriod application, if you can add a video also it will be perfect :D

Thanx
Title: Re: Russound RNET Plugin v1.4
Post by: Vodden on February 27, 2014, 10:35:13 pm
So, just to be clear, this is only designed to work over a serial connection, not via IP?

Thanks

V
Title: Re: Russound RNET Plugin v1.4
Post by: S-F on March 07, 2014, 01:45:11 pm
Well, yesterday I accidentally turned Vera on when it wasn't connected to my Russound amp. Now Vera doesn't see the amp.

When I looked at the UI for the first time I got a "RNET Interface: Choose the serial port for the URTSI" message. I go to serial port configuration and what I see is attached. I select the Russound controller, hit save and then get a "Russound RNET Controller: Failed to open IO port" message.

I did exchange the USB cable for a longer one, so maybe that's the issue here, but the serial/USB adapter is lit up so I know it's at least getting USB power from vera.

Am I missing something simple here?

This might be relevant also. I'm logging to a USB drive. Around the same time I ran Vera with no Russound amp I got this message on the logs tab:

Code: [Select]
Errors log:
2014-03-07_13:37:14 CHECKDISK: Starting to check device: /dev/sda1 with: /usr/sbin/e2fsck
2014-03-07_13:37:15 (/dev/sda1) : Successfully checked
 
Title: Re: Russound RNET Plugin v1.4
Post by: BulldogLowell on March 07, 2014, 02:07:51 pm
I get that message as a matter of course with the USB attached.

Fixing could be as easy as reconnect everything and do a restore from before you pulled it apart?

Title: Re: Russound RNET Plugin v1.4
Post by: S-F on March 07, 2014, 04:57:08 pm
Yeah, well, I guess I posted too soon. I put the original USB cable back on and now it works. Odd since the other cable works fine for everything else I've used it for.
Title: Re: Russound RNET Plugin v1.4
Post by: BulldogLowell on March 07, 2014, 05:16:04 pm
Don't you love it when it's that simple?
Title: Re: Russound RNET Plugin v1.4
Post by: S-F on March 07, 2014, 09:55:55 pm
Don't you love it when it's that simple?

Yes and no.

Yes because all I had to do was put the original cable back.

No because it's plain embarrassing to have posted a request for help when all that was needed was to put the original cable back.  :P
Title: Re: Russound RNET Plugin v1.4
Post by: AgileHumor on March 15, 2014, 10:50:37 am
Per this thread, it looks like:
http://forum.micasaverde.com/index.php/topic,23937.msg164505.html#msg164505

"RNET plugin is using the wrong serviceId for SwitchPower1. It should be urn:upnp-org:serviceId:SwitchPower1"

Just an FYI, thanks!
Title: Re: Russound RNET Plugin v1.4
Post by: S-F on March 15, 2014, 10:52:21 am
Garrettwp modified some of the files and attached them here earlier in the thread to address this issue. Unfortunately the changes haven't made their way into the plugin store version yet.
Title: Re: Russound RNET Plugin v1.4
Post by: AgileHumor on March 15, 2014, 11:00:17 am
Thanks sir!

Link to updated version:
http://forum.micasaverde.com/index.php/topic,15832.msg138902.html#msg138902
Title: Re: Russound RNET Plugin v1.4
Post by: vibracobra on April 05, 2014, 09:30:27 pm
I have the rnet 1.4 plugin and a russound caa66  connected to a vera lite. On my UI5 page I have the parent rnet controller and 2 audio zones show up under my devices tabs and I believe everything is installed correctly however and I cant get any of the commands to work. Does anyone have any suggestions of what could be wrong?
Title: Re: Russound RNET Plugin v1.4
Post by: S-F on April 06, 2014, 08:32:18 am
You have no error messages?
Title: Re: Russound RNET Plugin v1.4
Post by: vibracobra on April 06, 2014, 10:08:31 am
No, just no response
Title: Re: Russound RNET Plugin v1.4
Post by: AgileHumor on April 06, 2014, 10:23:22 am
What are your serial settings? They should be 19200 (not default 9600)
Title: Re: Russound RNET Plugin v1.4
Post by: vibracobra on April 06, 2014, 10:46:16 am
yes I have 19200
Title: Re: Russound RNET Plugin v1.4
Post by: AgileHumor on April 06, 2014, 12:06:41 pm
Worked pretty much right out of the box for me.  Have you used the USB to Serial cable converter with Vera before?
Title: Re: Russound RNET Plugin v1.4
Post by: S-F on April 06, 2014, 01:32:26 pm
If the USB to serial converter didn't work it wouldn't show up as an option in the UI I believe. Since there is no error message I can't imagine any possible issue.

Did the setup process go exactly as expected?
Title: Re: Russound RNET Plugin v1.4
Post by: AgileHumor on April 06, 2014, 02:40:25 pm
There still is the pinout of the serial adapter to ensure communications.  Using a supported cable will ensure that no custom pinouts could cause issues.   Having it show up is only the the first step.
This is the adapter I used that will connect directly without any other serial cables/adapters:
http://www.amazon.com/gp/product/B006PIU2KO

I've also had some issues with other serial devices of the parent not being set properly. Here would be the recommended next steps.

* Uninstall Plugin
* Swapping the usb port (to force reinstall) of the serial adapter.
* Make sure it is set 19200 and name it something like Serial_Russound
* Install Plugin
* Go back to serial settings and select your russound plugin name from the drop down list.
Title: Re: Russound RNET Plugin v1.4
Post by: vibracobra on April 06, 2014, 03:58:50 pm
I have never used the USB serial converter before. The setup didn't quite go as I expected. I had the plugin downloaded before I had the Cable, when I got the cable installed nothing showed up in the "serial port configuration" directory. I uninstalled plugin then downloaded again and then I could set the serial settings, everything seemed to be going fine but I couldn't get any of the commands to do anything.
Title: Re: Russound RNET Plugin v1.4
Post by: S-F on April 06, 2014, 05:36:50 pm
Yeah, sounds like a serial/USB converter issue. Which one are you using? Are you using a USB extension? I recently swapped out my USB extension cable with a known working one of greater length and it didn't work.
Title: Re: Russound RNET Plugin v1.4
Post by: vibracobra on April 07, 2014, 02:59:34 pm
The brand name is nexxtech and I am not using an extension
Title: Re: Russound RNET Plugin v1.4
Post by: vibracobra on April 07, 2014, 03:14:06 pm
Now I can't even connect to my vera anymore, the blue and orange light on the vera lite are solid and the green is flashing rapidly, wow this is becoming a mess haha, I need help.
Title: Re: Russound RNET Plugin v1.4
Post by: S-F on April 07, 2014, 03:47:19 pm
Is your USB/Serial adapter a FTDI chip? If not I suggest you replace it with one that is.

About your Vera being unresponsive, Have you tried the usual things like cycling power and assuring that it hasn't changed it's IP address?
Title: Re: Russound RNET Plugin v1.4
Post by: vibracobra on April 07, 2014, 11:02:07 pm
So I can connect to my vera again. However I uninstalled the rnet plugin but now In the "serial port configuration" nothing shows up. I don't have a usb serial adaptor but rather a usb to serial port cable if that means anything. I'm not sure if that is a fdti chip.
Title: Re: Russound RNET Plugin v1.4
Post by: S-F on April 07, 2014, 11:08:58 pm
I don't have a usb serial adaptor but rather a usb to serial port cable

That confuses the hell out of me.

I really think you should get a known good adapter.

Title: Re: Russound RNET Plugin v1.4
Post by: vibracobra on April 07, 2014, 11:31:10 pm
haha sorry, anyway after some time passed it did show up, I set the baud rate and then downloaded rnet again, everything seemed to go right and the parent controller and the 2 audio zones appeared under my devices tab, but again, their commands wont do anything, I guess ill just have to try a new adaptor but it seemed to me that if I get this far the adaptor would not be the problem.
Title: Re: Russound RNET Plugin v1.4
Post by: S-F on April 07, 2014, 11:38:41 pm
but it seemed to me that if I get this far the adaptor would not be the problem.

If you can rule everything else including your adapter out then I think you're free to raise hell. Until you use a known good adapter you're going to have to stick with the recommendations though.
Title: Re: Russound RNET Plugin v1.4
Post by: vibracobra on April 07, 2014, 11:47:24 pm
makes sense, thanks for the help
Title: Re: Russound RNET Plugin v1.4
Post by: big517 on April 08, 2014, 05:43:14 am
The brand name is nexxtech and I am not using an extension


Return that cable.  Im pretty sure I bought the same brand off Amazon and it didn't work for me either.  I'll bet that is the issue. 

Sent from my SCH-I535 using Tapatalk

Title: Re: Russound RNET Plugin v1.4
Post by: hifs on April 08, 2014, 07:49:22 am
I just purchased some additional Vantec USB To Serial Adapter (CB-USB20SR) cables from amazon. They have the FTDI chip and work with Vera.
Title: Re: Russound RNET Plugin v1.4
Post by: waynehead99 on April 18, 2014, 03:05:09 pm
Has there been any headway in IP to 232? I am getting my system in a few days and there is no way the two components can be near each other and would really love to be able to add this to my vera system.
Title: Re: Russound RNET Plugin v1.4
Post by: S-F on April 18, 2014, 03:24:39 pm
There have been no developments at all. Sorry.
Title: Re: Russound RNET Plugin v1.4
Post by: tb001 on June 14, 2014, 01:18:49 pm
Probably a dim question, but is there any way to get this working with a CA6 controller? Thought it should be fairly straightforward, but when I went to hook it up to vera, realized there is no serial port on the CA6. Guessing this is a no go, but really hoping I'm missing something obvious!
Title: Re: Russound RNET Plugin v1.4
Post by: wkearney99 on June 23, 2014, 02:56:09 pm
Does the plug-in support multiple amps?  I've two CAV66 and one CAM.  Would I just be connecting serially to one of them and the via RNET between the others?  Assuming they're setup properly, of course.  Or do I end up having multiple serial connections, one to each amp?
Title: Re: Russound RNET Plugin v1.4
Post by: Sundayfun on September 16, 2015, 11:30:50 am
@kabdalla Would you mind if I take over this plugin development? I think there are many peeps who have a Russound system and would like to have a plugin that can control it through a Itach IP2Serial device.

I control my Russound CAM with itunes, but I think it would be great to create a scene when I come home that turns on the music, or create a scene that alerts me or my family.

KP
Title: Re: Russound RNET Plugin v1.4
Post by: wilme2 on October 07, 2015, 02:26:10 pm
I think there are many peeps who have a Russound system and would like to have a plugin that can control it through a Itach IP2Serial device.

I would buy a Russound system if we had a non-directly-connected option...  And I have a spare Itach IP2Serial...
Title: Re: Russound RNET Plugin v1.4
Post by: jamenjay on October 10, 2015, 09:46:12 pm
@Sundayfun     I would love to see some better developments with this.....  I abandoned using it and now control with casatunes...  Great music server that can control russound via ios or android        I would still like to get everything in one app

I have
 lutron radio Ra    "first generation"   controlled via usb serial and the lutron rs232 device
 russound caa-66
 casatunes
 nest
 honeywell lynxx alarm

i also use veramate and had made some adjustments to the app layout files to make button sizes larger and remove buttons i didnt need

Im also using the vera edge I might add ...... my lite died :(
 
Title: Re: Russound RNET Plugin v1.4
Post by: silverhaze on October 21, 2015, 11:58:39 pm
I have 2 russound C3 6 zone amps in my system. I can get the app to control the first 6 zones perfectly but it will not allow me to add the zones on my second amp.  It will add zone 7 and 8 which do not work. I assume they would be for a single C5 amp?

Has anyone out there had experience with this that could help?
Title: Re: Russound RNET Plugin v1.4
Post by: joelc73 on October 22, 2015, 09:37:48 am
Does anyone know if this plug-in would work with Integra A-bus (which I believe is just a licensed version of Russound)?

Thanks,
JC
Title: Re: Russound RNET Plugin v1.4
Post by: LeonPhelps on March 29, 2016, 02:12:13 am
Upgraded to Vera Edge today and got RNET running, but it keeps saying cant detect device on the notification panel.
Title: Re: Russound RNET Plugin v1.4
Post by: jamenjay on June 03, 2016, 09:16:01 pm
did you re setup your serial port with the correct baudrate etc ?
Title: Re: Russound RNET Plugin v1.4
Post by: amikolajczyk on July 18, 2016, 11:16:12 pm
I know this plugin hasn't been developed for a good long while now, but I was wondering if anyone out there had any advice. Trying to use it with an MCA-C5. Serial-USB port looks good, logs check out OK but I'm getting a "Can't Detect Device"

Verified my USB-Serial is located at \dev\ttyUSB0 and that's what's listed in my controller's path variable as well as my serial port config.

What I'm seeing in the logs is lots and lots of these:
Code: [Select]
luup_log:281: Received full buffer from controller via serial F0 00 00 7D 00 00 7F 06 16 00 90 01 10 36 F7 <0x2e6e8680>
Is there something in particular that you have to do to tell the plugin which model of Russound controller it's using? Is there anywhere else to look or anything else to look for in the logs?

Thanks for any advice,
Adam
Title: Re: Russound RNET Plugin v1.4
Post by: e50golf on February 12, 2017, 08:54:58 am
Change Baud rate 38400. This solved problem for me.
Title: Re: Russound RNET Plugin v1.4
Post by: drweiler on October 22, 2017, 02:21:38 pm
Just got my VeraPlus, one of the first things to try was connecting to my Russound CAM6.6 using this Russound RNET plugin.  I may be missing something (am I?), but I didn't find any documentation other than this thread on the forum, which was somewhat helpful.
I did get it to connect almost right away, but I had two problems.  The first was that I was only able to control the first two of 6 zones, i.e. other than the master device, there were only 2 zone devices created.  After much experimentation, I got it to work by uninstalling and installing in this order:
1. install the plugin from the "Install apps" menu
2. From the Advanced settings, Variables tab, edit "ZoneIds" - was "01,02", changed to "01,02,03,04,05,06"
3. From Developer apps, Serial Port configuration - set "Used by device:" to "Russound RNET Controller"
At some point the 6 zone devices get created, I'm not sure exactly when, it seemed to be the first time I clicked "All on" or "All off".  But the trick seemed to be to add the 4 extra zone IDs before the zone devices get created, because if only two zone devices are created, there seems to be nothing you can do to add the other 4 except start over.
So control seems to be working reliably for what I wanted - turning zones on and off, setting the volume, and muting.
The second problem is minor - for the master device (all on/ all off), I have a permanent "Can't Detect Device" message in red, a minor annoyance.