garybixler

My issue has been solved by reinstalling Java. Upgrading from Win 10 to Win 11 seemed to cause problems for Java. Also i think the original Win 10 version of Java was 32 bit. But after installing a new Java App all is working great.

I think my issue has to do with my desk top PC upgraded to W-11 or the latest Java update. When using my lap top PC everything works fine. Lap top is also W-11 so no clue why the difference. Thanks

After upgrading to 5.7.1 on IoX and PG3 the AC is hanging when in the programs screen. Sometimes while loading. Tried package updates and power reboots but always the same. Tried deleting Java files several times. I have to use Task Manager to end task. Was there anything else needed to be upgraded besides packages like bios? Hanging at Create Scene Widgets.

I am finding that it does work. I needed to select off even though it showed off as selected before clicking Party Mode. So if I select On and click the Party Mode button it does go into party mode. Then selecting Off and clicking the PM button it will go off. Thanks so much for all the added features. Gary

Testing with Network Resources I found that this command did turn on party mode with that zone becoming the master. EVENT C[1].Z[3]!PartyMode ON\r

After looking more closely a space may be needed after the OFF in the event command. 2023-10-09 20:05:12,208 Command udi_interface DEBUG russound_main:Send: RIO: Sending b'EVENT C[1].Z[3]!PartyMode OFF\r\n'

Also if party mode was started on another zone the party mode off doesn't seem to work. This was the log. 023-10-09 20:05:12,207 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message command 2023-10-09 20:05:12,207 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING command 2023-10-09 20:05:12,208 Command udi_interface DEBUG zone:process_cmd: ISY sent: {'address': 'zone_1_3', 'cmd': 'PARTY', 'value': '0', 'uom': '25', 'query': {}} 2023-10-09 20:05:12,208 Command udi_interface DEBUG russound_main:set_param: sending Zone:C[1].Z[3] level:0 2023-10-09 20:05:12,208 Command udi_interface DEBUG russound_main:Send: RIO: Sending b'EVENT C[1].Z[3]!PartyMode OFF\r\n'

All seems to work except party mode. I captured the log when party mode was set to on. I think what may be missing is the master choice. On the keypad you click master to start party mode from that zone. On other zones if party mode is active you can choose master or off. If a zone's party mode is already off you can then choose on to join party mode. I think this should work. EVENT C[1].Z[3]!PartyMode master \r Thanks Gary 2023-10-09 19:16:02,140 MQTT udi_interface.interface INFO interface:_message: Successfully set zone_2_8 :: ST to 1 UOM 25 2023-10-09 19:16:10,266 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message command 2023-10-09 19:16:10,266 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING command 2023-10-09 19:16:10,266 Command udi_interface DEBUG zone:process_cmd: ISY sent: {'address': 'zone_1_3', 'cmd': 'PARTY', 'value': '1', 'uom': '25', 'query': {}} 2023-10-09 19:16:10,266 Command udi_interface DEBUG russound_main:set_param: sending Zone:C[1].Z[3] level:1 2023-10-09 19:16:10,266 Command udi_interface DEBUG russound_main:Send: RIO: Sending b'EVENT C[1].Z[3]!PartyMode ON\r\n'

@dbwarner5 Thanks that also works well for changing volume level.

When selecting party mode on a zone keypad the only choice was master unless party mode is already active then each zone can individually turn off party mode or become the master. I think On Off is to join or leave party mode.

I used this command to set Z3 as the master in partymode. All the zones turned on and followed what source is selected on zone 3. EVENT C[1].Z[3]!PartyMode master \r This command turned party mode off. All the zones then turned off. EVENT C[1].Z[3]!PartyMode off \r

I have tested these commands in Network Resources for all ON/OFF and Volume UP/DOWN. EVENT C[1].Z[1]!AllOn \r EVENT C[1].Z[1]!AllOff \r Also it would be nice to be able to raise and lower the volume. EVENT C[1].Z[${var.1.6}]!KeyPress VolumeDown \r EVENT C[1].Z[${var.1.6}]!KeyPress VolumeUp \r I used variable in the Vol UP/DOWN to limit repeated commands in Network Resources. Thanks Gary

HI, just a request for features that maybe added in the future to the RIO protocol. Party Mode and All Zones ON/OFF. There is a party mode button but it doesn't seem to work. It always returns an off state. Thanks for any consideration for the requests. Gary

Updated to 2.1.6 and all is good now. Thanks

Hi, Just installed update 2.1.5 for the MCA series and all seems good except the return of a source selection shows the lower adjacent source. For example selecting source 3 will show source 2 selected but source 3 will be active. Thanks Gary

After doing some testing the position of the Sunset Sunrise statement didn't really mater.

Just something to try. I have similar programs and they perform as expected. The only difference is that I have the Sunset Sunrise schedule first. Garage Lights 1 - [ID 001F][Parent 000F] If From Sunset To Sunrise (next day) And 'ELK / Area 1 / Driveway Sense' Logical Status is Violated And 'Outside Garage Lights' Status is Off Then Run Program 'Garage Lights on/off' (Then Path) Else - No Actions - (To add one, press 'Action') Also I might suggest putting the 'Set 'Entry Front Door Light' On' last.

