Yes, I pretty much concluded that the javascripting add-on didn’t work at all, except that it did try to load the file, but nothing resulted from it. So, I removed it again, and it will have to wait until this is “solved” (if ever): Running `org.openhab.demo.app` with `org.openhab.automation.jsscripting` enabled
But, as I said, I’ve gotten JRuby working, so I can still test “scripting based rules” as long as they’re in Ruby.
I’ll be happy to be pointed to examples so that I can test JRuby rules in the UI. But, I’m not so sure that it will be a problem.
As I see it, there are triggers and conditions that are of the “standard type” that RuleEngine can evaluate and act on. Those should be possible to display. In addition, scripts can make any additional criteria they want, that won’t be displayed. That’s because they’re not conditions seens from RuleEngine, they are merely conditions that makes the “action”/script abort. So, to see them, you will have to read the script.
Is this correct, or am I missing something major?