bmercier

Thanks for the update, and sorry for the trouble.

For now, here's a temporary solution that should work. SSH to your eisy and use these commands: cd /var/polyglot sudo service pg3 stop sudo rm -rf node_modules sudo pkg remove pg3x sudo pkg install pg3x sudo service pg3 onestart

We just identified the root cause and currently working on a fix.

Please check the PG3x log using: tail -f /var/polyglot/pg3/logs/pg3-current.log If you see nothing useful, please open a ticket, and attach the content of: tail -n 200 /var/polyglot/pg3/logs/pg3-current.log

Please open a ticket. When not detecting local IoX, it's a symptom of a bigger problem with either the UDX or ISY service.

Hello everyone, This is the support thread for PG3x v3.2.4. UPDATE: PG3x 3.2.4 has been fixed.

Hello everyone, Here's the latest PG3x release. Release notes for: 3.2.4 - 09/07/2023 Fixed update/install for higher version than license (Bug introduced in 3.2.3) Fixed bug preventing older UD Mobile version to install plugins (node servers) Refactor code to get uuid from IoX Refactor node server info page Refactor store page edit for developers Fixed bugs when trying to save multiple times. (Node server ID in undefined will be replaced by the node server ID from the Local entry.) Added more strict validation of the version number with semver Hide cost field when this is a trial or free tier Hide url/branch/file upload fields when this is a tier upgrade

@bgrubb1, I can reproduce the problem. You can expect a fix in 3.2.4 this week.

It looks like PG3 from your former polisy is still logged in to your account. If the polisy has been migrated to PG3x and is fairly recent, the proper way is to click on System | Switch Portal profile. The new owner will be prompted to reenter his portal credentials. He can create a new account if he does not already has one. If he purchased licences, this will follow his polisy as this is tied to the uuid, not the account.

@bgrubb1, which node server did you try to purchase, and what was the error?

Thanks for the feedback. On my system, I only had warning. This is the expected output: [admin@eisy /var/polyglot/pg3/ns]$ sudo pip3 uninstall aioquic Found existing installation: aioquic 0.9.21 Uninstalling aioquic-0.9.21: Would remove: /usr/local/lib/python3.9/site-packages/aioquic-0.9.21.dist-info/* /usr/local/lib/python3.9/site-packages/aioquic/* Proceed (Y/n)? y Successfully uninstalled aioquic-0.9.21 WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv [admin@eisy /var/polyglot/pg3/ns]$ sudo pip3 install aioquic Collecting aioquic Downloading aioquic-0.9.21.tar.gz (153 kB) ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 153.4/153.4 kB 1.4 MB/s eta 0:00:00 Installing build dependencies ... done Getting requirements to build wheel ... done Preparing metadata (pyproject.toml) ... done Requirement already satisfied: certifi in /usr/local/lib/python3.9/site-packages (from aioquic) (2023.7.22) Requirement already satisfied: pylsqpack<0.4.0,>=0.3.3 in /usr/local/lib/python3.9/site-packages (from aioquic) (0.3.17) Collecting pyopenssl>=22 (from aioquic) Obtaining dependency information for pyopenssl>=22 from https://files.pythonhosted.org/packages/f0/e2/f8b4f1c67933a4907e52228241f4bd52169f3196b70af04403b29c63238a/pyOpenSSL-23.2.0-py3-none-any.whl.metadata Downloading pyOpenSSL-23.2.0-py3-none-any.whl.metadata (10 kB) Requirement already satisfied: cryptography!=40.0.0,!=40.0.1,<42,>=38.0.0 in /usr/local/lib/python3.9/site-packages (from pyopenssl>=22->aioquic) (41.0.3) Requirement already satisfied: cffi>=1.12 in /usr/local/lib/python3.9/site-packages (from cryptography!=40.0.0,!=40.0.1,<42,>=38.0.0->pyopenssl>=22->aioquic) (1.15.1) Requirement already satisfied: pycparser in /usr/local/lib/python3.9/site-packages (from cffi>=1.12->cryptography!=40.0.0,!=40.0.1,<42,>=38.0.0->pyopenssl>=22->aioquic) (2.21) Downloading pyOpenSSL-23.2.0-py3-none-any.whl (59 kB) ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 59.0/59.0 kB 2.9 MB/s eta 0:00:00 Building wheels for collected packages: aioquic Building wheel for aioquic (pyproject.toml) ... done Created wheel for aioquic: filename=aioquic-0.9.21-cp37-abi3-freebsd_13_1_release_p7_amd64.whl size=92308 sha256=38f9a1084a60c2ecf26499995128b9a4d2ecaac0462ae4583e52ecc153327630 Stored in directory: /root/.cache/pip/wheels/ac/a8/24/70b950af1c5ceb452388b3562e6c80b085bc5f71c799f7e813 Successfully built aioquic Installing collected packages: pyopenssl, aioquic Attempting uninstall: pyopenssl Found existing installation: pyOpenSSL 21.0.0 Uninstalling pyOpenSSL-21.0.0: Successfully uninstalled pyOpenSSL-21.0.0 Successfully installed aioquic-0.9.21 pyopenssl-23.2.0 WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv There is probably a more direct command to update pyopenssl to 23.2.0 but could not test it.

Hello everyone, We found that a system update is causing issues with node server startup on eisy. We are working on a permanent fix. But for now, here's a solution: ssh to your system (on Windows, you can use putty) Run these 2 commands: sudo pip3 uninstall aioquic sudo pip3 install aioquic You can ignore the warnings. This will reinstall aioquic at the same version (0.9.21). However it does check dependancies. On my system, this uninstalled pyOpenSSL 21.0.0 and reinstalled it at 23.2.0. This solved the problem.

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.