Read an AnB Rimex TRICOM alarm panel from KNX

The ANB-KNX transmits the status of up to 96 TRICOM program steps to the KNX bus over the panel's RS485 port. Each step — a detector, an area state or a custom output — becomes a 1-bit KNX group object in ETS. Data flows one way, from the alarm panel to KNX: this gateway monitors, it does not control.

What it does

Monitor 96 program steps on the bus. Map any detector, area status or output to a TRICOM program step; the gateway publishes it as a KNX object the moment it changes.

Turn alarm detectors into KNX presence sensors. A TRICOM PIR switches a KNX object — enough to light a corridor, start a staircase timer or wake a HyperVisu screen.

Report a broken link. A communication-fault object goes high if the RS485 connection to the panel is interrupted.

Scale to 192 steps. A second ANB-KNX with the zone offset set covers program steps 97–192.

What it spares you

No second set of presence detectors: the alarm PIRs light the rooms.
No termination resistor to add: it is built into the gateway.
No extra power supply: 12 VDC from the panel's auxiliary output.
No separate enclosure: screw it inside the TRICOM panel, or use the optional DIN-2TE on the rail.

Scenarios

A TRICOM PIR in the entrance hall trips at night; an Elausys SAE-810 lights the hall at 30 % for two minutes.
The TRICOM "armed" state, mapped to a program step, sets the heating to eco mode on the KNX thermostats.
A fire detector zone on the panel lights the escape route and opens the blinds through KNX.
Every program step visible on a HyperVisu dashboard for the building manager.

Technical proof

Alarm side: AnB Rimex TRICOM panels, onboard RS485 port (A/B screw terminals)
Direction: alarm → KNX only. Arm / disarm, PG outputs, virtual inputs and scene recall are present in the ETS application for consistency with the other Elausys alarm gateways but marked NOT USED on this model
Zones: up to 96 program steps; 97–192 on a second gateway via zone offset. Program step 0 is not transferred
Communication fault monitoring on the RS485 link
Power: 12 VDC external; KNX bus < 6 mA @ 29 VDC; galvanic isolation between panel and bus
Housing: 89 × 29 × 20 mm, one screw hole; optional DIN-2TE enclosure for 35 mm DIN rail; +5 to +45 °C
KNX connection: pluggable micro terminal
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 TRICOM panel keeps its own keypads, sirens and monitoring; KNX is added alongside the security system, never in place of it.

FAQ

Can I arm or disarm the TRICOM from KNX? No. The ANB-KNX is monitoring-only. For bidirectional control, see the JA-KNX (Jablotron), EVO-KNX (Paradox), NXG-KNX (Interlogix) or AJAX-KNX.

What exactly is a "zone" here? A TRICOM program step. You decide on the panel what each step reports — a detector, an area state, an output — and the gateway forwards it to KNX.

Why doesn't program step 0 appear on KNX? Step 0 is reserved on the TRICOM side and is not transferred. Start at step 1.

Do I need to add a termination resistor? No, it is built into the gateway.

AnB Rimex TRICOM KNX Interface