2N
Helios IP video intercoms with native KNX module for door release and scenes
2N (Prague, Czech Republic — founded 1991, Axis Communications subsidiary since 2016) produces IP video intercoms used across Europe as the standard for door communication in smart buildings. The Helios IP product family — Verso, Force, and Helios panel intercoms — offers a unique native KNX module (article 916010) that connects the door station directly to the KNX TP bus without any IP gateway, Modbus adapter, or middleware. This makes 2N Helios the cleanest and most reliable intercom-to-KNX integration available, with full ETS6 application support for commissioning by any KNX-certified installer.
Role in our panels
How we use 2N
The 2N 916010 KNX module is a hardware add-on that installs inside the 2N Helios IP Verso backbox — a plug-in board connecting to the Helios mainboard via a ribbon cable. The KNX TP bus (2-wire, 29V DC SELV) connects to the KNX terminals on the 916010 board. Once installed and powered, the 2N Helios appears on the KNX bus as a standard ETS6 device. Download the 2N ETS6 application database (.knxprod file) from 2n.com/download → ETS Applications. Import into ETS6, drag onto the KNX bus, and configure group object assignments. KNX group address scheme for a 2N Helios installation: the ETS6 application exposes three primary group objects: (1) Door Call (DPT 1.001, send-on-press) — when a visitor presses the door call button, the Helios sends a KNX telegram with value 1 to the assigned GA. KNX logic reacts: HA notification, KNX room controller display update, DALI entrance lighting on. (2) Door Release (DPT 1.001, receive) — when KNX sends telegram value 1 to the Door Release GA, the Helios closes its relay output for the configured door-open pulse duration (0.5–10 seconds, configurable in ETS6), opening the electric door strike. (3) Open/Closed status (DPT 1.001, read-back) — reports current door lock state for KNX visualisation dashboards. All three objects are bidirectional — the 916010 module handles all KNX telegram encoding/decoding on-bus. For multi-apartment buildings, 2N Helios IP with the 99-button video module supports up to 99 apartment call buttons per panel (expandable with additional button modules for larger blocks). Each button can be assigned a unique KNX group address for call telegram — when apartment 42 calls, the Helios sends a telegram to GA 6/0/42 (DPT 5.010, apartment number, or DPT 1.001 per apartment). KNX apartment controller (e.g. HDL Buspro or LOYTEC room controller per apartment) receives the call telegram and activates the apartment's indoor call chime (KNX group write to apartment chime GA) and doorbell display. This eliminates a separate SIP PBX for multi-apartment call routing — pure KNX native. For commercial buildings where BACnet/IP is the primary building protocol (BMS, HVAC, access control), 2N Helios supports both BACnet/IP and native KNX simultaneously. The KNX module handles door call and release for KNX-integrated floors, while the Helios BACnet interface reports door open/close status, call events, and RFID card access logs to the BACnet BMS. This dual-protocol capability makes 2N Helios suitable for buildings with mixed KNX (floors, meeting rooms) and BACnet (plant room, HVAC) infrastructure.
2N Helios IP installs the 2N 916010 KNX interface module — a hardware add-on to the Helios door station. ETS6 application (download from 2n.com) provides group objects: Door Call (DPT 1.001, send telegram on call press), Door Release (DPT 1.001, receive telegram → open door relay), Open/Closed status (DPT 1.001). The KNX module connects to KNX TP bus terminals in the Helios backbox. The integration is fully bi-directional, ETS6 native — no IP gateway or middleware required.
Used in these project types
2N products
Key components we install
Helios IP Verso
Modular flush-mounted IP video door station — the premium 2N choice for villas and commercial buildings. Accepts KNX module 916010, RFID reader module, keypad, display module, and up to 99-button name-plate module. 5MP camera, 120° view. IP65/IK07. ETS6 application for direct KNX TP integration without gateway.
Indoor Compact
2N 7-inch indoor touchscreen for SIP video intercom answering and door release. SIP client — registers to any SIP PBX or directly to Helios. Does not have native KNX module; pairs with KNX-integrated Helios Verso at the door. Used in apartments, hotel rooms, and office receptions for video door answering.
IP Base
Entry-level 2N IP video door station for cost-sensitive installations. 2MP camera, SIP, one relay output, one tamper input. Does not support KNX module (916010 only compatible with Helios IP Verso). KNX integration via relay output → MDT SCN-8V.01 binary input (doorbell press) + KNX relay actuator → IP Base relay input (door release). Hardware-path integration only.
KNX Module 916010
Native KNX TP hardware module for 2N Helios IP Verso. Plug-in board inside Helios backbox. KNX TP bus (29V DC) connects to module terminals. ETS6 .knxprod application from 2n.com. Group objects: Door Call, Door Release, Door Status. The only hardware needed for clean, reliable ETS6-native 2N KNX integration — no gateway required.
Access Unit 2.0
2N standalone RFID/fingerprint access reader with Wiegand output for integration with third-party access control systems. IP65, IK08. MIFARE DESFire EV2/EV3, 125kHz EM, fingerprint (optional). Used alongside Helios intercom for gated entrances and car park barriers where Wiegand access control panel drives the barrier while Helios handles video intercom on the KNX bus.
2N FAQ
How does the 2N 916010 KNX module install and configure in ETS6?
Installation: order 916010 separately (not included with Helios Verso). Open Helios backbox → insert 916010 board onto mainboard ribbon connector → connect KNX TP bus 2-wire to the KNX+/KNX- terminals on the 916010 board. The Helios draws KNX bus power from the TP bus (no separate 24V supply needed for the module). ETS6 configuration: download 2N ETS6 application database (.knxprod) from 2n.com/download → ETS Applications. In ETS6, open Catalogs → Import .knxprod → drag 2N device onto your KNX bus topology → set individual address → assign group addresses to Door Call, Door Release, and Door Status group objects. Total setup time: 30–60 minutes for a single Helios installation.
Can 2N Helios work without SIP in a pure KNX installation?
For door call and release, yes — the 916010 KNX module operates fully independently of SIP. Door call button press → KNX telegram (Door Call GA). KNX telegram received → door release relay (Door Release GA). No SIP PBX, no network phone required for this basic function. However, the video intercom functionality (answering the call on a screen with live video, two-way audio) requires SIP — either a SIP server (Asterisk, 3CX, FreePBX) or direct SIP registration to 2N Indoor Compact or 2N Indoor View indoor station. For KNX buildings where the primary use case is automated door release (RFID, KNX schedule), pure KNX operation without SIP is viable.
What is the advantage of 2N native KNX module vs using relay output with a KNX binary input?
Three key advantages: (1) Bidirectional ETS6 native — Door Release is sent from KNX to 2N as a KNX telegram (no extra relay wiring from panel to door). Relay-output integration requires a separate relay actuator output wired to the Helios relay input for door release — two separate cable runs vs one KNX TP cable. (2) Richer group objects — Door Status (open/closed feedback), call active status, and future firmware group objects are available without additional hardware. Relay output provides only a single binary alarm (motion or call press). (3) ETS6 commissioning — any KNX-certified installer can configure the 2N in ETS6 alongside all other KNX devices in the project, without needing separate 2N configuration tools for the KNX integration points.
Need a panel with 2N components?
We select, procure, assemble and certify. Free initial consultation.
Request consultation →