TJF1960

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

Awesome, thank you @DennisC and @MrBill for putting my mind at ease! Here I go, No guts no glory, as they say.

Hi @DennisC, I have read the this thread. My major concern is that I hadn't seen anyone mention getting the "wrong part" listed in the console. I don't want to upgrade and take a chance of being in the same boat as Larry above. Also, I don't know what the time frame is for the early units that was referred to? I think I bought mine in the first half of last year.

I was getting ready to update from 5.4.0 but ran "sudo cat /var/udx/logs/log | grep bios" first. I am wondering if anyone else's came up with "wrong part?" I am a little worried about whether I should upgrade or not. [admin@polisy ~]$ sudo cat /var/udx/logs/log | grep bios Password: Sat Feb 19 08:51:51 PST 2022: bios mfr: Sat Feb 19 08:51:51 PST 2022: bios product: Sat Feb 19 08:51:51 PST 2022: bios has wrong mfr/product Sat Feb 19 09:05:24 PST 2022: bios mfr: Sat Feb 19 09:05:24 PST 2022: bios product: Sat Feb 19 09:05:24 PST 2022: bios has wrong mfr/product Sat Feb 19 11:20:10 PST 2022: bios mfr: Sat Feb 19 11:20:10 PST 2022: bios product: Sat Feb 19 11:20:10 PST 2022: bios has wrong mfr/product Sun Feb 27 06:54:52 PST 2022: bios mfr: Sun Feb 27 06:54:52 PST 2022: bios product: Sun Feb 27 06:54:52 PST 2022: bios has wrong mfr/product Sun Feb 27 16:03:24 PST 2022: bios mfr: Sun Feb 27 16:03:24 PST 2022: bios product: Sun Feb 27 16:03:24 PST 2022: bios has wrong mfr/product Sun Mar 6 06:02:35 PST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios mfr: Universal Devices Sun Mar 6 06:02:35 PST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios product: Polisy Sun Mar 6 06:02:35 PST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios ver: 1.0.0 Sun Mar 6 06:02:35 PST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios version 100 is old and needs to be upgraded Sun Mar 6 06:04:04 PST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios mfr: Universal Devices Sun Mar 6 06:04:04 PST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios product: Polisy Sun Mar 6 06:04:04 PST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios ver: 1.0.0 Sun Mar 6 06:04:04 PST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios version 100 is old and needs to be upgraded Sun Mar 6 06:42:27 PST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios mfr: Universal Devices Sun Mar 6 06:42:27 PST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios product: Polisy Sun Mar 6 06:42:27 PST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios ver: 1.0.0 Sun Mar 6 06:42:26 PST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios version 100 is old and needs to be upgraded [admin@polisy ~]$

Thank you for the quick response. I will stop messing with it. Tim

