garybixler

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

I got this message again while AC was open. Didn't do a restart but closed and reopened the AC. Seems OK for now. This just started in the last few days. eisy 5.5.7

Been running 5.5.6 for many days now with no issues. Just discovered that I could not log into PG3x. Logged into eisy and saw the message about upgraded packages available for your system so I did the Upgrade Packages. Still was unable to log into PG3x and eisy didn't reboot. Tried a system hard shutdown (6 button push) but that did not work. Had to do a power off/on reboot and now all is good again.

I have a couple of devices that offer MQTT integration and was wondering if they could be added to PG3x? One is Genmon that has an MQTT addon. Thanks

Got through the upgrade from 5.5.5 to 5.5.6 on the eisy with a few reboots. While the AC was open and 4 hrs. later I get the message "Event received for a different subscription restart" and the eisy rebooted. Any ideas what this may be about? Thanks

Just received the dingtian sdk relay switch module. Looks like all the info is included for any type of communications. I think it would be a great NS. Total zip file is 47 MB so it can't seem to be able to be attached. Just wondering if there may be any interest. The zip file can be found here. https://dingtian-tech.com/sdk/relay_sdk.zip

Good Idea. Maybe do "Whenever Output XX is turned on" "Then Disable NON-Alarm Voice Messages" . Good Idea I am going to give it a try and toggle or keep on a virtual output from the NS.

@bpwwer Hi, I upgraded to version 3.1.21 this morning and although I didn't notice any NSs stopping I did find that they did in the PG3x log. But automatically restarted. I attached the PG3x log. Thanks Node servers.txt

@bpwwerMy NSs are still stopping in the early afternoon and now in the early evening. I can not find any reason for this. The IoX is not doing anything at those times. Checked all the programs. I attached the PG3x log file but it just shows the same as before. I am now only running the essential NSs in hopes this can be narrowed down. It happened today at 1:35 PM and again at 7:07PM. I checked the IoX event viewer and nothing seemed to be a problem. This issue may have started after upgrading to 5.5.4. Can't be sure however. Also removed the latest updated Z-Wave devices. Node servers.txt

@bpwwerLast night it broke from the pattern and happened around 10:30:00 pm instead of early afternoon. At that time there would be nothing happening except receiving data from the NSs. I'll look for any correlations. Thanks

I needed to restart the LiFX node server after the SSH commands for it to discover the bulbs. Using the Re-Discover button didn't seem to work.

Pretty much this over and over before the servers were stopped. If it happens tomorrow I'll get a debug log. 1/20/2023, 13:08:37 [pg3] info: [00:21:b9:02:60:38_14] controller reporting command DOF 1/20/2023, 13:09:39 [pg3] info: [00:21:b9:02:60:38_3] wtcontroller reporting command DON 1/20/2023, 13:09:52 [pg3] info: [00:21:b9:02:60:38_4] controller reporting command DON 1/20/2023, 13:11:09 [pg3] info: [00:21:b9:02:60:38_12] controller reporting command DOF 1/20/2023, 13:12:37 [pg3] info: [00:21:b9:02:60:38_14] controller reporting command DON 1/20/2023, 13:12:44 [pg3] info: Verifying node servers are installed on IoX correctly 1/20/2023, 13:12:44 [pg3] info: IoX entry for WeatherLink::1 OK 1/20/2023, 13:12:44 [pg3] info: IoX entry for VenstarCT::2 OK 1/20/2023, 13:12:44 [pg3] info: IoX entry for WirelessTag::3 OK 1/20/2023, 13:12:44 [pg3] info: IoX entry for Notification::4 OK 1/20/2023, 13:12:44 [pg3] info: IoX entry for Wemo::5 OK 1/20/2023, 13:12:44 [pg3] info: IoX entry for WeatherBit::6 OK 1/20/2023, 13:12:44 [pg3] info: IoX entry for LiFX::7 OK 1/20/2023, 13:12:44 [pg3] info: IoX entry for iTach-IR::8 OK 1/20/2023, 13:12:44 [pg3] info: IoX entry for iTach-IR::9 OK 1/20/2023, 13:12:44 [pg3] info: IoX entry for Bond::10 OK 1/20/2023, 13:12:44 [pg3] info: IoX entry for TeslaEV::12 OK 1/20/2023, 13:12:45 [pg3] info: IoX entry for AVRemote::13 OK 1/20/2023, 13:12:45 [pg3] info: IoX entry for ELK::14 OK 1/20/2023, 13:12:45 [pg3] info: IoX entry for iTach-IR::17 OK 1/20/2023, 13:13:47 [pg3] info: [00:21:b9:02:60:38_14] zone_30 reporting command DON 1/20/2023, 13:14:04 [pg3] info: [00:21:b9:02:60:38_14] zone_30 reporting command DON 1/20/2023, 13:16:09 [pg3] info: [00:21:b9:02:60:38_12] controller reporting command DON 1/20/2023, 13:16:37 [pg3] info: [00:21:b9:02:60:38_14] controller reporting command DOF 1/20/2023, 13:17:44 [pg3] info: Verifying node servers are installed on IoX correctly 1/20/2023, 13:17:44 [pg3] info: IoX entry for WeatherLink::1 OK 1/20/2023, 13:17:44 [pg3] info: IoX entry for VenstarCT::2 OK

