bmercier

I have reports that downgrading PG3x to 3.2.2 does not help. This means that during the upgrade packages process, something else gets updated and breaks. Willl need @Michel Kohanim's help to figure out what got updated and find a fix.

I'm not sure what the problem is with node servers not connecting. I can't see any change that would affect that. I suspect update package updated something else that may cause this problem. Until this is resolved, if you want to try a downgrade to 3.2.2: Download PG3x 3.2.2: https://universaldevices-my.sharepoint.com/:u:/g/personal/benoit_universal-devices_com/ETyQLncGwUdFkEvYT93duF0BTEwrHzMfoXQJjDyVvqYdhg?e=Y8Uuez Transfer this pkg to your eisy using a transfer tool such as winscp or mobaterm SSH to your eisy using a tool such as putty or mobaterm Go to the folder you transferred the pkg sudo pkg install -f pg3x-3.2.2.pkg sudo service udx restart If that does not work, you may want to power cycle. To troubleshoot this problem further, we need a ticket with a log showing a reboot followed by nodeservers not connecting. This needs to be at 3.2.3 (Before downgrading)

This means UDX is not responding. If no upgrades are underway, I would try to power cycle your eisy. Sent from my iPhone using Tapatalk

It appears that support for tiers & versions was not fully implemented. On the purchases page, for each options, the page determines if owner has a license for that option. The code was not tier-aware and version-aware. This means that when showing the Standard option, it's as if the user had a license for that option. This is fixed with yesterday's release of PG3x 3.2.3. There's some more development and testing to do to fully support tiers & versions, which I'm currently focusing on.

This should be fixed in 3.2.3. If the free option is installed, then the second line should show "Purchase" instead of "Update".

It should show which option is installed in which slot. When an option is purchased, the option ID is tracked and used to determine which option is installed. If the option no longer exists, then it won't show. What I think may have happened is that the node server option have changed since it was installed. You may have the option with the same version, ID and tier, but if it has been removed and recreated, this is what would happen. Is this plausible in the case of the Notification node server?

Hello everyone, This is the support thread for PG3x v3.2.3. After updating to 3.2.3, please click on System | Reinstall all node servers, which will reinstall all your node servers including the new UDI python interface 3.2.0. If you were on PG3x 3.2.1+ and you already re-installed your node servers, there is no need to re-install them as there has been no changes to UDI Python interface with 3.2.2 or 3.2.3.

Hello everyone, Here's the latest PG3x release. Release notes for: 3.2.3 - 08/29/2023 Fix purchase buttons for higher tier & version Fix bottom-right notification duplicates Fix store table default values (Fixes isyAccess field error following a factory reset) Silence unnecessary logging when adding nodeservers to the store tables After updating PG3x, unless you are migrating from PG3x 3.2.1+, please click on System | Re-install all node servers. If you were on PG3x 3.2.1 or 3.2.2 and you already re-installed your node servers, there is no need to re-install them.

Looks like UDX is not started. The easiest would be to power cycle your eisy.

Hi everyone, The Upgrade Packages that you are used to do in admin console is now available from portal, under Select tool | Maintenance. Benoit

@Jim P PG3x 3.2.2 is out. This will fix your problem.

Hello everyone, This is the support thread for PG3x v3.2.2. After updating to 3.2.2, please click on System | Reinstall all node servers, which will reinstall all your node servers including the new UDI python interface 3.2.0. If you were on PG3x 3.2.1 and you already re-installed your node servers, there is no need to re-install them as there has been no changes to UDI Python interface with 3.2.2.

Hello everyone, Here's the latest PG3x release. Release notes for: 3.2.2 - 08/18/2023 Added support for Bonjour discovery for UD Mobile (Upcoming UD Mobile feature) Enhanced error handling with Bonjour discovery (UD Mobile & Node Server requests) Update node's controller field when connection status is set On the purchases page, add Re-install button when node server is already installed and up to date. Fix for isyAccess flag when the same nsid is used across multiple stores Fix for developerMode It was previously allowing developers to install other node servers in dev mode if developer had purchased it Fix nodeserver table schema update Enhanced logging of isyAccess flag's uuid & slot After updating PG3x, unless you are migrating from PG3x 3.2.1, please click on System | Re-install all node servers. If you were on PG3x 3.2.1 and you already re-installed your node servers, there is no need to re-install them.

