bpwwer Posted January 3, 2023 Posted January 3, 2023 Hello all, We are very happy to introduce PG3x v3.1.22 for eisy. This is a minor update to 3.1.21. The eisy is using a new version of Polyglot version three called PG3x. PG3x has infrastructure changes to make node servers (and PG3x) more secure. Both PG3 and PG3x have the same feature set with the exception of a feature in PG3x that allows migration of node servers from PG3 to PG3x. For now, Polisy users should remain on PG3 and eisy users will use PG3x. This fixes a number of bugs in the original PG3x 3.1.16 release and adds the ability to migrate from Polisy/PG3. To upgrade PG3x: In the Admin Console, click on Configuration, Upgrade Packages (note, this can take many minutes, depending on how long it's been since you last updated.). After the upgrade is complete you may need to restart PG3x. From PG3x UI select System-> Restart Polyglot 3x. Once PG3x has restarted, reload /refresh the browser page. Migrating from Polisy/PG3 Make a PG3 backup on the Polisy. From the PG3 UI select System -> Backup/Restore -> Backup. This will download a backup file Restore the PG3 backup on eisy. From the PG3x UI select System -> Backup/Restore -> Migrate from PG3 backup. Select the Polisy PG3 backup file and when the button changes to "Restore" click it. Depending on how many node servers need to be migrated it can take a while. The UI should pop up messages showing the status as it migrates node servers. There are some limitations to the migration process. Only one IoX device can be migrated. If your Polisy was connected to more than one IoX device (say the local IoP and an i994), the migration process will only migrate one of these and it will use whichever one shows up first when it does it's database query. This will remove any previously installed node servers in PG3x and possibly overwrite them with a node server from the backup. You should start this process with no node servers installed. Any node servers on the Polisy that were installed from the "Local" store will fail to properly migrate (applies mostly to developers). All node servers will be left in the "Stopped" state. You will need to manually start each node server after the migration. Changelog for 3.1.22 - Rebuild package to work with Node version 19.5 Changelog for 3.1.21 - Don't loop over non-existent nodes when displaying node details in UI - Add ability to handle system upgrade messages and display a notice in the UI when the system is being upgraded. - quote password when sending to pg3.ops. Fixes issue with passwords containing special characters like '$$' - Try and trap network errors when verifying node servers installed on IoX. - Fix typo in log message. - Fix bug that caused dashboard to ignore "un-managed" node servers. Changelog for 3.1.20 - Fix minor bug in UI where we tried to use settings before they were set. - remove debugging messages. - Return status = 500 , and error if authentication crashes - Revamp verify node servers behavior. PG3x will now try to make the IoX match what is in it's database to better keep IoX and PG3x synced on what node servers are installed. - Fix IoX auto discover to not overwrite existing entry's username/password. - Change how the UI authenticates with the MQTT broker. This should resolve issues with logging and and bring back the ability to use multiple browsers to access PG3x at the same time. - Stop printing the mqtt frontend password in the log - Quote the user name so that it now works if the name has space characters. Changelog for 3.1.18 - Pass the correct structure to installProfile. Fixes profile files not being sent to IoX on node server install. - Allow 127.0.0.1 for IoX node config ip address. Stops PG3 from replacing the localhost IP with network IP on node server verification.Changelog for 3.1.17 - Change the IP address written to the IoX node server configuration to use 127.0.0.1. - Fix typo status should be stats in checkLicense. Caused licence check to fail for some purchased node servers. - Change ISY to IoX throughout the UI. - Always route reinstall through nsinfo, specifically fixes issues when re-installing via the purchases page. - add logging and pg3_install fixes to get permissions correct after install of node server. - fix typo in error message, puchase should be purchase. - Update database to indicate we've migrated to PG3x. - Add ability to migrate from PG3 backup. - Enable check for PG3 node server migration on start. - Add count of node servers re-installed to reinstallNS response. - Add ability to re-install all node servers via the System menu. - Handle alert and reinstallNS messages. - Add pg3x flag to global settings. - Don't update node name to 'undefined' - Remove "Running on Polisy" from footer. - Make node server verification errors more verbose. - Run update check every 12 hours. - Check for updates of PG3x. Support thread: 1 4
bpwwer Posted February 5, 2023 Author Posted February 5, 2023 Version 3.1.22 is simply a rebuild of the 3.1.21 to allow PG3x to work with the latest system update. No new features or bug fixes are included in this release.
Recommended Posts