Table of Contents

Technical Use Case

In many buildings, intrusion detection systems and KNX building automation operate in parallel without their data being meaningfully connected. As a result, valuable information remains unused while additional sensors are installed at the same time. Lighting and temperature functions are often implemented using separate KNX sensors, even though security systems already provide this information. This leads to redundant hardware, increased installation effort and unused synergies in building operation – both technically and economically. This is where the integration of the NOX intrusion detection system into a KNX/EIB environment comes into play: Security-relevant events and system statuses are made available for building technology functions and specifically integrated into the building automation system. Lighting, temperature, blinds and shutters can therefore be controlled automatically whenever the status of the intrusion detection system changes. The NOX TIO functionality provides the basis for standardised, bidirectional communication between the security system and KNX. Existing sensors can therefore be used for multiple purposes, installation costs can be reduced, and security and energy efficiency can be intelligently combined – while maintaining clear system separation and ensuring future-proof integration into KNX building automation.

Initial Situation

In buildings with KNX building automation and separate intrusion detection systems, lighting and temperature functions are often implemented redundantly using separate sensors, such as motion detectors. The aim is to use security-relevant events from the NOX system for building technology functions.

System Overview

Technical Communication Integration

The IP-based integration connects NOX and KNX via the TIO functionality of the NOX system and an IntesisBox serving as a gateway. Security-relevant events and status messages are transmitted bidirectionally and can be used specifically for functions such as lighting, temperature control or shading. The existing network infrastructure provides the basis for efficiently connecting security and building automation.

1. Protocol:
KNX/EIB
2. Physical Interface:
TCP/IP
3. NOX Connection:
TIO via IP
4. Bidirectional Communication:
Yes – sending and receiving messages
5. Additional Middleware:
IntesisBox

Application Scenarios

Lighting Control via NOX Motion Detectors

Scenario 1

Scenario:

  • A motion detector connected to NOX detects movement
  • NOX generates a message
  • The message is transmitted to the KNX system
  • KNX switches the defined lighting circuits

Technical Advantage:

No separate KNX motion detectors required -> lower hardware and installation costs.

Temperature Control upon Activation

Scenario 2

Scenario:

  • The intrusion detection system is armed
  • KNX receives a status message
  • KNX adjusts the defined temperature setpoints for the entire building or selected zones

 

Technical Advantage:

Automated energy optimisation based on the system status.

Blind Control via NOX Status

Scenario 3

Scenario:

  • The intrusion detection system is armed or disarmed
  • NOX sends a status message to KNX
  • The KNX system raises or lowers the blinds or shutters for the entire building or selected areas

Technical Advantage:

The armed/disarmed status is used as an automatic control signal for blinds and shutters.

Technical Advantages

  • Use of existing sensor technology across multiple systems

  • Reduction of redundant field devices
  • Clear system separation with simultaneous integration

  • Standardised KNX communication
  • Scalable for additional KNX functions
  • Energy savings through reduced energy losses

Economic Benefits and ROI

By using existing security and access data, energy consumption, space utilisation and operating processes can be controlled intelligently without installing additional sensors. Based on an example office building with approximately 5,000 m² of usable floor space, occupancy-based control can generate savings in the following areas:

ⓘ As existing security and access data is used, additional sensors are often not required. As a result, the integration frequently pays for itself within 6 to 24 months.

Added Value for Planning, Implementation and Operation

NOX not only connects security technology and building automation on a technical level but also makes existing security data usable for more economical building operation.

While conventional integrations primarily enable data exchange between systems, NOX actively uses status and event data to control building technology functions. This creates additional value for everyone involved in the project, from planning and implementation through to the subsequent operation of the building.

Typical Areas of Application

  • Office buildings
  • Public buildings
  • Commercial properties
  • Energy-efficient buildings
  • Warehouses
  • Rarely used buildings or areas

Discover NOX Solutions for Your Building Integration

Learn how NOX security solutions and KNX building automation can be intelligently connected in your projects.

Share this page

Related Articles

  • Enhancing Security in a Historic School

Topics