-
Notifications
You must be signed in to change notification settings - Fork 4
Hardware FAQ
FAQ about hardware for the openHAB runtime
This page summarizes helpful information on how to get openHAB working on specific hardware. Users are very welcome to provide tips&tricks here, e.g. on JVM experiences, embedded systems etc.
Please note: This page is NOT about home automation hardware (sensors, switches, etc) - consult other websites for such questions. For a list of the systems openHAB can connect to, please see available bindings.
The openHAB Runtime is a Java application. It requires JVM 1.6 or later.
openHAB is expected to run on all platforms (i.e. processor architectures and operating systems) where the required JVM version is available. This includes Windows, Mac OS X, and various distributions of Linux on x86, x86_64, and ARM architectures.
openHAB can be installed and operated on AMD or Intel powered commodity laptop, a desktop computer, or a special form factor platform, such as a popular Raspberry PI single-board computer.
Below are configuration notes for specialized hardware.
ARM-based embedded computers is a popular choice among home automation enthusiasts due to low cost and low power consumption. They are typically extensible with available add-on components and via programmable GPIO. Based on the community feedback and information about the openHAB requirements here is the short comparison of the SBC platforms: (April 2014) (click here for bigger picture).
Raspberry Pi Model B has an attractive price/performance point and is a proven choice for small to medium residential installations. Large installations with few dozens of devices and/or a significant amount of rule logic may experience sluggish event processing and delayed response to control commands.
Raspberry Pi has FPU coprocessor supported by Raspbian Wheezy Linux. According to this press release, the current and all future Raspbian images will ship with hard-float Oracle Java 7 by default.
To setup your Raspberry Pi board for openHAB:
-
Install Raspbian Wheezy release 2014-01-07 or later. It includes Java 7 JRE that meets openHAB pre-requisite JVM requirements.
-
Install openHAB.
Optionally, a complete JDK 7 or 8 for Linux ARM v6/v7 Hard Float ABI is available for download from Oracle or from Apt Repository.
- Stay up to date with rpi-update (https://github.com/Hexxeh/rpi-update/)
- For headless, use a memory split of 240 (e.g. run
sudo rpi-update 240
) - For headless, add these to /etc/rc.local:
- fbset -xres 16 -yres 16 -vyres 16 -depth 8
- /opt/vc/bin/tvservice -o
- Overclocking does not seem to have big influences
1. Install Linux distro
On a separate system download:
-
For CubieBoard2: Cubiuntu - Lubuntu - runs well with OpenHAB Cubian - Debian - runs well with OpenHAB
-
For BeagleBoneBlack TBD
-
For ODroid TBD
2 Make ISO image on micro-SD card Use Win32DiskImager (or dd on Linux/OSX) to make ISO image on micro-SD card (4 GB minimum. UHS-1 speed recommended)
3. Increase size of partition If you have a larger card, increase the partition.
4. Install Java Hard Floating point Download Java ARMHF from Oracle if its not already present.
5. Use symlinks if you use more than one USB port for bindings. See section on Symlinks (https://github.com/openhab/openhab/wiki/Samples-Tricks#how-to-configure-openhab-to-connect-to-device-symlinks-on-linux)
6. Install and setup OpenHAB Follow instructions at Quick Setup or use apt-get as below (https://github.com/openhab/openhab/issues/641?source=cc)
A package of OpenHAB 1.4.0 for Synology Diskstations is stored at OpenHAB google groups and on the package server https://www.hofrichter.at/sspks.
This package can be installed in DSM via the package manager -> manual installation or by adding https://www.hofrichter.at/sspks/ as package source - there is a tutorial on the Synology support pages about how to do that.
This package is tested on DS213+ with oracle's java 7 from PC load letter.
In the Synology package manager you can
- install
- start
- stop
- uninstall
OpenHAB.
This package comes without any demo files - so the UI will not show much without giving OpenHAB some configurations ;-)
It takes some time after the start of OpenHAB before the UI starts responding (less than a minute on a DS213+).
####Paths
OpenHAB is installed at /var/packages/OpenHAB/target/
(which is linked to /volume1/@appstore/OpenHAB
).
If the directory /volume1/public/OpenHAB/configurations
exists, this directory will be used for all OpenHAB configuration files. This should make it easier to work with the OpenHAB designer installed on your PC.
If the directory /volume1/public/OpenHAB/addons
exists, this directory will be used for all OpenHAB addons (bindings) files.
####Ports The UI is on port 8081, the console (via telnet) is on port 5555.
####Demo files In the OpenHAB google groups and on the package server https://www.hofrichter.at/sspks is an install-able package of the OpenHAB 1.4.0 demo files (only the demo files!) for Synology NAS. Prerequisite is that the OpenHAB package is installed.
After the installation of OpenHAB and the demo files http://your.synology.URL:8081/openhab.app?sitemap=demo should show the UI with the demo configuration.
"Text to speech" is disabled in configurations/rules/demo.rules otherwise the demo files are unchanged. This change was necessary (at leased on a DS213+) else OpenHAB stops responding. Give OpenHAB a minute or so after the start of OpenHAB before you expect any response in the UI ;-) ####Kernel drivers Some bindings (e.g. EnOcean) work with USB-sticks that require some kernel drivers. For qoric CPU Diskstations (e.g. DS213+) there is a short guide how to install those drivers at Samples-Tricks.
Installation
Community
- Support
- News Archive
- Presentations
- How to Contribute
- IDE Setup
- How to Implement a Binding
- How to Implement an Action
- Projects using openHAB
- User Interfaces
- Classic UI
- iOS Client
- Android Client
- GreenT UI
- CometVisu
- Bindings
- Asterisk Binding
- Astro Binding
- Bluetooth Binding
- Comfo Air Binding
- CUL Binding
- CUPS Binding
- digitalSTROM Binding
- DMX512 Binding
- EnOcean Binding
- Epson Projector Binding
- Exec Binding
- Fritz!Box Binding
- Fritz AHA Binding
- GPIO Binding
- HDAnywhere binding
- Heatmiser Binding
- Homematic Binding
- HTTP Binding
- IHC / ELKO Binding
- Insteon Hub Binding
- Insteon PLM Binding
- Ir-Trans Binding
- KNX Binding
- Koubachi Binding
- MAX!Cube-Binding
- MiLight Binding
- Modbus TCP Binding
- MPD Binding
- MQTT Binding
- MQTTitude binding
- Neohub Binding (Preview)
- Netatmo Binding
- Network Health Binding
- Nibe Heatpump Binding
- Nikobus Binding
- Novelan/Luxtronic Heatpump Binding
- NTP Binding
- One-Wire Binding
- Onkyo AV Receiver Binding
- Open Energy Monitor Binding
- OpenPaths presence detection binding
- OpenSprinkler Binding
- OSGi Configuration Admin Binding
- Philips Hue Binding
- Piface Binding
- Pioneer-AVR-Binding
- Plugwise Binding
- PLCBus Binding
- Pulseaudio Binding
- RFXCOM Binding
- Samsung TV Binding
- Serial Binding
- Snmp Binding
- Squeezebox Binding
- System Info Binding
- Somfy URTSI II Binding
- Sonos Binding
- Swegon ventilation Binding
- TCP/UDP Binding
- Tellstick Binding
- TinkerForge Binding
- VDR Binding
- Velleman-K8055-Binding
- Wake-on-LAN Binding
- Withings Binding
- XBMC Binding
- xPL Binding
- Z-Wave Binding
- Persistence
- db4o Persistence
- rrd4j Persistence
- MySQL Persistence
- MongoDB Persistence
- Sen.Se Persistence
- Cosm Persistence
- Logging Persistence
- Exec Persistence
- MQTT Persistence
- Automation
- Scripts
- Rules
- Actions
- Misc
- REST-API
- Security
- Google Calendar Support
- Twitter Action
- Service Discovery
- Dropbox Bundle
Samples
- Item definitions
- Sitemap definitions
- Binding configurations
- Rules
- REST Examples
- Tips & Tricks
- FAQ
- XSLT Transforms
- Scripts
- Integration with other applications
- Syntax highlighting for external editors
- Update-Scripts
- Samples-Comfo-Air-Binding
- Samples WAC Binding
Release Notes