2N

2N is a global leader in IP intercom and access control solutions. They specialize in modern, secure, and network-based door communication systems, including IP intercoms, access readers, and audio solutions used in residential, commercial, and industrial buildings. Their products integrate easily with third-party systems and focus on reliability, innovative design, and high-level security.

• Manufacturer: 2N
• Product name: 2N API and IP Verso devices
• Website: 2N
• Manual: 2N API documentation

Device preparation

Enable the HTTP API service — via the device’s web UI under Services → HTTP API. By default, some services might be disabled. Set transport protocol and authentication method for the API — you must select whether you want HTTP or HTTPS, and which authentication (None / Basic). Create at least one API user account — the 2N device allows up to 5 HTTP-API user accounts. For each account you define a username/password and assign privileges for which API services are allowed. Without a valid account, all API requests will be rejected. ake sure the device is reachable on the network — the device must have a properly configured IP address (static or via DHCP), and be on the same network (or routed correctly) so your automation/homesystem (e.g. your KNX + bOS setup) can reach it.

Configuration

Download the example from our website and import it into your configuration. Step by step instructions on how to import are available in our instructional video. Fill out the correct IP address of your intercom under the main 2N HTTP node. To view life feed from the camera, use the Camera nodes in the example, discover the correct intercom, fill out the login credentials and the camera feed should be set. The example contains visualization panels for 4 different intercoms, where clients can set up their user with their information and cards as well. Using bOS client, they can update or reset the user settings. The icons in the visualization will reflect the correct or incorrect settings: If the field is green, it means the information has been sent correctly and matches what is stored in 2N. If the field is red, it means there is a mismatch or the update has not been applied correctly. The example already has a generic KNX project, make sure to link the group addresses with your current project so the outputs control your actual devices.