IP telegrams with values - sample project
These settings are required to exchange IP telegrams with values between 2 HomeServers.
In this example, HomeServer device 1 sends the conditions of a singe-room temperature controller to another HomeServer (device 2).
In device 2, the values are then shown in the Visu (see below).

The sample project is provided with documentation at www.dacom-homeautomation.de Downloads.
Receiver settings, HomeServer device 2
The IP-address of the receiver in this example is: 192.168.0.151



receive mask IP telegram



On arrival of the telegram, an
entry in a report archive command is simultaneously run (see below).




The single parts of the value IP telegram of a communication object are assigned here
Example: The incoming actual temperature is assigned to an internal communication object.
The identifier ITA identifies the beginning of the value.
The identifier ITE identifies the end of the value within the IP telegram.



Example: Status of the SR


Example: Cool object of the SR


A command is run for every telegram.
This function is not required in order to exchange values between the HomeServers.


The received values are shown in a Visu page.
Requesting of the values is also implemented via an IP telegram. In this sample example, however, this is not documented.
Transmitter settings, HomeServer device 1
The following settings are required for data transfer.
The IP-address of the transmitter in this example is: 192.168.0.158




In this example, the data are transferred on request via an IP telegram and the "send IP telegram" command.
A binary trigger (logic) would also be possible; this would then send an IP telegram every time the actual temperature arrives.




Connection of the EIB communication object with the IP telegram part ACTUAL temperature.
Here also, the beginning of the value within the IP telegram is set via identifiers e.g. ITA and ITE.