jwagner010 Posted February 24, 2022 Posted February 24, 2022 Question on PG3. How do I upgrade a Node Server like I do in PG2? Let me explain. In PG2 if a new version of a Node Server is released, the button in the node server store says Upgrade (or something like that). Makes it easy to upgrade and keeps any programs intact I have written in the ISY with the Node Server. In PG3 I don't get an upgrade option. If the developer publishes a new version of the Node Server to the store, I only get an Install option, I then need to Delete the old/existing Node Server (destroys any programs written in the ISY interacting with that Node Server) and then I need to Install it and Configure the new version. Its a pain, so wondering if I am missing something here? ps Using the Dyson Node server on PG3 where this is happening but I believe this is a PG3 thing not a specific Node Server thing.
dbwarner5 Posted February 24, 2022 Posted February 24, 2022 8 minutes ago, jwagner010 said: Question on PG3. How do I upgrade a Node Server like I do in PG2? ..... Its a pain, so wondering if I am missing something here? ps Using the Dyson Node server on PG3 where this is happening but I believe this is a PG3 thing not a specific Node Server thing. Yes.. For PG3, you just have to stop and restart the NS and it automatically gets the latest version upon restart. 1
Jimbo.Automates Posted February 24, 2022 Posted February 24, 2022 Currently PG3 doesn't give you any visual indication that an upgrade is available, that's coming in the future. (remember this is Alpha) Just cross reference your version with the one shown on the store page for now. To upgrade you just have to restart the nodeserver. 1
DennisC Posted February 24, 2022 Posted February 24, 2022 9 minutes ago, jwagner010 said: Question on PG3. How do I upgrade a Node Server like I do in PG2? Let me explain. In PG2 if a new version of a Node Server is released, the button in the node server store says Upgrade (or something like that). Makes it easy to upgrade and keeps any programs intact I have written in the ISY with the Node Server. In PG3 I don't get an upgrade option. If the developer publishes a new version of the Node Server to the store, I only get an Install option, I then need to Delete the old/existing Node Server (destroys any programs written in the ISY interacting with that Node Server) and then I need to Install it and Configure the new version. Its a pain, so wondering if I am missing something here? ps Using the Dyson Node server on PG3 where this is happening but I believe this is a PG3 thing not a specific Node Server thing. For PG3 Nodeserver upgrades, just stop and restart the Nodeserver. The newer version will install itself with no impact to programs. For that matter, if you delete and then reinstall the same Nodeserver in the same spot your programs are also not impacted.
jwagner010 Posted February 24, 2022 Posted February 24, 2022 1 minute ago, DennisC said: For PG3 Nodeserver upgrades, just stop and restart the Nodeserver. The newer version will install itself with no impact to programs. For that matter, if you delete and then reinstall the same Nodeserver in the same spot your programs are also not impacted. Got it, so next time I see a new version number in the store I just stop and then restart the node server and it will auto upgrade. Got it. Will try it next version release. Thanks all, I knew I was missing something. 1
stillwater Posted March 4, 2022 Posted March 4, 2022 (edited) Just got a Polisy and have some comments on the process just sort of fyi from someone new to polisy and polyglot. I mostly bought the polisy to future proof ISY/Insteon PLM combination from PLM or SD card failure. (Via usb plm or stick). So my intent was to just put it back in the box after I checked that it worked, and wait until IoP gets beyond ALPHA. I am NOT asking for troubleshooting or help -- just reporting my experience. I'm putting this on this thread because my positive suggestions relate to PG3. Caveats: (a) Because I wasn't making a permanent install I didn't initially set up a static IP address. Once I set one up in Polisy and in Router it didn't make much difference. Though Chrome did allow access (b) I didn't use with the ISY finder Experience: 1) Though I have a "modern router" (unifi edgerouter + unifi APs) i could not access the polisy using https://polisy on either chrome or opera browsers. (I could see on my router that it was indeed advertising the polisy name. ) Chrome also initially refused connection via the IP address owing to "scrambled" certificate.... I could access using Safari on MAC. Suggested work arounds (https://polisy.local and installing bonjour on a pc) made no difference. Also Putty on the pc wouldn't find the host polisy though it does find raspberry pis by hostname. Can ping raspberry pis by hostname (replies with suffix .local) but not polisy. Just weird but since I know its IP address it doesn't botehr me. 2) Polisy upgraded fine. I found it easier to SSH in rather than using the dashboard. Dashboard didn't always keep its promises on providing a second message if upgrade not required. So this didn't inspire confidence. 3) Despite looking at the wiki I could not find how to connect to PG3. Only by finding this thread did I discover I had to go to another port (3000). Since the wiki mentions PG3 how to access it should be included there too. 4) It was disconcerting that the default user/password combination still provides access via SSH and via PG3 dashboard even after password is reset to a different value via PG2 dashboard. I think the default behavior is that resetting the password in one place should reset the password in the other access modes as well. Since the stated plan is to get away from SSH the current behavior would leave the SSH access open forever via admin/admin. Not good! I hope this is useful to someone. Looking forward to moving from ISY994i to IoP when IoP and PG3 are more stable. Edited March 5, 2022 by stillwater typo; also added more information on inability to access by hostname 1
smileyw Posted March 7, 2022 Posted March 7, 2022 On 3/4/2022 at 11:01 AM, stillwater said: I have this same issue on my Mac. PG2 It can only be accessed from Safari. Not a huge deal, but annoying none the less. 1) Though I have a "modern router" (unifi edgerouter + unifi APs) i could not access the polisy using https://polisy on either chrome or opera browsers. (I could see on my router that it was indeed advertising the polisy name. ) Chrome also initially refused connection via the IP address owing to "scrambled" certificate.... I could access using Safari on MAC. Suggested work arounds (https://polisy.local and installing bonjour on a pc) made no difference. Also Putty on the pc wouldn't find the host polisy though it does find raspberry pis by hostname. Can ping raspberry pis by hostname (replies with suffix .local) but not polisy. Just weird but since I know its IP address it doesn't botehr me.
DennisC Posted March 10, 2022 Posted March 10, 2022 @bpwwer, Hi Bob, This is just a reminder, not trying to rush you. I noticed in the known bug issues for the PG3 v3.0.45, there was no mention of the backup function not working. I just tried and it is not working. If you already knew that, just disregard this note.
macjeff Posted March 10, 2022 Posted March 10, 2022 I can confirm the backup button seems to do nothing
bpwwer Posted March 10, 2022 Posted March 10, 2022 I don't know what's going on with the backup. Last time I tried it it did work. It's possible that me switching between a development branch and release branch to make the bug fix, that something isn't getting setup right. But why it seems to only effect the backup button, I don't now. Thanks for letting me know. I'll make sure to check it before doing the next release.
macjeff Posted March 16, 2022 Posted March 16, 2022 On 3/10/2022 at 1:00 PM, bpwwer said: I don't know what's going on with the backup. Last time I tried it it did work. It's possible that me switching between a development branch and release branch to make the bug fix, that something isn't getting setup right. But why it seems to only effect the backup button, I don't now. Thanks for letting me know. I'll make sure to check it before doing the next release. Just ran the new update. Backup took a while but worked. And I tried it twice. When I do a backup ALL the node servers go to fail. I did grab a log. I rebooted PG3 after that finished and they all came back online.
bpwwer Posted March 16, 2022 Posted March 16, 2022 1 hour ago, macjeff said: Just ran the new update. Backup took a while but worked. And I tried it twice. When I do a backup ALL the node servers go to fail. I did grab a log. I rebooted PG3 after that finished and they all came back online. If it took a while, that's probably because you have a lot of large log files. That's also probably why the node servers went into failed state, PG3 was too busy doing the backup to talk with the node servers and they gave up. I'd like to have it skip the log files and not back those up, but the libraries I've tried, don't seem to support that. You should have been able to simply start each of the node servers without restarting PG3.
macjeff Posted March 16, 2022 Posted March 16, 2022 Sorry I did try that. It worked but then it failed again about a min later. After a reboot its working fine now for a while.
bpwwer Posted March 16, 2022 Posted March 16, 2022 Ok, thanks. I didn't notice any node servers going into failed state when I tested, but I may have had them stopped at the time. I'll try again to see if I can reproduce what you're seeing.
TJF1960 Posted March 17, 2022 Author Posted March 17, 2022 (edited) 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 Edited March 17, 2022 by TJF1960
macjeff Posted March 17, 2022 Posted March 17, 2022 7 minutes ago, TJF1960 said: 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 I seem to attract Bugs. Ask Michel from UDI. LOL Anyways I also got the not connected but if I wait it eventually connected. I did use the restart polyglot option and that seemed to help a lot. Seems to be the backup button that starts it all. My backup is 28,984,356 bytes (29 MB on disk) But if the reason is logs I set all my log levels to ERROR only. Jeff
vbPhil Posted March 17, 2022 Posted March 17, 2022 21 hours ago, bpwwer said: Ok, thanks. I didn't notice any node servers going into failed state when I tested, but I may have had them stopped at the time. I'll try again to see if I can reproduce what you're seeing. Just tried the Backup after upgrading to 3.0.46. I'm getting the same issues; lost connection to server and NS in Failed state. Refreshed page and server connection finally restored. Restarted each NS. I don't think it produced a backup, if so, where does it get saved?
macjeff Posted March 17, 2022 Posted March 17, 2022 27 minutes ago, vbphil said: Just tried the Backup after upgrading to 3.0.46. I'm getting the same issues; lost connection to server and NS in Failed state. Refreshed page and server connection finally restored. Restarted each NS. I don't think it produced a backup, if so, where does it get saved? Mine was saved to the default downloads folder set by my browser but took a couple minutes to show up. It might be the node servers are all down while it’s backing up so next time leave it alone and see what happens for maybe 15 minutes. Like you I got impatient the first time and re started
vbPhil Posted March 17, 2022 Posted March 17, 2022 3 minutes ago, macjeff said: Mine was saved to the default downloads folder set by my browser but took a couple minutes to show up. It might be the node servers are all down while it’s backing up so next time leave it alone and see what happens for maybe 15 minutes. Like you I got impatient the first time and re started @macjeffI don't see anything in Downloads. What name does it get? I'll do a search.
macjeff Posted March 17, 2022 Posted March 17, 2022 1 hour ago, vbphil said: @macjeffI don't see anything in Downloads. What name does it get? I'll do a search. I know it started with polyglot or PG3 But I am nowhere near the house today so I can’t tell you for sure 1
bpwwer Posted March 17, 2022 Posted March 17, 2022 The big difference in this version vs. the previous version is that the operation to create the zip archive is a blocking operation. I.E. while it is running, PG3 does nothing else. This makes it quite a bit faster, but also causes the UI and it looks like the node servers to loose their connection to PG3 thinking PG3 is down. I'll keep looking for a better solution to this.
vbPhil Posted March 17, 2022 Posted March 17, 2022 4 hours ago, macjeff said: I know it started with polyglot or PG3 But I am nowhere near the house today so I can’t tell you for sure Backing up isn't very intuitive. When doing a Backup select the Download button from the Settings/Polyglot Settings menu and then wait (about 20 seconds for me). A message will appear with a red background. Do not refresh the page as it states but wait (about another 20 seconds for me), the red message will disappear, and the Browser's Download popup will appear giving you choices depending on your Browser type. I'm using Edge. From the Browser's popup you can select where to save the backup, and a new name if you don't like the default. The default name for me this time was: pg3-backup-3-17-2022_14819_PM.zip The first time I tried this today I refreshed the page when I saw the red message and that prevented the download from happening so the backup process never completed, and I was left scratching my head.
macjeff Posted March 18, 2022 Posted March 18, 2022 5 hours ago, vbphil said: Backing up isn't very intuitive. When doing a Backup select the Download button from the Settings/Polyglot Settings menu and then wait (about 20 seconds for me). A message will appear with a red background. Do not refresh the page as it states but wait (about another 20 seconds for me), the red message will disappear, and the Browser's Download popup will appear giving you choices depending on your Browser type. I'm using Edge. From the Browser's popup you can select where to save the backup, and a new name if you don't like the default. The default name for me this time was: pg3-backup-3-17-2022_14819_PM.zip The first time I tried this today I refreshed the page when I saw the red message and that prevented the download from happening so the backup process never completed, and I was left scratching my head. Mine does that and I get the backup but never comes out of this and all say failed until I restart pg3.
macjeff Posted March 18, 2022 Posted March 18, 2022 UPDATE- Ran new version 3.0.47. Same issues. No change I can see.
vbPhil Posted March 18, 2022 Posted March 18, 2022 On 3/16/2022 at 7:26 PM, macjeff said: I seem to attract Bugs. Ask Michel from UDI. LOL Anyways I also got the not connected but if I wait it eventually connected. I did use the restart polyglot option and that seemed to help a lot. Seems to be the backup button that starts it all. My backup is 28,984,356 bytes (29 MB on disk) But if the reason is logs I set all my log levels to ERROR only. Jeff @macjeffHow did you set all your log levels to Error only?
Recommended Posts