2N Helios IP Verso KNX Integration via the 916010 Module
The 2N 916010 module bolts inside the Helios IP Verso backbox and puts door call, code entry and release events onto the KNX TP1 bus as group objects. This guide covers backbox mounting, ETS6 group address setup, the door release relay logic, and where SIP call forwarding to KNX room panels needs its own configuration.
Where does the 916010 module physically fit in the Verso backbox?
The 2N 916010 module mounts inside the Helios IP Verso backbox as a stacked module, in the same physical format as a call-button or keypad module. It does not need a deeper or wider enclosure than a standard Verso frame already provides.
It sits between the intercom's internal module interconnect — the bus that links the camera, keypad and display modules together — and a separate screw terminal for the building's KNX TP1 line. The two buses stay electrically independent: KNX data never touches the intercom's internal module bus.
The most common ordering mistake is specifying a single-module Verso frame with no free slot left for the 916010 — check the frame's module count against camera, keypad, card-reader and speaker modules before the panel ships.
How do you wire the KNX bus terminal without starving the line?
Connect the module's KNX terminal to the building's TP1 line with standard bus cable, such as J-Y(St)Y 2×2×0.8, respecting the red/plus and black/minus polarity of the bus pair.
The module draws only its own logic current from the KNX bus — it does not power the door station. The Verso itself is powered separately, typically PoE 802.3at (for the heated outdoor variants) or a local 12-24 V DC supply; sizing the KNX power supply for the intercom's electronics is a wiring error to avoid.
Bus loading: the 916010 module adds its own current draw to the KNX line's budget like any other device. On a line already close to a 640 mA supply's limit, adding the module next to other door-side devices — motion sensors, additional push-buttons — can push the line over budget and cause random bus errors under load.
Add the module's current draw to your line's total before commissioning, and move it to a separate line through a line coupler if the existing line has little headroom left.
How do you commission the module in ETS6?
Download the 916010's ETS product database (.knxprod) from 2N's product support page for the exact firmware version installed on the module, then import it into ETS5 or ETS6 and drag the device into your project's building structure.
2N does not publish fixed group addresses for the module — every communication object gets the group address you assign, following whatever GA structure (free, two-level or three-level) the rest of the project already uses.
- Firmware version read from the module's info screen or ETS diagnostics
- Matching .knxprod database downloaded for that firmware
- Project GA structure already decided (free / 2-level / 3-level)
- KNX bus physically connected and the line terminated
A .knxprod database built for an older firmware can hide communication objects that a later firmware version added, or expose objects that no longer exist. If an object you expect is missing after import, check the module's firmware against the database version before assuming the wiring is at fault.
What does the 916010 put on the KNX bus?
The table below groups the communication objects the module typically exposes once imported into ETS. Treat the categories as stable; read the exact object numbers and any manufacturer-specific extensions from the imported device itself, since these can shift between firmware releases.
| Object group | Direction | Typical DPT | Purpose |
|---|---|---|---|
| Door call ringing | Verso → KNX | 1-bit, DPT 1.001 Switch | Drive a KNX display or LED indicator for an active call |
| Call answered / active | Verso → KNX | 1-bit, DPT 1.001 Switch | Duck background audio or pause a scene while the call runs |
| Door release request | KNX → Verso | 1-bit, DPT 1.010 Start/Stop | Trigger the door strike relay from a KNX push-button or panel |
| Access code entered | Verso → KNX | 1-byte, e.g. DPT 5.010 | Log which keypad code opened the door |
| Motion / tamper | Verso → KNX | 1-bit, DPT 1.005 Alarm | Trip an alarm scene or notification |
Object numbering is firmware-specific; the categories above are what installers consistently find, not a substitute for reading the imported .knxprod device.
How do you trigger the door strike relay from a KNX panel?
Link a KNX push-button or room panel's output group address to the module's door-release object, and send an impulse rather than a bare switch telegram.
Use a Start/Stop or timed-impulse telegram with a defined release duration (typically a few seconds, matched to the door strike's own hold time) instead of a plain 1-bit switch. A bare switch left in the 'on' state by a dropped telegram or a KNX line fault can leave the door unlocked indefinitely; an impulse telegram degrades to 'locked' instead.
Earthing loop: if the door strike's own low-voltage supply is bonded to building earth at a different point than the KNX SELV reference, the resulting loop can inject noise onto the bus near the door. Keep the door-side low-voltage returns on a single, defined earthing point and don't rely on the door strike's chassis for a second one.
Does KNX carry the live call, or only the door-release event?
KNX only carries the ringing, answered, release and code-entry events as group objects — the live video and two-way audio of the call itself travels over SIP, entirely outside the KNX bus.
To show the live call on a KNX room display, the panel needs its own SIP client, registered to the same SIP proxy (or configured peer-to-peer) as the Helios IP Verso, and the intercom's call-forwarding or ring group must include that panel's SIP address. The module's ringing object is only useful to wake the panel's screen to the intercom app before the SIP session actually connects.
SIP NAT traversal: if the intercom and the KNX SIP panel sit behind different NAT routers — common in split-VLAN or multi-building office deployments — call signalling can connect while the RTP audio/video path fails silently. Keep the intercom, its SIP proxy and any KNX SIP panels on one flat, trusted network segment, or configure a proper session border controller rather than relying on carrier-grade NAT.
Frequently asked questions
Does the 2N 916010 module power the Helios IP Verso from the KNX bus?
No. The module draws only its own logic current from the KNX TP1 bus. The intercom's camera, display and relay electronics are powered separately, typically by PoE 802.3at on the heated outdoor variants or a local 12-24 V DC supply.
Which ETS version works with the 916010 module?
Both ETS5 and ETS6, using the .knxprod product database published on 2N's support page. Match the database version to the module's installed firmware, since a mismatch can hide or duplicate communication objects after import.
Can the 916010 module trigger the door strike relay from a KNX panel?
Yes. Wire a KNX push-button or panel's group address to the module's door-release object, and send a Start/Stop or timed-impulse telegram rather than a bare switch so a dropped telegram degrades to locked instead of leaving the door open.
Does KNX carry the live video and audio from a door call?
No. Video and two-way audio travel over SIP between the intercom and the answering device. KNX only carries ring, answer, release and code-entry events as group objects; a KNX room panel needs its own SIP client to show the live call.
Where does the 916010 module physically fit in the Verso backbox?
It occupies one internal module slot inside the modular Verso backbox, wired to the intercom's internal module interconnect on one side and to the building's KNX TP1 line on the other. Order a frame with a free slot reserved for it.
What causes KNX objects to go missing after a Verso firmware update?
Usually a mismatched .knxprod database version against the module's new firmware. Re-download the database that matches the installed firmware from 2N's support page and re-import the device in ETS before assuming the wiring has failed.
Need the KNX wiring pre-planned before your Verso ships?
PanelCraft pre-wires the KNX bus terminal, door-release relay and earthing reference for 2N Helios IP Verso installations inside the panel it ships in.
Request a quote →