Si vous n’avez pas de compte pour accéder à la médiathèque 2N, veuillez remplir le formulaire d’inscription en ligne pour demander l’accès.
Veuillez noter que l'accès à la médiathèque est réservé aux représentants autorisés des partenaires commerciaux de 2N. Par conséquent, votre demande sera examinée et approuvée par 2N.
Que vous recherchiez un catalogue détaillant nos solutions d'interphonie d'appartement ou que vous vouliez une fiche technique pour le 2N IP Style, tout se trouve ci-dessous. Cherchez, trouvez, téléchargez, partagez !
2N Access Commander version 3.6 introduces a faster way to configure devices through device templates, a centralised call log for intercoms, a dedicated Company Admin role for managing organisation-level settings, and several quality-of-life improvements throughout the system.
Bugs fixed in 3.6.1:
Addresses a critical bug that a ects a small number of Access Commander Box installations and My2N app pairing.
New Features:
Device Templates
Admins can now save and edit the configuration file of any 2N OS–based device and apply it to other devices individually or in bulk.
Create templates from an existing device, a configuration file, or a device backup.
Templates can include only selected parts of the configuration, allowing controlled or
limited deployments.
Before a template is applied, Access Commander automatically creates a backup of the
target device.
Templates can be downloaded and uploaded to existing or future Access Commander
installations.
Important:
Templates are an advanced feature. Always review the configuration parameters and
values before applying a template.
Some parameters are automatically excluded (for example, static IP address) to prevent
unwanted duplication.
Certain parameters are highlighted with warnings; verify these carefully before
deployment.
Templates are supported only on 2N OS–based IP devices. They are not supported on 2N
Electronic Locks or 2N Indoor Touch.
Call logs
Call logs provide administrators with a single, unified view of incoming and outgoing calls from all intercoms and elevator communication devices.
One consolidated list: Calls from every managed device appear together.
Door unlock during a call: If a door is opened during a call, the event is recorded in both
the Call log and the Access log, and clearly marked with an icon.
Optional CAM logs: Enable CAM logs to capture images from intercoms when a call
begins.
Please note: If both the caller and receiver are managed by Access Commander, the system
may record two entries for the same call — one outgoing and one incoming. Call logs are
created in Access Commander once a call is terminated.
Company admin role
The new Company Admin role gives designated users control over company-specific settings that previously required full administrator rights. This role can be combined with others such as User Manager or Visitor Manager, depending on requirements. Company Admin rights include:
Viewing system log events related to their company.
Managing company details such as the name, default language, working hours,
holidays, and visitor settings.
Creating and editing email templates.
Managing LDAP user synchronisation.
Initiating lockdown of company devices (intercoms and access units).
Other improvements:
Pairing with the My2N mobile app is now faster and more secure. Users can pair the app via a QR code displayed in Access Commander or from a link or QR code sent by email. (Supported on devices running FW 2.50/3.0 and higher).
Access Commander can now be discovered on the local network using the 2N IP Utility
application, together with 2N OS and Axis devices. (Windows only; the Access
Commander IP address cannot be configured through the tool).
mDNS domain name support added. Access Commander can now be reached on the
local network at https://accesscommander.local
Network discovery features (mDNS domain and 2N IP Utility) can be disabled in
Settings>Configuration.
The linux console welcome message has been updated to include the mDNS domain in
addition to the IP address.
Access Commander now supports MIFARE DESFire cards in use by a third-party. Cards
must support anonymous application creation.
Required Device Firmware Versions for Full Feature Support
2N IP Intercoms: 2.50.x/3.2.x
2N Access Units: 2.50.x/3.2.x
2N Answering Units: 2.50.x/3.2.x
2N Emergency Elevator Communicators: 3.2.x
Note - some older 2N devices cannot support versions higher than 2.50.
Minimum Supported Firmware Versions (Devices running firmware older than these versions will not sync with Access Commander)
2N IP Intercoms: 2.47.x
2N Access Unit: 2.47.x
2N Answering Units 2.47.x
2N Indoor Touch 2.0: 4.3.x (Devices running earlier versions will be disabled in Access
Commander)
2N Indoor Touch 1.0 is not supported in Access Commander
API Changes
2N Access Commander version 3.6 introduces a faster way to configure devices through device templates, a centralised call log for intercoms, a dedicated Company Admin role for managing organisation-level settings, and several quality-of-life improvements throughout the system.
Bugs fixed in 3.6.1:
Addresses a critical bug that a ects a small number of Access Commander Box installations and My2N app pairing.
New Features:
Device Templates
Admins can now save and edit the configuration file of any 2N OS–based device and apply it to other devices individually or in bulk.
Create templates from an existing device, a configuration file, or a device backup.
Templates can include only selected parts of the configuration, allowing controlled or
limited deployments.
Before a template is applied, Access Commander automatically creates a backup of the
target device.
Templates can be downloaded and uploaded to existing or future Access Commander
installations.
Important:
Templates are an advanced feature. Always review the configuration parameters and
values before applying a template.
Some parameters are automatically excluded (for example, static IP address) to prevent
unwanted duplication.
Certain parameters are highlighted with warnings; verify these carefully before
deployment.
Templates are supported only on 2N OS–based IP devices. They are not supported on 2N
Electronic Locks or 2N Indoor Touch.
Call logs
Call logs provide administrators with a single, unified view of incoming and outgoing calls from all intercoms and elevator communication devices.
One consolidated list: Calls from every managed device appear together.
Door unlock during a call: If a door is opened during a call, the event is recorded in both
the Call log and the Access log, and clearly marked with an icon.
Optional CAM logs: Enable CAM logs to capture images from intercoms when a call
begins.
Please note: If both the caller and receiver are managed by Access Commander, the system
may record two entries for the same call — one outgoing and one incoming. Call logs are
created in Access Commander once a call is terminated.
Company admin role
The new Company Admin role gives designated users control over company-specific settings that previously required full administrator rights. This role can be combined with others such as User Manager or Visitor Manager, depending on requirements. Company Admin rights include:
Viewing system log events related to their company.
Managing company details such as the name, default language, working hours,
holidays, and visitor settings.
Creating and editing email templates.
Managing LDAP user synchronisation.
Initiating lockdown of company devices (intercoms and access units).
Other improvements:
Pairing with the My2N mobile app is now faster and more secure. Users can pair the app via a QR code displayed in Access Commander or from a link or QR code sent by email. (Supported on devices running FW 2.50/3.0 and higher).
Access Commander can now be discovered on the local network using the 2N IP Utility
application, together with 2N OS and Axis devices. (Windows only; the Access
Commander IP address cannot be configured through the tool).
mDNS domain name support added. Access Commander can now be reached on the
local network at https://accesscommander.local
Network discovery features (mDNS domain and 2N IP Utility) can be disabled in
Settings>Configuration.
The linux console welcome message has been updated to include the mDNS domain in
addition to the IP address.
Access Commander now supports MIFARE DESFire cards in use by a third-party. Cards
must support anonymous application creation.
Required Device Firmware Versions for Full Feature Support
2N IP Intercoms: 2.50.x/3.2.x
2N Access Units: 2.50.x/3.2.x
2N Answering Units: 2.50.x/3.2.x
2N Emergency Elevator Communicators: 3.2.x
Note - some older 2N devices cannot support versions higher than 2.50.
Minimum Supported Firmware Versions (Devices running firmware older than these versions will not sync with Access Commander)
2N IP Intercoms: 2.47.x
2N Access Unit: 2.47.x
2N Answering Units 2.47.x
2N Indoor Touch 2.0: 4.3.x (Devices running earlier versions will be disabled in Access
Commander)
2N Indoor Touch 1.0 is not supported in Access Commander
API Changes
2N Access Commander version 3.5 introduces enhanced support for 2N Fortis Locks, a new card search function, company specific time profiles, support for emergency elevator communicators and other improvements.
This subsequent 3.5.2 release adds support for 2N OS firmware 3.1 and resolves a few small issues. If you are upgrading from version 3.5 or earlier it also includes the following fixes and improvements from 3.5.1.
Resolved an issue which prevented the syncing of more than 2000 users to devices for some installations. Note: If the issue persists after upgrade please suspend and resume management of affected devices.
Fixed an issue where User Managers could no longer edit card IDs.
Added missing Force 2.0 icon.
Translation improvements.
New Features in 3.5.0
Enhanced support for 2N Fortis electronic locks
Integration with 2N Fortis Commander - Access Commander now supports export to 2N Fortis Commander, our new Windows-based tool for electronic lock setup and maintenance. Fortis Commander simplifies initial lock pairing and ongoing servicing. It is available as a standalone download from 2n.com. This replaces the third-party tool introduced in version 3.4.
Event Logging - Access and system events—such as access granted/denied, low battery, battery replaced, or lock jammed—are now transferred to Access Commander when cards are presented to IP-based readers. Events are logged with both the event timestamp and the time received. Devices with low battery are highlighted in the status column of the device list. Event collection can be configured to include access and system events, system events only or no events (to conserve card storage)
Lock Groups - Electronic locks can now be grouped, making it easier to manage access rights for areas like cleaning cupboards on each floor or “Access All Areas” permissions. When creating zones, you can assign individual locks or lock groups. Locks may belong to multiple groups simultaneously.
Unified Maintenance Card Functionality - The ‘New locks setup’ card has been merged into the service card. The updated service card now supports both brand-new locks and those already deployed in a project.
Customizable Maintenance Card Validity - The default one-year validity period for maintenance cards is now editable, allowing for greater flexibility in card lifecycle management.
New search improvements
The main search box has been centralised in the application header for greater visibility.
When a USB based card reader is enabled (Settings > Credentials > Enabled USB readers) a card icon appears next to the search box. Clicking this icon and presenting a card to the reader looks up the card informing the user of the owner or permissions that this card has (maintenance cards). Perfect for finding the owner of a found card or fob.
Presenting an access card used with Fortis locks will update that card and also transfer any card events to Access Commander's System and Access Logs.
Company specific time profiles
In multi-company installations, admins can now assign new time profiles to companies. An access manager will only see system-wide time profiles or time profiles assigned to their company. The creation of a new time profile by an access manager will not be visible to other companies.
2N Emergency Elevator Communicator support
Access Commander now supports 2N OS based elevator devices (LiftIP 2.0 and Sentrio). The online state of these devices can be monitored from the device list, monitoring page and can be notified by email. As with all 2N OS devices, access to the device web configuration is also supported, with Access Commander remembering the device password.
Other improvements:
CAM log images can now be downloaded in bulk rather than individually.
User access PINs created by managers are now random preventing the unintentionally discovery of existing user PINs of other companies. Applies to multi-company installations only. Admins still have the option to set a pin of their choice.
CSV exports of logs now include time stamps that match the application system time zone. For installations that span multiple time zones the option to choose UTC+0 remains.
User login now persists after reboot.
From the user profile page all browser login sessions are visible with IP address, operating system, browser type and last activity timestamp. All sessions can be logged out with a single click.
Required Device Firmware Versions for Full Feature Support
2N IP Intercoms: 2.50.x/3.1.x
2N Access Units: 2.50.x/3.1.x
2N Answering Units: 2.50.x/3.1.x
2N Emergency Elevator Communicators: 3.1.x
Note - some older 2N devices cannot support versions higher than 2.50.x
Minimum Supported Firmware Versions (Devices running firmware older than these versions will not sync with Access Commander)
2N IP Intercoms: 2.45.x
2N Access Unit: 2.45.x
2N Answering Units: 2.45.x
2N Indoor Touch 2.0: 4.3.x (Devices running earlier versions will be disabled in Access Commander)
2N Indoor Touch 1.0 is not supported in Access Commander
2N Access Commander version 3.5 introduces enhanced support for 2N Fortis Locks, a new card search function, company specific time profiles, support for emergency elevator communicators and other improvements.
This subsequent 3.5.2 release adds support for 2N OS firmware 3.1 and resolves a few small issues. If you are upgrading from version 3.5 or earlier it also includes the following fixes and improvements from 3.5.1.
Resolved an issue which prevented the syncing of more than 2000 users to devices for some installations. Note: If the issue persists after upgrade please suspend and resume management of affected devices.
Fixed an issue where User Managers could no longer edit card IDs.
Added missing Force 2.0 icon.
Translation improvements.
New Features in 3.5.0
Enhanced support for 2N Fortis electronic locks
Integration with 2N Fortis Commander - Access Commander now supports export to 2N Fortis Commander, our new Windows-based tool for electronic lock setup and maintenance. Fortis Commander simplifies initial lock pairing and ongoing servicing. It is available as a standalone download from 2n.com. This replaces the third-party tool introduced in version 3.4.
Event Logging - Access and system events—such as access granted/denied, low battery, battery replaced, or lock jammed—are now transferred to Access Commander when cards are presented to IP-based readers. Events are logged with both the event timestamp and the time received. Devices with low battery are highlighted in the status column of the device list. Event collection can be configured to include access and system events, system events only or no events (to conserve card storage)
Lock Groups - Electronic locks can now be grouped, making it easier to manage access rights for areas like cleaning cupboards on each floor or “Access All Areas” permissions. When creating zones, you can assign individual locks or lock groups. Locks may belong to multiple groups simultaneously.
Unified Maintenance Card Functionality - The ‘New locks setup’ card has been merged into the service card. The updated service card now supports both brand-new locks and those already deployed in a project.
Customizable Maintenance Card Validity - The default one-year validity period for maintenance cards is now editable, allowing for greater flexibility in card lifecycle management.
New search improvements
The main search box has been centralised in the application header for greater visibility.
When a USB based card reader is enabled (Settings > Credentials > Enabled USB readers) a card icon appears next to the search box. Clicking this icon and presenting a card to the reader looks up the card informing the user of the owner or permissions that this card has (maintenance cards). Perfect for finding the owner of a found card or fob.
Presenting an access card used with Fortis locks will update that card and also transfer any card events to Access Commander's System and Access Logs.
Company specific time profiles
In multi-company installations, admins can now assign new time profiles to companies. An access manager will only see system-wide time profiles or time profiles assigned to their company. The creation of a new time profile by an access manager will not be visible to other companies.
2N Emergency Elevator Communicator support
Access Commander now supports 2N OS based elevator devices (LiftIP 2.0 and Sentrio). The online state of these devices can be monitored from the device list, monitoring page and can be notified by email. As with all 2N OS devices, access to the device web configuration is also supported, with Access Commander remembering the device password.
Other improvements:
CAM log images can now be downloaded in bulk rather than individually.
User access PINs created by managers are now random preventing the unintentionally discovery of existing user PINs of other companies. Applies to multi-company installations only. Admins still have the option to set a pin of their choice.
CSV exports of logs now include time stamps that match the application system time zone. For installations that span multiple time zones the option to choose UTC+0 remains.
User login now persists after reboot.
From the user profile page all browser login sessions are visible with IP address, operating system, browser type and last activity timestamp. All sessions can be logged out with a single click.
Required Device Firmware Versions for Full Feature Support
2N IP Intercoms: 2.50.x/3.1.x
2N Access Units: 2.50.x/3.1.x
2N Answering Units: 2.50.x/3.1.x
2N Emergency Elevator Communicators: 3.1.x
Note - some older 2N devices cannot support versions higher than 2.50.x
Minimum Supported Firmware Versions (Devices running firmware older than these versions will not sync with Access Commander)
2N IP Intercoms: 2.45.x
2N Access Unit: 2.45.x
2N Answering Units: 2.45.x
2N Indoor Touch 2.0: 4.3.x (Devices running earlier versions will be disabled in Access Commander)
2N Indoor Touch 1.0 is not supported in Access Commander
2N® Access Commander version 3.4.2 (September 2025)
2N® Access Commander version 3.4 introduced a range of new features, detailed below. This subsequent 3.4.2 release adds support for 2N OS firmware 2.49, delivers minor text improvements, and resolves a few small issues.
This release includes security fixes and addresses concerns regarding the following user reported vulnerabilities.
CVE-2025-59783 - improper input validation, could lead to command injection (requires authenticated administrator account).
CVE-2025-59784 - improper sanitisation of application logs, risking malicious injections exploitable by downstream systems.
It is strongly recommended that all users upgrade to version 3.4.2 to ensure the security of their installation. As with all Access Commander upgrades, this release updates external dependencies critical for security.
IMPORTANT - Due to a redesign of the proxy server settings, upgrading to this version from 3.3.1 or lower will erase any existing configuration—administrators will need to re-enter the proxy details after the update.
New Features & Improvements:
2N Fortis electronic locks
This release supports 2N Fortis wireless electronic locks (handles and cylinders) in offline mode. Locks can be added to Access Commander and assigned to zones, similar to other access readers in the software. 2N Fortis locks adhere to the OSS Secure ID standard, where access rights are stored and encrypted on the card or fob (DESFire EV3) rather than the device itself. Due to the offline nature of these devices, active monitoring or control is not supported. In this version of Access Commander, a 2N intercom or 2N Access Unit is required for writing access rights to cards and must be part of the installation.
Proxy exceptions
2N Access Commander now supports more granular proxy configuration, allowing administrators to define proxy server exceptions (domains or addresses). This improvement simplifies network management in complex environments, ensuring external services can connect via network proxy while local devices can remain unaffected. This update addresses key customer requests and lays the foundation for future cloud-based functionality.
Extended visitor duration
Until now visitors in Access Commander were limited to a maximum visit of 30 days. From Access Commander 3.4 we are increasing this duration to a maximum of 90 days allowing temporary access that can span months. Ideal for customers integrating Access Commander with third-party systems that need support for longer visits.
Device types
We've added a new column to the device list page called 'Types'. It's now even easier to see which device is an intercom, Access Unit, answering unit or electronic lock. The list can be filtered based on the selected type.
New Devices
This release supports the new 2N IP Force 2.0 intercom the 2N Clip 2wire-IP answering unit, and of course, 2N Fortis electronic locks.
Additional Notes
IMPORTANT - For security reasons, this version of Access Commander is not compatible with 2N Intercoms and 2N Access Units running firmware version 2.37 or older. Access Commander will not manage devices with these firmware versions even if compatibility mode is enabled. Please ensure all devices are running firmware version 2.38 or newer before upgrading.
Required Device Firmware Versions for Full Feature Support
2N IP Intercoms: 2.49.x
2N Access Unit: 2.49.x
Minimum Supported Firmware Versions (Devices running firmware older than these versions will not sync with Access Commander)
2N IP Intercoms: 2.43.x
2N Access Unit: 2.43.x
2N Indoor Touch 2.0: 4.3.x (Devices running earlier versions will be disabled in Access Commander)
2N Indoor Touch 1.0 is not supported in Access Commander
2N® Access Commander version 3.4.2 (September 2025)
2N® Access Commander version 3.4 introduced a range of new features, detailed below. This subsequent 3.4.2 release adds support for 2N OS firmware 2.49, delivers minor text improvements, and resolves a few small issues.
This release includes security fixes and addresses concerns regarding the following user reported vulnerabilities.
CVE-2025-59783 - improper input validation, could lead to command injection (requires authenticated administrator account).
CVE-2025-59784 - improper sanitisation of application logs, risking malicious injections exploitable by downstream systems.
It is strongly recommended that all users upgrade to version 3.4.2 to ensure the security of their installation. As with all Access Commander upgrades, this release updates external dependencies critical for security.
IMPORTANT - Due to a redesign of the proxy server settings, upgrading to this version from 3.3.1 or lower will erase any existing configuration—administrators will need to re-enter the proxy details after the update.
New Features & Improvements:
2N Fortis electronic locks
This release supports 2N Fortis wireless electronic locks (handles and cylinders) in offline mode. Locks can be added to Access Commander and assigned to zones, similar to other access readers in the software. 2N Fortis locks adhere to the OSS Secure ID standard, where access rights are stored and encrypted on the card or fob (DESFire EV3) rather than the device itself. Due to the offline nature of these devices, active monitoring or control is not supported. In this version of Access Commander, a 2N intercom or 2N Access Unit is required for writing access rights to cards and must be part of the installation.
Proxy exceptions
2N Access Commander now supports more granular proxy configuration, allowing administrators to define proxy server exceptions (domains or addresses). This improvement simplifies network management in complex environments, ensuring external services can connect via network proxy while local devices can remain unaffected. This update addresses key customer requests and lays the foundation for future cloud-based functionality.
Extended visitor duration
Until now visitors in Access Commander were limited to a maximum visit of 30 days. From Access Commander 3.4 we are increasing this duration to a maximum of 90 days allowing temporary access that can span months. Ideal for customers integrating Access Commander with third-party systems that need support for longer visits.
Device types
We've added a new column to the device list page called 'Types'. It's now even easier to see which device is an intercom, Access Unit, answering unit or electronic lock. The list can be filtered based on the selected type.
New Devices
This release supports the new 2N IP Force 2.0 intercom the 2N Clip 2wire-IP answering unit, and of course, 2N Fortis electronic locks.
Additional Notes
IMPORTANT - For security reasons, this version of Access Commander is not compatible with 2N Intercoms and 2N Access Units running firmware version 2.37 or older. Access Commander will not manage devices with these firmware versions even if compatibility mode is enabled. Please ensure all devices are running firmware version 2.38 or newer before upgrading.
Required Device Firmware Versions for Full Feature Support
2N IP Intercoms: 2.49.x
2N Access Unit: 2.49.x
Minimum Supported Firmware Versions (Devices running firmware older than these versions will not sync with Access Commander)
2N IP Intercoms: 2.43.x
2N Access Unit: 2.43.x
2N Indoor Touch 2.0: 4.3.x (Devices running earlier versions will be disabled in Access Commander)
2N Indoor Touch 1.0 is not supported in Access Commander