bmercier

Hello everyone, This is the support thread for PG3x v3.2.12. Please note that this releases fixes 2 regression bugs introduced with 3.2.11. There are no new features specifically with 3.2.12. PG3x 3.2.12 changes: PG3x 3.2.11 changes:

Hello everyone, Here's the latest PG3x release. Release notes for: 3.2.12 - 10/23/2023 Fixed 2 regression bugs introduced with 3.2.11

Hello everyone, Unfortunately, 2 regression bugs were introduced with this release. Look for 3.2.12 to be released later today.

Will release PG3x 3.2.12 to fix this. Benoit

No, it is not related.

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

Hello everyone, Here's the latest PG3x release. Release notes for: 3.2.11 - 10/23/2023 Fix license check for node servers with multiple editions. UI: Rename Node Servers -> Plugins. UI: Hide the developer menu when logged out. UI: Fix Migrate from PG3 backup file selection. UI: Updated reinstall all confirmation message. oAuth: Add logging of authorization failure. Enhance error handling when isy is not found in the config.

I would just reboot. Sent from my iPhone using Tapatalk

When you change the timezone in the admin console, it should also change the timezone of the OS. PG3 will take the timezone from the OS on startup. So if you change the timezone in AC, I think you would need to reboot to get PG3 to use the new time zone.

After a re-install, it's normal that it restarts automatically. This has been enhanced a few releases ago. Will update the warning accordingly. Thanks for reporting this.

Hi everyone, We just released UDI Python interface 3.2.3. The main change is to fix an error that can happen if 2 threads attempt to publish to MQTT at the exact same time. The symptom will be a restart of the node server. To update, use System | Re-install all node servers. If you want to know what version of UDI Python interface a node server is using, restart the node server and look for a line like this: 2023-10-19 09:15:53,244 MainThread udi_interface INFO __init__:<module>: UDI Python Interface for Polyglot version 3 3.2.3 Starting... Thanks to @bpwwer for this fix. Benoit

Sounds like a great idea! How do you trigger the Sonos speakers - Are you using Sonos or ST-Sonos plugin? Can you expand on what you do with the Sonos integration? Are you using spotify, or have the Sonos talk with the text to speech?

Thanks for the tip. I think there is an easier way to do the same thing though. Create a state variable. In portal, expose the variable as a contact sensor (or whatever else you prefet) Then use the device to trigger a routine.

Hello, I was wondering if anyone is using automation for Halloween. I was thinking that it may be cool to use Ring as a trigger for sound outside, or perhaps activate some movement. This could be when kids ring the bell, or as they approach the door. Anyone has plans like this? If so, share your ideas!

Hello everyone, This is the support thread for PG3x v3.2.10. If you are already on 3.2.9, there is no need to update unless you are a node server developer.

Hello everyone, Here's the latest PG3x release. Release notes for: 3.2.10 - 10/12/2023 Fixed the profile upload when in developer mode

Hello, Please open a ticket, reference this post, and also attach the result of https://eisy.local:8443/WEB/sysconfig.txt. Thanks, Benoit

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

Hello everyone, Here's the latest PG3x release. Release notes for: 3.2.9 - 10/09/2023 Restore process: Allow restore to a new system (it will do a reinstall all) Restore process: Go back to login after completing restore Fixed the "No IoX was automatically discovered on your local network." error.

This means that the update was completed successfully (no additional reboot is required).

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.