I’d like to share some details on the latest new features that made it into the 2.3 snapshot build (#1230):
- First of all, it includes a new update from Eclipse SmartHome with quite some changes (see the details here) - most of them being small fixes, not worth to mention individually.
- The one really big change coming from Eclipse SmartHome is the newly introduced support for units on numbers - you can now choose your measurement system and have any sensor values automatically converted for you and you can also do unit-safe calculations within rules. @henning wrote a blog post about this feature and he will also soon add some details to the openHAB documentation.
Important for all binding developers: In order to have full support of this feature, bindings should be enhanced in a way that they declare the units of the values that they are providing. Please see here for an example how it is done in the YahooWeather binding. There are still a few known limitations of this feature, so please be aware of them. If anyone is interested in helping to implement those missing parts, please leave a comment on the issue - it would be very welcome.
- We have a new KNX binding! This has been in the works for at least 2 years and is now finally merged. It replaces the KNX 1 binding, which has now be moved to the legacy bindings (so if you are using it, please make sure to enable legacy add-ons in your addons.cfg file). We tried to keep the configuration similar to the 1.x KNX binding, so that it is not too hard to migrate - the config strings with the GAs are mainly moved to *.things files, where they can be structured per device. Nonetheless, depending on the size of your setup, the migration might keep you busy for a moment. I have myself done this excercise a few weeks ago and have the binding running in my production environment since then and can assure you that it is working pretty smoothly. So if you are using snapshot builds of openHAB, please have a go and test this binding yourself.
- Karaf has been upgraded from 4.1.3 to 4.1.5, which brings a couple of fixes for the console (see release notes of 4.1.4 and 4.1.5).
As it is quite a big update, please keep an eye on any regression that you might encounter and enter issues on Github for them.
Enjoy the update!