Shoot.. maybe someone at UD can move the post out of that folder to the EISY UI folder. ? Not sure who to ask. If you would like I can copy my 2-4 posts and DM them to you?

4 minutes ago, dbwarner5 said:

Shoot.. maybe someone at UD can move the post out of that folder to the EISY UI folder. ? Not sure who to ask. If you would like I can copy my 2-4 posts and DM them to you?

I have been using eisy-ai for a couple of weeks now, I was just interested in another view point.

I completed my first plugin with assistance from eisy-ai and I recently published it in the Plugin Store. It's NOAA Tides and it offers:

Tide predictions and observed marine conditions for one or more NOAA tide stations.

24 minutes ago, dbwarner5 said:

Shoot.. maybe someone at UD can move the post out of that folder to the EISY UI folder. ? Not sure who to ask. If you would like I can copy my 2-4 posts and DM them to you?

Feel free to post them here if you believe they will be helpful to us. Sounds like they would be.

Thanks,

Ross

From another forum... some of my learnings from my initial use of EISY-AI.

After watching a video of Javi creating a pet door Plugin, I decided to venture in. Had some serious learnings that all ended with an amazing success on a plug in that I had been working on and off with a developer for almost a year w/o success.

It took me about 1 hour to actually create the plugin, but, because of my total lack of understanding of AI (see points below) total time was about 4-5 hours.

COST: $5.80 ! And its appears to be working 100%! Plug-in is for Meross brand wifi switches / plugs / bulbs etc

TOTALLY AMAZING......Some learnings:

1) UD is positioning Eisy-AI as a "tool" for ease of use / troubleshooting and developing. However, the documentation that is available is anything but clear to someone w/o AI experience The irony here is that with Claude or other AI, a truly user friendly how-to document could easily be created by UI. Most of my time was spent on just figuring out things related to AI, GitHub, SSH ing with Github tokens (not passwords), buying anthropic tokens, etc etc etc. One hour alone was just finding the "sparkle" icon in the upper right corner to open the Eisy-AI chat window.... which is literally NOT documented anywhere!

2) I started simple. Had AI create a simple program that turns on a corresponding Zwave plug on when a separate light gets turned on by a motion detector and then turns it off 5 minutes after the trigger light is turned off. Took about 40 seconds and cost $0.30. Program was clear, named a common sense name and had comments below that described its purpose. Worked immediately. I then had it move the program to a folder of my choice which it did easily.

3) For the plugin, I had a free Claude window open separately where I created a parallel effort to help understand all the things I needed to do such as buying tokens, setting up tokens passwords, explaining the plugin. It also created the language that I needed to paste into Esiy Ai to be the most efficient, clear, protective of personal info and cost effective. Without that help I would have not succeeded.

4) I had to do several things within Eisy and on my Mac that made me nervous such as direct downloads and ssh commands that I didnt understand. SIDE NOTE: I just tried to go back in history to find these to give as examples and there does not seem to be a way to go back in history in the Eisy Ai chat window. I can see my "session" but cant do anything with it.

5) Currently the repository is private as I only have 8 of my ~30 devices connected (remodel work being done). In about a month, I will have a higher variety of meross products connected and will further pressure test the plugin. After that I would like to publish it to the store, but have no idea how. Again will rely on Claude and Eisy AI to do it for me.

Overall it was a great success and I already have 3-5 more plugins that I want to create. Maybe after that, I will actually understand what I am doing, or better said, what AI is doing!

Cheers and thanks for a great product!!!

A second post from above forum page:

I relied heavily on Claude (free) desktop app on my Mac to guide me through everything.

It helped me set up my Anthropic account where I purchased $20 worth of tokens and received the API that then got put into the JSON string of the eisy ai plug in per the configuration.

Down below is what Claude produced which I used to guide eisy AI in the plug in development. I would have never come up with all of that.

I also had to install python on my Mac.. Claude -> Option A (simplest): install Python directly

1. Go to python.org/downloads and download the latest macOS installer for Python 3.

2. Open it and click through the installer.

