2N intercom and KNX with Link’nX: doors and events
With Link’nX, a 2N intercom declared on the gateway becomes part of the installation’s scenarios. An action controls one of its switches, numbered 1 to 4: open, close, lock, hold a door open. A trigger reacts to its events: code or card entered, call, door state, motion or noise detection. In a scenario, these items combine with the project’s KNX triggers and actions.
What the 2N integration does
Section titled “What the 2N integration does”| Need | Where to configure it | Guide |
|---|---|---|
| Declare the intercom and its HTTP API access | Devices → Security & Access → 2N | Declare a 2N intercom |
| Take over the intercom’s configuration and users | Import configuration, .xml file | Declare a 2N intercom |
| Open, lock or hold a door open | 2N action | Control a 2N switch |
| Start a scenario on a code, a card, a call or a door state | 2N trigger | React to 2N events |
| Send KNX commands after a 2N event | KNX action in the same scenario | Prepare a KNX action |
| Control the door from a KNX button | KNX trigger combined with a 2N action | Create a KNX trigger |
Step-by-step commissioning
Section titled “Step-by-step commissioning”- Prepare the intercom in its web interface: Switch API and Logging API enabled, HTTP API account enabled with its privileges.
- Declare the intercom: name, IPv4 address, HTTP API account, password and both authentication methods. Import its XML file if needed, then save.
- Prepare the 2N actions: device, switch number and command.
- Prepare the 2N triggers, filling in only the filters the automation needs.
- Compose the scenario with these triggers and actions, adding KNX actions or triggers if needed.
- Then check the actual operation of the door and the reception of events.
Each guide ends with its own troubleshooting: floppy disk grayed out, values missing after the import, event that does not arrive, command without effect.
Good to know
Section titled “Good to know”- The switch API and the logging API each have their own authentication method: None, Basic or Digest, identical in the intercom and in the declaration. If commands work but events do not, check the second one.
- The XML import prepares the Link’nX declaration; it does not restore the intercom. It may replace values already entered, and the password still has to be filled in before saving.
- In a trigger, all the criteria filled in must match the event received. An empty field or the — choice ignores the criterion.
- Unlock and Release / cancel hold-open are two separate commands. A switch that is both locked and held remains held after it is unlocked. Before holding a door strike open, check that it can withstand this over time.
- The usable functions and events depend on the hardware: detectors, readers and the door contact must be configured on the intercom.
For other door stations and access solutions, see Access control and Security and video surveillance.