openHAB Packages for QNAP NAS systems
- QTS firmware version minimum 4.1.0
- At least Java 1.8.101 is required
- The running service needs after installation about 200MB of System Memory. When adding bindings like Z-Wave, the amount of RAM used can rise above 1GB. If QTS does swapping, you could experience speed problems if you have too less RAM.
-
Download the QPKG from the releases section over on GitHub.
-
Create a directory for your addons, configurations and userdata, by either
- Creating a share called "openHAB" (recommended)
- Creating a folder called "openHAB" inside the "Public" share
- Not creating any of them and therefore using
.qpkg/openHAB/distribution
for all data (for testing or demonstration)
-
Go to your NAS's App Center and make sure you have got "JRE" (for x86-CPU based NAS) or "JRE_ARM" (for ARM-CPU based NAS) installed. If that is not the case, go to the "Developer-Tools" section of the App Center, install the appropriate version and wait for a while until the Java installation has finished.
-
Open the "Install manually" dialog in the App Center by clicking the gear-wheel on the upper-right corner of the App Center and choose the
qpkg
you have downloaded. -
Confirm the installation
-
Wait while the package is being installed
-
When finished just close the dialog and wait for a while until openHAB has completely started. This may take several minutes.
-
Access openHAB via "http://NAS_IP_or_DNS_address:8090". If the interface does not start, retry after another minute. The initial startup takes some time.
If you want to keep configuration files, copy them to a save place outside of the openhab-path.
- Go to the "App Center" and remove the app like any other.
- Additionally if wanted or needed, please remove the folders "addons", "conf" and "userdata" from the your directory, eg. "openHAB" share or "Public"/openHAB"
If you have installed openHAB2 to
.qpkg
(see "How to install", third option) then all files get removed automatically.
- (1) Wrong start/stop behaviour: openhab/openhab-distro#258
- (2) Version 2.2.0 has problems with update from previous versions.