bmercier

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.

As Javier pointed out, the web UI is not available remotely. PG3 Remote Connections allows you to: Use Node Server webhooks. Currently, only the Ring Node Server uses webhooks. Use the new Reinstall all Node Servers from portal UD Mobile Node Server management. Look under Admin | Plugins

Hello everyone, Please note that the menu in ISY portal has been updated. Under Select tool, there is now a new PG3 option: Purchased Node Servers: This option shows your node server purchases, which should be the same list as shown in PG3 under Purchases. Remote Connection: This option is used to allow a Remote Connection from portal & UD Mobile to PG3. The Ring Node Server uses this. This option used to be under Maintenance | PG3 Remote Connection. Reinstall all Node Servers: This option is the same as the PG3 option System | Re-install all node servers. This may become useful if you need to remotely update your node servers. Please note that Remote Connection and Reinstall all Node Servers will show up only if you are using PG3x with the minimum firmware level.

Yes. You can expect a 3.2 which will include this to come out soon.

If you can access it locally, you probably don’t need the backup. Did the owner give you his portal account, or did you set a new one? Polisy should automatically connect to portal when powered on. In your portal account, under the ISY tab, you should see your Polisy uuid, the same that you see in the admin console. Do you? If so, what’s the color of the round indicator after the uuid?

First of all, are you able to access the device locally with the admin console?

This means that UDX is not working. Troubleshooting steps: 1. Leave it a bit of time after boot up 2. Power down, wait a few secs, power on 3. In SSH: sudo service udx restart Sent from my iPhone using Tapatalk

Hello all, Once again we are resquesting help to beta test PG3x. 3.1.37 is now in beta and has again major changes and bug fixes: Changelog: Dashboard now shows node servers connected state in real time Fix the Purchase page with duplicated entries In the purchase page, show the update button only if an update is available Please note that if a node server advertises itself at a version which is different than the version in the store, then the update button will appear. Some node servers will therefore still show the update button although they are at their latest release. 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 (To be tested further) In node server nodes, property variable can be copied using copy icon Add support for dynamic property texts (UOM 150) - (To be tested further) General code enhancement Security fixes We would appreciate your feedback. Since this is a beta release, the installation is done through ssh with two commands: sudo pkg add -f https://pkg.isy.io/udx13.staging/All/pg3x-3.1.37.pkg sudo service udx restart We would appreciate your feedback.

@MrBill, are you on slack? Please change the node server status to new Sent from my iPhone using Tapatalk

Will look at it later today Sent from my iPhone using Tapatalk

AVremote needs to be fixed by the node server developer. I believe the node server is 2.0.6, but still advertises itself as 2.0.5, which makes PG3x display the update button. Sent from my iPhone using Tapatalk

It will be available later today Sent from my iPhone using Tapatalk

Hello everyone, This is the support thread for PG3x v3.1.36. After updating to 3.1.36, please click on System | Reinstall all node servers, which will reinstall all your node servers including the new UDI python interface 3.0.60. UDI interface 3.0.60 fixes a bug where the node servers loses their connectivity with PG3 when eisy loses network connection. You will have to restart your node servers after the update. You can check the UDI interface version in the node server's logs near the start. 3.1.36 will be available for installation on July 11th,

Hello everyone, Here's the latest changes. After updating to 3.1.36, please click on System | Reinstall all node servers, which will reinstall all your node servers including the new UDI python interface 3.0.60. UDI interface 3.0.60 fixes a bug where the node servers loses their connectivity with PG3 when eisy loses network connection. You will have to restart your node servers after the update. You can check the UDI interface version in the node server's logs near the start. Changelog for 3.1.36 "System | Re-install all node servers" now also updates the UDI interface module for all node servers. This is to update UDI interface to 3.0.60 Minor security fixes Changelog for 3.1.35 Significant rework on error handling in async functions Login API has been enhanced (Login should always work, or give an error message) Restore backup/Migrate from PG3: Made the UI more intuitive Notifications from PG3 now specify the uuid Restart required bug fixed