bmercier

I can't see how 3.2.20 would impact this. I see your other post. Let's see what Goose thinks.

That's very odd. Were you on 3.2.19 before? The changes between version is minimal. The only possible impact would be that it may be running faster. I would recommend a post in the MagicHome forum. I have no clue what may be causing this.

Every MQTT messages coming to PG3x go through up to 2 queues which are used to rate limit the requests; 1. MQTT messages from plugins are in their own queues, in order to prevent a plugin to take up all resources, and frontend messages are also in their own queues, to prevent attack. These queues have their own rate limit sets. 2. A global Queue, which applies system wide limits. This is the latter that has been disabled as it has been observed to cause problems on some systems.

Hello everyone, This is the support thread for PG3x v3.2.20. Starting with PG3x 3.2.19, if you are using the Backup or ELK plugin, please make sure to select the "Allow ISY Access By Plugin" in the configuration page.

Hello everyone, Here's the latest PG3x release. Release notes for: 3.2.20 - 03/12/2024 Disable the global MQTT queue (Fix to the Auto-Logout) Minor fixes

Please check if you still have the problem. I have reports from another user that it started working today. You may have to recreate the routine. If not, please open a ticket and let us know: The uuid The type of ISY "device" you are using. Is it an ISY state Variable? Insteon IOLinc? Something else? The device address What time you did the test and in what time zone (Or better, the UTC time you did the test)

Updating PG3 does not update the interface. Reinstall all is used to update the interface & the plugins versions.

@TJF1960@macjeff Looks like this plugin needs access to the rest API. The author needs to edit his store entry and check "Require ISY Access". Then, in the configuration page, PG3x will display the "Allow ISY Access" checkbox. Not sure who the author is, and if this plugin is still maintained.

This applies to plugins that want to make rest requests. Other apps can still use rest requests the same way as before.

Hello everyone, This is the support thread for PG3x v3.2.19. If you are using the Backup or ELK plugin, please make sure to select the "Allow ISY Access By Plugin" in the configuration page.

Hello everyone, Here's the latest PG3x release. Release notes for: 3.2.19 - 02/26/2024 Enforce ISY access security - For plugins that require ISY access, user has to click Allow ISY Access PG3x Logging to syslog now only includes the startup and shutdown sequence On addnode, if creating the node on IoX fail, log the error If oAuth authorization code exchange fails, log the token endpoint response ISY Access security Starting with this release, plugins can no longer directly access your eisy/polisy using the rest API unless you allow it. Most plugins don't need direct access. Some plugins like Backup and ELK may need it. If the plugin needs direct ISY access, a checkbox "Allow ISY Access By Plugin" will appear in the configuration page. If you are using the Backup plugin, you need to enable ISY Access. If you are using the ELK plugin, and if you are using ELKID or ELKNAME you must enable ISY Access as well.

Please open a ticket and write your uuid and a reference to this thread. I will take a look at the server logs. The 994 is no longer supported, but I will take a look for you.

First of all, there is no "ISY Portal Event log" or "ISY Portal Error log". Those are the ISY Error log and ISY event log. They are just accessible from ISY Portal. There is nothing in there that relates to Alexa. Please try what I suggested: Delete the Alexa routine and re-create it.

In my opinion, either your 994 is not sending events, or Alexa is not processing them. Let's take the Alexa side first. You did not mention how you exposed your state variable to Alexa. Could be as a light, a contact sensor, etc. But regardless, I'm assuming that you are using said Alexa device to trigger an Alexa routine which does not work. My suggestion would be to delete the routine and re-create it. I have seen cases where a routine would stop working and it had to be recreated. On the ISY side, I do now know what the problem would be, but I would say that the messages -170001 UDQ: Queue(s) full is suspicious.I think something might be overloaded. Are you able to login to the Admin console? Does it show your 994 as busy?

Yes you should. When you upgrade to 3.2.19, then the plugin will continue to work.

Hi Paul, This would require major changes. We are currently working on a new eisy/PG4. New features to PG3 will be limited to bug fixing and small enhancements. For remote access to PG3, you can use UD Mobile. Click on Admin | Plugins.

My apologies, I made a mistake in the changelog. ISY Access security is something coming in PG3x 3.2.19 - not the Python interface. I intended to release PG3x 3.2.19 today as well, but will wait for the Backup plugin to be updated first. You can safely update the python interface on all plugins. The benefits are limited though as the changes are mostly for upcoming plugins which will require this version of the interface, or for new installations of plugins (it needs to install paho-mqtt 1.6.1 instead of 2.0.0rc2 - existing installs should have 1.6.1).

Please be aware of these changes in the new interface:

Hi everyone, We just released the UDI Python interface 3.3.1. Change log: Ensure the interface does not use paho-mqtt v2 (paho-mqtt v2 is still beta and it breaks plugins) Don't load the server.json if not needed setDriver now returns a flag indicating if the value is different than before New integrated oAuth module (Some new plugins will need this) Enhancements to the Custom class To update to the new version, use System | Reinstall all plugins. If you want to know what version of UDI Python interface a plugin is using, restart the plugin 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.3.1 Starting... Benoit

The fix to the interface is implemented. If you have a plugin with the error, delete and reinstall the plugin.

Paho-mqtt now has a new version 2.x of their library which is breaking plugins. You will see this error in the log: ValueError: Unsupported callback API version: version 2.0 added a callback_api_version, see migrations.md Traceback (most recent call last): File "/var/polyglot/pg3/ns/0021b902606d30/hunterdouglas-poly.py", line 77, in <module> polyglot = udiinterface.Interface([]) File "/var/polyglot/pg3/ns/0021b902606d_30/.local/lib/python3.9/site-packages/udi_interface/interface.py", line 253, in __init self.mqttc = mqtt.Client(self.id, True) File "/var/polyglot/pg3/ns/0021b902606d30/.local/lib/python3.9/site-packages/paho/mqtt/client.py", line 766, in __init raise ValueError( ValueError: Unsupported callback API version: version 2.0 added a callback_api_version, see migrations.md This impacts new installation of plugins. Plugins already installed will continue to work as long as they are not reinstalled. On monday a new UDI interface will be release to fix this. Stay tuned.

It is now at the top. I just forgot to pin the topic.

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

Hello everyone, Here's the latest PG3x release. Release notes for: 3.2.18 - 02/07/2024 Rate limiter: Increase limits on the global queue Add support for the upcoming python interface oAuth module When UI requests "customs", return a key for all requested "customs" Fixed Authenticate button which sometimes does nothing Fixed devd configuration when in developer mode

For everyone following this thread, the problem was resolved by unlinking and relinking the skill.