- Installation was accomplished via download of v2.5.5 (Windows) stable distribution from the openHAB2 download site.
- The Zip file was installed to C:\openHAB2.5.5 on my home Win64 primary computer.
- Installation followed the procedures outlined below which were taken from the instructions provided on the openHAB2 website and modified here to define the customization options used for the prototype 148Avenida installation.
- The prototype 148Avenida installation, described here, is a re-install of a 2017-18 trial use of openHAB2. Neither install was accomplished in the full manner a routine production install should follow. The primary difference being that for a production install, openHAB should be installed on a dedicated computer, not on a notebook or workstation used for personal work. The prototype installation is being accomplished as a development, not a production deployment. This is noted in some areas below where practices associated with production deployments are noted as such.
Typical hardware and software requirements are:
- 24/7 availability: A dedicated system connected by Ethernet and running continuously.
- Energy and space efficient: A device capable of performing the task at hand without being exaggerated
- Extendibility: Your system should be capable of running additional software like an MQTT broker or a persistence and graphing software.
- Peripherals: Depending on your home automation hardware, you will need additional peripheral devices such as a WiFi interface or a special USB radio module.
- The Raspberry Pi as a minimal sufficient device. A a quick setup identified as openHABian is available. This is one option for an ultimate target platform.
- An popular alternative the Synology DiskStation as an ultimate target, which also has a pre-built solution.
- For development purposes, we are using a Windows x64 installation.
Make sure that you have an up to date Java 8 platform installed on your host system. Zulu is currently the recommended Java platform for openHAB2. Download and installation instructions can be found on Azul Systems’ Zulu website.
Please download and install the Java 8 version of the JVM. openHAB2 does not work well with newer Java versions such as Java 9 or Java 11.
The 64-bit version of the JVM is recommended on platforms using a 64-bit OS and an Intel or AMD processor.
The 32-bit version of the JVM is recommended on ARM platforms such as the Raspberry Pi. The 32-bit JVM performs better on the ARM platform and some add-ons use libraries that do not work with a 64-bit JVM on the ARM platform.
For best compatibility, namely with the openHAB2 Cloud service myopenHAB2.org and the Eclipse IoT Marketplace, the minimum recommended Java 8 revision is “161”. Attention: Most package managers serve an older revision. Check your current Java version by opening a command line console and typing
Old version of Oracle (Eclipse?) Java JDK/JRE
java version "1.8.0_152" Java(TM) SE Runtime Environment (build 1.8.0_152-b16) Java HotSpot(TM) 64-Bit Server VM (build 25.152-b16, mixed mode)
JAVA_HOME=C:\JDK JRE_HOME=C:\JRE Path=C:\JDK\bin;C:\JRE\bin;...
was replaced by new Zulu version using the Zulu MSI installer. Zulu versions were found to work for openHAB, but had issues with other systems. We therefore fell back to the current Java8 version supplied by Oracle.
java version “1.8.0_251“
Java(TM) SE Runtime Environment (build 1.8.0_251-b08)
Java HotSpot(TM) 64-Bit Server VM (build 25.251-b08, mixed mode)
openjdk version "1.8.0_252" OpenJDK Runtime Environment (Zulu 188.8.131.52-CA-win64) (build 1.8.0_252-b14) OpenJDK 64-Bit Server VM (Zulu 184.108.40.206-CA-win64) (build 25.252-b14, mixed mode))
- Manual setup: Download and extract a platform independent zip archive: macOS, Windows, Linux
- Stable: Use the latest official release (hosted on Bintray)
- Download the latest Windows Stable ZIP archive file for manual installation from the Download page.
- Unzip the file in your chosen directory (C:\openHAB2.5.5).
Standard openHAB2 install directory map
- Start the server: Launch the runtime by executing the script C:\openHAB2.5.5
\start.batand wait for it to complete.
- Point your browser to http://localhost:8080. You should be looking at the openHAB package selection page. For 148Avenida, we selected the Standard package.
After you get openHAB2 set up and running, on a production deployment there are a few additional setup steps you should consider. The reason for this is that the production device will typically be on a headless server, one which does not have a keyboard and monitor device attached, and will not typically be placed in a position which is convenient for administrative activities. Rather, these activities will need to be accomplished over a network connection from a separate administrative desktop, notebook, or tablet.
- On the production openHAB2 host device configure a network share and mount it locally: Linux Samba Share, Windows file sharing, …
- Assuming you are using a Windows workstation as an administrative terminal to manage the production device, install Visual Studio Code and the openHAB2 VS Code Extension on your Windows administrative machine, to manage your (remote) production device configuration files. The openHAB2 VS Code Extension comes with built-in support for the openHAB2 syntax and elements.
openHAB2 Community Forum provides support. Use the search function or open a new thread with your detailed question.
- 148Avenida Configuration
- Security Configuration