All nodes now connected. Thanks

The previous version. I think it was 3.2.2 and 3.2.1 before that

Log from PGx 9/2/2023, 14:13:42 [pg3] info: Verifying node servers are installed on IoX correctly 9/2/2023, 14:13:42 [pg3] info: IoX Request: [Try: 1] [00:21:b9:02:60:38] :: - http://127.0.0.1:8080/rest/profiles/ns/1/connection 9/2/2023, 14:13:42 [pg3] info: IoX Response: [Try: 1] [00:21:b9:02:60:38] :: [200] :: 21.203976ms - http://127.0.0.1:8080/rest/profiles/ns/1/connection 9/2/2023, 14:13:42 [pg3] info: IoX entry for WeatherLink::1 OK 9/2/2023, 14:13:42 [pg3] info: IoX Request: [Try: 1] [00:21:b9:02:60:38] :: - http://127.0.0.1:8080/rest/profiles/ns/2/connection 9/2/2023, 14:13:42 [pg3] info: IoX Response: [Try: 1] [00:21:b9:02:60:38] :: [200] :: 9.988015ms - http://127.0.0.1:8080/rest/profiles/ns/2/connection 9/2/2023, 14:13:42 [pg3] info: IoX entry for VenstarCT::2 OK 9/2/2023, 14:13:42 [pg3] info: IoX Request: [Try: 1] [00:21:b9:02:60:38] :: - http://127.0.0.1:8080/rest/profiles/ns/3/connection 9/2/2023, 14:13:42 [pg3] info: IoX Response: [Try: 1] [00:21:b9:02:60:38] :: [200] :: 2.175943ms - http://127.0.0.1:8080/rest/profiles/ns/3/connection 9/2/2023, 14:13:42 [pg3] info: IoX entry for WirelessTag::3 OK 9/2/2023, 14:13:42 [pg3] info: IoX Request: [Try: 1] [00:21:b9:02:60:38] :: - http://127.0.0.1:8080/rest/profiles/ns/4/connection 9/2/2023, 14:13:42 [pg3] info: IoX Response: [Try: 1] [00:21:b9:02:60:38] :: [200] :: 3.467582ms - http://127.0.0.1:8080/rest/profiles/ns/4/connection 9/2/2023, 14:13:42 [pg3] info: IoX entry for Notification::4 OK 9/2/2023, 14:13:43 [pg3] info: IoX Request: [Try: 1] [00:21:b9:02:60:38] :: - http://127.0.0.1:8080/rest/profiles/ns/5/connection 9/2/2023, 14:13:43 [pg3] info: IoX Response: [Try: 1] [00:21:b9:02:60:38] :: [200] :: 2.120451ms - http://127.0.0.1:8080/rest/profiles/ns/5/connection 9/2/2023, 14:13:43 [pg3] info: IoX entry for Wemo::5 OK 9/2/2023, 14:13:43 [pg3] info: IoX Request: [Try: 1] [00:21:b9:02:60:38] :: - http://127.0.0.1:8080/rest/profiles/ns/6/connection 9/2/2023, 14:13:43 [pg3] info: IoX Response: [Try: 1] [00:21:b9:02:60:38] :: [200] :: 2.248131ms - http://127.0.0.1:8080/rest/profiles/ns/6/connection 9/2/2023, 14:13:43 [pg3] info: IoX entry for WeatherBit::6 OK 9/2/2023, 14:13:43 [pg3] info: IoX Request: [Try: 1] [00:21:b9:02:60:38] :: - http://127.0.0.1:8080/rest/profiles/ns/7/connection 9/2/2023, 14:13:43 [pg3] info: IoX Response: [Try: 1] [00:21:b9:02:60:38] :: [200] :: 2.066712ms - http://127.0.0.1:8080/rest/profiles/ns/7/connection 9/2/2023, 14:13:43 [pg3] info: IoX entry for LiFX::7 OK 9/2/2023, 14:13:43 [pg3] info: IoX Request: [Try: 1] [00:21:b9:02:60:38] :: - http://127.0.0.1:8080/rest/profiles/ns/8/connection 9/2/2023, 14:13:43 [pg3] info: IoX Response: [Try: 1] [00:21:b9:02:60:38] :: [200] :: 6.318889ms - http://127.0.0.1:8080/rest/profiles/ns/8/connection 9/2/2023, 14:13:43 [pg3] info: IoX entry for iTach-IR::8 OK 9/2/2023, 14:13:43 [pg3] info: IoX Request: [Try: 1] [00:21:b9:02:60:38] :: - http://127.0.0.1:8080/rest/profiles/ns/9/connection 9/2/2023, 14:13:43 [pg3] info: IoX Response: [Try: 1] [00:21:b9:02:60:38] :: [200] :: 2.299228ms - http://127.0.0.1:8080/rest/profiles/ns/9/connection 9/2/2023, 14:13:43 [pg3] info: IoX entry for iTach-IR::9 OK 9/2/2023, 14:13:43 [pg3] info: IoX Request: [Try: 1] [00:21:b9:02:60:38] :: - http://127.0.0.1:8080/rest/profiles/ns/10/connection 9/2/2023, 14:13:43 [pg3] info: IoX Response: [Try: 1] [00:21:b9:02:60:38] :: [200] :: 2.103385ms - http://127.0.0.1:8080/rest/profiles/ns/10/connection 9/2/2023, 14:13:43 [pg3] info: IoX entry for Bond::10 OK 9/2/2023, 14:13:43 [pg3] info: IoX Request: [Try: 1] [00:21:b9:02:60:38] :: - http://127.0.0.1:8080/rest/profiles/ns/11/connection 9/2/2023, 14:13:43 [pg3] info: IoX Response: [Try: 1] [00:21:b9:02:60:38] :: [200] :: 2.026874ms - http://127.0.0.1:8080/rest/profiles/ns/11/connection 9/2/2023, 14:13:43 [pg3] info: IoX entry for Russound::11 OK 9/2/2023, 14:13:43 [pg3] info: IoX Request: [Try: 1] [00:21:b9:02:60:38] :: - http://127.0.0.1:8080/rest/profiles/ns/12/connection 9/2/2023, 14:13:43 [pg3] info: IoX Response: [Try: 1] [00:21:b9:02:60:38] :: [200] :: 3.36697ms - http://127.0.0.1:8080/rest/profiles/ns/12/connection 9/2/2023, 14:13:43 [pg3] info: IoX entry for TeslaEV::12 OK 9/2/2023, 14:13:43 [pg3] info: IoX Request: [Try: 1] [00:21:b9:02:60:38] :: - http://127.0.0.1:8080/rest/profiles/ns/13/connection 9/2/2023, 14:13:43 [pg3] info: IoX Response: [Try: 1] [00:21:b9:02:60:38] :: [200] :: 2.093063ms - http://127.0.0.1:8080/rest/profiles/ns/13/connection 9/2/2023, 14:13:43 [pg3] info: IoX entry for AVRemote::13 OK 9/2/2023, 14:13:43 [pg3] info: IoX Request: [Try: 1] [00:21:b9:02:60:38] :: - http://127.0.0.1:8080/rest/profiles/ns/14/connection 9/2/2023, 14:13:43 [pg3] info: IoX Response: [Try: 1] [00:21:b9:02:60:38] :: [200] :: 2.216399ms - http://127.0.0.1:8080/rest/profiles/ns/14/connection 9/2/2023, 14:13:43 [pg3] info: IoX entry for ELK::14 OK 9/2/2023, 14:13:43 [pg3] info: IoX Request: [Try: 1] [00:21:b9:02:60:38] :: - http://127.0.0.1:8080/rest/profiles/ns/15/connection 9/2/2023, 14:13:43 [pg3] info: IoX Response: [Try: 1] [00:21:b9:02:60:38] :: [200] :: 2.125973ms - http://127.0.0.1:8080/rest/profiles/ns/15/connection 9/2/2023, 14:13:43 [pg3] info: IoX entry for iTach-IR::15 OK 9/2/2023, 14:13:43 [pg3] info: IoX Request: [Try: 1] [00:21:b9:02:60:38] :: - http://127.0.0.1:8080/rest/profiles/ns/0/connection 9/2/2023, 14:13:43 [pg3] info: IoX Response: [Try: 1] [00:21:b9:02:60:38] :: [200] :: 2.447125ms - http://127.0.0.1:8080/rest/profiles/ns/0/connection

