Home Automation can be integrated with OpenRemote.Org using this software in Java.

So it can work on any hardware with a Java virtual machine implemented.

Export data from eHouse system to OpenRemote

After you set up the software in a text file “JavaORServer.cfg”, set global variables of software which are the main features of the application.

Setting the variable “ehousecommunication.ExportOpenRemoteDesignerObjects=true” allows you to export eHouse system settings to OpenRemote.Org .

Because OpenRemote.Org in the current version does not have a data import interface, for integration with external systems , it is necessary to directly write to the database OpenRemote.Org named “Beehive”.

User parameters to local databases are included in the variables:

• ehousecommunication.BeehiveUserName – Beehive user database
• ehousecommunication.BeehiveUserPassword – password
• ehousecommunication.Dbhost – mysql server address
• ehousecommunication.MysqlPort – mysql server port

Additional options related to the export eHouse to OpenRemote:

• ehousecommunication.IgnoreAtChar – ignore all signals that includes a ‘@’ for export
• ehousecommunication.DisabledOpenRemoteExportTCP – Export settings for Ethernet controllers
• ehousecommunication.DisabledOpenRemoteExportEhouse1 – Export settings for eHouse1 controllers

EHouse4OpenRemote application after running the above settings, loads the complete configuration to OpenRemote database, comprising:

• “Digital outputs buttons” with the possibility of changes state and reading state
• Read the status of the digital inputs
• Analog/Digital converter input, Measuring and reading value
• Alarm inputs divided into security mask (active , alarm , warning , monitoring) and read status
• “Programs buttons” with the ability to change the Program
• “Rollers and security programs buttons” with the ability to change the program
• “ADC Programs Buttons” with the ability to change the
• “Security zone button” changes and the reading of the current zone

There is a lot of Data, so unused signals should be limited by changing their names by adding the sign ‘@’ and blocking exports by setting the variable ehousecommunication.IgnoreAtChar = true.

The data are divided into separate units together with suitable additives “-Outputs” , “-Programs” , “-ADCPrograms” etc.

After exporting data from the system average there are thousands Comfort , So it is necessary to manually remove items , we do not want to monitor.

Otherwise OpenRemote will ask for each device individually which is very inefficient way.

This is a much worse controller status update method, comparing to eHouse native panel applications, in eHouse system visualization for different platforms, which processes all the data from the binary status of the controller on panels side. Statuses are received in packages, one for each controller premises at about 15 seconds each , containing a few hundred bytes.

Therefore, for the platforms supported by eHouse system, always better to use our applications , which, moreover, does not require an additional PC with eHouse4OpenRemote software and OpenRemote.Org. eHouse Software connects directly to the Ethernet network controllers. In the case of system controllers eHouse1 under the supervision of CommManager connect indirectly via CommManager. Home Automation eHouse4OpenRemote – JAVA

After the export to databases OpenRemote.Org “Beehive” “designer” can create a configuration panel individually, using the ready signal , command , Labels , Switches , sensors according to the needs of each individual panel.