PG3x version 3.1.23 (eisy) - OUTDATED

Hello all,

We are very happy to introduce PG3x v3.1.23 for eisy.  

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.  This release includes features already available in PG3 3.1.18 for Polisy.

For now, Polisy users should remain on PG3 and eisy users will use PG3x.  

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 should restart/reboot the eisy.  Do this from the Admin Console, Configuration, Reboot.

  
Once PG3x has restarted, reload /refresh the browser page.

Changelog for 3.1.24

 - Fix bug that would sometimes cause node server delete to fail.

Changelog for 3.1.23

 -  Add setClientState API framework to support remote access to PG3x
 -  Add device config remove for node servers that make use of hardware device configuration
 -  Handle cases where the purchase entry from my.isy.io is unable
 -  Rework handling of incoming requests with requestId from IoX
 -  Filter package upgrade messages to only show PG3x upgrades
 -  pg3_helper: Use onerestart instead of onestart to start node server.
 -  Don't display new version available in footer (use upgrade available messages from UDX instead)
 -  Return discovered IoX when ISY discovery is called
 -  Enhance error message when uuid is invalid (uuid must be available and valid for PG3x to run)
 -  Be better about trapping errors in UDXstart
 -  Add some additional log messages around node server start
 -  Implement node server rating support
 -  Remove the "Log Out Of Portal" button from pages. Being logged into Portal is required.
 -  Add a button to display the Node Server  EULA license
 -  Change startup message to PG3x from PG3
 -  Missing uuid from IoX is fatal
 -  Add support for Node Servers that need device hardware support
 -  Check for existence of UDX socket, this is required for PG3x to run
 -  Node Server info can now list which controllers the node server will work with (eisy and/or Polisy)
 -  Add local store backup/restore feature
 -  Add button to download system log messages (to help with debugging issues)
 -  Check for existence of log file before streaming it
 

Migrating from Polisy/PG3

1. Make a PG3 backup on the Polisy.  From the PG3 UI select System -> Backup/Restore -> Backup.  This will download a backup file
2. 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.

1. 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.
2. 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.
3. Any node servers on the Polisy that were installed from the "Local" store will fail to properly migrate (applies mostly to developers).
4. All node servers will be left in the "Stopped" state.  You will need to manually start each node server after the migration.