There were two node-server file-permission issues that caused the native eisy-ui system backup endpoint ( /api./system/backup/create) to return HTTP 500.

1. SmartLife/Tuya: The plugin's web_auth.txt file lacked the FreeBSD ACL permissions needed by the eisyui service account. Repairing the ACL resolved the problem. Subsequently added automatic ACL repair during plugin startup.

2. eisy Backup: The plugin's persist/backup_hisotry.json file could be updated or atomically replaced without preserving the required ACL. This caused an EACCES error during native backup. Corrected the file-permission handling in version 1.1.1. This bug only showed up in 1.4.9, not 1.4.8

Both problems demonstrate that files created or replaced by node servers can interfere with system backups if the eisy-ui backup process lacks sufficient filesystem access.

It may be useful for the native backup process to identify the offending file and return a more descriptive error instead of a generic HTTP 500. It may also be worth reviewing whether the backup process should require access to every file in a plugin's persistent directory.

I'd like to introduce you to eisy-ai: it can do pretty much anything you can imagine including diagnostics/patterns, and developing, testing, and running plugins for you! Here's the link to [ README.md ]. It's in Beta, and you can install it from the plugin store. And, everything is done right from your eisy-ui!

Notes:

1. Although we have tested with OpenAI, Grok, and Gemini, most of the development and test was done with Claude. So, we would love to know your experience with other LLMs

2. We took great care in reducing token count especially for very large installations. That said, depending on the model used, and your installation, you might reach the limits of the context window

3. Although we have put strict guards for irrecoverable changes, such as deletions, this is still in Beta and it's still AI, so it will make mistakes

4. We are not collecting any information from you, BUT we may ask you to provide your nucore.prompt.jsonl in case we need to debug something that we cannot reproduce

Very much looking forward to hearing your feedback!

With kind regards,
Michel

After watching @Javi's video of his pet door Plugin creation, 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 @bpwwer 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!!!

Grok says:

This is almost certainly a client-side (browser) issue with the eisy-ui chat interface, not a problem with the eisy hardware or the AI plugin’s core logic.

eisy-ai (accessed via the sparkle icon in the top-right of eisy-ui) is a relatively new feature. Long chat sessions build up a large conversation history in the browser’s JavaScript/DOM state. After roughly an hour, keystroke handling and re-renders become expensive, which produces the “typing slows to a crawl” symptom. This is a very common early-stage problem in web-based AI chat UIs when they don’t aggressively virtualize the message list or prune/summarize history for the frontend.

Solutions were to refresh the page, but this lost all my ability to scroll back up to see things.

FYI.

Attached is the amount of interaction when typing because laborious.

Eisy ai chat.rtf

Thanks.

I migrated two differnt nodes (VUE and DSC) to the new nodes (Hoping the eisy-ai would be able to see them)

However, the migration looked ok, but they nodes are no longer running. to make it worse, I cannot delete the migrated node and install the original one as eisy-ui still holds the slot

I had no issues moving nodes I created my self

It seems somehow one of the nodes recovered after multiple restats, but the other still hold the slot (VUE) and I will not run without errors - I seem to recall thisnode required developer libraries to be installed when I installed iy initially

All too often lately, I find some switch in the house no longer functions, then I realize everything is what I will call "hung". The last two time this has happened, a couple of days ago and then again just now, the first thing I do is download all log files so I can try to figure it out, but there is nothing that I can see. I previously had some instances that were causing "queue full" conditions. I worked on some program and plugin poll times, and that is not what is happening here.

Then I reboot eisy.

So are others experiencing anything like this? I will open a ticket if needed, of course.

Thanks for any feedback.

Rob

I feel like creating/editing programs is taking a lot more clicks & scrolls compared to the AC. Would be nice to reduce this if possible.

• When creating programs the AC remembered the last Action which a lot of times is very helpful especially if it's a complicated action like sending a UDMobile notification which requires many clicks to do the same thing, and when a different node is selected have it remember they last way that nodes options were selected.

• It would be great if UDMobile notification action as made a first class action instead of having to go find the node, but would be really nice if all Notification nodes were first class since I use a few.

• The "Select Notification Template" modal is great, suggestions:

  • Sort by Name

  • Open with details collapsed, otherwise it can be a lot of scrolling.

  • newlines seem to be ignored when showing body?

• drag/drop programs to move into a folder

• cntl & shift click for selecting multiple programs to drag/drop into a folder

That's it so far, but will add to this post if I have more suggestions or add yours if you have any.

• Jim

Also ... will Generate Topology be an option in web ui ?

Weekend - [ID 0070][Parent 0001]

If
On Sat, Sun

Then
Run Program 'abc' (Then Path)

Else
- No Actions - (To add one, press 'Action')

This is a poll to see what time intervals work best for everyone.

With kind regards,
Michel

Where do Notices / notifications show after nodes are migrated to eisy. Some nodes use this to guide startup - like press authentication button etc.

I am happy to announce our new and improved eisy-ai version 2.1.0. For most up-to-date documentation, please go here.

New Features

• More token efficiency

• Fixed permissions (see Breaking Changes)

• Code view so that you can see the code and update it manually (needs updated eisy-ui)

