UPDATE 8/12/2016: CoRE has moved on to Beta Milestone 2. Please kindly follow us here.
In an attempt to fill the huge void left by the withdrawal of Rule Machine, a few brave community members started their journey to creating a new rule engine to rule them all. We’ve decided to call it CoRE, an abbreviation that stands for “Community’s own Rule Engine”, courtesy of @SBDOBRESCU (his idea, really).
WARNING: This SmartApp is in an alpha BETA development stage and may be quirky. It may also change rapidly and drastically, involving a full reset of the app in order to upgrade.
It is not recommend to install this SmartApp in a “production” environment, but we encourage people to try it out.
IMPORTANT: This topic is here for general information and peer assistance. If you want to point out errors, omissions, or ask for features, please do so at CoRE and Piston Rules Engine, first design steps
We have @BoSTon who has volunteered to write documentation on how the CoRE works, from beginners to advanced, to power users. If anyone wants to help, please don’t hesitate. It’s a community’s effort, after all.
The SmartApp can be installed via GitHub integration into your IDE or can be found here
To install the SmartApp using GitHub integration, go to your IDE, go to SmartApps, tap on Settings and Add new repository with ady624 / CoRE / master in the three fields. Then use the Update from Repo button. Make sure you either tick the Publish option while updating from the repository, or publish the app after each update.
NOTE: It is not required, nor necessary to donate to use this SmartApp. This is a free open source software and it is my way to pay my dues to those before me. But if you feel like it, you can donate here. Thank you.
UPDATE 6/13/2016: 45 days into development, finally reached the 1st beta milestone!
UPDATE 7/26/2016: As a result of the ST issues with lost state information on 7/25/2016, some pistons might have been corrupted. The first sign of such a corruption is an empty dashboard. CoRE is able to revive them, but as of today, this process is manual (once this process is deemed worthy, CoRE may automatically rebuild pistons when it needs to). You can find the rebuild option under Advanced Options in each piston’s main page. If you are affected, the easiest way to determine which pistons are faulty is to open the Live logging in the IDE and then attempt to view the dashboard. Each affected piston will output an error about a null object. Visit each of them in the CoRE UI and tap on the Rebuild this CoRE piston under the Advanced Options section. Then repeat the process until the dashboard works again. Sorry for the trouble, I will get them to automatically rebuild in the near future, should such a rare event happen again.
UPDATE 7/26/2016: Official wiki is here. It’s still a work in progress, but it’s a good starting point.