This topic can be used for any discussions around the openHAB 5.3 Milestone builds as it has been announced in openHAB 5.3 Milestone Builds.
Hi Kai,
[[DSL] Make context information available for rules/scripts by Nadahar · Pull Request #5607 · openhab/openhab-core · GitHub] needs apparently [Fix DSL implicit contexts variables for '.rules' based rules by Nadahar · Pull Request #5788 · openhab/openhab-core · GitHub] to work with DSL rule files. Its missing in 5.3M1 Is there any chance to add that to get it into 5.2.2?
Thanks!
We forgot to add a breaking change alert for that … will take care.
Thanks for mentioning. I have just merged the follow-up PR and backported it to 5.2.x, so that it will also be available in an upcoming 5.2.2 release!
Is there a difference between a Milestone and a Snapshot? Or is a Milestone just the Snapshot of a certain day, which is then declared the Milestone for the coming month?
Milestones are more or less a specific snapshot, yes. They are both build from the main branch without a code or feature freeze or RC builds.
However, they are more stable than snapshots as we test the latest snapshot before building a milestone and we also try to avoid merging risky PRs before building a new milestone.
So snapshot builds are the bleeding edge and automatically build (usually every night), whereas milestones builds are manually triggered when we think the current snapshot is stable enough to be published as a milestone.
And M2 is just around the corner, I have the feeling?
Yes, will be released in the next days.
Since 5.3.M3 broke myopenhab.org, will there be a fix (M4, I guess, then?) with @digitaldan’s fix (Fix broken auth with cloud and proxies by digitaldan · Pull Request #5875 · openhab/openhab-core · GitHub)?
Or should I just upgrade to tomorrow’s snapshot?
We will likely do an M4 on the weekend. But feel free to update to the latest snapshot and confirm that the fix is working for you!
Today’s? Or tomorrow’s?
The fix is already included in openHAB-Distribution #5630 - Jenkins
Installed. It works! ![]()
Possible inconsistency in the ON/OFF colors
I noticed that the colors for “ON” and “OFF” appear to switch between the screenshots when going through the days in the new milestone build. In the first screenshot, “ON” is blue and “OFF” is green; in the next, it’s the other way around.
I’m not sure whether this is specific to the new milestone build, but I thought I’d mention it.
There never have been fixed colors in oh-time-series. It’s depends on what ECharts picks on rendering …
Thank you Florian for your prompt reply. Sorry, I wasn’t aware of that, I’ve only just noticed it. I haven’t changed any chart settings; everything is set to the default.
Your question tells that the current behaviour is confusing. I think we should introduce a default color scheme for ON and OFF (green and red).