• MCP Support so that you can use your own subscription through Claude Desktop, OpenAI Desktop, Google AI Studio, etc.

  • WARNING - we are using self-signed certs, the configuration may not be trivial

  • The URL for setup is https://eisy.local:8260/mcp

Breaking Changes

• The plugin directory has changed to /tmp/eisy-ai/generated_plugins

• Your existing plugins will continue to work but eisy-ai will not know anything about them

• If you want your existing plugins to also be available to eisy-ai (for modifications/fixes/etc.):

  • Copy the contents of /home/admin/eisy-ai/generated_plugins to /tmp/eisy-ai/generated_plugins

  • sudo chown -R admin:polyglot /tmp/eisy-ai

  • sudo chmod -R 777 /tmp/eisy-ai

  • Update the path for each local plugin and reinstall in the same slot

Upgrade Instructions

• Upgrade all your packages in eisy-ui | System menu (you need updated udx and eisy-ui) - Please use the Staging Repo

• Reboot

• Go to your eisy-ai plugin and click on the Reinstall button

With kind regards,
Michel

The config is rather complicated to fill out the node form - In the past you could release from a local to a production and from Production to local (when neeeding to make changes) - I have figured out how to do this - and I gave up to get eisy-ui to do it - it keeps wanting to generate new code

Is there a simple way going between the two - especially from prodution to local - I need to do this for all my nodes that exists already - quite a bit of work

Thanks

Log file missing: Both history queries failed with "unable to open database file." The log is expected at /var/isy/FILES/LOG/DEVLOG.DB, but that file doesn't exist on this host.

Not sure if this belongs in the eisy-ai group, but it is here for now

HOw can I get the files reestablished

1) Programs: When I hit collapse, they all collapse as expected to one level. When I hit expand, roughly 15% of my program folders DO NOT expand. See example screen shots below. Also, it would be nice if each click on the expand or collapse would do ONE level at a time, not an all or nothing approach.

2) Nodes: It appears that the expand is only applied to Folders / Groups vs nested Nodes. This is probably by design. Similar to above, it would be nice to have each click expand on level at a time, including nested nodes. See screenshot below.

Thanks!!

Started the upgrade from web ui, had one message about possible reboot and clicked ok ...
On AC, messages appeared as per screen grab, web ui shows nothing ... zero indication of any progress or the upgrade has completed

Since this roadmap discussion is looking for input and "others" have requested web ui show some form of progress previously ...

I'm asking for again, PLEASE add some form of status or progression of upgrades in web ui

I appreciate the notifications in UDM of hte status of the upgrade.

Two suggestions to further add to this for ease of use for users:

1) Can those same notifications in UDM (see screenshot below), appear in the UI?

2) In both cases, it is not clear whether a reboot is needed. There is the comment during upgrade that a reboot may be necessary but to not do it unless needed. It would be great if at the end of the other notifications, it told us to reboot if needed or in the Upgrade complete! it said it is NOT needed. This seems like something that could be built into the upgrades?

thanks!

Working on a Scene where I needed to set Hue X and Y values.

Screen opens up a drop down with value.. starting at 0.0001. I need values around 0.8400..To scroll down that far is not practical.

Tried to input the number directly (which the open box says you can do), but there is no way to save it. Hitting return just resets the drop down.

I am pretty sure this is a "global UI" issue, but havent verified it in other drop downs.

thanks.

1) Whenever I reboot after an upgrade, Holiday and SUN plugins are Disconnected as shown below under the NODE tree

2) However, under Plugins, they will show as Connected, see below. A Restart of the plugin quickly fixes the problem and both will show connected.

It seems there is only support for local (in the sense of development direcly on the eISY) - I normally use local towards the end of a development to test and ensure the installation works correctly. Is that nolonger possible ?

I am on ET/EDT

9:48AM, which is correct.

log viewer 7:49AM

Backup file time stamp 7:49AM

I have a combination of hard wired and battery Z-wave devices, with the majority being battery operated. In particular, I have four ZSE42 and one ZSE42 800LR leak detectors.

Here are some of my roadmap desires for Z-wave:

• Improve the inclusion process, such that all identical devices receive the same node groups and icons. Currently, I may see 4 nodes for some and 5 nodes for others.

• When a faulty device needs to be replaced, or more commonly, when it has to be reset for troubleshooting, can a mapping table be created such that when I remove, e.g., ZY_003 and add it again as the next sequential device e.g., ZY_044, I can then map the two and let eisy correct my programs automatically.

• Currently, when eisy has to be rebooted for any reason at all, I find that it can take days, or maybe never, for a battery operated leak detector to show up with a value for battery and/or wet/dry status. Even with a programmatic query after a wakeup event, this is often the case. There is something wrong with that process in my experience.

• OTA updates for battery devices is horrible, where I must hold the device, continuously pressing the button 4 times to ensure it stays awake. Even if I have to manually wake up the device to initiate the OTA, I would like eisy to tell the device to stay awake until the OTA is complete.

Rob

I would like to see an easy way to determine if a variable is used anywhere. For example, as a start, perhaps a new column "Variable Usage" which shows a count of how many instances of the var exists. Then perhaps be able to click on that and see a list of clickable links to the programs. But just knowing if a var is even used would be valuable.

Thank you,

Rob