TJF1960

I am away from my office computer but if memory serves isn't there a PG3 node server called backup the does something like that?

Does this node server show data from all 16 C.T.'s if connected? Also, will it recognize the new smart plugs that Emporia sells now which also monitor power consumption? Thanks!

EOL likely meant some parts from the part manufacturers are at the end of their life for being manufactured. A while back I was repairing a SL and looking to order some parts for it and found some of the IC's were already out of production.

Hi @bpwwer, I was wondering if you were able to fix the Emporia node server on PG3? Am thinking about getting one, but whatever choice I make I would like it to be supported on IoP. Thanks! Tim

@brettaI'm too am sorry that you had problems as well.This forum is full of great people who would be willing to go to great lengths to help you out. UDI's customer support is beyond the best as well. I found them to be very responsive and on many occasions have gone above and beyond to help out. I'm not sure what's your basing your opinion on, but, it is your opinion And you know what they say about opinions... I could be reading more into it but my first thoughts after reading the last couple of your posts, if you approached Tech support support with the same chip on your shoulder that you seem to have on this forum then I don't blame them for cutting their losses with you. Likely the best $400 they ever spent.

Also if you married the PLM to your Polisy then ditched the Polisy and went back to the ISY994 then you will have to restore the PLM to the ISY994. In other words If you Restored a backup from ISY994 to the new Polisy, then hooked the PLM back up to the ISY994, then you need to restore the PLM back to the ISY994.

Has there been a change to program execution between 994 and IoP where on the 994, for instance, if running a query all devices the program would not execute the next line until the query had finished. It appears now in IoP the program no longer waits, it executes the query then moves on to the next line during the query. Has anyone else found this to be true. I imagine it has to do with the much faster processing speed of IoP? Thanks! Tim

Thank you all who have ported over they're node servers from PG2 To PG3. I am now fully PG3. The question is should I worry about shutting down PG2 or just leave it be?

Hi @bpwwer, just upgraded PG3 to v3.0.59, IoP is v5.4.3 and after reboot tried backup pg3, after 20 or so seconds the red banner appeared across the top saying it was disconnect. Let it alone to see if it would start up by itself again. After coming back 5 minutes later it indeed was working and was able to download the backup. But 8 of the 9 node servers reported in failed state. The backup file is huge again as it was a fer revs ago, 63,878kb. I currently have 9 node servers. Is this the new norm? If you need logs or anything else I am available. Thanks, Tim

@bpwwer, I looked back through previous backups, the last 3 were only 1kb files and likely are no good. Previous to March 6th the average backup file was around 90kb. Then on March 16th thru March 20th they averaged about 70,000kb. I am sorry, I have no idea what f/w each back up came from but there could have been about a 3-5 day leadtime from when you pushed a new version of pg3 to when I installed it. I believe it was during this time that the backup included logs(?). If it helps any, I have the following node servers on PG3: MQTT WeatherFlow Envisalink TimeData Notification MyQ ST-Inventory Kasa Wireless Tags

@bpwwer, is version 3.0.56 backup still backing up logs as well? I have just set all nodes to critical reporting in logs. What can I do to limit the logs if that is what is holding it up? Or could it be something else?

Hi @bpwwer, Was not sure where to post PG3 interface questions. On v3.0.56 and am unable to download a backup. Logs indicate starting backup and backup done but I get no notification on IE, Chrome or FireFox. Logs available just let me know where to send them. ISY v5.4.3 PG3 v3.0.56

Thank you for the help @bpwwer, I deleted Weatherflow from one slot and installed it in another in an attempt to test. I will have to wait until tomorrow for a value to be present in yesterday's eto in order to test again. I did notice Hubs Seconds Since Seen transferred to a variable just fine, just not yest. eto. Question, is there any way for yesterdays eto to carry thru a reboot? Also, now that I installed Weatherflow in a new slot, yesterdays eto is in mm not inches, how can I change this? Lastly, the bottom row on the 2nd picture, is there a way to be able to view the last three items on the screen? Thanks, Tim

Good catch @DennisC, thank you. @JimboAutomates, as Dennis pointed out, my log indicated 3.3.0 as well. Thanks! INFO Controller:handler_start: Started Notification Node server 3.3.0

