Connect a GE Interlogix NetworX alarm panel to KNX

The NX-KNX puts a NetworX (Caddx) alarm system on the KNX bus through the panel's NX-584E RS232 module. Every zone and every area becomes an ordinary KNX group object in ETS: 96 zones, 4 areas, 9 status objects per area and a KNX scene per area status.

What it does

Monitor 96 zones on the bus. Each zone is a 1-bit group object. A PIR that trips in the alarm panel switches a KNX object — the same object any actuator, logic module or visualisation reads.

Arm and disarm from KNX. Full arm, partial arm and disarm for up to 4 areas from a KNX push-button, a HyperVisu screen or a timer. The user code is stored in the ETS parameters.

Report area status in detail. 9 objects per area: disarmed, entry delay, exit delay, armed, partial armed, fire alarm, siren on, panic alarm, intrusion alarm.

Recall a KNX scene on every status change. One scene number (0–64) per area status: armed → night scene, intrusion → all lights on, disarmed → welcome scene.

Report a mains failure. AC failure on the panel reaches KNX as a status object, ready for a notification from your visualisation.

What it spares you

No second set of presence detectors: the alarm PIRs light the corridors.
No PC, software bridge or cloud service between the panel and the bus.
No new ETS application to learn: the same Elausys alarm gateway application as the JA-KNX, EVO-KNX, NXG-KNX and AJAX-KNX.
No extra power supply: 12 VDC from the panel's AUX output, under 6 mA.

Scenarios

Arm the NetworX panel from the KNX push-button at the front door; the scene switches every light off and lowers the blinds.
A NetworX PIR in the hallway trips at night; the Elausys SAE-810 switching extension lights the path for two minutes.
Fire alarm on the panel: HyperVisu shows the alarm, KNX opens the blinds, lights the escape route and stops the ventilation.
Two NX-KNX with zone offset: 192 zones and 8 areas of an office building on one KNX visualisation.
Mains failure in the technical room: the AC-failure object triggers a push notification from HyperVisu.

Technical proof

Alarm side: GE Interlogix NetworX (Caddx) panels fitted with the NX-584E RS232 module; DB9 cable and gender changer supplied
Zones: 16 / 32 / 48 / 64 / 72 / 96 selectable in ETS; zones 97–192 on a second gateway via zone offset
Areas: 4 (areas 5–8 with offset), 9 status objects each, arm / partial arm / disarm from KNX
Scenes: KNX scene 0–64 per area status
Not available on this model: PG outputs and virtual inputs (limit of the NX-584E protocol)
Power: 12 VDC external, < 6 mA; KNX bus < 4 mA @ 29 VDC
Housing: 66 × 44 × 25 mm, 4 screw holes, mounts inside the alarm panel; +5 to +45 °C
Panel settings: enable zone status and partition status messages on the NX-584E; on NX V2 panels remove jumper J7
Configuration: ETS5 / ETS6

Local, standard, independent

Everything the gateway does surfaces as KNX group objects in ETS — nothing is hidden in a proprietary app. It runs without an internet connection, an account or a subscription. The NetworX panel keeps its own keypads, sirens and monitoring; KNX is added alongside the security system, never in place of it.

FAQ

Which NetworX panels are supported? Any GE Interlogix NetworX / Caddx panel fitted with the NX-584E RS232 module.

Can I arm the alarm from a KNX push-button? Yes. Arm, partial arm and disarm commands are sent with the user code stored in ETS.

Can KNX switch a PG output on the panel? No. The NX-584E protocol does not expose PG outputs or virtual inputs. For KNX-to-alarm actions, see the EVO-KNX (Paradox) or JA-KNX (Jablotron).

I have more than 96 zones. Install a second NX-KNX with the zone offset parameter set; it covers zones 97–192 and areas 5–8.

Does it work with HyperVisu? Yes. The zone and area objects are standard KNX objects; HyperVisu reads them like any other.

GE NETWORX KNX Interface - Caddx