|
|
Post by hanshi on Sept 16, 2010 17:59:53 GMT -5
It might work partially but will be highly unreliable. The device is not designed to operate with multiple sessions.
|
|
|
|
Post by fiasco on Sept 16, 2010 21:10:50 GMT -5
It might work partially but will be highly unreliable. The device is not designed to operate with multiple sessions. If that were the case, why have multiple telnet logins. I don't have any issues at all running four simultaneous connections(ipad x 2, iphone x 2). I've been doing this for months (I think I installed my RA2 system in February or March) I have the odd disconnect referred to in the other thread but I use a heartbeat send/receive to reestablish the session if it is dropped (using the #MONITORING,255,1\x0D\x0A command and ~MONITORING,255,1\x0D\x0A response) |
|
|
|
Post by hanshi on Sept 17, 2010 7:41:34 GMT -5
My point is that it's not a supported feature. If the code changes on the product and you lose the functionality, then that poses the problem. The project team has confirmed. I am having them continue the testing. No issues have been seen on the next release code but I want them to test on older code as you were using.
|
|
|
|
Post by fiasco on Sept 17, 2010 17:56:28 GMT -5
I could always use a RS232->IP device that supported multiple connections if this unsupported feature were to be eliminated.
|
|
|
|
Post by fiasco on Oct 23, 2010 21:00:49 GMT -5
An attempt to fix this was made in the last Ra Essentials version but it is still screwed up.
The Ra Repeater integration buttons now correctly respond to a query.
However, if the state of the Ra Repeater Integragtion LED changes, the RA repeater doesn't automatically report it.
So, for example. I have #monitoring,255,1
If I change the state of the ra integration button on the main repeater the repeater should report a status change but it doesnt.
|
|
|
|
Post by fiasco on Nov 29, 2010 13:30:57 GMT -5
Any word on the issue in my above post being corrected?
|
|
|
|
Post by Jimm Reifsnyder on Dec 7, 2010 10:47:34 GMT -5
I have pinged a couple of the engineers that I know at Lutron and no idea when this issue will be resolved. I will see if Hanshi has any better insight on this one.
|
|
