As requested by many users, the next version of the controller will include an updated version of drools (version 6.4) and be fully compatible with Java 8.
This new version of drools is a big upgrade compared to the 5.x version included in Controller 2.5 and earlier and as such might bring some incompatibilities with existing rules.
This means that some users might need to update their rules in order to have them compile and work as expected with this controller.
For those of you who want to give it a try, the release is available at https://github.com/openremote/Controller/releases/tag/v2.6.0-alpha1
We welcome any feedback on this release, the gotchas with the new drools version and any information on required steps to upgrade existing rules to work in this version.
Note that this is a pre-release version and that some features might be added or removed in the final 2.6 release.
I tried to link in this designer the mac adress but this doesn’t work. So the controller can’t update because of wrong account
The comercial designer (https://designer.openremote.com/login.jsp) doesn’t accept the ol user account -> Do I need a new account? With the pilling information I didn’t get a user/password information.
The designer-test site is a test web site that we’re temporary using to experiment with a potential solution for people to transfer their free account to the 2.5 release but is not ready for public usage.
There seems to have been a mix-up when your account was created, it should have been on the 2.5 designer.
Can you please send me an e-mail (eric at openremote dot org) with the user name your received ? I’ll check to re-create your account.
We will post soon when we have a solution for people to transfer their free account to the 2.5 version.
A small detail is that images attached to buttons don't seem to get transferred at all.
The following rule works perfectly in ORPro 2.5.0 with Java 1.6, but doesn't work at all with ORPro 2.6.0 and Java 1.8
rule "Velbus_to_Loxone_Target Temps"
timer (int: 2s) // Debounce timer
when
$evt:Event(source matches "^.*_Velbus_Target-Status$", $source : source)
then
// The sensor value is the target temperature from Velbus panels
String strValue = $evt.getValue().toString();
int sensorNumber = 0;
String SensorPrefix = "";
try {
// Extract the number from the sensor name
Pattern p = Pattern.compile("^(.*)_Velbus_Target-Status$");
Matcher m = p.matcher($source);
m.matches();
sensorNumber = new Integer(m.group(1));
Given both the move to GitHub and the change in build system in 2.6, the rules folder is indeed not present in the generated controller file structure.
In 2.6 Alpha this was causing an issue.
In 2.6 Beta, this is taken care of by the code itself, the rule engine creating the folder at startup if not present, so no manual folder creation should be required.