Mobotix
Decentralised IP cameras with relay output for KNX alarm and DALI integration
Mobotix (Langmeil, Rhineland-Palatinate, Germany — founded 1999, owned by Konica Minolta since 2016) makes edge-processing IP cameras where motion detection, object classification, and recording all happen inside the camera on a dedicated ARM processor, eliminating NVR dependency for core functions. This decentralised architecture means Mobotix cameras continue recording and sending alarms even if the network switch or NVR goes offline — a critical advantage for KNX security integration where reliability is essential. The built-in relay output on Mobotix cameras provides a direct hardware path to KNX binary inputs without software dependencies.
Role in our panels
How we use Mobotix
Mobotix M73 (4K outdoor hemispheric) and S74 (4K indoor/outdoor body camera with replaceable lens) include a built-in relay signal output (dry contact, NO/NC, rated 1A/30V DC) that closes on camera-detected events: motion, person, vehicle, or custom video analytics trigger. Wire this relay output to one channel of an MDT SCN-8V.01 KNX binary input module (8-channel, 24V DC). ETS6 assigns the channel a KNX group address (GA 5/1/x, DPT 1.005, camera motion alarm zone x). KNX logic reacts: GA = 1 triggers DALI outdoor floodlight scene 8 (full brightness), sends alarm notification via ARISTO BewO or Home Assistant, and activates KNX alarm horn relay output. For more granular event-based integration beyond the relay output, Mobotix MxManagementCenter (MxMC) VMS supports HTTP action profiles — when any configured camera event occurs (motion, loitering, camera tamper, object left behind), MxMC sends an HTTP POST request to a configurable URL. A Home Assistant webhook receives this POST, and the HA KNX integration sends a KNX group write telegram to the alarm group address. This software path enables richer event categories (specific analytics events rather than just generic motion) but introduces a dependency on the VMS and HA server availability. The Mobotix MxBell video doorbell and T26 door station include SIP calling capability — when a visitor presses the call button, an SIP call is placed to the resident's SIP client (phone, tablet, 2N Indoor View). For KNX integration of door station events (call pressed, RFID card accepted, door opened), the T26 relay output path provides a direct hardware-to-KNX connection. The SIP call event can also be bridged to KNX via a 2N/Akuvox SIP gateway that has a native KNX module — in mixed Mobotix camera + 2N intercom deployments, using 2N for the door station and Mobotix for perimeter cameras is a common and complementary architecture. Mobotix offers a dual optical+thermal camera option (M73 with thermal sensor, or dedicated Mx-M16 Thermal) for 24-hour perimeter intrusion detection. The thermal sensor detects body heat independent of lighting conditions and camera orientation towards light sources — unaffected by car headlights, sun glare, or total darkness. Combined with the M73 optical channel for visual verification, the thermal+optical combination reduces false alarms to near zero and is the recommended configuration for high-security perimeter KNX alarm integration where false alarm response (triggering DALI floodlights and alarm notifications) must be minimised.
Mobotix cameras have a built-in signal output (relay contact) that closes on motion detection alarm. Wire relay output to MDT SCN-8V.01 24V binary input. ETS6: GA 5/1/x (DPT 1.005) = camera motion alarm. KNX reaction: DALI outdoor zone full brightness (scene 8), send alarm GA to ARISTO BewO for email/SMS notification. For bidirectional integration with Mobotix analytics events: use MxManagementCenter HTTP action → Home Assistant webhook → KNX group write via HA KNX integration.
Used in these project types
Mobotix products
Key components we install
M73 IP Camera
4K outdoor hemispheric IP camera with 360° or 180° lens options. On-board ARM processor for edge motion detection, person detection, and vehicle detection. Built-in relay signal output (NO/NC, 1A/30V DC) for direct KNX binary input connection. MicroSD recording slot. IP66, IK10 vandal protection. PoE+ (802.3at, 15.4W). Optional thermal sensor module.
S74
4K indoor/outdoor body camera with interchangeable sensor unit (wide-angle, telephoto, fisheye). Modular design: sensor unit separates from processing unit for flexible mounting. Edge analytics and relay output identical to M73. Suited for indoor corridors, lobby areas, and covered outdoor zones where full dome housing is not required.
T26 Door Station
Modular IP door camera with relay output for door release (12V DC electric strike or 24V door controller). SIP calling to any SIP client. RFID module option. Relay output wired to MDT SCN-8V.01 for KNX doorbell-press telegram. Alternative to 2N for installations where Mobotix camera ecosystem consistency is preferred.
MxBell
Compact SIP video doorbell with HD camera, speaker, and microphone. Flush or surface mount. SIP integration with 2N/Akuvox KNX gateway for door call → KNX scene trigger. Can also use relay output wired to MDT SCN-8V.01 for simple doorbell-press KNX binary alarm. Suitable for residential and small commercial installations.
MxMC VMS
Mobotix MxManagementCenter on-premise video management software for multi-camera Mobotix installations. HTTP action profiles send event notifications (motion, analytics, camera tamper) to Home Assistant webhooks → KNX group write. Supports ONVIF for mixed-camera installations. For Mobotix-only installations, MxMC provides full recording, live view, and event management without third-party NVR.
Mobotix FAQ
How does Mobotix camera relay output connect to KNX?
Mobotix M73, S74, and T26 have a signal output port (2-pin connector, NO relay contact, rated 1A/30V DC). Wire this output to one channel input of an MDT SCN-8V.01 KNX binary input module (8-channel, 24V DC input). In ETS6, configure the MDT channel as binary input, group address DPT 1.005 (alarm), debounce time 200ms. When Mobotix detects motion (or any configured analytics event) and closes the relay, MDT sends KNX telegram value 1 to the alarm group address. Ensure the Mobotix relay is set to latching mode (not momentary pulse) in MxMC event configuration for reliable KNX polling.
What is the difference between Mobotix relay output and MxMC HTTP action for KNX integration?
Relay output is hardware-level — always reliable, independent of VMS, network software, and Home Assistant availability. Relay output provides a single binary signal (motion on/off) per camera. MxMC HTTP action is software-level — requires MxMC server running, network connectivity, and Home Assistant webhook; but provides rich event categories (person vs vehicle vs loitering vs tamper vs specific analytics zones). For critical KNX alarm integration (perimeter security relay to alarm horn), use the hardware relay path. For smart automation (person detected at entrance → unlock KNX access zone + notify via KNX BewO), use MxMC HTTP → HA webhook → KNX group write.
How does Mobotix thermal camera improve KNX security automation?
Mobotix M73 with the MX-O-M5T-ThermalRadiation thermal sensor unit adds a 336×252 pixel LWIR (long-wave infrared) thermal image alongside the main 4K optical sensor. KNX integration: the thermal sensor triggers the same relay output as optical motion detection, but thermal detection is immune to darkness, camera glare from car headlights, and foliage motion. For KNX perimeter alarm automation where false alarms cause DALI outdoor lighting to activate and alarm notifications to send, thermal detection dramatically reduces unwanted triggers. The dual thermal+optical approach is: thermal triggers relay (KNX alarm) + MxMC saves optical video clip for verification — human review confirms the alarm without attending site.
Need a panel with Mobotix components?
We select, procure, assemble and certify. Free initial consultation.
Request consultation →