• Building automation in various standards
• Intelligent buildings in various standards
• Audio / Video , HiFi various manufacturers
• the possibility of any integration with java

OpenRemote.Org environment is completely written in Java that allows adding additional systems , protocols and control codes of external devices .

OpenRemote.Org great advantages of the system are:

• Free software – freeware
• Free source code – opensource
• Ability to integrate with any system OpenRemote by Java applications to communicate
• ongoing development of the system with new communication protocols with different systems
• A huge database of infrared signals to control devices like TV, HiFi, Audio, Video, etc.

The Server “Remote Controller” is running on “Tomcat” Application Server, transferring data between the panels and the controllers quering their status , input , outputs, measurement signals etc. .

Panels cooperating with OpenRemote have installed the client software to communicate with the server .

Currently the software is available for panels:

• Android
• iPhone/iPad/iPod
• Web Browsers

It is possible to create any panels on the above platform (smartphones , Tablets , touchphones , PCs etc) .

for integration EHouse system with OpenRemote java application (eHouse4OpenRemote) is required , which is equivalent to the query server OpenRemote , and send control commands .

EHouse4OpenRemote overlay software is dedicated to OpenRemote having the following functions:

• It acts as a “Proxy Server” or “gateway” between “OpenRemote” and controller eHouse
• Controller status updates are sent via UDP Broadcast – continuous listening
• Loading configurations , names of internal controls for application cache
• quering for current status , output states , inputs , dimmers , measuring inputs to the internal application cache
• Contains TCP/IP server , which can receive events from OpenRemote and other applications
• Includes TCP/IP client , which allows you to send commands to the controllers and allows authorization to eHouse Home Automation system
• Includes multi-thread TCP/IP server , that listens for queries about the status of controllers and application cache events to be sent to controllers
• This allows the full import of the “OpenRemote Designer” all signals of the controllers: inputs , Outputs , measuring inputs , dimmers , programs , security zones. It reads the status or condition of a signal making it easier to implement and significantly reducing the time
• This allows the full import of the “OpenRemote Designer” eHouse system events associated with controllers – OpenRemote as system commands much easier and speeding up implementation and system integration

The application needs to be configured in a single configuration file “JavaORServer.cfg” located in the directory where the file was placed “eHouse4OpenRemote.jar” of eHouse4OpenRemote applications.

All names and controllers configuration is read from the specified path of the eHouse installation directory on Windows system .

the configuration file is as follows (in brackets is a description which must be removed):

192.168.0.254 (Address CommManager or application server eHouse PC)

9876 (TCP/IP, CommManager or eHouse server PC application – to send commands)

6789 (UDP broadcast listen port – reception status of the controllers)

passwd (password to CommManager for authorization with normal or encrypted password)

00000000000000000000000000000000000000 (No change)

c:\e-house\ (path to eHouse application server )

4321 (Port for TCP/IP Server – to communicate with OpenRemote or other services)

127.0.0.1 (link-address of local machine where eHouse4OpenRemote is installed )

localhost (the local hostname to reach the Beehive database of OpenRemote)

3306 (Port Access to MySQL)

Cp1250 (windows code page to read configuration files)

beehive (user name to the database beehive of OpenRemote)

beehivepass (user password to access the database beehive of OpenRemote)

To initiate configuration eHouse one controllers software for eHouse4OpenRemote must be run “eHouse.exe /mobile” after each change of name in the system and adding/removing controller.

Configuring the Ethernet driver automatically creates a record whenever the new settings of controller will be performed.