just updated to 3.2.3 and none of the node servers are connecting. Tried reloading packages, reloaded all server, rebooted several times but servers will not connect. All have these messages in the log. IoX version 5.6.4 023-09-02 14:04:47,331 MainThread udi_interface INFO polylogger:set_basic_config: set_basic_config: enable=True level=30 2023-09-02 14:04:48,633 MainThread udi_interface INFO polylogger:set_basic_config: set_basic_config: enable=True level=30 2023-09-02 14:04:50,318 MainThread udi_interface INFO polylogger:set_basic_config: set_basic_config: enable=True level=30 2023-09-02 14:04:52,331 MainThread udi_interface INFO polylogger:set_basic_config: set_basic_config: enable=True level=30 2023-09-02 14:04:54,262 MainThread udi_interface INFO polylogger:set_basic_config: set_basic_config: enable=True level=30 2023-09-02 14:04:56,512 MainThread udi_interface INFO polylogger:set_basic_config: set_basic_config: enable=True level=30 2023-09-02 14:04:58,824 MainThread udi_interface INFO polylogger:set_basic_config: set_basic_config: enable=True level=30

Will this NS be able to communicate directly to a station like the new Weatherlink Console? Thanks Gary

@DennisC, Thanks for the info. I haven't been following the threads very close lately. I am giving that a try and hopefully that will fix the issue. Thanks Gary

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