Introduction
What happens in your KNX installation when the alarm goes off? If the answer is "the siren rings" — your building isn't as smart as it could be. The new AJAX-KNX Gateway by Elausys bridges the gap between one of the fastest-growing alarm platforms in Europe and the KNX ecosystem, giving integrators full bidirectional control between AJAX security and KNX building automation.
What Is a KNX Alarm Gateway — and Why Does It Matter?
A KNX alarm gateway is a hardware interface that connects a professional alarm system to the KNX bus, enabling real-time, bidirectional communication between security events and building automation functions.
In practical terms, this means your KNX installation can react to alarm events — and your alarm system can be controlled from any KNX visualisation, touch panel, or push-button.

Why does this matter for integrators?
Without a gateway, alarm systems and KNX operate as two separate islands. The alarm detects an intrusion, but the building doesn't respond. The client arms the system at night, but the lighting and blinds don't adjust. A KNX alarm gateway eliminates this disconnect. It turns passive alarm events into active building automation triggers — and it allows clients to manage everything from a single interface.
Key terms to understand:
- Bidirectional communication — the gateway both reads status from the alarm system and sends commands back to it
- Zone status — the state of individual alarm sensors (motion detectors, door/window contacts, etc.) mapped to KNX group objects
- Area control — the ability to arm and disarm alarm partitions and control global Night Mode directly from KNX
- Scene recall — automatic activation of predefined KNX scenes when alarm states change (e.g., arming triggers a "night" scene)
- SIA protocol — the standard alarm communication protocol used by AJAX to transmit events to monitoring stations and third-party devices
AJAX Meets KNX: What the AJAX-KNX Gateway Brings to Your Projects
Why AJAX?
AJAX Systems has rapidly become one of the most popular professional alarm platforms in Europe and beyond. Known for its wireless reliability, sleek design, and user-friendly app, AJAX is increasingly specified in residential and commercial projects where KNX is already the building automation backbone.
Until now, integrators working with both AJAX and KNX had no native way to connect the two. Security operated in its own silo — separate app, separate logic, no interaction with the rest of the building.

