bmercier

We are getting many reports of portal being offline. At this time, it looks like it's up and most isy/polisy/eisy are online and working. We are currently investigating this and will post an update here when we have more information.

Please update the plugin to version 1.1.7, that should fix it.

Login to portal using the same portal credentials. Click on My Profile (top-right), and change the preferred ISY to your eisy.

Please open a ticket referencing this thread. Make sure to mention your uuid and the node address that is “matched properly in my.isy.io” but that won’t appear in google home when syncing. I will investigate further.

Those settings only control the discovery of devices. Once they are discovered by Alexa, the devices will continue to work as long as the spoken still exists and the ISY is still in the account.

Did you login with the same portal user and password? If so you should see them there. The "Showing 51 to 1 of 1 entries" seems to indicate a UI problem. I suspect there may be special characters that may be messing the display. Are you able to reproduce the problem? Please open a ticket, attach the screen shot, and please let me know the uuid. Will also need to know what browser you are using as it may be browser-dependant. If you know how to reproduce it, please let me know how.

It could have been that it was not approved in the admin console, then you approved it before trying it again? Or perhaps it was just not online, but then, the message would have been different.

My recommendation would be Alexa. I developed both the Alexa skill and Google Home action, and I can tell you the integration is slighty more advanced with Alexa. We also have significantly more customers using Alexa than GH.

I'm not sure what are the capabilities of this node. I guess it's used to arm and disarm. Does it accept commands like DON/DOF? if so, with the right hint, it could be exposed as a light. @KHouse, You could try hint 1.2.9.0 as a test. After changing a hint, you need to add or remove/re-add the node to the spokens, then have Alexa discover your devices. The main problem I see though is that if you expose this node directly like this, then turning on/off will allow to arm and disarm. If you only want to arm by voice, and prevent disarm, then I would take this approach: Create a program, in the then statement, have it arm your elk. Leave the else empty. Expose the program as a light. Add the program to the spokens, have Alexa discover your devices. "Turn on" will run then, "turn off" will run else... which means it won't do nothing. @Jimbo.Automates, the hint for an alarm panel should be 1.1.1.x, as defined in hints.yaml. But that will not make it work with Alexa. The skill does not currently have support for an alarm panel. But that could be a future enhancement.

I don't think the log level was persistant in the past. There were no database fields & no code to support that. When changing the level in the UI, the setting was also not persistant in the UI. Just switching to Dashboard and back to the Log did reset the selector to Info (But the back end stayed at whatever was previously selected). Now, the UI properly reflects the current logging level in the back end AND is persisted following a restart.

Hi @Xathros, The PG3 log level has always reset to info on reboot, and the UI would not persist the state when navigating. I made the PG3 log level persistent, and this will be included in the next PG3x release. Thanks, Benoit

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

Hello everyone, Here's the latest PG3x release. Release notes for: 3.2.16 - 11/9/2023 When PG3 start/stop, send a single notification (instead of one per plugin) Auto-install default node servers after login Add install.log to the log packages Include stderr to install.log

No it is not automatically updated with other updates. The only case where it is installed is on installation (or réinstallation) of node servers.

Hi everyone, We just released UDI Python interface 3.2.4. The main change is an attempt to fix an SSL error that can happen once in a while when publishing messages to PG3x. To update, use System | Reinstall all plugins. 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.4 Starting... Thanks to @bpwwer for this fix. Benoit

Hello everyone, This is the support thread for PG3x v3.2.14 & v3.2.15. For currently working systems, there is not much benefits to upgrade. These versions are useful for new installations.

Hello everyone, Here's the latest PG3x release. Release notes for: 3.2.15 - 11/6/2023 Fix IoX showing disconnected following initial startup Fix store selector being blank following initial startup

Hello everyone, Here's the latest PG3x release. Release notes for: 3.2.14 - 10/26/2023 Add capability to restore a backup from another PG3x Minor bug fixes

@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.