Can I physically remove plugins from Vera Edge

Although I uninstalled unwanted plugins from the Vera Edge and they no longer appear on the UI it appears they are still physically on the Vera Edge.

Is there a straightforward way of physically removing them from the Vera Edge. It’s filling up rapidly.

ssh in to vera
cd /etc/cmh-ludl (to navigate to folder)
ls -a (to show files)
rm file_name (to remove)

1 Like

And another option that I use is WinSCP, where you can open that same folder and delete the files using a user interface.

1 Like

Absolutely but do you know exactly what files you should remove. Remove the wrong one and that’s Vera screwed.

I’m happy enough in the command line but thanks for the heads up.

It’s hilarious. They give you an option to install but give you no option to delete. It’s a case of “if you can’t see it it’s not there”. That’s just asking for trouble and product support requests. Maybe there’s method in their madness after all.

Best to ask developer his/her file names, or they may be on github. Or you could ask support for a list of standard files.

I thinks it’s here to prevent cross referenced file from being removed but still be useful for plugins. If it was me to be in charge for plugins architecture, I’d be chosen a separate folder structure for each plugin and a manifest to describe them.

1 Like

Yes there is a possibility that you could delete dependencies for other plugins while manually deleting a plugin. The question I am asking is could a plugin have an uninstall feature included in its package that would reverse the install process and physically remove all of its own components.

I doubt that this would be a problem to implement. Possibly an uninstall script supplied with each plugin would resolve this.

The first thing any new user does is to try out plugins, when they can get the App Store to load of course :joy: They soon fill their Vera device and of course processes like firmware updates become an issue.

1 Like

Your suggestion does not resolve the problem with dependencies between plugins.
Say for example you install two plugins relying on one same file. If one plugin has it in its file list, upon removal, it will also affect the second plugin.
This would require a repository like recording of dependencies which the vera does not have for its plugin management. The separate folders per plugin is more elegant but may lead to larger (precious) storage. Would not be a problem if the vera was not so limited.

Obviously the plugin folder would be a more sensible route to go but the Vera Edge is what it is. A low spec Z Wave controller souped up to run a home automation system way beyond its capabilities. Too many features crammed in and it stops working efficiently.

A SBC along the lines of the Raspberry or Orange Pi would make more sense but that would be entering dangerous territory :joy:

…which is, of course, what openLuup was written to do.

And therein lies the solution. I’ve not tried that option yet. Are there any setup tutorials on the forum for this.

There is a fair amount of info in the openLuup User Guide

Also users on the forum ready to help.

MiOS actually knows (mostly) which files are used by a plugin. Sadly, you’d have to look at the user_data InstalledPlugins2 structure to find out… unless, of course, you were using AltUI, in which case the Plugins page has a handy Files menu against each plugin.

You can’t guarantee, though, that another plugin doesn’t use those files, although this is unlikely.

Proper namespace managerment would certainly help with addressing this issue.

Yes I’m using AltUI so I’ll check that out. Thanks.

Best Home Automation shopping experience. Shop at getvera!

© 2020 Vera Control Ltd., All Rights Reserved. Terms of Use | Privacy Policy