Well, it has been asked before, but not adequately answered! It’s possible to do, but high maintenance, and the forum is littered with attempts to do similar for other systems (eg. UI5/6/7 and now the other radios on the Plus) all of which fall quite rapidly into a state of disrepair. I’m afraid I simply can’t be an expert on everybody else’s plugin!
You would be more than welcome to start a thread and maintain it. It would mean that both you and I could edit it, but nobody else. This is a limitation with this forum software.
There are some general rules: nothing encoded or licensed will work; ones that expect and manipulate compressed files; anything that reads or writes raw ZWave data to device #1; … There are threads here on generic classes of plugin, eg. AV and alarms.
I am in the process of migrating all (possible) plugins and scenes from my Vera Lite to a Raspberry Pi running openLuup and have been stumbling on 3 plugins that I could not yet migrate...
Happy to help. Always pleased to hear that another plugin IS compatible.
1) Smart Virtual Thermostat: runs but cannot read sensors or actuate heater switches... I suspect this is due to the numbering offset of devices in openLuup that do not get parsed properly in the Lua implementation file but did not yet have time to probe/debug this... Will report my findings later.
Maybe numbering, but more likely the fact that the parent/child relationship is not maintained by bridged devices… everything is a child of the bridge. This is something I must change, and don’t see a fundamental barrier in doing so.
2) Weather Underground: the D_ xml file is encrypted so does not run within openLuup... I am writing a small plugin based on the pusblished WU API to at least capture current temperature and humidity (that I need for some other devices and scenes)... Will post the files when it reaches beta stage if this is of interest to anyone.
Yes, that would be useful. Early versions of this plugin were not encrypted, but later ones are. Actually, I had been thinking of adding WU to the Netatmo plugin that I wrote. It would be very straight-forward to do, since all the infrastructure for child devices, etc, is in place.
3) System Monitor: rather a "nice to have" than a "must have" but by design it cannot read from the remote Vera. If I find the time (and get approval from the original plugin developer to reuse much of his code), I am thinking of splitting the plugin into a) a lua module with a timer (not a device as my goal is to free memory) on the vera that serves a json file with the relevant data and b) a plugin on the openLuup machine that reads that json by an http GET and displays it exactly like the original plugin... Any comment on that approach welcome...
It rather depends what parameters you need. CPU usage and memory are key and trivial to obtain. Other things, like logs, are definitely harder. It also depends on how successful you are in migrating the rest of your logic and plugins to openLuup. The idea, of course, is to relieve Vera of so much of the work that it just runs and runs without any attention. Certainly, most of mine, now, are just used for ZWave device access and often run continuously for two or three weeks without spontaneously reloading.
Does any of this help?