After attending the webinar, I thought I'd give EISY AI a try to create a plugin. After installing EISY AI, the plugin status is "Starting". Is there something that needs configuring?

I do notice some errors in the log. The following is after clicking on Restart:

2026-11-07 17:20:30.017 MainThread udi_interface INFO init:<module>: Loading interface module

2026-11-07 17:20:30.065 MainThread udi_interface INFO interface:<module>: Loading MQTT module

2026-11-07 17:20:30.609 MainThread udi_interface INFO interface:<module>: MQTT module loaded

2026-11-07 17:20:30.839 MainThread udi_interface INFO init:<module>: Loading udi_interface module

2026-11-07 17:20:30.840 MainThread udi_interface INFO init:<module>: Loading node module

2026-11-07 17:20:30.840 MainThread udi_interface INFO init:<module>: Loading custom module

2026-11-07 17:20:30.840 MainThread udi_interface INFO init:<module>: Loading isy module

2026-11-07 17:20:30.840 MainThread udi_interface INFO init:<module>: Loading OAuth module

2026-11-07 17:20:30.840 MainThread udi_interface INFO init:<module>: UDI interface initialized

2026-11-07 17:20:30.840 MainThread udi_interface INFO init:<module>: UDI Python Interface for Polyglot version 3 3.4.8 Starting...

2026-11-07 17:20:30.841 MainThread udi_interface ERROR udi_interface:write: Traceback (most recent call last):

2026-11-07 17:20:30.841 MainThread udi_interface ERROR udi_interface:write: File "/var/eisyui/ns/plugin_6/eisyai.py", line 8, in <module>

2026-11-07 17:20:30.842 MainThread udi_interface ERROR udi_interface:write: from ioxplugin import Plugin

2026-11-07 17:20:30.842 MainThread udi_interface ERROR udi_interface:write: ModuleNotFoundError

2026-11-07 17:20:30.842 MainThread udi_interface ERROR udi_interface:write: :

2026-11-07 17:20:30.842 MainThread udi_interface ERROR udi_interface:write: No module named 'ioxplugin'

31 minutes ago, Nestor said:

After attending the webinar, I thought I'd give EISY AI a try to create a plugin. After installing EISY AI, the plugin status is "Starting". Is there something that needs configuring?

I do notice some errors in the log. The following is after clicking on Restart:

2026-11-07 17:20:30.017 MainThread udi_interface INFO init:<module>: Loading interface module

2026-11-07 17:20:30.065 MainThread udi_interface INFO interface:<module>: Loading MQTT module

2026-11-07 17:20:30.609 MainThread udi_interface INFO interface:<module>: MQTT module loaded

2026-11-07 17:20:30.839 MainThread udi_interface INFO init:<module>: Loading udi_interface module

2026-11-07 17:20:30.840 MainThread udi_interface INFO init:<module>: Loading node module

2026-11-07 17:20:30.840 MainThread udi_interface INFO init:<module>: Loading custom module

2026-11-07 17:20:30.840 MainThread udi_interface INFO init:<module>: Loading isy module

2026-11-07 17:20:30.840 MainThread udi_interface INFO init:<module>: Loading OAuth module

2026-11-07 17:20:30.840 MainThread udi_interface INFO init:<module>: UDI interface initialized

2026-11-07 17:20:30.840 MainThread udi_interface INFO init:<module>: UDI Python Interface for Polyglot version 3 3.4.8 Starting...

2026-11-07 17:20:30.841 MainThread udi_interface ERROR udi_interface:write: Traceback (most recent call last):

2026-11-07 17:20:30.841 MainThread udi_interface ERROR udi_interface:write: File "/var/eisyui/ns/plugin_6/eisyai.py", line 8, in <module>

2026-11-07 17:20:30.842 MainThread udi_interface ERROR udi_interface:write: from ioxplugin import Plugin

2026-11-07 17:20:30.842 MainThread udi_interface ERROR udi_interface:write: ModuleNotFoundError

2026-11-07 17:20:30.842 MainThread udi_interface ERROR udi_interface:write: :

