2N Helios IP product line — which model for which project

2N manufactures three main outdoor IP door station families. Choosing correctly saves integration hours — the Verso supports hardware modules including the KNX add-on card, while Base and Force rely on API or SIP-only integration.

The Helios IP Verso accepts up to two hardware add-on modules. Common combinations: KNX module + RFID module, or KNX module + fingerprint module.

SIP configuration — local server vs direct SIP

2N Helios IP stations act as SIP clients. For audio/video calls to indoor stations or smartphones, you need either a local SIP PBX or direct SIP peering between the door station and indoor panels.

# 2N Helios IP → Services → Phone → SIP
SIP Proxy:       192.168.1.50        (Asterisk server IP)
SIP Port:        5060
Registration:    Enabled
Username:        1001                (door station extension)
Password:        [your SIP password]
Authentication:  1001
Display name:    Front Door

# Video codec order (for Gira X1 / indoor panels)
Codec priority: H.264 > G.711 > G.722

# DTMF relay (for door opening via keypad)
DTMF mode:      RFC 2833
Open door code: #  (or configure digit sequence)

For multi-tenant apartment buildings, each apartment has its own SIP extension. The 2N button module has programmable button-to-extension mapping — button 1 rings apartment 101 (extension 1101), button 2 rings 102, and so on. This mapping is configured in the 2N web interface under Directory.

2N KNX module (9137331) — native KNX integration

The 2N KNX module is an optional hardware add-on card that fits inside the Helios IP Verso and Access Unit 2.0 chassis. It connects the 2N station directly to the KNX TP bus — no gateway server required.

The KNX module exposes the following communication objects in ETS:

Alternative: 2N REST API + Home Assistant KNX bridge

If you are using a Helios IP Base, Force, or Solo (which have no hardware module slot), or want to avoid the extra cost of the KNX module, you can bridge 2N to KNX via Home Assistant. This path also unlocks more complex automation logic than the native KNX module allows.

# configuration.yaml — REST sensor polling 2N relay state
sensor:
  - platform: rest
    name: 2N Front Door Bell
    resource: http://192.168.1.80/api/switch/status
    username: admin
    password: !secret twoN_password
    value_template: "{{ value_json.result[0].active }}"
    scan_interval: 2

# automations.yaml — doorbell → KNX group address
automation:
  - alias: "2N Doorbell → KNX scene"
    trigger:
      platform: state
      entity_id: sensor.2n_front_door_bell
      to: "true"
    action:
      - service: knx.send
        data:
          address: "5/1/1"    # doorbell notification GA
          payload: [1]
          type: "binary"

  - alias: "KNX relay trigger → 2N door open"
    trigger:
      platform: state
      entity_id: binary_sensor.knx_door_open_command
      to: "on"
    action:
      - service: rest_command.2n_open_relay
        data:
          relay: 1

rest_command:
  2n_open_relay:
    url: "http://192.168.1.80/api/switch/ctrl?switch=1&action=trigger"
    method: GET
    username: admin
    password: !secret twoN_password

The REST API approach requires enabling HTTP API access in 2N web interface under Services → HTTP API. The 2N also supports webhooks — it can POST to a Home Assistant webhook URL on events like doorbell press, card authentication, or motion detection, removing the need for polling.

Door relay wiring — electric strikes and magnetic locks

The 2N Helios IP has a built-in door relay (NO/NC, max 2A / 30V DC). For most residential and light commercial doors this relay can drive the electric lock directly. For heavy-duty applications, use the relay to trigger a dedicated door power supply with relay output.

Face recognition — on-device and Axis Camera Station

2N Helios IP Verso and Force models with the camera module (2MP wide-angle, optional IR illumination) support face recognition as an access method — alongside RFID and keycode.

For GDPR compliance in EU installations, face recognition data must be stored only on systems within the facility. On-device FR (2N license) stores templates locally in encrypted form. Axis Camera Station with local server also meets this requirement. Cloud-based FR services are generally not permissible under GDPR Article 9 without explicit user consent in most EU jurisdictions.

OSDP — Open Supervised Device Protocol

Select 2N models (Helios IP Verso, Access Unit 2.0) support OSDP v2 on the RS-485 port. OSDP is a serial access control protocol that allows the 2N to act as a reader connected to a third-party access control panel (Lenel, Genetec, AEOS, Paxton Net2).

Use case examples