Mobotix T24/T25


In this seminar, you will learn how to integrate a video-intercom with Loxone. This will enable you to get the camera’s image over the app or web interface and also speak through the intercom from wherever you are. Follow this link to go to the page on the Loxone Intercom.


The door controller function block can be used to communicate with IP cameras or door intercoms. The function block uses two separate techniques for audio and video, thus it is possible to use a video only, audio only or both video and audio for your IP camera or intercom.

JPG-Url for MOBOTIX T24/T25

Mobotix version under
Http: // url: port / cgi-bin / image.jpg? Size = 320×180? Quality = 60
Mobotix version from
Http: // url: port / cgi-bin / image.jpg
Or you can change to “Basic” in the “Admin Menu” -> Web Server -> Authentication Method. Then the old stream works.

LoxonautFind out about how to setup your Loxone Intercom here!





To be able to see a live image from your camera in your Loxone application, you need to provide an url to the current camera image. This can be either a .jpg image or a .mjpeg. The majority of IP cameras support one of these types, meaning you can choose from a wide range of vendors and models.

The Mobotix stream is http://url:port/cgi-bin/image.jpg?size=320×240&quality=60

The username is admin, and the password is meinsm.


The audio connection is based on SIP. Through SIP the Loxone app basically calls your camera door intercom via VoIP. The main advantage to using SIP over a conventional audio stream from the camera is that you have bi directional communication. As an example please see steps required to confgure a Mobotix T24 below.

Icon Exclamation Mark LoxoneAudio communication works with Android devices from version 4.1.1 onwards, and Apple iPads from model 2 onwards.

Admin settings

Admin Menu

  • SIP-Server Settings
    – Activate SIP-Server
    – Create SIP-Account

Mobotix Setup

You must not delete account *201

SIP-Client Settings

  • Activate SIP-Client
  • Choose expert setup tab not the default quick setup tab
  • Add new SIP-Account (the one, just created)
    – Hostname = IP-Address of the Mobotix Cam
    – Username = Name of the user you have just created.
    – Port = Port from the SIP-Server-Settings (z.B.: 5061)
    – Check “Available as Proxy” & “Use as registrar”

Mobotix Setup 2

If you use an external SIP Server please write your account and server name into the fields.
Here is an example for

Incoming Call Settings

  • Accepted Phone Numbers or SIP Addresses – remove all entries.
  • Accepted SIP-Proxies – remove all entries.
  • Set Audio-Mode to “Intercom”.

Mobotix Setup Incoming Call


Using the Mobotix T24’s hardware buttons in the configuration software

In order to be able to use the ‘Ring’ and ‘Light’ hardware buttons in the configuration software, you will need to follow these steps:

1. Creating a virtual input in the configuration software

  • In the Periphery tree click on virtual inputs and then add a virtual input from the drop down list in the Context tab. It is important to know the number of your virtual input. In the following example, the Mobotix controller is configured to send a signal to virtual input number 1 (VI1).
  • Connect the newly created input to the Tr input of the door control function block.
  • Save this configuration on the Miniserver.

2. Setting an ‘IP notification profile’

  • Go to the admin menu of the Mobotix web interface
  • Under ‘Transfer Profiles’, select ‘IP Notify Profiles’
  • Insert a new ‘IP-Notify Profile’
  • Give the profile an easy-to-remember name, such as ‘Miniserver_VI1_pulse’
  • Under ‘IP Notify Type’ select ‘Custom Configuration’
  • Under ‘Destination Address’ enter the IP address and port of your Miniserver
  • In the ‘Data-Protocol’ section, select ‘HTTP/1.0 Request’
  • Also in the ‘Data-Protocol’ section, you must give the ‘CGI-Path’. Since you wish to send a signal to virtual input 1, you must enter ‘/dev/sps/io/VI1/pulse’. If you’d configured a different virtual input, then you must adjust the path depending on the input (/dev/sps/io/VI{x}/pulse)
  • Still in the ‘Data Protocol’ section, enter the username and password of your Miniserver in the following way: username:password. (Make sure you don’t enter the username and password for your Mobotix T24 door controller here instead!)
  • In order to reduce the volume of data sent, select ‘Plain Text’ under ‘Data Type’ and delete the content of the ‘Message’ text box.
  • Close the window by clicking on ‘Set’
  • Close the admin menu window

Mobotix Setup Notify Settings

Under ‘Destination Address’ you must always enter a Port even it is Port 80!

3. Create an ‘Action group’ in the Mobotix Setup menu