Hi @simplextech, Updated Polisy per Michel's last post via ssh. IoP on v5.4.0, PG3 on v3.0.41. After all rebooted and functioning normally I noticed ST-Inventory not connected. Version installed was 1.0.2, I stopped and started the node a number of times. Never would connect. I noticed you rolled out a new version this morning. But during restarts it was not updating. So I deleted the node and tried to reinstall in the same slot. It will not install. I tried installing in 2 other free slots, same results. Thank you, Tim 3/6/2022, 07:17:42 [pg3] debug: Stopping log stream for pg3frontend_YJPSY 3/6/2022, 07:17:55 [pg3] debug: Getting status for MyQ 00:0d:b9:59:39:b0 3cac3bad-92bb-40f4-966f-3b541e85c898 3/6/2022, 07:17:55 [pg3] info: [00:0d:b9:59:39:b0_10] tplkasactl reporting command DON 3/6/2022, 07:17:55 [pg3] debug: Scheduling http://localhost:8080/rest/ns/10/nodes/n010_tplkasactl/report/cmd/DON to group commandGroup 3/6/2022, 07:17:55 [pg3] debug: ISY Response: [Try: 1] [00:0d:b9:59:39:b0] :: [200] :: 7.062209ms - http://localhost:8080/rest/ns/10/nodes/n010_tplkasactl/report/cmd/DON 3/6/2022, 07:17:55 [pg3] debug: MQTT Results: [ns/command/00:0d:b9:59:39:b0,10] :: {"command":[{"address":"tplkasactl","success":true}]} 3/6/2022, 07:17:55 [pg3] debug: Scheduling http://localhost:8080/rest/ns/6/nodes/n006_cg085008f7c6/report/status/GV0/7397/58 to group statusGroup 3/6/2022, 07:17:55 [pg3] debug: ISY Response: [Try: 1] [00:0d:b9:59:39:b0] :: [200] :: 5.460989ms - http://localhost:8080/rest/ns/6/nodes/n006_cg085008f7c6/report/status/GV0/7397/58 3/6/2022, 07:17:55 [pg3] debug: SELECT * FROM driver WHERE (uuid, profileNum, address, driver) is ('00:0d:b9:59:39:b0', '6', 'cg085008f7c6', 'GV0') 3/6/2022, 07:17:55 [pg3] debug: UPDATE driver SET value = '7397',uom = '58',timeModified = 1646579875814 WHERE (uuid, profileNum, address, driver) is ('00:0d:b9:59:39:b0', '6', 'cg085008f7c6', 'GV0') 3/6/2022, 07:17:55 [pg3] debug: SELECT * FROM driver WHERE (uuid, profileNum, address, driver) is ('00:0d:b9:59:39:b0', '6', 'cg085008f7c6', 'GV0') 3/6/2022, 07:17:55 [pg3] debug: MQTT Results: [ns/status/00:0d:b9:59:39:b0,6] :: {"set":[{"address":"cg085008f7c6","driver":"GV0","value":"7397","uom":58}]} 3/6/2022, 07:17:55 [pg3] debug: Found info {"found":true,"isActive":true,"isInstalled":true,"expiry":"2023-02-06T03:16:34.000Z"} 3/6/2022, 07:17:55 [pg3] info: set to expire on 2023-02-06T03:16:34.000Z 3/6/2022, 07:18:03 [pg3] debug: ########## {"docs":"https://github.com/simplextech/pg3_docs/tree/main/ST-Inventory","version":"1.0.4","status":"active","oauth":"","prem":true,"url":"https://pg3store.isy.io/v2/nodeservers/production/pg3_inventory.zip","name":"ST-Inventory","language":"node","nsdata":"","desc":"Inventory of ISY nodes. Includes Insteon, Z-Wave, Scenes, Programs, Folders, Int and State Variables and Error log lines.","developer":"jeubanks@simplextech.net","ip_added":"107.77.204.108","purchaseOptions":[{"price":20,"isPerpetual":true}],"branch":"","uuid":"00:0d:b9:59:39:b0","ts_added":"1644790722","ts_updated":"1646539323","author":"Simplex Technology","price":20,"modified":"2022-03-06 04:02","profileNum":"17","nsid":"c126923a-afcd-4e6d-9e46-58576796f551","expires":0} 3/6/2022, 07:18:03 [pg3] info: [00:0d:b9:59:39:b0_17] :: Creating Nodeserver 'ST-Inventory' 3/6/2022, 07:18:04 [pg3] error: unhandledRejection REPORT THIS!: [object Promise], reason: Error: Request failed with status code 404 3/6/2022, 07:18:07 [pg3] debug: Sending logfile to frontend :: /var/polyglot/pg3/logs/pg3-current.log 3/6/2022, 07:18:16 [pg3] debug: Starting log stream for pg3frontend_YJPSY :: /var/polyglot/pg3/logs/pg3-current.log 3/6/2022, 07:18:25 [pg3] debug: Scheduling http://localhost:8080/rest/ns/2/nodes/n002_controller/report/status/GV1/18/0 to group statusGroup 3/6/2022, 07:18:25 [pg3] debug: ISY Response: [Try: 1] [00:0d:b9:59:39:b0] :: [200] :: 18.382399ms - http://localhost:8080/rest/ns/2/nodes/n002_controller/report/status/GV1/18/0 3/6/2022, 07:18:25 [pg3] debug: SELECT * FROM driver WHERE (uuid, profileNum, address, driver) is ('00:0d:b9:59:39:b0', '2', 'controller', 'GV1') 3/6/2022, 07:18:25 [pg3] debug: UPDATE driver SET value = '18',uom = '0',timeModified = 1646579905764 WHERE (uuid, profileNum, address, driver) is ('00:0d:b9:59:39:b0', '2', 'controller', 'GV1') 3/6/2022, 07:18:25 [pg3] debug: SELECT * FROM driver WHERE (uuid, profileNum, address, driver) is ('00:0d:b9:59:39:b0', '2', 'controller', 'GV1') 3/6/2022, 07:18:25 [pg3] debug: Scheduling http://localhost:8080/rest/ns/2/nodes/n002_controller/report/status/GV9/92598/0 to group statusGroup 3/6/2022, 07:18:25 [pg3] debug: MQTT Results: [ns/status/00:0d:b9:59:39:b0,2] :: {"set":[{"address":"controller","driver":"GV1","value":"18","uom":0}]} 3/6/2022, 07:18:25 [pg3] debug: ISY Response: [Try: 1] [00:0d:b9:59:39:b0] :: [200] :: 5.746094ms - http://localhost:8080/rest/ns/2/nodes/n002_controller/report/status/GV9/92598/0 3/6/2022, 07:18:25 [pg3] debug: SELECT * FROM driver WHERE (uuid, profileNum, address, driver) is ('00:0d:b9:59:39:b0', '2', 'controller', 'GV9') 3/6/2022, 07:18:25 [pg3] debug: UPDATE driver SET value = '92598',uom = '0',timeModified = 1646579905841 WHERE (uuid, profileNum, address, driver) is ('00:0d:b9:59:39:b0', '2', 'controller', 'GV9') 3/6/2022, 07:18:25 [pg3] debug: SELECT * FROM driver WHERE (uuid, profileNum, address, driver) is ('00:0d:b9:59:39:b0', '2', 'controller', 'GV9') 3/6/2022, 07:18:25 [pg3] debug: MQTT Results: [ns/status/00:0d:b9:59:39:b0,2] :: {"set":[{"address":"controller","driver":"GV9","value":"92598","uom":0}]} 3/6/2022, 07:18:55 [pg3] debug: Getting status for MyQ 00:0d:b9:59:39:b0 3cac3bad-92bb-40f4-966f-3b541e85c898 3/6/2022, 07:18:55 [pg3] debug: Scheduling http://localhost:8080/rest/ns/6/nodes/n006_cg085008f7c6/report/status/GV0/7457/58 to group statusGroup 3/6/2022, 07:18:55 [pg3] debug: ISY Response: [Try: 1] [00:0d:b9:59:39:b0] :: [200] :: 6.670109ms - http://localhost:8080/rest/ns/6/nodes/n006_cg085008f7c6/report/status/GV0/7457/58 3/6/2022, 07:18:55 [pg3] debug: SELECT * FROM driver WHERE (uuid, profileNum, address, driver) is ('00:0d:b9:59:39:b0', '6', 'cg085008f7c6', 'GV0') 3/6/2022, 07:18:55 [pg3] debug: UPDATE driver SET value = '7457',uom = '58',timeModified = 1646579935682 WHERE (uuid, profileNum, address, driver) is ('00:0d:b9:59:39:b0', '6', 'cg085008f7c6', 'GV0') 3/6/2022, 07:18:55 [pg3] debug: SELECT * FROM driver WHERE (uuid, profileNum, address, driver) is ('00:0d:b9:59:39:b0', '6', 'cg085008f7c6', 'GV0') 3/6/2022, 07:18:55 [pg3] debug: MQTT Results: [ns/status/00:0d:b9:59:39:b0,6] :: {"set":[{"address":"cg085008f7c6","driver":"GV0","value":"7457","uom":58}]} 3/6/2022, 07:18:55 [pg3] debug: Found info {"found":true,"isActive":true,"isInstalled":true,"expiry":"2023-02-06T03:16:34.000Z"} 3/6/2022, 07:18:55 [pg3] info: set to expire on 2023-02-06T03:16:34.000Z