bmercier

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.

When saving a spoken, it is looking for an oAuth access token that is used to communicate with Amazon. That token is created at the time of linking. This token does not exist if not linked. Previously, there were cases where if missing, this would create an HTTP 500 error. Now, the access token is still missing, but at least it is handled properly. If you have not unlinked and relinked, please try it. If this does not solve the problem, please open a ticket referencing this thread, mention your uuid, and whether you are initiating linking via the Alexa app, or UD Mobile.

Have you tried to unlink and relink today? I made a fix this morning.

Ed, Could you try to unlink and relink the skill? This is likely to solve the problem.

Notifications are now limited to 10 notifications per minute. The goal is to prevent such things as a program caught in a loop sending tons of notifications. If you see a case where this limit is too low, please let me know. This limit is enforced on a portal API that the notification plugin uses, and it is based on the source IP. This means that if you have 2 eisy at the same location, then the limit would apply to both units combined.

No, not related

We will be adding a rate limiter to the push notifications API to prevent this type of problems in the future. Unfortunately, eisy is too powerful

Currently investigating Sent from my iPhone using Tapatalk

I looked at the logs, and it looks like your problem is now resolved. If not, please open a ticket and it will be a pleasure to help you. Benoit

When adding/updating/deleting Alexa spokens from Portal or UD Mobile, changes are now immediately reflected in Alexa. It's no longer required to ask "Alexa, discover my devices" to send updates to Alexa. This change makes the maintenance of spokens easier and less error prone. This works as long as the skill is linked. You can still add or update spokens while the skill is not linked, however a device discovery will be required to send updates (it's done automatically after linking). If you delete spokens while the skill is not linked, then the corresponding Alexa device also has to manually removed from the Alexa app, just like before. A device discovery only add/updates the Alexa devices. It won't remove the spokens removed from portal or UD Mobile.

I have made a few more tests. Some that work: HDMI1 HDMI2 DVR ANTENNA Many don't though. When you hear <device> doesn't support that, it's a sign that the input was understood, but your A/V device did not have that input defined. If you hear any other error message or a beep, Alexa does not understand the input you spoke.

Wow, that's a neat trick. Never though of that, but it makes sense. Thanks for sharing!

Please try different and easier input names. Because the the input select names are custom, Alexa has to really understand very well the name so that it can be an exact match to what you entered.