Skip to end of metadata
Go to start of metadata

In this article we will explain how to connect 2N® Helios IP with the home automation system Loxone. At the end of this FAQ you will be able to make the video calls between the 2N® Helios IP  and Loxone mini server via your tablet or smartphone with Loxone app installed. To be able to make calls you need to have the internet connectivity in your LAN because the call will be established via external SIP Proxy server. The scenario with the local calls is not possible.



  • 2N® Helios IP Verso, firmware 2.18
  • Loxone Miniserver v.7

Intercom configuration

First of all we have to create the account on some public SIP Proxy server. Verified service is You just need to create single account. After that we can start with the configuration of the intercom. It is recommended to assign the static IP adrres for the intercom. In this example we will be using the static IP adrress:


FIgure 1: Static IP address setting

Secondly it is necessary to configure the SIP account in the intercom. Account is set based on the information obtained from  In this example the user vs.sip  with the appropriate password has been used. 


Figure 2: SIP account setting

The next step is to configure the quick dial button on the intercom. 

Figure 3: Quick dial button setting

It is necessary to fill in the field Helis IP Eye and specify the Loxone mini server IP address here and used port which is 7000 for the first button (7001 and 7002 for the button 2 and 3). The reason why we have to fill in this field is simple. The UDP packet will be send to the specific IP address if this specific filed is configured. This UDP packet has unique structure which allows the server to dected the incoming call. There is a second way how you can achieve the same functionality which can be realized via automation functions. In this case you can send http command towards the server and also add some user signalling for the person who is in front of the intercom. The automation example can be configured as follows: 



Object Type







Event=1; Uri=http://<local IP of Loxone Miniserver>/dev/sps/io/{virtual input name}/pulse; Username={user}; Password={Password}




Table 1: Automation example

For further details regarding to the automation function please refer here:


Lastly we have to enable automatic answer of the calls and also HTTP API of the camera for the video stream.

Figure 4: Camera's HTTP API

Figure 5: Automatic answer 

 Loxone mini server configuration

To be able to make the calls, it is necessary to use 2 components:

  • Virtual UDP input commnad (periphery>virtual inputs->virtual UDP input->Virtual UDP input command)
  • Door controller (My project->add function block->monitoring->door controller)

First of all it is necessary to configure the Virtual UDP input command. To be able to configure this object, it is necessary to capture the UDP packet. You can do that in the bottom section fo the Loxone configuration tool called UDP. Be aware that every change within your project has to be saved first and then you have to wait till the server restart itself. Once somebody press the button on the intercom, the unique UDP packets is send towards the specific IP of the server. The structure of the command is following:

Figure 6: UDP command 

The incoming packet is not the same all the time, this is the reason why we need to select just the specific part of the command which is always the same. This string is necessary to copy into the Virtual UDP input command section: command recognition.

Figure 7: Virtual UDP input command

  • Note:  In case of soume issues, please verify the UDP port number configured on Virtual input VUI1. The port number 7000 has to be used.

The next object is the Door Controller. For the video stream configuration it is necessary to use these fields:

  • Host for video stream (internal)
  • URL videostream (internal)

Use this URL link: http://<IP address of the intercom>/api/camera/snapshot?width=640&height=480&fps=1

The last parameters which has to be set are following:

  • Host for Audio - IP address of the intercom
  • Host for Audio (external) - filed for the external SIP Proxy address, in this example is in use.
  • Audio username (internal) - it is not necessary to use this field
  • Audio username (external) - The number or name of your created SIP account. In this example the user vs.sip is in use.


Figure 8: Door controller


IMPORTANT Call can be made just via mobile application and not via web interface in your PC.

  • No labels