3. When it finishes, open the Python folder in Applications and double-click Install Certificates.command. This avoids certificate errors when the script connects to Meross, which the library’s README warns about on Macs.

4. Close Terminal and open a new window, then check it worked

Had to check it using terminal via Claudes direction: python3 --version

Then it had me go and check the meross version number --> pip show meross_iot which then I needed to use with eisy ai for the development.

The rest below is what Claude told me to do to start the development. After I was done, it also walked me through, along with Eisy AI how to back up the local plugin to GitHub, which was extremely confusing and trying.

Claude-->

How to start

1. Open the eisy-ui chat (the sparkle icon). Back up the eisy first if you haven’t recently.

2. Send a message that contains only /developer. The README says that switches modes right away, and you should see “Switched to developer tools.” Using the command also means no conversation summary carries over, which is what you want here. github

3. Paste the brief below as your next message. Fill in the library version from pip show meross_iot, or delete that part if you don’t have it.

--> I want to build a replacement eisy plugin for Meross lights and switches. Follow your normal workflow: check the store, research, define the device profile, generate locally, and wait for my approval before installing anything.

GOAL

Control and show status for about 30 Meross devices (a mix of older and newer bulbs and wall switches/plugs) through the Meross cloud, US region, from eisy.

EXISTING PLUGIN

A Meross plugin (beta 1.0.1) already exists in the PG3x store. On my eisy it discovers my devices but can't send commands or update status, and its log shows nothing after discovery. Check the store and tell me what you find. Still build a new plugin unless you find a working replacement.

LIBRARY: ALREADY VERIFIED

The Python library "meross_iot" (MerossIot by albertogeniola, version ___) works for me today. With my email, password, and API base URL https://iotx-us.meross.com it logs in, connects, discovers devices, and turns one on and off. The flow that worked: MerossHttpClient.async_from_user_password(api_base_url, email, password) -> MerossManager(http_client) -> await manager.async_init() -> await manager.async_device_discovery() -> manager.find_devices() -> device.async_update() -> await device.async_turn_on(channel=0) / async_turn_off(channel=0) -> manager.close() and await http_client.async_logout(). Use that library's official docs and examples as your main source and keep other web research short.

REQUIREMENTS

1. Concurrency: run the library on ONE dedicated asyncio event loop in its own background thread. Commands from IoX must be handed to that loop in a thread-safe way, with timeouts and error handling, so a failure can never freeze the plugin.

2. Login hygiene: log in once, not per command, and log out cleanly when the plugin stops. Avoid repeated logins on restart, since Meross can temporarily block accounts for too many. If the library supports reusing saved login credentials, use that.

3. Rate limits: Meross can suspend accounts for high-frequency requests. Use push notifications for status, no tight polling loops, queue commands with a short delay between them so a scene with many lights doesn't flood the cloud, and back off on errors.

4. Reconnect: detect a dropped connection, reconnect automatically, and show connection status on the controller node.

5. Devices: one node per device, with a stable address from the device ID, named from the Meross name. Support on/off and status for bulbs and switches first. Add brightness and color for bulbs if it can be done cleanly. Query must refresh state, rate limited.

6. Controller node: connection status and a working Discover command.

7. Config: Meross email, password, and region (default US; also EU and Asia-Pacific), plus an optional command delay. The password must never appear in code, logs, or chat.

8. Logging: at debug level, log every command sent, every acknowledgment or timeout, and every connect, disconnect, and reconnect, with passwords and tokens masked. Something must be logged every time I send a command.

9. Include the starter test suite, a README with setup steps, and the license.

PROCESS

- Do the one-time developer identity step first and ask me for what you need.

- Show me the proposed device profile before generating.

- Generate locally only, show me the file list, and wait for my go-ahead before installing.

- I will enter my Meross credentials in the plugin's config page after install, not in chat.

- After install, help me test with ONE non-critical switch and ONE bulb first, confirming each command in the logs, before anything else.

- Install into a new slot. Do not uninstall or delete my existing Meross plugin. I'll stop it myself so only one client is logged in at a time.

