bmercier

Hello everyone, This is the support thread for PG3x v3.2.8.

Hello everyone, Here's the latest PG3x release. Release notes for: 3.2.8 - 09/29/2023 Fixed node server service configuration file On a restore, ensure udi_interface is installed at the latest version Return success response to node server on a successful node rename PG3 Developer Help: Change from Slack to Discord Fixed case where recurringPeriod may be present but undefined Fixed case where developer mode may be set incorrectly on store entries

Are you perhaps running a VPN? Can you check if you can login directly to Ring?

I do, replied in the ticket.

Google Home action has not changed and is still working.

That's an excellent question that I should have clarified first. It's not necessary to update PG3x for non-developers as there are no real benefits, but it does not hurt to update either. You can wait for the next release to update.

Hello everyone, This is the support thread for PG3x v3.2.7.

Hello everyone, This release features enhancements for node server developers. Release notes for: 3.2.7 - 09/21/2023 Implementation of the new developer mode Developing node servers using PG3x is now much easier. PG3x can run your node server under development directly from your development location, and run as the user of your choice. When saving to the store, validate that custom parameters, device configuration & oauth config are valid JSON Removed capability to create upgrade options (for now) Fixes to store management UI When updating local store entry, update time modified Minor logging enhancements IMPORTANT: If you are currently using developer mode, I recommend you commit and push your changes, then delete your existing developer mode nodeserver. In the new version, deleting a developer mode node server will leave it intact on the file system. BUT, node servers installed using the previous method WILL BE DELETED. For developer support, please use our Discord channel.

It's not possible and not in the plans. Components have dependencies on other components, so we can't cherry-pick which ones we want to upgrade.

Hello everyone, This is the support thread for PG3x v3.2.6.

Hello everyone, Here's the latest PG3x release. Release notes for: 3.2.6 - 09/15/2023 Fix a problem which makes UD Mobile detect a reboot is required Fix to the store update (Fix url rewrite if the url uses "production"/"beta"/"local") Refactored code when updating store record

This means you are on PG3, not PG3x. To upgrade PG3 to PG3x: https://wiki.universal-devices.com/index.php?title=Polisy:User_Guide#Upgrading_to_PG3x

If anybody still has problems, you can upgrade packages again. Problem has been solved.

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.