openhab/openhab-distro 2.5.0

openHAB 2.5.0

on GitHub

This is the official release of openHAB 2.5.0.

The binaries are available on Bintray and via "Stable" on our APT repository.

New and Noteworthy

The openHAB 2.5 release contains many new features, enhancements and bug fixes, both for the core runtime and for many add-ons.
You can find the most relevant ones listed in detail below.

Quick links:

• Notes about new add-ons
• Notes about the core runtime
• Notes about the add-ons
• Notes about the legacy add-ons
• Upgrade Process for openHABian, APT, RPM, Manual Installations
• Breaking Changes that require manual interaction after the upgrade.

Relevant Changes

New Add-ons

The following add-ons are newly introduced with the 2.5 release:

Runtime

2.x Add-ons

1.x Legacy Add-ons

Upgrade Process

openHABian

If you are working with an openHABian setup, the upgrade is quite easy. Regardless of if you are currently using the openHAB 2.5 stable release or one of the latest 2.5 SNAPSHOT builds, switching to openHAB 2.5.0 stable is done in just a few steps:

1. Connect to the SSH command line and execute: sudo openhabian-config
2. Select the "Update" option
3. Wait for the openHABian update to finish, reenter the openHABian configuration tool
4. Select the "openHAB 2.5.0 stable" option

Package-based Installations

For package based installations, you may be asked to replace some configuration files in /var/lib/openhab2. For best results select yes at each of these prompts. Old configurations can be found in the same place, but with dpkg-old appended to it.

APT

Make sure that openHAB is sourced from the latest location, has the correct GPG signing key and that your system can download .deb packages via HTTPS by following the instructions for a stable installation in the docs.

If the above is correct, simply upgrade by using:

sudo apt-get update
sudo apt-get upgrade

Alternatively, you can force apt to install 2.5.0 and its optional add-ons with:

sudo apt-get install openhab2=2.5.0-1

## optional add-ons for offline installation ##
sudo apt-get install openhab2-addons=2.5.0-1
sudo apt-get install openhab2-addons-legacy=2.5.0-1

RPM

openHAB is also distributed in RPM packages. To use them, make sure that openHAB is sourced from the latest location, and has the correct GPG signing key for verification by following the stable installation instructions outlined in the docs.

If the above is correct, then simply upgrade using your systems package manager (yum, dnf, etc.)

sudo yum update

Alternatively, you can force apt to install 2.5.0 and its optional add-ons with:

sudo yum install openhab2-2.5.0

## optional addons for offline installation ##
sudo yum install openhab2-addons-2.5.0
sudo yum install openhab2-addons-legacy-2.5.0

Manual Installations

Official update scripts are available that let you update your 2.4 installation to version 2.5:

Linux/MacOS

1. Change to your openHAB root directory (e.g. cd /opt/openhab2)

2. Now simply run the command:

sudo ./runtime/bin/update 2.5.0

Breaking Changes that Require Manual Interaction after the Upgrade

REST Docs

This add-on is now part of the UIs. When previously installed using a UI, uninstall the REST Docs before updating and reinstall it after the update to prevent errors. When installing it using textual configuration, update services/addons.cfg by removing restdocs from misc and add it to ui instead.

Textual Configuration

All add-ons (including UIs) now use the openHAB configuration namespace.
Because the openHAB namespace is the default namespace, update the add-on configuration files in the services directory by removing the namespace from the keys.
For example replace org.eclipse.smarthome.basicui:defaultSitemap=demo in services/basicui.cfg with defaultSitemap=demo .

Scripted Automation (JSR223)

All Java classes in the org.eclipse.smarthome.automation package have been moved to the org.openhab.core.automation package.
When scripted automation has imports referencing these packages, they need to be updated.
The latest helper libraries have been updated to check which libraries are available, so that they are also backwards compatible with previous openHAB versions.

Next Generation Rule Engine

Rules created through Paper UI, REST API and directly in JSON files will be have the DTO modified by the upgrade script. If the upgrade script is not used, openHAB will need to be shutdown and all references to org.eclipse.smarthome.automation.dto.RuleDTO need to be changed to org.openhab.core.automation.dto.RuleDTO in $OPENHAB_USERDATA/jsondb/automation_rules.json, $OPENHAB_USERDATA/jsondb/automation_rules_disabled.json and in any backups of these files in $OPENHAB_USERDATA/jsondb/backup/.

Legacy Add-ons

The following openHAB 1.x add-ons have been replaced by openHAB 2.x add-ons and are now part of the legacy add-ons:

• Denon Binding
• IHC Binding
• KM200 Binding
• Mail Action
• Neohub Binding
• Network UPS Tools Binding
• Pushbullet Action
• SNMP Binding
• XMPP Action

To continue using legacy add-ons, enable "Include Legacy 1.x Bindings" in the UI system configuration.
When using file based configuration add legacy = true to addons.cfg.

Discontinued Add-ons

Azure IoT

Due to changes in the Azure API, this add-on is no longer working and has been removed.

Sen.se Persistence Service

The Sen.se service has been discontinued, therefore there is no longer any use of this openHAB persistence service. It has thus be removed from the distribution.

Breaking Changes in Add-ons

DarkSky Binding

The item type of 'rain' and 'snow' channels have been changed to 'Number:Speed'.

EnOcean Binding

Channel 'receivingState' has been removed, because this was a string containing many information. For this, there are three new channels: 'rssi', 'repeatCount' and 'lastReceived'.

Homekit

Some tags have been renamed. Old names will not be supported in future versions. Please check documentation.

LGWebOS Binding

The binding parameter 'localIP' has been removed. The binding now uses system defaults for network communication. The thing type parameter 'deviceId' is no longer a parameter, but a property. Parameters 'host' and 'key' have been added.

MQTT Binding

Homie channel names may have changed if special characters are used for MQTT topic names.

OneWire Binding

The thing types ms-th and ms-tv have been marked deprecated and will be updated to ms-tx automatically.
The thing types counter2, digitalio, digitalio2, digitalio8, ibutton, temperature have been marked deprecated and will be updated to basic automatically.

Please note that auto-upgraded things keep their thing UID including the deprecated thing type.

Manually (via textual configuration) defined things need to be changed to ms-tx or basic respectively.

Deprecated thing types will be removed with the next official release.

OpenSprinkler Binding

The stationXX channels have been removed and replaced by a bridge/thing combination. See documentation for further information.

OpenSprinkler Binding

The Pi interface was removed, as it does not provide all of the features of the binding anymore. Please use the HTTP interface instead.

senseBox Binding

The senseBox binding is now using Units of Measurements, and the channel name for Illuminance has changed. The Items must be reconfigured.

Somfytahoma Binding

The following channels have been renamed: 'cyclic_button_state' to 'cyclic_button', 'battery_status_state' to 'battery_status' and 'lighting_led_pod_mod_state' to 'lighting_led_pod_mode'.

Systeminfo Binding

The 'cpu#load' channel has been removed because the OSHI library no longer provides this information.

TP-Link Smart Home Binding

The energy and rssi channels are now using Units of Measurements. Items must be adapted and the things must be recreated.

Tesla Binding

The binding has been heavily refactored. It is required to delete old Tesla Things and set them up from scratch.

Vitotronic Binding

The following channels have been renamed: 'outsite_temp' to 'outside_temp', 'pelletburner:power' to 'pelletburner:powerlevel', 'party_temp' to 'party_temp_setpoint' and 'save_temp' to 'save_temp_setpoint'