Time permitting, I plan to merge this PR over the weekend. The intent of the PR is to make it easier for us to have a single set of modules and scripts for core functionality, and a place to store, share, and collaborate on community contributions. If starting up with JSR223-Jython before the merge, I suggest using the files from that branch. After the merge, I’ll be working on merging lucid, weatherStationUploader, and ideAlarm back into this repo (after updating them to use the recent changes in the automation API), adding in all of my own modules and scripts as community contributions and examples, and adding examples illustrating the DPs from the forum.
If you have built an understanding of the rules DSL, or have any programming experience, I would think using Paper UI to build your rules will be a bit of a let down. The functionality is very limited. If Flows Builder picks up again, the UI will be greatly improved, but I don’t foresee it having anything more than basic/beginner functionality.
Keep in mind that there is also a very real possibility of a new DSL being built for use with the NGRE, which will be compatible with rules written for the rules DSL. Personally, if I need to learn something new, it’s worthwhile putting the time and effort into a real programming language, where the knowledge can be used outside of OH. Jython/Python is very easy to pick up and well documented.
- For beginners and simplicity, build rules in Paper UI (or hopefully in the future, Flows Builder). This will also allow for using rule templates, for easier ramp up.
- For people with existing DSL rules, the new DSL will be a logical progression and easy migration.
- For anyone wanting to do more with automation than what is available out of the box, use JSR223, which provides more than just the ability to create rules… entire bindings are possible. And multiple JVM languages can be used at the same time.
There are lots of options and all of them can be used simultaneously, so no need to chose only one!