TASTE-OF-IT

openHAB 2.2 veröffentlicht

JARVIS
openHAB Logo

openHAB Logo

Nach mehr als 6 Monaten hat das openHAB Projekt das Update 2.2, für die gleichnamige Hausautomatisierungslösung, veröffentlicht. Das mit Java entwickelte Serversystem ist seit 2010 auf den Markt und wird inzwischen von einer aktiven Gemeinschaft vorangetrieben. openHAB ist herstellerunabhängige und setzt auf auf viele übliche Protokolle.

openHAB 2.2 wesentliche Punkte

Amazon: Homematic IP Fenster- Und Türkonta.

Amazon: Homematic IP Smart Heizkörperther

Amazon: Homematic IP Steckdose

Amazon: Hmoematic IP Access Point Gateway

openHAB 2.2 Home Builder
  • neues Release von openHABian 1.4 für alle Raspberry Pi Modelle von 0W bis 3 sowie PINE A64 mit leichterer Installation und neuen Optionen neben openHAB, wie Node-RED, KNXd, Grafana und FIND uvm.
    • openHAB 2.2 openHABian
  • Integration von neuen Geräten (Bindings) wie Loxone, webOS-based LG TV Support, iCloud Binding mit “find my iPhone” Funtkion
    • openHAB 2.2 iPhone Finding
  • Überarbeitung von Bindings wie DMX, Nest  und Plugwise
  • weiterhin wurde die iOS und Android App aktualisiert

    • openHAB 2.2 vollständige Release Notes

    Core Runtime

    Enhancements
    Bug Fixes

    Add-ons

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

    The following changes were done on existing 2.x add-ons:

    Paper UI

    Enhancements
    Bug Fixes

    Basic UI

    Enhancements
    Bug Fixes

    HABPanel

    Enhancements
    Bug Fixes

    2.x Addons

    AllPlay Binding

    Enhancements

    Astro Binding

    Enhancements
    Bug Fixes

    AVM FRITZ! Binding

    Enhancements

    Chromecast Binding

    Enhancements

    CometVisu UI

    Enhancements

    CoolMasterNet Binding

    Bug Fixes

    Gardena Binding

    Enhancements

    Harmony Hub Binding

    Enhancements

    HD PowerView Binding

    Bug Fixes

    Homematic Binding

    Enhancements
    Bug Fixes

    Hue-emulation

    Enhancements

    Keba Binding

    As of 2.2 the Keba binding supports all P20 and P30 variations of the Keba EV Charging stations. In doing so the supported Thing type changed from “kecontactp20” to “kecontact”, and users should therefore alter their .things definition files.

    Kodi Binding

    Enhancements

    LIFX Binding

    Enhancements
    Bug Fixes

    Lutron Binding

    Enhancements

    MiHome Binding

    Enhancements

    Netatmo Binding

    Enhancements

    The binding has been largely updated and enhanced with the support of new devices like the Welcome camera.
    You will have to update your thing definition (or re-create them if you are using Paper UI) because few parameters have been renamed like for example “equipmentId” renamed into “id”.

    Bug Fixes

    Network Binding

    The binding has been enhanced with many new features like
    ARP ping, an iOS specific presence detection and correct access rights for DHCP.
    The former “device” Thing has been split into “pingdevice” and
    “servicedevice”. The following configuration is now a binding configuration:

    Onkyo Binding

    Enhancements

    PioneerAvr Binding

    Enhancements

    RFXCOM Binding

    Enhancements
    Bug Fixes

    SamsungTV Binding

    Enhancements

    Silvercrest Binding

    Enhancements

    Sonos Binding

    Enhancements
    Bug Fixes

    Squeezebox Binding

    Enhancements

    TRADFRI Binding

    Enhancements
    Bug Fixes

    WiFiLED Binding

    Bug Fixes

    Zigbee Binding

    Enhancements

    ZWave Binding

    Enhancements
    Bug Fixes

    openHAB 1.x Add-ons

    The following changes were done on existing openHAB 1.x add-ons:

    Anel Binding

    Enhancements

    Bticino Binding

    Enhancements

    CalDav Binding

    Bug Fixes

    Cardio 2é Binding

    Enhancements

    Denon Binding

    Enhancements
    Bug Fixes

    DynamoDB Persistance

    Enhancements

    eBUS Binding

    Bug Fixes

    Epson Projector Binding

    Enhancements

    Fritzbox TR064 Binding

    Enhancements

    HTTP Binding

    Enhancements
    Bug Fixes

    InfluxDB Persistance

    Bug Fixes

    JDBC Persistence

    Enhancements

    KNX Binding

    Bug Fixes

    LightwaveRF Binding

    Bug Fixes

    mapDB Persistance

    Bug Fixes

    Novelan Heatpump Binding

    Bug Fixes

    OneWire Binding

    Enhancements

    Satel Binding

    Bug Fixes

    Swegon Binding

    Enhancements

    TCP Binding

    Enhancements

    Telegram Action

    Enhancements

    Weather Binding

    Enhancements
    Bug Fixes

    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.1 stable release or one of the latest 2.2 SNAPSHOT builds, switching to openHAB 2.2.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.2.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.2.0 and it’s optional addons with:

    sudo apt-get install openhab2=2.2.0-1

## optional addons for offline installation ##
sudo apt-get install openhab2-addons=2.2.0-1
sudo apt-get install openhab2-addons-legacy=2.2.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.2.0 and its optional addons with:

    sudo yum install openhab2-2.2.0

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

    Manual Installations

    Offical update scripts are available that let you update your 2.1 installation to version 2.2:

    Linux/MacOS

    1. Change to your openHAB root directory (e.g. cd /opt/openhab2)
    2. If you are upgrading from a version after and including 2.1.0, then simply run the command:
    sudo ./runtime/bin/update 2.2.0
    1. If you are upgrading from a version before 2.1.0, you can download and run the update script in one command using:
    sh -c "$(curl -fsSL https://raw.githubusercontent.com/openhab/openhab-distro/2.2.0/distributions/openhab/src/main/resources/bin/update)" -- 2.2.0

    Windows

    This is the first stable version with a Windows update script, therefore you will need to download the one packaged with 2.2.0 to upgrade. To do this, make sure to download update.ps1 and backup.ps1 from the github repository (right-click the page then “Save-As”) then save it to the runtime/bin folder of openHAB. To start the update process, run PowerShell as an administrator and use the following commands. Assuming you have openHAB saved in C:\openHAB:

    cd C:\openHAB
. .\runtime\bin\update.ps1
Update-openHAB -OHVersion 2.2.0

    Now that openHAB has updated, you only need to run the above commands again for future versions.

    Breaking Changes that Require Manual Interaction after the UpgradeGeneral Changes

    Rules

    Running openhab using docker

    There are small changes for running openHAB using docker. For both docker and docker-compose you have to pass a parameter to inform docker that it should ‘allocate a pseudo-TTY’. The examples have been updated but the short explanation is that docker run needs either the -t or --tty parameter and docker-compose needs configuration format 2.1 and tty: true.

    Die mobile Version verlassen