garybixler

I did clear Java after the last firmware update. Will try again however. But there is still an issue communicating robustly with the ELK. Just today the change in the logical status back from violated to normal was not detected causing the program to loop. eisy V 5.6.4 PG3x V 3.2.1 Thanks Gary

Been having issues with not being able to log in locally (LAN) after a few days. Can log in via cloud but nothing is available for change. Sometimes programs end up in a loop. Didn't try reboot from the cloud login. Usually I just do a power re-boot. Also ELK seems to be a bit sluggish sometimes and I can get a TCP error when querying a zone. TCP client read response failed. (NS-14-ELK) Thanks Gary

I have noticed a few things that maybe connected with the latest upgrades of IoX, ELK or PG3. Sometimes the logical status is not returned correctly. Also a query of a zone will sometimes return a TCP error. There doesn't seem to be the instantaneous responses as before. After upgrading the IoX to 5.6.4 many of my programs were enabled. A different issue I'm sure. Overall the ELK seems to perform correctly with the exception of those non alarm zones where the logical state may change rapidly like a mail box or driveway alert. I did check the ELK with M1ToGo and the statuses are always correct. Just thought I'd pass this info along. Thanks Gary IoX 5.6.4 PG3 5.6.4 ELK 3.8.1

Installed 2.0.10 and all looks good. Will check to make sure the connection is kept alive. So far it seems to be OK. Thanks so much. Gary