2026-11-07 17:20:30.842 MainThread udi_interface ERROR udi_interface:write: No module named 'ioxplugin'

Yes - the plugin requires configuration. There's additional info when you click on "More Info" on the Plugin About page in the Plugin store, including a working JSON example for integrating Claude.

One thing that is a bit different for this plugin from several others is how the configuration parameters are setup. Best I can tell, the only parameter is "Configuration" and the full set of JSON with all of the additional config parameters gets put into the Values field next to that.

Edited Saturday at 11:04 PM2 days by dwengrovitz

What version is your UDX at? If you upgraded it sometime yesterday (Friday) and it's at 5.3.0 or more, then that will need to be rolled back by UDI. Are your other plugins working?

You're trying this on a eisy (not Polisy) right?

I'm pretty sure you still need to be on Staging to run this. Before entering the sample JASON, you need to update it with your AI key. Afterwards, restart the plugin.

12 hours ago, Guy Lavoie said:

What version is your UDX at? If you upgraded it sometime yesterday (Friday) and it's at 5.3.0 or more, then that will need to be rolled back by UDI. Are your other plugins working?

You're trying this on a eisy (not Polisy) right?

Still at 5.1.0 as far as I can tell.

8 minutes ago, Nestor said:

Still at 5.1.0 as far as I can tell.

UDX v5.1.0 had a eisy-ai generated plugin permission issue that was fixed in v5.2.1. That doesn't sound like your issue.

I would suggest trying to reinstall eisy-ai. It's possible something went wrong with the install. After reinstalling, if you have the same issue, stop and then restart the plugin with the log open to see if any potential errors. Also, take a look at pg3 log.

13 hours ago, dwengrovitz said:

Yes - the plugin requires configuration. There's additional info when you click on "More Info" on the Plugin About page in the Plugin store, including a working JSON example for integrating Claude.

One thing that is a bit different for this plugin from several others is how the configuration parameters are setup. Best I can tell, the only parameter is "Configuration" and the full set of JSON with all of the additional config parameters gets put into the Values field next to that.

Ah. Okay. Seems there's more to it than I originally thought. I'm not set up with any particular LLM so it looks like I will need to do that first.

7 minutes ago, Nestor said:

Ah. Okay. Seems there's more to it than I originally thought. I'm not set up with any particular LLM so it looks like I will need to do that first.

That is what the Configuration Parameter on the Configuration Tab is for. That is where you enter the JSON string, after you subscribe to the AI agent of your choice and receive your key. The example uses Claude, but you are free to use whichever one you want.

There are instructions for this in the readme.

1 hour ago, Nestor said:

Still at 5.1.0 as far as I can tell.

I don't know exactly which version I had but my first attempt at installing eisy-ai was also stuck at "starting", until I upgraded UDX to 5.2.0.

I had the same problem with same errors with the eISY Ai plug-in on an eISY box and UDX v5.1.0, I just deleted the AI plugin and I will go back and do some reading and try again latter.

My AI using Gemini starts but won’t process chat requests.

Everything seems ok. I checked my api key and as I’m owner, I have permissions necessary.

Not sure what to check next.

2 minutes ago, mmb said:

My AI using Gemini starts but won’t process chat requests.

Everything seems ok. I checked my api key and as I’m owner, I have permissions necessary.

Not sure what to check next.

Have you tried restarting the plugin? There should be something in the log, set at debug.

I would suggest checking the formatting of the JSON and that nothing else was added or changed.

There should be something in the log.

Just now, DennisC said:

Have you tried restarting the plugin? There should be something in the log, set at debug.

I would suggest checking the formatting of the JSON and that nothing else was added or changed.

There should be something in the log.

Tried everything, the formatting is fine I think, I get the AI chat box. The debug file suggested the test chat didn’t go beyond the eisy.

There isn’t that much to configure in the json, Gemini, Gemini-flash, api key and same for author.

Maybe I’m missing something.

Update: created a chatgpt api key using same json and it works fine.

This suggests missing bits to process Google models.

Edited Sunday at 09:14 PM1 day by mmb