bmercier

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

Hello everyone, Here's the latest changes. Changelog for 3.1.32 Fixed queuing of nodeserver commands. This is likely to increase reliability of commands sent to IoX. Fixed double portal credential login Remove option "System | Restart PG3x option" PG3x should not be restarted without UDX Added spolisy topic and API for notifications from IoX Handle notification requests coming in via the MQTT connection. Listen for messages on the spolisy topic. The WebUI already uses this to capture messages about system events (upgrades/reboots/etc). Add API for notifications. This allows incoming notification messages to be forwarded via the notification service to UD Mobile. On login, automatically add the Notification nodeserver to the list of purchases For developers, in the nodeserver edit, allow to use a blank version Submit was failing if the main form version was blank (or not in the proper format) We want to leave this in place for now because not all node server entries have been updated to the new purchase option format. Allow the node server to include a 'name' field in the driver array and if there, save it in the database. Note, updating an existing node server won't update the driver database. This TBD. In the list of properties of a node, display the driver name, and also the variable to be used in notifications. On the nodeserver info page, display the slot number it is installed in In the nodeserver info, along with the nodeserver name, display the version for reinstall/update Version upgrade messages kept being added multiple times Handle random parameters in POST from IoX. Changed the config pg3xVersion to pg3Version so the UI don't fail Updated a few modules to keep current Changelog for 3.1.31 In the nodeserver config, add pg3xVersion & isPG3x. This allows a nodeserver to determine if minimum requirements are met. Changelog for 3.1.30 Handle more complex notification POSTs from IoX Check the latest pkg version of PG3x to get the current release

Hello everyone, June 16th update: The existing smart home action "Universal Devices" should continue to work. We are in the process of reconfiguring the smart home action, and we are working with Google to make the change transparent to our users. No action should be required for those who already have it enabled.

Hello everyone, June 14th update: Apparently the action is still working. In our google actions console, it now shows as sunset and can't no longer be modified. The new action we submitted is still not reviewed by google. There has been back and forth with support, but there is no resolution yet. It's possible that the existing action will continue to work without interruptions.

Hello everyone, Just a quick update; Our updated Google Home action was submitted for review Wednesday last week. I escalated the review with Google, and as of yesterday, they confirmed it was under review. However, as of this morning, there is no update yet. Hopefully it will be available in the next few hours. Benoit

Hello everyone, Our current Google Home action will stop working on June 13th and will need to be replaced. This is due to Google which sunset Google conversation actions. Ref: https://developers.google.com/assistant/ca-sunset We are currently working on the new action "Universal Devices V2", and it should be ready on time by next week. Whenever it becomes available, you will have to unlink "Universal Devices" and relink using "Universal Devices V2". All of your "spokens" that you have configured in portal will still be there. However, whenever you unlink and relink, this will remove the devices in Google Home/Google assistant, and re-create the same devices. You will have to reassign rooms, and it will probably break your routines as well, if you are using them. Stay tuned.

Portal is up, and ISYs/Polisys/eisys are currently reconnecting.

Maintenance has started a bit late and is currently underway.

Why are you using polyglot.isy.io? Sent from my iPhone using Tapatalk

A forum post here is a good option. Often, the problem is not portal itself, and the community can help. Alternatively, a opening a ticket is another option, when you are certain that there is a problem and the community can't help. I do not actively follow forum posts, but I get notified of posts in this topic. I saw your post and investigated immediately.

One of the server lost it's connection to the database and was restarted.

Hello everyone, We will have a maintenance on Monday 06-05-2023 at 5:00 AM Pacific time which will last about 30 minutes. During this period, Portal will be offline. Benoit

I guess the Update button does not exists when the nodeserver is installed from the beta store. You should reinstall from the production store. There is a trial available.

In PG3, go to the Ring nodeserver (ISY Dashboard | Ring | Details), then click Update

FYI, Ring 1.1.0 is now available. New feature: Add support for shared devices. To support shared devices, you need to add a custom param "shared" with a value of "true" (without the double quotes)

Try this URL in a browser: https://<your eisy>:3000/frontend/cloudlink Make sure that <your eisy> is the same IP or hostname that you are using to access PG3 This URL should give you an error. Then try again the Authenticate button Not sure why the Update button would pop info about the node though. Benoit

Make sure you are using Ring from the Production store. The Non-Production store will not authenticate with the current settings.

Unfortunately no, as this is not available in the API.

Use Select tool | Connectivity | Device Hint Editor Choose your device and change the hint to 1.0.0.0. This will make it recognized as a dimmable device.

Portal maintenance is completed.

Please try again, this should work better now.

Hello everyone, We will have a maintenance on Tuesday 05-02-2023 at 5:00 AM Pacific time which will last about 30 minutes. During this period, your ISY may disconnect briefly from portal. The purpose is to update SSL certificates.

This is happening because the device type is not recognized. If you try to use /rest/nodes/<your device address>, the type is probably 0.0.0.0. This is typical of early nodeservers. To fix this, use Select Tool | Connectivity | Device Hint Editor. I'm not sure what this device can do, but if it can be set to a value of 0 to 100, I would suggest to try 4.17.x.x, which is the equivalent of a dimmable ZWave dimmer. If this is only fully on/off, you can also use 2.x.x.x, which is the equivalent of an insteon non-dimmable switch.

There are many reasons why a connection may drop. If it's just once in a while, there is nothing to be concerned about. I would suggest to look at the ISY error log, there might be something happening there.

Portal maintenance is now completed.