It seems to be happing around the same time everyday. Early afternoon. I'll look for any previous problem before the shutdowns. Thanks.

My Node Servers come to a stop for no reason that I am aware of. Need than to start back up one at a time. I captured the log when I think it happened. I changed it to debug so maybe better info if it happens again. So far seems to be daily since updating to 3.1.20. /20/2023, 13:35:23 [pg3] error: uncaughtException: read ECONNRESET Error: read ECONNRESET at TCP.onStreamRead (node:internal/stream_base_commons:217:20) 1/20/2023, 13:35:23 [pg3] error: uncaught ECONNRESET exception: Error: read ECONNRESET at TCP.onStreamRead (node:internal/stream_base_commons:217:20) 1/20/2023, 13:35:23 [pg3] info: Caught SIGTERM/SIGINT Shutting down. 1/20/2023, 13:35:23 [pg3] info: Stopping running node servers... 1/20/2023, 13:35:23 [pg3] info: [WeatherLink(1)]: Stopping Node Server 1/20/2023, 13:35:23 [pg3] info: [VenstarCT(2)]: Stopping Node Server 1/20/2023, 13:35:23 [pg3] info: [WirelessTag(3)]: Stopping Node Server 1/20/2023, 13:35:23 [pg3] info: [Notification(4)]: Stopping Node Server 1/20/2023, 13:35:23 [pg3] info: [Wemo(5)]: Stopping Node Server 1/20/2023, 13:35:23 [pg3] info: [WeatherBit(6)]: Stopping Node Server 1/20/2023, 13:35:23 [pg3] info: [LiFX(7)]: Stopping Node Server 1/20/2023, 13:35:23 [pg3] info: [iTach-IR(8)]: Stopping Node Server 1/20/2023, 13:35:23 [pg3] info: [iTach-IR(9)]: Stopping Node Server 1/20/2023, 13:35:23 [pg3] info: [Bond(10)]: Stopping Node Server 1/20/2023, 13:35:23 [pg3] info: [TeslaEV(12)]: Stopping Node Server 1/20/2023, 13:35:23 [pg3] info: [AVRemote(13)]: Stopping Node Server 1/20/2023, 13:35:23 [pg3] info: [ELK(14)]: Stopping Node Server 1/20/2023, 13:35:23 [pg3] info: [iTach-IR(17)]: Stopping Node Server 1/20/2023, 13:35:23 [pg3] info: Making reqeust to socket for /rest/pg3.stop.ns 1/20/2023, 13:35:23 [pg3] info: Making reqeust to socket for /rest/pg3.stop.ns 1/20/2023, 13:35:23 [pg3] info: Making reqeust to socket for /rest/pg3.stop.ns 1/20/2023, 13:35:23 [pg3] info: Making reqeust to socket for /rest/pg3.stop.ns 1/20/2023, 13:35:23 [pg3] info: Making reqeust to socket for /rest/pg3.stop.ns 1/20/2023, 13:35:23 [pg3] info: Making reqeust to socket for /rest/pg3.stop.ns