bpwwer

That's what works for me, but I may have changed some of the restrictions on the polyglot account on my Polisys. I don't know any other way to do that.

@tmorse305If you refresh the store and try re-installing it should work now.

When node servers don't start, the PG3 log will have more information on why they don't start. We just discovered an issue today where if a node server was installed during the early alpha test time frame (before there were multiple node server stores) it can now fail to start because it's missing information in the local database records telling PG3 what node server store it was originally installed from. That's the working theory anyway. If the PG3 log shows a failure with auto update, then it's the same problem. I'm not sure how best to handle this. 1) it's not hard for me to add a check for this condition in PG3 and then assume the node server was installed from the production store. However, there have been other similar changes so it may just fail later because some other piece of info is missing from the database. 2) you can try simply re-installing the node server. With this version of PG3 you can simply click the "install" button in the store for this node server and you will have the option to re-install it to the same slot. This will download the latest version of the node server and update everything. The downside is that it will put the configuration parameters back to the default settings so you have to re-configure the node server. But nothing on the ISY/IoP side will change so programs remain intact.

Looks like the update process failed. This is the second report of this same failure, UDI is looking into why and how to resolve it.

I believe you. I just don't like it when PG3 does something it shouldn't.

Nothing should be able to reset the login credentials except you manually doing that (either through the menus or by running the reset_password command on the command line). The only other way the credentials could be reset would be if the database was removed and re-created. In that case, it would be a lot more than just credentials that would be reset. From the menus, use the Settings -> Profile option to set the credentials

Try upgrading packages again and get version 3.1.8. I think this will resolve the issue. It it still says the node server has expired, try restarting the node server and see if that fixes it.

Try updates packages again and restart with version 3.1.8. If it still says it's expired, restart the node server and pm me the PG3 log

You should be able to attached it to a PM to me. I'm building a new release now that I think will resolve the issue.

@garybixlerThere's another thread about the same problem: So I'll ask you the same question. Did you previously have a trial license before purchasing the perpetual license? I'm wondering if the trial license info is still saved in PG3 and isn't getting updated by perpetual license purchase. There should be some PG3 log messages for checkLicense, seeing those might help some.

Sorry about all the trouble with the update process. That's not something I can do much about, but others are working to make that better. After PG3 3.1.6 was released, a bug was discovered in one of the developer only functions. 3.1.7 fixes that bug but otherwise is identical to 1.0.6. So unless you are a node server developer, there's no reason to update from 3.1.6 to 3.1.7. @MrBillThanks for pointing that out, you're right that text is very confusing and wrong. Since I took over development of PG3, I hadn't bothered to actually look at the text.

The PG3 log file might help. It only checks for an expired license if the expiration data is set and is non-zero. For a perpetual license, it should be either null or zero. Did you activate a trial for these originally? I'm wondering if the query for a license is returning both an expired trial and perpetual and PG3 is using the expired trial license for some reason.

Unfortunately, that's not the way it was designed. PG3 holds no state information for the user interface so it has no knowledge of how many browsers are currently connected to it. When something changes, those changes are pushed to all connected browser clients. While PG3 can manage node servers on multiple ISY/IoP devices, it can only work with one at time. Also, for this specific case it may be desirable for it not to do this, for most other cases it would be far worse. For instance, if you had two browser windows open to the same node server configuration page and you change a configuration parameter on one you'd either be confused or possibly even undo the change if you looked at the other page and it didn't have the correct values for the configuration.

There is a script to reset the PG3 username/password back to admin/admin included in the update. You can only access it via a ssh command line. The following commands should reset the password. sudo su polyglot node /var/polyglot/node_modules/@universaldevices/pg3/bin/password_reset.js exit