What the AJAX-KNX Gateway delivers
The Elausys AJAX-KNX Gateway provides a full integration layer between AJAX Hub systems and the KNX bus:
- Up to 96 zone statuses mapped to individual KNX group objects — monitor every AJAX sensor (MotionProtect, DoorProtect, GlassProtect, etc.) directly on the KNX bus when the system is armed, in Night Mode or when zones are set to Always Active.
- Up to 4 area controls — arm and disarm AJAX partitions from any KNX visualisation, touch panel, or wall switch, and activate or deactivate global Night Mode
- 7 area status feedbacks on KNX — disarmed, armed, partial armed (night mode), exit delay, fire alarm, panic alarm, intrusion alarm
- Automatic KNX scene recall — assign a KNX scene (1–64; 0 disables recall) to each area status, triggered automatically when the status changes
- Power supply monitoring — AC failure and battery failure status available as KNX group objects
- Camera events and relay control — use up to 32 shared PG channels to map AJAX camera events such as person, pet and vehicle detection to KNX, or control AJAX relays and sockets with status feedback. Cloud connection required.
- Panic and photo requests — up to 16 virtual inputs trigger an AJAX panic alarm or request a photo from a compatible AJAX detector, directly from KNX. Cloud connection required.
- Cloud or encrypted local SIA — full cloud integration provides events and commands while leaving the hub’s SIA connection available for an external monitoring company. Local SIA provides status monitoring without internet access.
Same ETS workflow, new alarm brand
If you've already deployed other Elausys alarm gateways (Jablotron, Paradox, Interlogix, GE Caddx, or AnB Rimex), the AJAX-KNX Gateway follows the exact same unified ETS application concept. The parameter structure, group objects, and commissioning workflow are consistent across all models. Learn once, deploy everywhere — regardless of the alarm brand on site.
Practical Implementation: How to Set Up the AJAX-KNX Gateway
Step-by-step integration process
Step 1 — Hardware installation
Mount the AJAX-KNX Gateway on a DIN rail. Connect the KNX bus on the top side and the external 12–30VDC power supply on the bottom, alongside the RJ45 Ethernet cable. The gateway receives AJAX events through the cloud or over the local network using SIA. Cloud events, arming/disarming and the new device functions require internet access.
Step 2 — Choose cloud or local SIA
Use the cloud connection for all gateway features; no SIA configuration is needed on the hub. Alternatively, for local status monitoring without internet, configure the AJAX Hub to send SIA DC-09 events to the gateway’s IP address on port 2410. Enable SIA encryption using the key shown on the gateway’s Ajax configuration page. Local SIA does not provide arming/disarming, camera events, relay/socket control or virtual inputs.
Step 3 — Invite Elausys as Security Company (for cloud connection)
For cloud connectivity, invite Elausys as a Security Company in the AJAX app using info@elausys.be. This grants the gateway access to receive events and send commands to the AJAX Hub.
Open https://192.168.1.51, set a web password and a fixed IP address, then enter the 8-character Hub ID on the gateway’s Ajax configuration page. Match Partition mode to the hub’s Group mode. On the Device mapping page, assign the PG channels and virtual inputs you want to use.
The new web interface uses password protection and HTTPS, with optional automatic security updates.
Note: The invitation is not required for local SIA monitoring. For that mode, switch Cloud connection off in the gateway settings.
Step 4 — ETS configuration
Import the AJAX-KNX Gateway into your ETS project using the NXG-KNX Interface application. Configure the parameters:
- Set the number of zones (up to 96)
- Set the number of areas (up to 4) and area mapping to match the AJAX groups
- Assign KNX scene numbers (1–64; 0 disables recall) to each area status (armed, disarmed, fire, intrusion, etc.)
- Link zone and area group objects to your KNX visualisation, lighting, blinds, or HVAC groups
- For the channels assigned on the Device mapping page, enable PG Control, PG Status and Virtual inputs in ETS, and link the corresponding group objects.
Step 5 — Verify and commission
Check the front panel LEDs: Network confirms Ethernet connectivity, Connected confirms active communication with the AJAX Hub. Test zone triggers and area commands from your KNX visualisation to verify bidirectional operation. Check the connection status on the gateway’s Ajax configuration page, and test any assigned relay/socket controls, camera events, panic inputs and photo requests. In local SIA mode, verify status feedback only.
Understand zone reporting behaviour
By default, AJAX motion detectors (MotionProtect) and door/window contacts (DoorProtect) only report zone status to the gateway when the system is armed or in night mode. This means that in disarmed state, motion and door events are not transmitted to KNX.
If you want zone status available on KNX at all times — for example, motion-triggered lighting during the day or door-triggered welcome scenes — you can configure individual devices as Always Active (24hrs) in the AJAX app.
Important: setting a device to Always Active means it will also trigger the alarm even when the system is not armed. This is by design in the AJAX platform. Use this setting selectively and only on zones where permanent reporting is needed.
Real-world use cases
- Night mode activation: The client arms the system before leaving or going to bed → the gateway sends the armed status to KNX → a "Night" scene is recalled automatically: all lights switch off, blinds close, heating shifts to setback mode, and presence simulation activates on selected rooms. The entire building shifts into security mode from a single action on the AJAX app or KNX panel.
- Intrusion response: An intrusion is detected on Area 1 → the gateway sends the intrusion alarm status to KNX → a predefined emergency scene activates automatically: escape route lighting turns on, exterior lights illuminate the perimeter, and blinds open to provide visibility. The building doesn't just sound a siren — it actively responds to protect people and property.
- Fire alarm coordination: A fire alarm triggers on Area 2 → the gateway sends the fire alarm status to KNX → the assigned scene recalls immediately: all blinds open to clear escape routes, emergency lighting activates across the affected zone, and ventilation shuts down to prevent smoke spread. One alarm event orchestrates the entire building response — no manual intervention needed.
- Camera-triggered lighting: An AJAX camera reports a person → the mapped PG status is sent to KNX → the configured lighting logic switches on the entrance lights.
Common mistakes to avoid
- Not understanding zone reporting behaviour — AJAX sensors only report zone status to KNX when the system is armed (or in night mode). Setting devices to Always Active enables daytime reporting, but also means those zones will trigger the alarm when the system is disarmed. Plan which zones genuinely need 24/7 KNX reporting and which can rely on armed-state reporting only.
- Not inviting Elausys as Security Company — cloud events and commands, including camera events, relay/socket control and virtual inputs, require this step and internet access.
- Skipping the scene assignment — the gateway supports automatic scene recall, but scenes default to 0 (disabled). You have to configure them manually in ETS for every area status you want to automate
- Using the gateway for 97+ zones — a single gateway covers zones 1–96 maximum.
- Expecting group disarm to exit Night Mode — with groups enabled, Night Mode is independent of group arming. Send Partial Arm OFF to disable it.
Conclusion & Next Steps
The AJAX-KNX Gateway opens the door to fully integrated security and building automation for every project using AJAX alarm systems. By bridging alarm event monitoring, area control, and sensor-driven automation into your KNX installation, integrators can deliver smarter buildings — and offer their clients a single, unified control experience for security, lighting, blinds, and HVAC.
Ready to integrate AJAX into your KNX projects?
→ Browse the full Elausys KNX Alarm Gateway range — compare all supported alarm brands
→ Download the AJAX-KNX Gateway datasheet and ETS database — everything you need to start your first project
→ Contact Elausys support — get help with configuration, commissioning, or multi-gateway setups
Topics : AJAX KNX gateway, AJAX alarm KNX integration, KNX alarm gateway, AJAX smart building, KNX security integration, alarm system building automation, KNX zone monitoring, bidirectional alarm communication, ETS alarm configuration, SIA protocol KNX, alarm scene recall, smart building security, KNX group objects alarm, intrusion detection KNX
Frequently Asked Questions
What AJAX systems are compatible with the AJAX-KNX Gateway?
The AJAX-KNX Gateway is compatible with AJAX Hub, Hub Plus, and Hub 2 models. The connection can use the AJAX cloud or local SIA.
Can I arm and disarm the AJAX system from a KNX touch panel?
Yes. With internet access and the cloud connection, once you invite Elausys as a Security Company in the AJAX app, the gateway supports full bidirectional area control: arm, global Night Mode, and disarm commands can be sent from any KNX visualisation, touch panel, or push-button.
Can I use AJAX motion detectors to control KNX lighting?
Yes, but with an important limitation. By default, AJAX motion detectors only report zone status when the system is armed or in night mode — so motion-triggered KNX lighting works automatically in those states. If you need motion detection on KNX while the system is disarmed (e.g., daytime corridor lighting), you can set individual MotionProtect devices to Always Active (24hrs) in the AJAX app. Be aware that Always Active zones will also trigger the alarm when the system is not armed, so use this setting selectively and only where appropriate.
How many zones and areas does the gateway support?
The gateway supports up to 96 zones with individual KNX group objects and up to 4 areas with arm/disarm control plus global Night Mode and 7 status feedback objects per area.
Is the ETS configuration the same as other Elausys alarm gateways?
Yes. The AJAX-KNX Gateway uses the same ETS application concept as all other Elausys alarm gateways (using the NXG-KNX Interface application). If you've configured one, you already know how to configure all of them.
What happens if the Ethernet connection between the gateway and the AJAX Hub drops?
The front panel Connected LED will turn off, indicating communication loss. The gateway's module status group object will send an error code to KNX, allowing your visualisation to display a connectivity fault. Zone statuses will hold their last known state until communication is restored.
Does the gateway require cloud connectivity?
The gateway can receive events through the AJAX cloud or through local SIA without internet. Cloud connectivity is required for arming/disarming, camera events, relay/socket control, panic commands and photo requests. Full cloud mode requires internet for both events and commands.
Can I trigger KNX scenes automatically when the alarm state changes?
Yes. Each of the 7 area statuses (disarmed, armed, partial armed (night mode), exit delay, fire alarm, panic alarm, intrusion alarm) can be assigned a KNX scene number (1–64; 0 disables recall). When the status activates, the corresponding scene is automatically recalled on the KNX bus.
How is the gateway physically installed?
The AJAX-KNX Gateway is DIN rail mounted, requires an external 12–30VDC power supply, and connects to the KNX bus via the standard KNX connector. The Ethernet connection to the network uses a standard RJ45 cable. Galvanic isolation from the KNX bus is provided.
Can I use the AJAX-KNX Gateway alongside a security company that already receives SIA events?
Yes. With the gateway in full cloud mode, the AJAX Hub’s SIA connection remains available for your existing security company or monitoring station. The gateway receives events and sends commands through the cloud, so there is no need to redirect the monitoring company’s SIA feed. If the gateway uses local SIA instead, the hub’s SIA destination is used by the gateway.