- I'm paying per use, so keep it efficient and tell me your plan before long multi-step work.

Last post from above forum posting

An additional note:

Esiy AI was awesome in that it tested itself several times, made changes / fixes. Found with me that status upon startup were not correct due to a timing issue and redid something to create a delay so that the device would get created and then the status would be checked / populated. Jointly tested with me, etc.

The point is that it took about 3-4 iterations for it to get it 100% working right, all with very limited interaction from me.

again. Simply AMAZING!!

Edited 17 hours ago17 hr by dbwarner5

@Javi have you seen this before?

My brother is stuck at Starting after installing eisy-ai plugin:

2026-11-11 14:39:21.716 MainThread udi_interface INFO init:<module>: UDI Python Interface for Polyglot version 3 3.4.9 Starting...
2026-11-11 14:39:21.717 MainThread udi_interface ERROR udi_interface:write: Traceback (most recent call last):
2026-11-11 14:39:21.717 MainThread udi_interface ERROR udi_interface:write: File "/var/eisyui/ns/plugin_3/eisyai.py", line 8, in <module>
2026-11-11 14:39:21.717 MainThread udi_interface ERROR udi_interface:write: from ioxplugin import Plugin
2026-11-11 14:39:21.717 MainThread udi_interface ERROR udi_interface:write: ModuleNotFoundError
2026-11-11 14:39:21.717 MainThread udi_interface ERROR udi_interface:write: :
2026-11-11 14:39:21.717 MainThread udi_interface ERROR udi_interface:write: No module named 'ioxplugin'

He did install the most recent Staging modules rebooted as required..

Thanks!

Edited 11 hours ago11 hr by mmb

2 minutes ago, mmb said:

@Javi have you seen this before?

My brother is stuck at Starting after installing eisy-ai plugin:

2026-11-11 14:39:21.716 MainThread udi_interface INFO init:<module>: UDI Python Interface for Polyglot version 3 3.4.9 Starting...
2026-11-11 14:39:21.717 MainThread udi_interface ERROR udi_interface:write: Traceback (most recent call last):
2026-11-11 14:39:21.717 MainThread udi_interface ERROR udi_interface:write: File "/var/eisyui/ns/plugin_3/eisyai.py", line 8, in <module>
2026-11-11 14:39:21.717 MainThread udi_interface ERROR udi_interface:write: from ioxplugin import Plugin
2026-11-11 14:39:21.717 MainThread udi_interface ERROR udi_interface:write: ModuleNotFoundError
2026-11-11 14:39:21.717 MainThread udi_interface ERROR udi_interface:write: :
2026-11-11 14:39:21.717 MainThread udi_interface ERROR udi_interface:write: No module named 'ioxplugin'

He did install the most recent Staging modules rebooted as required..

Thanks!

I have seen that and the fix was upgrade packages and reinstall eisy-ai.

However, I see he is at eisy-ui v1.4.10_1, so he must have updated packages recently, since that is a new upgrade.

I would suggest to try reinstalling eisy-ai. If he still gets that error, open a support ticket with UD right away. Maybe something with v1.4.10_1?

10 minutes ago, DennisC said:

I have seen that and the fix was upgrade packages and reinstall eisy-ai.

However, I see he is at eisy-ui v1.4.10_1, so he must have updated packages recently, since that is a new upgrade.

I would suggest to try reinstalling eisy-ai. If he still gets that error, open a support ticket with UD right away. Maybe something with v1.4.10_1?

Ya the first thing he did was reboot and reinstall.

The missing IOXPlugin is a bit baffling. Maybe it got lost as it's not one you can install yourself.

I think this may be a requirement while eisy-ai is in beta, after firmware upgrade, delete then reinstall plugin.....or at least this was the case in early eisy-ai versions.

1 hour ago, Javi said:

I think this may be a requirement while eisy-ai is in beta, after firmware upgrade, delete then reinstall plugin.....or at least this was the case in early eisy-ai versions.

Thanks Javi, he submitted a ticket. Michel was looking into last I heard.