eHouse Home Automation , Building Management Ethernet version enables direct communication with a virtually unlimited number of panels display the current status of Home Automation Controllers using the UDP protocol on the LAN. home Automation eHouse – update panels over UDP (User_Datagram_Protocol) .

Unlike the TCP protocol is a connectionless protocol, ie. does not require a permanent connection between the client and the server , session tracking , lack of mechanisms to control data , flow and retransmission.

This makes it much faster than the TCP protocol, however, it is possible to loosing data and other errors .

In the case of User Datagram (Individual frames for any system) , transmission correctness must deal with communication software .

UDP is ideal for sending broadcasts (messages , broadcast to multiple devices at once, without making further connections with the clients from the server).

The most important features are the following:

• Connectionless protocol receiving another device connection to server will not load server
• messages are sent globally to all devices on the LAN
• the server does not matter if it sends messages to 0 or more devices or listening devices such as messages
• transmission errors have no impact on server suitable data
• data transmission is unprotected against errors , there is: no confirmation , no flow control

Because UDP does not have protection against transmission errors, to use it in the eHouse , and to enable error checking data packets are sent width check-sum for verification.

This allows them to compare and use of client-side when sent check-sum is equal to calculated one.

For eHouse , a comparison of the data is in the client and its software.

Data is sent from the server in binary form and must be decoded by the client software .

The server sends the data to the specified port (default 6789) , and the client must listen for incoming messages asynchronously on the port .

Asynchronous means , that the data is not cached, and your device must receive packets on an ongoing basis at the time of dispatch (real time).

Selecting UDP port depends on the architecture of the system and depends on the type of installation , if all the controllers are sending packages to the same status that each port to another and can be selected individually from eHouse system applications.

A data packet is the same as in the case of transmission via the TCP communication with the Ethernet drivers or software eHouse.exe for PC sending binary data over UDP .

This allows the use of a single function (procedure) decoding of a frame, regardless of whether the transmission medium, transmission protocol is.

The data are not secured to facilitate the decoding of the individual control panels and software for visualization.

This will allow the display of information on the panels in only a limited number of subnet mask IP, ie .255 . Because these are the only devices status without the possibility of run the system event ,it may be released to the public outside the firewall LAN.

In special cases, you can create a VPN (Virtual_Private_Network) – tunneled connection to receive the status of the drivers for the external panels outside the network , or use TCP logging a challenge – response (with dynamic verification code) , which is still active.

These data are not critical and without decoding packages by eHouse application, this is bunch of ones and zeros, that must be decoded by software package eHouse system for panels of any type.

eHouse.exe Software has been updated , that allowed the collection of such data by the UDP – User Datagram Protocol. It only refers for Ethernet eHouse or eHouse 1 under CommManager supervision systems.

To do this, run the application with a parameter eHouse “eHouse.exe /VIAUDP” capitalization does not matter.

This will allow for a much more reliable reception of the status of CommManager , and connected to it eHouse_1 controllers working with RS-485 interface.
EHouse application receives (listens) only incoming packages with drivers. Packages are sent with check-sum and if any data errors appears, are simply ignored, and will be updated with the correct reception of the next valid packet containing the status of the controller .

This method also frees clients from the server and network errors, Routers , switch , since there is no case of breaking the communication with the server , due to the connectionless UDP protocol idea.

It does not cause a suspension or permanent loss of application updates, As in the case of a combination of protocols to the server, but only temporarily during a link failure , and only loosing packages during failures or excessive load on the network .

Losing the package status of the controllers is acceptable , as they are cyclically repeated with a change in the status of each controller, and the minimum period is about 15 seconds if there is no change.

For UDP broadcast from controllers broadcast from ehouse.exe application must be disabled. If you select this option for eHouse.exe application ceases to send its own binary status of the UDP , because these are the same data , that currently are spread directly from the Ethernet controllers eHouse and it will duplicate network traffic.

Status text (decoded by the application eHouse) may continue to broadcast , if eHouse.exe application is activated , giving the user the ability to use the old control panels , text-based log files and binary packages not applicable.

In this case, the application passes through eHouse.exe , which is another link in the chain , from a combination of panels also depends of the computer .

This use, however, is good for the system running completely in the standard eHouse 1 (no CommManager) because it gives you the opportunity to work with panels receiving data from the eHouse.exe application , despite the lack of built-in interface for Ethernet transmission in controllers.

Control Lights