dbwarner5

Thanks. I opened a ticket to understand what these errors mean as this seems to be the original of the problem: 5/30/2023, 09:19:59 [pg3] error: uncaughtException: read ECONNRESET Error: read ECONNRESET at TCP. onStreamRead (node: internal/stream_base_commons:217:20) 5/30/2023, 09:19:59 [pg3] error: uncaught ECONNRESET exception: Error: read ECONNRESET at TCP.onStreamRead (node: internal/stream_base_commons:217:20) 5/30/2023, 09:19:59 [pg3] info: Caught SIGTERM/SIGINT Shutting down. 5/30/2023, 09:19:59 [pg31 info: Stopping running NodeServers...

Wow.. that's a huge bummer. I wish I had known before I did the "upgrade" (whenever pg2 disappeared) as this is clearly a downgrade losing pg2 RussoundRIO. I have migrated all my other NS to PG3/X and am happily supporting the developers, but this is a very unpleasant surprise as I have lots of things tied into my whole house audio system via the RussoundRIO NS. @bpwwer hope things can settle down enough for you to port this over! let me know if you need test cases. Thanks.

@bpwwer Bob, a separate question, I did the upgrade from PG3 to PGX. Now my one RussoundRIO NS on PG2 is no longer working and I can no longer access PG2.. was this a result of the upgrade or is it something else? Best solution is to port RussoundRIO to PG3/X but havent see that addressed yet. thanks.

Ok Thanks Bob. I will keep an eye on it and maybe reboot the Polisy one more time. What is also interesting is that it is almost instantaneous that it shuts down and then starts the restart procedure. If it persists, will open ticket. Regards...

@bpwwer yes i get all of the above. What i dont get is why is PGx telling the NS to shut down? I am not telling it to do anything. These disconnects, reconnects, as shown on the logs appear to be directed by Stopped by Polyglot. Why?

@bpwwer Here are my PGx and system logs in case that would help? pg3_5-26-2023_62259-PM.zipsystem_5-26-2023_62303-PM.zip

This is happening to me as well. PGx ... today alone, I have 79 messages of connect / reconnects... ~15 messages per event, had three disconnects, but only two connects: two disconnects happened back to back w/o reporting the connect. Any suggestions of why or what to look for to solve on my end would be great, as well as @BigMojos suggestion? However notice the log from Sun NS. Time corresponds with notification exactly: 2023-05-26 13:59:57,575 Command udi_interface.interface INFO interface:_handleInput: Received stop from Polyglot... Shutting Down. 2023-05-26 13:59:57,586 Command udi_interface.interface INFO interface:stop: Disconnecting from MQTT... localhost:8883 2023-05-26 13:59:57,588 Command udi_interface.interface INFO interface:_disconnect: MQTT Graceful disconnection. 2023-05-26 14:00:25,539 MainThread udi_interface INFO polylogger:set_basic_config: set_basic_config: enable=True level=30 2023-05-26 14:00:31,870 MainThread udi_interface INFO __init__:<module>: UDI Python Interface for Polyglot version 3 3.0.59 Starting... 2023-05-26 14:00:32,204 MainThread udi_interface.interface INFO interface:__init__: Initialization received from Polyglot V3 3.1.27 [ISY: 5.6.0, Slot: 7] 2023-05-26 14:00:32,208 MainThread udi_interface.interface INFO interface:__init__: Connect: Network Interface: {'addr': '192.168.68.76', 'netmask': '255.255.252.0', 'broadcast': '192.168.71.255'} 2023-05-26 14:00:32,314 Interface udi_interface.interface INFO interface:_startMqtt: Connecting to MQTT... localhost:8883 2023-05-26 14:00:32,416 Interface udi_interface.interface INFO interface:_startMqtt: Using SSL certs: 000db9532a30_7.cert 000db9532a30_7.key 2023-05-26 14:00:32,480 MQTT udi_interface.interface INFO interface:_connect: MQTT Connected with result code 0 (Success) 2023-05-26 14:00:32,482 MQTT udi_interface.interface INFO interface:_connect: MQTT Subscribing to topic: udi/pg3/ns/clients/00:0d:b9:53:2a:30_7 - MID: 2 Result: 0 2023-05-26 14:00:32,526 MQTT udi_interface.interface INFO interface:_subscribe: MQTT Subscribed Succesfully for Message ID: 2 - QoS: (0,) 2023-05-26 14:00:32,573 MainThread udi_interface.interface WARNING interface:db_getNodeDrivers: sunctrl not found in database. 2023-05-26 14:00:32,577 MainThread udi_interface.interface INFO interface:addNode: Adding node Sun Position(sunctrl) [None] 2023-05-26 14:00:32,580 MainThread udi_interface.interface INFO interface:setController: Using node "sunctrl", driver "ST" for connection status. 2023-05-26 14:00:37,819 Thread-1 udi_interface.custom INFO custom:_save: Sending data notices to Polyglot. 2023-05-26 14:00:39,037 MQTT udi_interface.interface INFO interface:_message: Successfully set key = notices 2023-05-26 14:00:39,375 Thread-3 udi_interface INFO sun-poly:start: Started Sun Position And similar result from iAqualink: 2023-05-26 13:59:57,590 Command udi_interface.interface INFO interface:_handleInput: Received stop from Polyglot... Shutting Down. 2023-05-26 13:59:57,603 Thread-4848 udi_interface INFO iaqualinkns:stop: iAquaLink node server is shutting down... 2023-05-26 13:59:57,629 Thread-4848 udi_interface.node DEBUG node:setDriver: service:iAquaLink Service Reporting set ST to 0 to Polyglot 2023-05-26 13:59:57,630 Thread-4848 udi_interface.node DEBUG node:reportDriver: Updating value to 0 2023-05-26 13:59:57,632 Thread-4848 udi_interface.interface DEBUG interface:send: PUBLISHING {'set': [{'address': 'service', 'driver': 'ST', 'value': '0', 'uom': 2}]} 2023-05-26 13:59:57,634 Thread-4848 udi_interface.interface INFO interface:stop: Disconnecting from MQTT... localhost:8883 2023-05-26 13:59:57,637 Thread-4848 udi_interface.interface INFO interface:_disconnect: MQTT Graceful disconnection. 2023-05-26 13:59:57,640 MQTT udi_interface.interface DEBUG interface:_startMqtt: MQTT: Done 2023-05-26 14:00:30,419 MainThread udi_interface INFO polylogger:set_basic_config: set_basic_config: enable=True level=30 2023-05-26 14:00:38,157 MainThread udi_interface INFO __init__:<module>: UDI Python Interface for Polyglot version 3 3.0.59 Starting... 2023-05-26 14:00:38,240 MainThread udi_interface.interface INFO interface:__init__: Initialization received from Polyglot V3 3.1.27 [ISY: 5.6.0, Slot: 10] 2023-05-26 14:00:38,253 MainThread udi_interface.interface INFO interface:__init__: Connect: Network Interface: {'addr': '192.168.68.76', 'netmask': '255.255.252.0', 'broadcast': '192.168.71.255'} 2023-05-26 14:00:38,254 MainThread udi_interface INFO iaqualinkns:run: Starting iAquaLink node server...

did the above. no problems. gave it plenty of time to reboot. Just completed second reboot. all looks good with one exception: -Notification NS is now asking for a Portal API. didnt know what this was, but here is the info for anyone else.

Thanks, cant do it tonight though, but will try in the next few days.

are you on a Mac? I am using safari on a Mac and am wondering if that could be the cause?

Thanks.. loaded the https page.. received this response: <This XML file does not appear to have any style information associated with it. The document tree is shown below.> Nothing was below. I rebooted PG3 several times, with long delays in between. Not sure how to tell if anything happened as it's still showing PG3 Version 3.1.21 on the main screen. I went into AC and did another package upgrade. nothing happened. Do I need to reboot the whole Polisy for PGx to take affect? (Reboot and wait for a beep + 1.) Am also seeing the following in the log, not sure if it's related or not. 16:44:34 [pg3] warn: MQTTS: keepaliveTimeout: pg3frontend_z8ggT 5/23/2023, 16:44:34 [pg3] error: MQTTS: clientError: pg3frontend_z8ggT keep alive timeout 5/23/2023, 16:44:34 [pg3] info: MQTTS: Client Disconnected: pg3frontend_z8ggT 5/23/2023, 16:44:39 [pg3] info: MQTTS: Client Connected: pg3frontend_z8ggT Thanks.

@bpwwer Bob, in the announcement you mention that you can. convert from PG3 to PG3x on Polisy. How is this done? When I click on the upgrade packages, it just takes me to the next level of PG3. Thanks.

Maybe a simple interim answer would be to have 'admin' type of postings for releases for each NS section of the forum so at least there is a place to validate each one?

It would be nice if there was a way to see all the current versions of each node server on the list of either the store or purchases so that I know which node servers need to be restarted / reinstalled to update them w./o having to go look at each one, note its version, and then go back to the store and click through to find the current version. The updates aren't happening very well. For example, just looked at my Weatherflow NS. it was one version behind, even though I have recently updated packages, restarted, IOX, restarted PG3 several time. Am I missing something? thanks.

Will check the log when I get a chance. It literally drops and picks back up at the same clock time which to (possibly wrong assumption) that it isn’t cable or hardware related

I understand that during Portal maintenance periods, my Polisy will briefly disconnect and reconnect. However if you look at the image below, these times / dates don't directly correlate with the maintenance periods. Is this anything to be concerned about ? why is it happening? Thanks.

Have you looked at the Notification Node server? I use it to successfully send variables. Here is the link to the readme on the NS. if you scroll down, it gives multiple examples. https://github.com/UniversalDevicesInc-PG3/udi-poly-notification/blob/master/README.md

If if remember correctly, there was only one node, not the three that are there now. And if you click on users, a four box dialogue would open: Set User, Set Time, Set Schedule and Enable Schedule. You could then set the day, hour period for any user, the time, and enable or disable the schedule.

I have three of the Yale YRD 120 zwave. Just tested to be sure, but they work as expected with Alexa replying “the front door is locked” The only thing that has changed since all the updates / conversion to zmatter is that i have lost the ability to put a schedule on the users. That option has disappeared in the AC I used this feature with service people to ensure they only can get in when i allow it ie garbage collection in the garage on tuesday mornings. @Chris Jahn any thoughts on this missing component in the AC? Thaniks

Upgraded w/o any issues. Very smooth, just took time. Thanks @bpwwer

@ShawnW The above outline from @oberkc is a great approach. As he mentioned there are many different ways to accomplish this, but his outline is very straight forward and right on. If you need further help with the actual programs as you develop them, feel free to post them by right clicking on them and at the bottom of the pop up menu, select copy to clipboard. That will paste the actual syntax of the program into this forum. good luck!

Have you tried to unplug it, wait 60 seconds and plug it back in? (POWER)

This is the "trick" that experienced programmers miss with ISY state related programming. The IF statement will be evaluated ANYTIME one of the if condition's state changes. In this case, the light changing states causes the program to be evaluated and the result is FALSE, because the time condition in the IF is not met. The easiest way to test this and verify it is to simply turn the light on during the day. You should see that every time you turn the light on or off, (the state of the light changed), the IF will be evaluated and the program will run, resulting in a FALSE condition. The time in the status time should match exactly when you turn the light on or off. Cheers.

Any time this light is turned on or off, ie: the state of the light changed, this program will run because evaluating the state of the light is part of the IF. And subsequently, if the time is outside of your designated window, it will be false.

Hi Bob, I know you continue to be swamped with all the current release issues. Just Fyi, my russound MCA-88 continues to crash / lock up about once every 3-4 weeks. Am not sure if it's the NS or something else. I have attached my log fyi. It looks like all was fine at 3am when the system query ran, but then I have the following program that runs at 4am, and it looks like the Russound went down. Not sure which event caused it, if either. FYI for when you get around to converting the NS from PG2 to PG3. Thanks! Doug Rus Reset all to A - [ID 02ED][Parent 02EC] If Time is 4:05:00AM Then Set 'RussoundRIO / Bedroom Sound' Source Source 1 Wait 5 seconds Set 'RussoundRIO / Bedroom Sound' Zone Off Wait 5 seconds Set 'RussoundRIO / Deck Sound' Source Source 1 Wait 5 seconds Set 'RussoundRIO / Deck Sound' Zone Off Wait 5 seconds Set 'RussoundRIO / Game Room Sound' Source Source 1 Wait 5 seconds Set 'RussoundRIO / Game Room Sound' Zone Off Wait 5 seconds Set 'RussoundRIO / Garage Sound' Source Source 1 Wait 5 seconds Set 'RussoundRIO / Garage Sound' Zone Off Wait 5 seconds Set 'RussoundRIO / Kitchen Sound' Source Source 1 Wait 5 seconds Set 'RussoundRIO / Kitchen Sound' Zone Off Wait 5 seconds Set 'RussoundRIO / Laundry Room Sound' Source Source 1 Wait 5 seconds Set 'RussoundRIO / Laundry Room Sound' Zone Off Wait 5 seconds Set 'RussoundRIO / Screened Porch Sound' Source Source 1 Wait 5 seconds Set 'RussoundRIO / Screened Porch Sound' Zone Off Wait 5 seconds Set 'RussoundRIO / Sunroom Sound' Source Source 1 Wait 5 seconds Set 'RussoundRIO / Sunroom Sound' Zone Off RussoundRIO_logs_2-21-2023_105846_AM.zip RussoundRIO_2-21-2023_114606_AM.txt