bmercier

inactive is good. This means it's at the latest release and no more actions are required. If a reboot was required, which we suspect is the case in mbking's situation, we would see it there.

Could you check https://eisy.local:8443/desc Look at the bottom, what do you see on the tag upgradeStatus?

Excellent question. I would first recommend to upgrade packages in admin console.

Hello everyone, PG3 is now in end of life. This means that there will be no more enhancements or fixes to it. This also means that as PG3x evolves, you will see more and more plugins (node servers) that will start to work on PG3x, but not PG3. I am using a Polisy, do I need to upgrade? Polisy came preinstalled with PG3, but can be upgraded to PG3x. We encourage you to migrate to PG3x, as this will allow you to stay current and use all of the plugins available. All the plugins working on PG3 also work on PG3x as PG3x is backward compatible. PG3x is also using a different architecture which allows the platform to be more secure. If you are unsure if you are already running PG3x or not: If you are doing an "upgrade packages", but the version does not upgrade beyond 3.1.23, this means you are on PG3 (PG3x current release is 3.2.8) Go to https://polisy.local:3000. If you see "Polyglot 3x" on the top left, you are on PG3x. I am using an eisy, do I need to upgrade? If you are using an eisy, it comes pre-installed with PG3x. Therefore, all you have to do to stay current is use the admin console or portal to "upgrade packages", which will update your PG3x version and other eisy components. Upgrading to PG3x First upgrade packages in admin console. Enable PG3x by clicking this link: https://polisy.local:8443/rest/pg3x.enable Reboot and wait for a beep, then a second beep. Migrating node servers from PG3 to PG3x might take up to 2 minutes per node server. So, please be patient Once all node servers show connected, reboot again. NOTE: This process will remove PG2 and PG3. Furthermore, there is no "undo" for this process. Please make sure you take a backup first.

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.