It should only say it needs rebooting if the Frontend Version is different from the Version (see below). However, sometimes browser caching can confuse the check. If the two versions are the same, all is good. If the frontend Version is less than Version, reload the page in the browser. If the frontend Version is greater than Version then restart PG3. (in this case it should say needs restart0

Hello all, We are very happy to introduce PG3 v3.1.6 which is the second production release of PG3. To use the latest version of PG3, you should also be running the latest version of IOP. Follow the instructions in the IOP release announcement to upgrade IOP to the latest version. To upgrade PG3: - In the Admin Console, click on Configuration, Upgrade Packages (note, this can take many minutes). - After the upgrade is complete you will need to restart PG3. From PG3 select System-> Restart Polyglot 3 3.1.11 Fix bug in the developer tools related to adding purchase options. Changed the default logging level from full debug to info (to reduce the size of PG3 log files) Added ability to change PG3 log level at runtime. 3.1.10 Fix a bug that prevented PG3 from recognizing subscription licenses for install/re-install 3.1.9 Update wording in dialog box displayed when restarting PG3 Fix a typo that prevented PG3 from reporting subscription licenses as valid Update node server store info for node servers installed before multiple node server stores existed. 3.1.8 Update the PG3 database with license expiration when checking the node server license. 3.1.7 Fix bug in developer add new node server form. If you aren't a node server developer and have already updated to 3.1.6, you do not need to update to 3.1.7. Bug Fixes: Fix case in createHomeDir function Properly handle install of non-free node servers by developers. Rework deploy and extract node server directory creation. Skip pg3 version check on login Fix error message when node server store entry is not found. Make buttons for displaying node server all the same width. Add check for license expired improve upgrade available message Clean up node server validation check messages. Send purchase option edition to node server when starting. re-install only applies to target isy. Wait for store and ISY to finish initializing before starting node servers. Add checkLicense() check when starting node servers. fix issue with install display. Update for node version 18 Fix spelling errors Handle installs using new purchase options Migrate node server home directory to not have ':' characters Handle old store records. Simplify what is sent to backend for install Update error messages when checkTransaction fails. Tweak error handling Improve toaster messages to user when sync transactions fails. Handle ISY communication errors better. Handle new style purchase options Improve error message Remove unnecessary import Remove dead code. Trap errors when running the shutdown process. ISY returning no node servers is a warning not an error Fix issue removing node server from cache. Fix expire check poll. Store database primary key now autoincrement Update the store database with new constraint Update store database get() to take both uuid and store. Store record updates now need both uuid and store. Enhancements: Require purchases for free node servers but make the purchase automatic Allow node servers to be re-installed Move purchase options and node server information to a new screen Skip purchasing backend for trial activation. Node Server Developer Fixes/Enhancements: Allow packages to be uploaded for local store. Adding sales info under developers menu. Add node server delete to developer tools Add developer help section to menu Enhance purchase options; upgrades, multiple editions, etc. Create developer token if needed. Add related node server table to developer edit form Add installation type to install options table Allow the same node server id to exist in different stores so single license can cover node server in non-production and production store Warn user if node server submission may change node server id. trap error if no package file entered. When defaulting edition use price to determine default Allow developer to installed node servers they own and bypass license check Handle typo in payment ref for July 2022. Create purchase options table to allow developer to define the various purchase options and install choices. Notify user of form errors when submit fails. Fix table sorting. Create UUID in edit form before submitting. Support Thread:

Hello Everyone, This is the support thread for PG3 v3.1.6 to v3.1.16

Ok, I'm going to try and do a new release of PG3 by the end of the week. This will be version 3.1.6. Since it will be a new release with a new version, the package update should pick it up. I'll do some testing to verify that before I actually announce it.

The node server does have a 30 day trial you can use to test it before purchase. Also, the node server will log info about the devices it doesn't know about and if you send me that info for the Diva I'll have a head start in making it a non-generic device.

I was able to reproduce the problem with ST-Nuheat on that test version. It is an issue with that specific version of PG3 that has been fixed in the latest test version. I know how to update the various packages using the pkg command line, but I'm not sure that's a good idea anymore. I suggest you do an update packages from the IoP configuration page in the admin console and see if that gets you a new version. ideally, it will move you back to the latest production version 3.0.63.

I stopped by a HomeDepot today to see if they had any of the new switches/dimmers but nope, the selection of Caseta devices was very limited.

I believe they will show up as generic switches and generic dimmers. Currently, there's no difference in the node server between a generic device and a known device other than the node type for a generic device says "Generic" and the known device will show the actual model number.

I'm running on my Fedora system using icedTea. Over the years I've had to fiddle with it a bit to keep it working but I don't have any specific recommendations. I'm currently using java-11-openjdk-11.0.13.0.8-2.fc33.x86_64 if that helps at all. My launcher icon on the desktop is configured like this: [Desktop Entry] Version=1.0 Name=ISY Launcher GenericName=Java Web Start Application Comment=This utility finds ISY and launches the correct version of the UI-Admin Console-Dashboard Categories=Network;ISY Launcher;Java;Javaws; Type=Application Icon=/home/bpaauwe/.config/icedtea-web/icons/udlogo.png X-Vendor=Universal Devices- Inc. Exec=/usr/libexec/icedtea-web/javaws --verbose --nosecurity "https://isy.universal-devices.com/launcher/isy.jnlp" > /tmp/isy.log 2>&1 That launches the ISY finder and then I do have to manually add (or load a saved listing) of my ISY/IoP devices as it only seems to ever automatically find one ISY.

Store updated and version 2.0.1 with callback URL changes in README/Config docs.

Use the Refresh Store button to refresh the store listing. Otherwise, it auto updates the list every 8 hours.