-
EISY-AI "stuck" at Starting
2nd plugin created for an RX-V2700 receiver. This receiver is older so it took a bit more work. It's connected to an iTach Global Cache via RS232 and uses a serial protocol that's a PITA to work with. At first I provided commands I already had in Network Resources but after I told it I had a pdf for the protocol, it suggested I simply copy and paste the text from the entire file and paste it into the prompt. Progress sped up considerably from there. What took me days to figure out on my own took me about 3 hrs with EISY AI. And I can now work with the statuses of the receivers in my tiles, something I didn't have with Network Resources. Great job, UDI! ๐
-
EISY-AI "stuck" at Starting
My first plugin. I've been using Network resources for commands to my Yamaha receiver for several years. While they do their job, it's tedious to add new commands and I'm unable to get feedback from the receiver (eg. volume level, etc. ). I asked EISY AI to create a plugin and in about 20 mins, here's what it has created so far.... EISY_AI is a game changer.
-
EISY-AI "stuck" at Starting
-
EISY-AI "stuck" at Starting
Running the upgrades from staging repo. Will report back once everything is up and running.
-
EISY-AI "stuck" at Starting
Yes. I have done all of those. I did find some errors in the log. Here's the status of my packages. Should I be looking to the staging repo for upgrades? FWIW, since I now have Claude, I asked Claude (edited for brevity, Italics is my side of convo)... udi_interface:write: No module named 'unified' That error means a Polyglot (PG3) plugin is trying to import a Python module called unified that isnโt installed on your eisy. The udi_interface:write prefix is just how PG3 logs the pluginโs Python traceback. I didnโt find anyone reporting this exact module, but the same โNo module named Xโ error shows up for other plugins, so the usual fixes apply. ........ Which plugin is throwing this, and is it eisyAI-related? If you paste the few log lines above the error, I can help work out whatโs being imported. Yes. eisyAI related. Here are the log lines above the error: 2026-11-14 09:39:07.360 MainThread udi_interface ERROR udi_interface:write: Traceback (most recent call last): 2026-11-14 09:39:07.360 MainThread udi_interface ERROR udi_interface:write: File "/var/eisyui/ns/plugin_6/eisyai.py", line 55, in <module> 2026-11-14 09:39:07.360 MainThread udi_interface ERROR udi_interface:write: from EisyaiControllerNode import EisyaiControllerNode 2026-11-14 09:39:07.361 MainThread udi_interface ERROR udi_interface:write: File "/var/eisyui/ns/plugin_6/EisyaiControllerNode.py", line 8, in <module> 2026-11-14 09:39:07.361 MainThread udi_interface ERROR udi_interface:write: from start_eisyai import start_eisyai 2026-11-14 09:39:07.361 MainThread udi_interface ERROR udi_interface:write: File "/var/eisyui/ns/plugin_6/start_eisyai.py", line 9, in <module> 2026-11-14 09:39:07.361 MainThread udi_interface ERROR udi_interface:write: from unified.provider_clients import build_provider_clients_from_runtime_config 2026-11-14 09:39:07.361 MainThread udi_interface ERROR udi_interface:write: ModuleNotFoundError 2026-11-14 09:39:07.361 MainThread udi_interface ERROR udi_interface:write: : That traceback narrows it down. The failing import is from unified.provider_clients import ... in start_eisyai.py, which lives inside the pluginโs own folder (/var/eisyui/ns/plugin_6/). So unified is most likely a package bundled with eisyAI, not something pip should install. That makes this probably a broken or incomplete plugin install, where the unified/ folder is missing or didnโt get extracted. Thatโs an inference from the log, not something Iโve confirmed in eisyAIโs docs.
-
EISY-AI "stuck" at Starting
Yeah, definitely not seeing any icons.
-
EISY-AI "stuck" at Starting
Plugin is now connected but I'm not seeing any node for EISY AI. I set up Claude and obtained a key. Copied the entire json code and replaced the text with my api key. Copied edited text, pasted into the plugin parameter and saved. Plugin Log shows no errors. I tried refreshing my browser and rebooting, along with restarting and even reinstalling the plugin. Suggestions?
-
EISY-AI "stuck" at Starting
As a fellow AI newb, this fills in the blanks of Michelโs readme. Thank you.
-
EISY-AI "stuck" at Starting
Asked Claude for an API key for EISY AI and it asked me to upgrade to "Pro", a paid sub. Is this the same for others?
-
EISY-AI "stuck" at Starting
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.
-
EISY-AI "stuck" at Starting
Still at 5.1.0 as far as I can tell.
-
EISY-AI "stuck" at Starting
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'
-
PG3 errors in EISY-UI
Had the same issue. Try rebooting the EISY. If that doesnโt work, try restarting the PG3 service by logging into EISY from command prompt with SSH, then use the following commands: sudo service pg3 onestop sudo service pg3 onestart
-
Nestor started following New Network Resources Page - Issues?
-
New Network Resources Page - Issues?
Good news! service restart did the trick. No further API errors that I can see. Also, Network resources are displaying properly and the Test button is functioning again. Thanks once again for your assistance!
-
New Network Resources Page - Issues?
Nestor
Members
-
Joined
-
Last visited