English

Installation OpenRemote.Org on the local PC for integration with eHouse home automation

Home Automation eHouse (eHouse4OpenRemote software).
Integration OpenRemote.Org (OR) with eHouse building automation.
OpenRemote.Org is an open project (open source) integrating different control systems ,remote ,automation ,HiFi ,TV ,SAT and building automation.
It is also possible to integrate OpenRemote.Org with eHouse intelligent building system.


It is necessary for OpenRemote.Org server a PC , and software (eHouse4OpenRemote) that will allow you to control , visualize and update the status of OpenRemote panels devices on various platforms:

  • Android Tablets , Smartphones
  • iPhone , iPad , iPod
  • Web browser

Although OpenRemote.Org runs on the following platforms:

  • Microsoft Windows
  • Mac OS X
  • Linux
  • Synology NAS
  • NETGEAR ReadyNAS
  • QNAP NAS
  • Raspberry Pi
  • ALIX PCEngines

We will describe the OpenRemote installation on Windows system, because all ehouse system applications for configuration, and so are written for Windows.

Nevertheless , that the list of supported hardware for OR is very wide, we do not recommend installing it on a mini single-core computers, because their performance can prevent proper operation of OpenRemote.

Please note that EthernetRoomManager controllers is a lot of resources checked by OR:

  • 24 to 35 digital outputs
  • 12 digital inputs
  • 3 dimmers
  • up to 16 measurement inputs
  • and 10 other signals

This means that in the case of not blocking unused signals, OpenRemote software asks almost 80 times the hardware resources of only one ERM .

CommManager has many more resources from the point of view OpenRemote queries:

  • up to 80 digital outputs
  • up to 48 alarm inputs (Active)
  • up to 48 alarm inputs (Alarm)
  • up to 48 alarm inputs (Warning)
  • up to 48 alarm inputs (Monitoring)
  • up to 16 measurement inputs
  • about 10 other signals

Assuming comfort version of eHouse with 10 EthernetRoomManager (ERM) + 1 CommManager , there are a lot of signals (resource controllers) to check by OpenRemote (1100) the single poll will signal a significant amount of CPU. In the event of poor performance machines may not be powerful enough for OR, so we recommend installing the PC with at least 2 processor cores and 2GB of memory.

To install OpenRemote.Org you need the following components (note the version of the component – not always the newest version will work):

  • Java JDK 1.6
  • Apache Tomcat 6 or 7
  • Apache Ant 1.7 (archive.apache.org/dist/ant/binaries/apache-ant-1.7.0-bin.zip)
  • Google GWT 2.4.0 of (google-web-toolkit.googlecode.com/files/gwt-2.4.0.zip)
  • MySQL Server (and administration program , eg.MySQL WorkBench , or PHPMyAdmin)
  • tool to get the sources from svn repositories , eg for WIndows.TortoiseSVN (tortoisesvn.net/downloads.html)


1.Installing Java components

  • Java SDK. The standard windows installer needs to be run with administrator rights
  • Tomcat 6 or 7 – instructions. Just unzip the contents of the directory: ” C:\Tomcat “.
  • Set the environment variable JAVA_HOME , pointing to the directory where Java is installed , eg.C:\Program Files\Java\jdk1.6.0_36

2.Installing MySQL , with the InnoDB engine and MyIsam.

  • create a schema “beehive”
  • Create a user with full access rights to the schema “beehive”
  • configure ehouse4OpenRemote application to set the same username and password as you created

Installing the Beehive (service is responsible for the management of users and configuration)

Download the source (openremote.svn.sourceforge.net/svnroot/openremote/trunk/Beehive)

Installing Eclipse: (If you are going to modify the OpenRemote project source codes)

  • Download Eclipse IDE for Java EE Developers (Windows) from (www.eclipse.org/downloads/)
  • GWT Plugin – installation according to the documentation developers.google.com/eclipse/docs/install-from-zip
  • download “OpenRemote Controller” source from svn
  • add Tomcat/controler/runtime in Windows Eclipse – > Show View – > Web Servers.mulesoft.com/tomcat-eclipse
  • create a new project by selecting the ” Existing Ant buildfile ”
  • in the project properties – improve parameter “Target Runtime”