Hi @JimboAutomates, same here, stuck at 3.2.4 Sent logs to your email. Thanks! Tim

Hi @bpwwer, Since switching to Weatherflow my eto values have not been working properly. ETO value is available from the admin console tree: So I set up a number of programs to copy the value to a variable at different times throughout the night like this: If Time is 1:00 AM Then $iEto_test6=Polyglot/weatherflow/yesterdays eto inches/day I found all the test variable values were all 0. Forcing a run then also returns a value of 0. Thanks, Tim

I just did as well. All seems right here as well.

Moving from PG2 to PG3 was pretty simple, all went well for me. If you decide to make the move but you are in a hurry, stop and do it another day, when you are in a hurry and pressed for time is when you will experience troubles. Backup PG2, PG3 and IoP. Take a screen shot of the config page in PG2 for Envisalink for use when updating the config page in PG3. Take a screenshot of the device tree in IoP, specifically Envisalink so that you can rename all the zones back to what you had named them previously. I decided to delete Envisalink from PG2 and install on PG3 to the same slot. After updating the new config in PG3 and letting it do its thing for a few minutes I opened the admin console, the new PG3 Envisalink had populated the device tree as expected. Open programs I only found 1 that needed attention, the program that monitors the panel battery. I expected this based on @Goose66 explanation in the first post. Even though only 1 program needed attention I noticed none of the programs were running true when they should have been. Opened a couple up, selected the first If line and hit update then save. That did the trick. I did a few more then decided to try a ISY reboot. This did the trick for the rest of the programs. All in all this was a much smoother transition that I was prepared for. All is working great! Thank you to @Goose66!! I hope the rest of you have the same or better results! Tim

Hi @brians, after looking at my programming and reading your response, we are basically doing the same thing. I had forgotten I had set up a state variable as well. I am sorry I shouldn't have responded without having the program at my fingertips but am glad you had figured it out. Nice job! Hi @Goose66, Not seeing "Alarm Restored" command in the Partition State field. Thanks, Tim

Hi @brians, I don't think the API includes a disarm node. I am away d from my ISY programs but I use something like this: If alarm panel is not armed stay And If alarm panel is not armed away And If alarm panel is not exit delay And If alarm panel is not entry delay Then Else The Program will be true it the alarm panel is disarmed, but The program will be false if either the entry delay or the exit delay are Active or if the alarm panel is armed either stay or away. Tim

Hi @Goose66, Honestly it doesn't make much difference to me. I vote for whatever you think makes the most sense and is the easiest on you. I will adapt either way you decide to go.I would just not prefer to have to do this a third time! LOL. I don't know anything about Envisalink-Vista But it seems like if you do the same thing for it wouldn't it make it easier on you in the long run? I was planning on installing this on Sunday morning. Whichever way you decide to go please just let us know. Thank you for an awesome node server! Tim

Hi @bpwwer, I just updated to the latest PG3 (v3.0.46) and I am seeing the same as @macjeff. In addition, the same two nodes always failed after pressing the backup button. The red banner pops up at the top of the screen saying Not connected to node server which last for about a minute then the same 2 nodes are failed. Backup up package size is huge now. Backup size used to be around 97kb, now the last two are 66,274kb each! Also log page seems to be taking a lot longer to load now as it did on v3.0.44 or before. Thanks, -Tim

Password should be " admin "

Hi @Goose66, EnvisaLink-DSC for PG3 posting you did has the Bond Bridge instructions linked instead. While I have your attention, should we be able to delete this program on PG2 and install it on PG3 in the same slot without loosing or having to update programs? Thank you very much for porting this over. I am looking forward to installing it! -Tim

Success! From start to finish was 8 minutes. Thank you both very much! Sat Mar 12 07:10:04 PST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: starting forcing bios update Sat Mar 12 07:10:05 PST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios mfr: Universal Devices Sat Mar 12 07:10:05 PST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios product: Polisy Sat Mar 12 07:10:05 PST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios ver: 1.0.0 Sat Mar 12 07:10:47 PST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios update ... rebooting Sat Mar 12 07:12:05 PST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios mfr: Universal Devices Sat Mar 12 07:12:05 PST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios product: Polisy Sat Mar 12 07:12:05 PST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios ver: 1.1.3 Sat Mar 12 07:12:05 PST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios has the correct version