Hi Jim, Found the problem. This is not specific to Ring. There will be a fix in PG3x 3.2.2. Look for a release later today. Thanks for reporting this. Benoit

This problem is related to a communication error with the PG3 embedded MQTT server. I recommend migrating to PG3x, this should fix this problem. PG3x uses Mosquitto MQTT server. In addition, we no longer maintain PG3.

I would reboot. I think UDX is not responding. If you ssh, you can also try: sudo service udx restart The latest packages are also more robusts, with fixes to UDX. Sent from my iPhone using Tapatalk

This means that the node server developer updated his node server to 3.1.2 but did not update the store to say it is 3.1.2. Sent from my iPhone using Tapatalk

This will be fixed in 3.2.2

I added the re-install button in the purchases page. It will be in the upcoming 3.2.2.

What was the problem and how did you fix it?

No I’m not sure why. I also don’t use server.json for Ring, and it works well. Does the log tells us anything? Sent from my iPhone using Tapatalk

Hi Bob, Previously you would see an update button on all the lines. One of the change was to show the update button only if an update is available (current version != latest version) Is this the Update button you are looking for? (Or install?) If so, do you have a use case where the update button would be useful? User comments were that the update button should only appear if an update was available.

I can't reproduce this. Can you set the "Require ISY Access" flag on your Backup Node Server in the production store? I personally don't use this, so I did not even notice a change here. Most node servers I have on that page shows an Install button (I have a license but it is not installed) The only changes on that page was that duplicates have been removed, and the Update button is only showing if an update is available. So what you are seeing may be a side effect of one of those changes. Can you describe the problem in more details? Is it that the node server line don't show Or does it show, but without an Install button? Is it a node server that is already installed? Is it a node server that you developed? I can see the problem. Will have a fix.

Hello everyone, This is the support thread for PG3x v3.2.1. After updating to 3.2.1, please click on System | Reinstall all node servers, which will reinstall all your node servers including the new UDI python interface 3.2.0.

Hello everyone, Here's the latest PG3x release. Release notes for: 3.2.1 - 08/14/2023 Dashboard now shows node servers connected state in real time Fix to the Purchase page with duplicated entries In the purchase page, show the update button only if an update is available Node server re-install: Restart node servers after re-installation if it was running Node server re-install: At the end, display a confirmation message Node servers can now update property names of existing nodes In node server nodes page, property variable can be copied using copy icon Add support for dynamic property texts (UOM 150) Fine tune IoX requests throttling Add support for Bonjour mDNS queries by node servers Add support for descriptions on properties shown in PG3x Make login more responsive if UDX is not responding Use socket to connect to onboard IoX (Instead of HTTP) Fix the PG3x Restart Required following an upgrade. Added developer mode when installing a node server (For developers only) Added flag to allow access to ISY by Node Server When changing credentials from admin console, update PG3x's cached credentials for node server accessing ISY When node server is in a failed state, allow to restart the node server without errors Fix a potential uncaugh exception that may happen during node server log rotation Fix handling of notifications from IoX On node server installation, clean the previous files if any Enhanced shutdown process General code enhancement Minor bug fixes & logging enhancements In addition, UDI python interface has also been updated to 3.2.0. After updating PG3x, please click on System | Re-install all node servers. UDI Python interface 3.2.0 changes: Added support for mDNS queries by node servers. This will allow them to discover devices they support. Added restriction to ISY credentials by Node Servers. Node servers will be prevented access to your ISY's REST API, unless you approve it under the configuration page. This restriction will be effective in a future release of PG3 to allow time for Node server developers to configure their Node Servers, and to allow you to grant access. When the next release with the restriction comes out, ISY access by Node Servers will be prevented unless you grant access. Please note that this feature only restricts direct access to ISY. Core PG3 capabilities such as creating nodes, removing nodes, updating properties etc are not affected by this restriction. This affects only a handful of Node Servers.