bmercier

@johnstonf I know you did not like my answer, but I would still recommend to give it a try. For case 1: Test from the GH app directly (Don't talk, use the buttons in the app). For case 2: Delete the device from GH app, then ask GH: Hey Google, sync my devices. If the device reappears, it is indeed in Portal. For case 3: Check your mapping in portal. Make sure the ISY address exactly matches the address you see in the admin console. For case 4: Make sure you can control the device from the admin console.

The problem I described is not the same thing then. The cannot contact universal devices error may be caused by many things. The first thing to do it figure out if this is for specific devices, or for any devices. If all devices have the problem, then relinking is the way to go. If it's just specific devices, this can be one of the following reasons: GH does not understand you correctly and turns on/off something else that indeed does not respond. The device in GH is orphaned (the device exists in GH, but no longer exists on portal) The device exists in both GH and Portal, but no longer exists on ISY The device exists in both GH, Portal and ISY, but actually does not respond ( This could be a communication issue (Insteon/ZWave issue, node server issue) Or the device is dead. First you have to figure out which GH device exactly does not respond. When you know which GH device does not respond, you need to figure out which of the above is the issue. For case 1: Test from the GH app directly (Don't talk, use the buttons in the app). For case 2: Delete the device from GH app, then ask GH: Hey Google, sync my devices. If the device reappears, it is indeed in Portal. For case 3: Check your mapping in portal. Make sure the ISY address exactly matches the address you see in the admin console. For case 4: Make sure you can control the device from the admin console.

If by disconnect you mean that you can no longer Send spokens to GH, but everything else works; this is a known problem. It seems that Google at some point loses track of the "agentUserId", which means that it no longer recognizes who the user is when sending spokens. When this happens, well, everything else works. This means you can continue to use use it. When you have new spokens to add, instead of clicking "Send spokens", ask "Hey Google, sync my devices". That should work. If that does not work then it means it may be a different problem.

If you have a paid Node Server that is not starting, please do this: Make sure your PG3x version is 3.2.13 or newer Go to Plugins Store, find the Plugin not starting On the plugin page, click on Install (Make sure you choose the Standard edition, not the Free edition) Reinstall on the same slot as it was installed. Explanation: Some Paid Plugins may have stopped working following a PG3x update. This can happen on Plugins that have multiple editions, such as a Free and a Standard edition. There has been a change in PG3x in a recent version which allows to own a license per edition. However, installations of plugins on versions prior to 3.2.13 did not properly record the edition it was installed with. This means that when PG3x is checking for a license, it could fail if it thinks that the Free edition is installed and the expiry of the Free trial is passed.

Please go to Plugins store, find the Kasa node server and re-install from there in the same slot.

I don't even see the restart of the Node server. I believe the restart must be a bit before.

I believe this is a core dump from Python. I would suggest to: Check the date and time of the code dump. Find the Kasa log file matching the date of the core dump, and transfer to your PC. (If not today's log, that will be a tar archive). Use a tool like Alzip to open the archive and get the log for that data. Check the node server log entries just before the time of the core dump. It could help to find out the cause of the crash.

This can be 4 things: GH does not understand you correctly and turns on/off something else that indeed does not respond. The device in GH is orphaned (the device exists in GH, no longer exists on portal) The device exists in both GH and Portal, but no longer exists on ISY The device exists in both GH, Portal and ISY, but actually does not respond ( This could be a communication issue (Insteon/ZWave issue, node server issue Or the device is dead. Now, this happens when turning off lights in a room. First you have to figure out which GH device exactly does not respond. When you know which GH device does not respond, you need to figure out which of the above is the issue. For case 1: Test from the GH app directly (Don't talk, use the buttons in the app). For case 2: Delete the device from GH app, then ask GH: Hey Google, sync my devices. If the device reappears, it is indeed in Portal. For case 3: Check your mapping in portal. Make sure the ISY address exactly matches the address you see in the admin console. For case 4: Make sure you can control the device from the admin console.

@Geddy, @btreinders, I don't know why there would be such a big difference. This is just a regular tar archive. I would suggest to open up 2 archives, one large and one smaller, and see if you can spot a difference. They should contain the PG3 database, and the content of the nodeserver folders. You can use a tool like alzip to open a tar archive on Windows.

I'm sorry to hear that. If ssh does not work after a reboot from the cli, somethings must have happened, and that would not be related to PG3x. Try a complete power cycle when you get home. If that does not help, please open a ticket we will make sure to get you back on your feet.

Yes, except that the reinstall node servers is not necessary most of the times.

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

Hello everyone, Here's the latest PG3x release. Release notes for: 3.2.13 - 10/24/2023 Fix purchase process so it is edition-aware (This fixes the license check) oAuth: Add the scope to the token endpoint (Some oAuth servers needs it) Fix adding nsdata/oauth to the custom table (Fixes a bug that could prevent oAuth Authentication) When installing a plugin, display the purchase date and expiry in local time

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?