Just loaded 2.0.9 but keep getting this log repeating. Not connecting. Thanks IndentationError: unexpected indent 2023-08-10 17:36:19,745 MainThread udi_interface INFO polylogger:set_basic_config: set_basic_config: enable=True level=30 2023-08-10 17:36:20,447 MainThread udi_interface INFO __init__:<module>: UDI Python Interface for Polyglot version 3 3.1.0 Starting... 2023-08-10 17:36:20,461 MainThread udi_interface ERROR udi_interface:write: Traceback (most recent call last): File "/var/polyglot/pg3/ns/0021b9026038_16/russound.py", line 9, in <module> from nodes import control File "/var/polyglot/pg3/ns/0021b9026038_16/nodes/control.py", line 15, in <module> from nodes import russound File "/var/polyglot/pg3/ns/0021b9026038_16/nodes/russound.py", line 673 ''' IndentationError: unexpected indent 2023-08-10 17:36:21,641 MainThread udi_interface INFO polylogger:set_basic_config: set_basic_config: enable=True level=30 2023-08-10 17:36:22,345 MainThread udi_interface INFO __init__:<module>: UDI Python Interface for Polyglot version 3 3.1.0 Starting... 2023-08-10 17:36:22,359 MainThread udi_interface ERROR udi_interface:write: Traceback (most recent call last): File "/var/polyglot/pg3/ns/0021b9026038_16/russound.py", line 9, in <module> from nodes import control File "/var/polyglot/pg3/ns/0021b9026038_16/nodes/control.py", line 15, in <module> from nodes import russound File "/var/polyglot/pg3/ns/0021b9026038_16/nodes/russound.py", line 673

I only have the C5 but polling wasn't necessary for the MCA-88. That was learned from the first RIO NS on PG2. So I am thinking that the C3, C5 being the first RIO devices my be the only ones requiring polling.

Update on polling. The MCA C3, C5 do need to be polled in order to keep the connection alive for receiving status updates. Volume, Power, Source etc.. Thanks Gary

WOW everything looks great. I just need to check if the C3, C5 series needs to be polled in order to keep the connection alive so that status info is received. If needed I have been using this program. I think it will take about an hour to find out. If needed maybe there would be a cleaner way of doing it within the NS. But many thanks for all you work. Thanks Gary Russound Keep Alive - [ID 0095][Parent 0054][Not Enabled] If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Repeat Every 20 minutes Set 'RussoundCtl_1 / Bedroom 1' Treble -1 Wait 10 seconds Set 'RussoundCtl_1 / Bedroom 1' Treble 0 Else - No Actions - (To add one, press 'Action')

I just tried 2.0.7 but nothing is being discovered. Just shows RussoundCtl_1. I entered the IP address, port 9621, TCP and RIO into the config. Did a Re-Discover but no nodes were found. I included the log from restart and Re-Discover. Hope it helps. Thanks Gary I did delete 2.0.6 and installed 2.0.7. New Text Document (3).txt

Just another thought. In the original config under PG2 it may have asked for the number of controllers and the number of zones in each.

The second controller isn't connected to Ethernet. Not sure how it would react seeing that the first controller is connected to Ethernet and talks to the second controller using the RNET link allowing each to control global functions like Party Mode. Thanks Gary

Got it. So far the only thing I see is that the source selections are one off. My sources (AM/FM, Cable, Computer, ECHO, etc) When selecting Cable I get AM/FM and when selecting Computer I get Cable. When selecting AM/FM it defaults to Cable but is on AM/FM source. Thanks Gary

@bpwwer Hi. I did inadvertently click the add controller button but later removed it. In the previous version of Russound RIO in PG2 the second controller was seen as one with 12 zones. Should actually be 16 zones as two on each controller are line out zones. Previously the only difference between the MCA- 88 and the MCA-C5 was that the C5 needed to be polled every so often to keep it alive. After a restart I Just discovered that Source selection no longer appears. Just 0. Didn't see 2.0.6 yet but will give that a try when available. Thanks Gary When I do a Zone On on zone 3 (0ffice) I get this response. 2023-08-04 17:59:17,765 Command udi_interface.interface ERROR interface:_handleInput: _parseInput: node address zone_3 does not exist. {'address': 'zone_3', 'cmd': 'DFON', 'query': {}} 2023-08-04 17:59:17,765 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING command 2023-08-04 17:59:17,765 Command udi_interface.interface ERROR interface:_handleInput: _parseInput: node address zone_3 does not exist. {'address': 'zone_3', 'cmd': 'DFON', 'query': {}} 2023-08-04 17:59:19,091 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message shortPoll 2023-08-04 17:59:19,091 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message shortPoll 2023-08-04 17:59:19,091 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING shortPoll

I installed the Russound NS 2.0.5 from the non production store. I selected RIO and port 9621. The 6 zones for the first controller was loaded but the second controller was not. They are connected together with the required patch cords. This was the setup for the PG2 version. I noticed that I was not getting any status returns such as Source number and volume db. After a few minutes I was unable to select a source. This is the log when selecting a source. 2023-08-03 20:49:23,120 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message shortPoll 2023-08-03 20:49:23,120 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING shortPoll 2023-08-03 20:49:31,557 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message command 2023-08-03 20:49:31,557 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING command 2023-08-03 20:49:31,557 Command udi_interface DEBUG zone:process_cmd: ISY sent: {'address': 'zone_3', 'cmd': 'SOURCE', 'value': '2', 'uom': '25', 'query': {}} 2023-08-03 20:49:31,557 Command udi_interface DEBUG russound_main:Send: RIO: Sending b'EVENT C[1].Z[3]!KeyRelease SelectSource 2\r\n' I included the log from startup. Thanks Gary New Text Document (3).txt

Went through the update and all is working fine. I do have an issue with updating NS AVRemote from 2.0.5 to 2.0.6. It goes through the update fine but the version never gets updated. Otherwise works as before. Thanks Gary

Hi, I have tried updating a few times but the server always stays on version 3.6.5 never goes to version 3.7.0. I will eventually receive another message that an update is available. All is working fine so not a pressing matter. Thanks I keep getting this error message but nothing shows up in the log. ERROR: 06/15/2023 18:19:55 See log for: ISY None is not initialized, see l UPDATE: My error. Didn't notice the new update method.

Sorry was away for awhile. I updated to version 3.6.5 and all looks good now. Thanks.

I updated to version 3.6.4 but am still not seeing polling of the zone voltages. Area1 and zone 'Poll Voltage' are set to true. Doing a query on the zone will load the latest voltage level. Short Poll is set to 30 seconds. Power reset the eisy but no difference. New Text Document (3).txt

Hi, just update PGx to version 3.1.24 and it seems that the poll zone voltages aren't working. Did a restart on the NS but still no polling. Also the eisy was rebooted. The log used to show polling but I no longer see that. After doing a query on the zone the correct voltage was filled in. I included a partial log. Also made sure 'set poll voltages' were set to true. ELK may have updated when PGx was rebooted. IOx 5.5.9 PGx 3.1.24 ELK 3.6.0 Thanks New Text Document (3).txt

That did it. All is good now. Thanks so much.

I did post on that thread also but now am looking for how to delete the NS from PG3 using SSH.

After a recent reboot of eisy the NS AVRemote updated to version 2.0.5. After that it no longer connects to the iox and can't be deleted for a fresh install. Gets the following message: "Failed to remove node server AVRemote from slot (13). Can not read properties of null (reading 'filename')". No log is produced. Would like the procedure to delete the NS through SSH. Hopefully a fresh install will fix the issue. Thanks

Also having issues with v 2.0.5. Just loaded after a reboot today. It is not communicating with eisy and I can not delete it for a fresh install. I keep getting the message: "Failed to remove node server AVRemote from slot (13). Can not read properties of null (reading 'filename')". No log is produced. Deleted all nodes but still won't delete from PG3. Thanks for any assistance.

Just now I received the message on the AC that update packages are available for you system. Shortly after it showed the message "Event received for a different subscription. Restart." I was able to OK the update message and not do a package update. Seemed to go back to normal operation. One thing I did notice is that it started a new AC session which I canceled. Then back to normal. I did have the AC running for quite awhile but never seemed to be a problem in the past or in version 5.5.6. This is what showed from the URL after the messages. There seems to be a pattern. Bringing up the AC I get the update package message and then the event received message and the start of a new AC session asking for a logon. I found that if I OK the "update packages" immediately I then don't get the the "event message' or request for a new login. All is OK after that. Thanks. <Subscriptions> <Sub isExpired="yes" isPortal="no" sid="-1" sock="-1" isReusingSocket="no" isConnecting="no"/> <Sub isExpired="no" isPortal="no" sid="35" sock="31" isReusingSocket="yes" isConnecting="no"/> <Sub isExpired="yes" isPortal="no" sid="27" sock="19" isReusingSocket="yes" isConnecting="no"/> <Sub isExpired="yes" isPortal="no" sid="-1" sock="-1" isReusingSocket="no" isConnecting="no"/> <Sub isExpired="no" isPortal="yes" sid="0" sock="30" isReusingSocket="no" isConnecting="no"/> <Sub isExpired="yes" isPortal="no" sid="29" sock="28" isReusingSocket="yes" isConnecting="no"/> <Sub isExpired="yes" isPortal="no" sid="-1" sock="-1" isReusingSocket="no" isConnecting="no"/> <Sub isExpired="yes" isPortal="no" sid="-1" sock="-1" isReusingSocket="no" isConnecting="no"/> <Sub isExpired="yes" isPortal="no" sid="-1" sock="-1" isReusingSocket="no" isConnecting="no"/> <Sub isExpired="yes" isPortal="no" sid="-1" sock="-1" isReusingSocket="no" isConnecting="no"/> After last episode: <Subscriptions> <Sub isExpired="yes" isPortal="no" sid="-1" sock="-1" isReusingSocket="no" isConnecting="no"/> <Sub isExpired="yes" isPortal="no" sid="35" sock="31" isReusingSocket="yes" isConnecting="no"/> <Sub isExpired="yes" isPortal="no" sid="36" sock="32" isReusingSocket="yes" isConnecting="no"/> <Sub isExpired="no" isPortal="no" sid="37" sock="33" isReusingSocket="yes" isConnecting="no"/> <Sub isExpired="no" isPortal="yes" sid="0" sock="30" isReusingSocket="no" isConnecting="no"/> <Sub isExpired="yes" isPortal="no" sid="29" sock="28" isReusingSocket="yes" isConnecting="no"/> <Sub isExpired="yes" isPortal="no" sid="-1" sock="-1" isReusingSocket="no" isConnecting="no"/> <Sub isExpired="yes" isPortal="no" sid="-1" sock="-1" isReusingSocket="no" isConnecting="no"/> <Sub isExpired="yes" isPortal="no" sid="-1" sock="-1" isReusingSocket="no" isConnecting="no"/> <Sub isExpired="yes" isPortal="no" sid="-1" sock="-1" isReusingSocket="no" isConnecting="no"/> </Subscriptions>

I have the UD Mobil app but haven't used it for quite awhile. 14 Node Servers. This mostly occurs randomly. Was also getting the 'package update available for your system' after bringing up the AC. So far I did another package update and cleared Java. Will need to see if anything made a difference. The package update messages after bringing up the AC seemed to have stopped after doing the package update. Maybe a connection? Thanks