Go to the Mobotix web interface and find the setup menu
Under ‘Event control’, select ‘Action group overview’
Insert a new group
Since you are creating an ‘Action Group” which always sends a signal to a virtual input on the Miniserver if someone presses the doorbell, call the group ‘Always’ and select both ‘Enable’ and ‘No time table’ in the ‘Arming’ section
Click on ‘Set’ to save this new ‘Action group’

Mobotix Setup Action Group Settings

4. Assigning the new ‘IP notification profile’ to the correct button in the ‘Action group’

  • In the same window ‘Action group overview’ select ‘Edit…’ for the action group you have just created to specify the details
  • The fields in the ‘Action group’ section are already correct, so nothing needs doing here
  • Under ‘Event selection’, select ‘Signal: CameraBellButton’
  • The ‘Action details’ section can be left as it is
  • Under ‘Actions’, click ‘Add new action’
  • In the ‘Value’ field of the newly created action, where FTP: FTP-Webcam is currently selected, you can now select the previously created IP notify profile. Select ‘Miniserver_VI1_pulse’
  • Click on ‘Set’ to save the changes
  • You can now close all browser windows

Mobotix Setup Action Group Settings Details


With the user interface

  • Ensure that the intercom function appears on the user interface (in the app or with a browser)
  • Start the user interface
  • Go to your T24 and click on the door bell
  • In the user interface, a pop-up should appear with the picture from your door controller
  • If this does not happen, please see the troubleshooting section

Without the user interface

  • Start Loxone Config
  • Connect to your Miniserver
  • Load the configuration from you Miniserver
  • Start Liveview
  • Go to your T24 door controller and press the door bell
  • You should now see that the Qb-output is active
  • Again, if this does not happen, please see the troubleshooting section

Example Virtual Input Door Controller Loxone Config Mobotix


  • Press the doorbell on your T24 door controller
  • Go to the Admin Menu on the Mobotix Webinterface
  • Select ‘System Messages’
  • You should find a new entry here which will read something like this:
  • 08:56:26 IPMSG Miniserver_VI1_pulse[10821]Notify sent to 179 bytes in 3.008s.

Icon Exclamation Mark LoxoneIn this list, there might by thousands of system messages, and the newest may not always be at the beginning. It might therefore be helpful to delete all the messages before attempting to troubleshoot.

  • If there is no message like the one given above, then there might be an error report describing an potential error.
    • 09:16:24 IPMSG Miniserver_VI1_pulse[14865]Unauthorized HTTP request to (HTTP code 401)
      A message like this suggests that the username and password which you added in the ‘Setting an IP Notification Profile’ section could be wrong.
    • 09:25:08 IPMSG Miniserver_VI1_pulse[16726]Connection at port 44 on host refused!
      This message suggests that the port for the Miniserver entered in the ‘Setting an IP Notification Profile’ section could be wrong.
  • If you get a success message such as 08:56:26 IPMSG Miniserver_VI1_pulse[10821]Notify sent to 179 bytes in 3.008s, but there is still no reaction from the Miniserver (no popup, or signal at the Qb output), then please check the following things:
    • In the configuration software: is the virtual input connected to the trigger input for the door controller function block?
    • Have you entered the correct path and input number in the ‘Setting an IP Notification Profile’ section (step 8)? If you have, then the signal will be sent to the wrong input.


For dropouts of the audio connection, activating the audio codecs PCMA can improve the voice connection.

The to enable PCMA codec go to the the Admin menu of the Mobotix, under the SIP client settings check the “use PCMA Codec” option.

PCMA Codec Mobotix T24/25

In the Loxone Smart Home App you now need to select the codec PCMA.
Open the app and go to the door control and in the settings as PCMA Audio Codec as highest priority.


From versions 6 onwards of Internet Explorer it is no longer possible to have username and password direct in the URL of the camera. This is however necessary for automatic authentication for an updated camera image in the door controller.

Therefore in order to use the door controller block we recommend that you use another browser such as Google Chrome or Mozilla Firefox. Please find the associated information from Microsoft here.


In the most recent versions of Google Chrome, the authentication process has changed, so you may see problems with the video stream being displayed when using the Loxone webinterface.

You can get round these issues by changing the target path in the properties of Google Chrome with a command.


Right click on the Chrome shortcut on your desktop and then click on ‘Properties’.

Google Chrome Properties


Click on the tab called ‘Shortcut’ and change the name of the target so that it includes the command “–allow-cross-origin-auth-prompt” to the end of the path.

So the target path would now be (depends on where you installed Chrome):

C:\Program Files\Google\Chrome\Application\chrome.exe” –allow-cross-origin-auth-prompt

Click Apply, approve any administrator prompts and then click OK to save these changes.

Google Chrome Properties Intercom URL