dbwarner5

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

@pjjameso If you need help setting this up the first time feel free to ask. It can be a bit confusing. At times there seems to be a bit of a circular path that can get confusing. The above may be overkill as you can simply put the Keypad button into the portal as a Scene to Alexa. Then within Alexa, write a routine that when that scene is on, open the shade, when off, close the shade. But another question for you would be, unless you plan to use the ISY to control the shades via time / sun position etc, if you just want to open and close them, you can just do that directly with Alexa , w/o involving the ISY. On the other hand, if want full integration with ISY, then you need to set up the keypad button scene to stay in sync with Alexa per my suggestion above, and then you can use the ISY to control the blinds, either via directly with the keypad or indirectly with programs.

@ShawnWJavi did a great job of pointing out the pros and cons. However, since the biggest con of an ISY based security is its overall lack of true security protocols, I wouldn't hesitate to use one of your 6 button keypads, where the letter D, becomes Disarm. I use an elk system, and yes I have keypads by the proper doors, but I also have 3 keypads where I can press the D to disarm the alarm. I would highly doubt anyone who breaks into your house would know that those buttons will do what they will do. My view is that I am trying to accomplish the following: -Ease of disarm for visitors and wife -Protect through sirens/ etc the average burglar and inform me of any intrusion -NOT protect me against a professional burglar who really thinks I have something of value other than household goods. The programs that I have follow the protocols below: -Who unlocks the door via zwave lock--> category 1: me and wife, cat 2, long term visitor (kids), cat 3, short term visitors like a cat sitter or plant waterer, or good friend dropping something off etc. -Based on the above category of user the following happens: Cat 1: Disarm, turn on lights if dark, turn on water pump, unlock several doors, turn on heat, etc. Cat 2: similar to cat 1 but more general lighting. Cat 3: lots of lights, inside and out, water pump on, disarm, then watch for the door to be locked again via the touchpad and then re-arm the system, turn off water pump, eventually turn off the lights, leave heat alone. I init the security status type (home away, home cat, etc) so I know how to set it back when needed. Lastly, if the security is set at Home, and I need to get up and let the cat in at 2am (ugh!), I simply press the D on my keypad near my bed, and the security goes off, and then if I press the D again within 15 minutes, the security re-arms. Security gets armed at night through an Alex command of Goodnight, with runs ISY programs that controls lights for getting ready for bed adn then 10-15 minutes later sets up nightlights around the house and monitors all lights to reset them back to nightlight setting after 20 minutes if someone gets up and leaves a light on, thermostat adjustments, outside lights adjust etc. When we leave for vacation etc, I use UD Mobile where I have a program for each state I want the elk to go into on my favorites page. Hope this gives you some ideas!

lol.. I am not sure.. it always seems like the initial is 4 +1.. in this instance when I clicked on upgrade packages, I got one beep... long pause (30-60 seconds ) two (or three) more beeps that were slow... then after another few minutes I got the 4 (+1) beeps. that is when I unplugged it and rebooted it.. During the reboot, fairly soon into it, I got another 4 beeps.

@macjeffJust finished the upgrade. My z-wave devices took a while to populate and then still a few would not populate all fields: locks and thermostat. I restarted the AC and now they are all working as expected. One oddity was that after the four beeps, I unplugged the Polisy, and replugged it in. Shortly after I got four more beeps. But everything including NS all started up and are reporting correctly.

May have spoke too soon. Since that last post, the IoX has rebooted 3 times. All three times I have been experimenting with the File / Themes / Theme size option. Each time I change it, it asks me to quit the AC. Per earlier posts, I was careful to only quit the AC via the File / Exit command versus Command Q (on Mac). However upon restarting the AC, all nodes were empty, as the IoX was going through a start up process. After 10 minutes, all is running again. Strange. Not sure what triggered the reboots; The quitting of the AC or the change of the theme size. Cheers.

My upgrade from 5.5.5 to 5.5.6 experience on IoX Polisy -Loaded AC and clicked on upgrade packages. Polisy acted as expected.. beeps, etc, unplugged and restarted it. -Loaded AC and found none of my PG3 nodes were connecting. Also I could not locally connect to PG3. It was unresponsive. Pg2 however was working just fine. -Unplugged Polisy, let it reboot. Still no PG3 -Loaded AC again and hit upgrade packages a SECOND TIME. Never heard any beeps etc, however after a delay PG3 was working again. Ecobee NS had to be manually restarted. ST inventory would not connect to AC. Reloaded AC, after a delay, everything is working just as expected. Now on 5.5.6 and all NS running.

Two cents on this: 1) for IoX Launcher, after you have added all the routes you may want (http://xxx.xxx.xx.xx:8080, https://my.isy.io/isy/xxxxxxx, and https://xxx.xxx.xx.xx:8443), then save it to an easy location.. Any time they dont come up, just hit load and choose the file you saved, 2) Avoid all of the above by going to http://xxx.xxx.xx.xx:8080/admin.jnlp in your browser and a file will download that will immediately take you to your isy w/o having to rely on anything els. (all xx's are your local ip address for your IoX.)

Only issue noticed is a mismatch of ISY firmware between IoX and PG3, on Polisy. Doesn't seem to be affecting anything though. Have restarted PG3. No change.

try typing this into your browser, replacing the x's with your isy address. it should download a local JAVA file that should access it. Be sure to clean out your JAVA cache first. http://x.x.x.x:8080/admin.jnlp