If you are running 2N® Access Commander version 1.9.1 or older, proceed please to this section for further details.

2N® Access Commander version 3.3.1 Firmware Support & Bugfix (April 2025)


2N® Access Commander version 3.3 introduces better support for devices in remote network segments, support for additional SIP accounts in our intercom products (FW 2.46 required) and enhances security by validating the unique device certificate of our connected devices.

This release includes security fixes and addresses concerns regarding two user reported vulnerabilities that have been published as CVEs. More details can be found on our website - www.2n.com/en-GB/newsroom/latest-cve-disclosures-reinforce-our-commitment-to-cybersecurity/. It is strongly recommended that all users upgrade to version 3.3 to ensure the security of their installation.

New Features & Improvements:

Maintaining connection with remote devices

The current method of device discovery and then using that discovered IP address for connection works well for flat networks where our discovery protocol works unhindered, but when devices are on remote connections (eg, VPN, NAT or multi-segment topology) and the device IP address changes (such as a DHCP lease expiration) then the connection to this device is lost and cannot be reconnected. This release supports an optional mode where devices can report back to Access Commander via HTTP in the event of an address change.

Support for additional SIP accounts

Intercom firmware 2.46 now supports two additional SIP accounts (SIP 3 and 4) and a dedicated account for calling MS Teams extensions. Users in Access Commander can now be assigned phone numbers that call out via these accounts by applying the suffix /3, /4 or prefix 'msteams:' as appropriate. For example, number '3008/3' would call extension 3008 from an intercom's third SIP account or 'msteams:15684999' would call number 15684999 via MS Teams. The status of these additional accounts can be monitored on the devices monitoring page and on the device detail page.

Device certificate fingerprint validation

Three security options are now available for connected devices.

Support for RFID card compatibility mode

RFID card compatibility mode allows cards with trailing characters that match, regardless of their overall length, to be treated as identical. Enabling this feature applies compatibility mode across all connected intercoms and access units. Prior to the introduction of this option, cards that 2NOS would recognize as identical were inconsistently handled by Access Commander, resulting in some cards being rejected when assigned to a user.

Corrections:

Additional Notes

Required Device Firmware Versions for Full Feature Support

Minimum Supported Firmware Versions (Devices running firmware older than these versions will not sync with Access Commander)

API Changes

2N® Access Commander version 3.3 (January 2025)


2N® Access Commander version 3.3 introduces better support for devices in remote network segments, support for additional SIP accounts in our intercom products (FW 2.46 required) and enhances security by validating the unique device certificate of our connected devices.

This release includes security fixes and addresses concerns regarding two user reported vulnerabilities that will be published as CVEs. Security advisory to be published on 2n.com. It is strongly recommended that all users upgrade to version 3.3 to ensure the security of their installation.

New Features & Improvements:

Maintaining connection with remote devices

The current method of device discovery and then using that discovered IP address for connection works well for flat networks where our discovery protocol works unhindered, but when devices are on remote connections (eg, VPN, NAT or multi-segment topology) and the device IP address changes (such as a DHCP lease expiration) then the connection to this device is lost and cannot be reconnected. This release supports an optional mode where devices can report back to Access Commander via HTTP in the event of an address change.

Support for additional SIP accounts

Intercom firmware 2.46 now supports two additional SIP accounts (SIP 3 and 4) and a dedicated account for calling MS Teams extensions. Users in Access Commander can now be assigned phone numbers that call out via these accounts by applying the suffix /3, /4 or prefix ‘msteams:’ as appropriate.
For example, number ‘3008/3’ would call extension 3008 from an intercom’s third SIP account or ‘msteams:15684999’ would call number 15684999 via MS Teams. The status of these additional accounts can be monitored on the devices monitoring page and on the device detail page.

Device certificate fingerprint validation

Three security options are now available for connected devices.

Support for RFID card compatibility mode

RFID card compatibility mode allows cards with trailing characters that match, regardless of their overall length, to be treated as identical. Enabling this feature applies compatibility mode across all connected intercoms and access units. Prior to the introduction of this option, cards that 2NOS would recognize as identical were inconsistently handled by Access Commander, resulting in some cards being rejected when assigned to a user.

Additional Notes

Required Device Firmware Versions for Full Feature Support

Minimum Supported Firmware Versions (Devices running firmware older than these versions will not sync with Access Commander)

API Changes

---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

2N® Access Commander version 3.2.2 Firmware Support & Bugfix (December 2024)


This release adds support for 2NOS FW 2.46 (released in December 2024).

2N® Access Commander version 3.2 introduces automation capabilities, the ability to assign logical names to installations, and several other security and usability enhancements. Please note that APIv2 has been removed in this version. Ensure that any third-party applications previously utilising APIv2 have been updated to version 3, specifically 2N Picard Commander and 2N Milestone plugin. Please go to the 2N website and download new versions of these applications.

This release includes security fixes and addresses concerns regarding the following user reported vulnerabilities.


It is strongly recommended that all users upgrade to version 3.2 to ensure the security of their installation.

New Features:

Automation (Node-RED)

Node-RED has been integrated into Access Commander. Node-RED, a flow-based programming tool from the OpenJS Foundation, allows users to create custom automations by connecting ‘nodes.’ These automations can facilitate simple or complex integrations with third-party APIs or trigger custom scenarios within Access Commander itself. The Access Commander implementation of Node-RED includes six custom nodes that enable automations based on System and Access Log events, SignalR topics, REST API queries, and a dedicated node for writing events to the system log. Automation is available only to users with Admin-level login rights.

Installation Naming

You can now assign a name to each Access Commander installation through Settings > Configuration. This name will be displayed in the application header, browser tab, and all outgoing e-mail notifications. This feature is particularly useful for administrators or installers managing multiple instances of Access Commander, making it easy to identify the origin of each e-mail.

Other Improvements

Corrections

Additional Notes


Required Device Firmware Versions for Full Feature Support

Minimum Supported Firmware Versions (Devices running firmware older than these versions will not sync with Access Commander)

API Changes

Automation in 2N Access Commander

We are pleased to announce the introduction of a powerful new Automation feature in 2N Access Commander, available under the Advanced, Pro, and Unlimited licences. Built upon the robust Node-RED platform, this addition brings extensive flow-based programming capabilities directly to our software, allowing users to seamlessly connect 2N Access Commander with various third-party systems and automate custom workflows based on events within the platform.

If you wish to take advantage of this versatile automation tool, please bear in mind the following:

Customer Responsibility for Security:

Users are responsible for ensuring that their Automation configurations and workflows are secure and in line with cybersecurity best practices. This includes securing the Node-RED environment, managing permissions appropriately, and safeguarding sensitive data within your automations.

Use of the REST API node:

If not used properly this node may lead to data loss or unintended modifications. It is the user’s responsibility to ensure that the node is configured and implemented correctly. Please exercise caution and double-check your settings to avoid potential risks to your data.

Third-Party Nodes and Add-ons:

2N is not responsible for the use or integration of any third-party nodes, add-ons, or custom modifications to Node-RED within the Automation feature. Customers should carefully evaluate and ensure the security and stability of any additional components they choose to install. Any issues arising from third-party extensions will need to be resolved by the customer or the respective third-party provider.

Technical Support Limitations:

While our support team will assist with issues related to the basic functionality of the Automation feature within 2N Access Commander, including our custom Access Commander nodes, they will not be able to provide assistance with the design, development, or debugging of custom Node-RED flows. Users who wish to create complex automations may need to seek additional support from qualified Node-RED experts or consult available resources.

For those looking to get started with Node-RED, we recommend exploring the wealth of online resources available, such as detailed manuals and numerous YouTube tutorials, which provide guidance on creating and managing your own flows.

For more information about our custom 2N Access Commander nodes and using the Automation feature within 2N Access Commander, please refer to our manual.

We believe this new feature will significantly enhance the capabilities of 2N Access Commander, and we encourage you to explore its potential, keeping in mind the importance of securing your configurations.

Thank you for your understanding.

---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

2N® Access Commander version 3.1.1 Firmware Support & Bugfix (June 2024)


2N® Access Commander version 3.1.1 includes support for Intercom and Access Unit firmware 2.44 and a few minor bug fixes in addition to the features introduced by 3.1 listed below.

2N® Access Commander version 3.1 (April 2024)

2N® Access Commander version 3.1 introduces a more secure method of login (2FA), Dutch Language and other improvement


**IMPORTANT** Due to security reasons this version of Access Commander is not compatible with 2N Intercoms and 2N Access Units running FW 2.37 or older. Access Commander will not manage devices with these FW even with enabled compatibility mode. Please ensure that all devices are running FW 2.38 or newer before upgrading.


New Features:

Two factor authentication is now available for login. When enabled each user requires both password and secondary authentication via an authenticator app such as Google Authenticator in addition to their unique user name. This extra level of security can be optional for all users, mandatory for users with a role (Managers), or mandatory all users and is set by Admin. 2FA works even for installations that are offline (have no internet connection).

Dutch is now included as a language variant in Access Commander's web environment. The online and offline manual also supports machine translated Dutch.

* Access Commander now supports API Keys - access without user authentication opening up further possibilies for integration.
* When setting up Access Commander from the browser for the first time the linux root password is now synchronised with the system admin password if the root password hasn't yet been changed from default.
* Access Unit QR is supported in this version.


Corrections

* Device sensor (door sensor) status is now correctly displayed in the device monitoring page.
* User name for access granted/denied now displayed in the Access Log widget.
* Device configuration can now be accessed from the device list as it was in Access Commander version 2.


Additional notes

**IMPORTANT** - In May 2023 we announced that the old APIv2 will be retired in place of a more advanced APIv3 and gave a transition period of one year where the two versions run side by side. From this release APIv2 will be no longer supported, and will be removed completely from Access Commander 3.2 (Q3 2024). 
If you are using Access Commander with a third-party integration, please ensure that this integration is compatible with APIv3 soon to avoid loss of functionality in future versions.
For more information on Access Commander's API see the documentation in the user manual
- The old user interface is no longer available in this version
- Known issue - In 3.1 it is not possible to manually approve a device firmware on a Basic (free) license. Please ensure all devices meet the firmware requirements listed below. Fix comming in Access Commander 3.2 (August)
- Integration with the Milestone Xprotect plugin is not compatible with 2FA. Do not enable 2FA for the Milestone user login.


Required device firmware versions for full feature support

2N IP intercoms 2.43.x
2N Access Unit 2.43.x

Minimum supported firmware versions (devices prior to these versions will not be synchronised with Access Commander)

2N IP intercoms 2.39.x
2N Access Unit 2.39.x
2N Indoor Touch 2.0: 4.3.x (devices running versions prior to this will be disabled in Access Commander)
2N Indoor Touch 1.0 is not supported in Access Commander

API changes 

* [APIv2 Change log] No changes were made
* [APIv3 Change log] https://www.2n.com/documents/22902/2323545/Diffv3_v3.0-v3.1+2.md/c8a5ad20-6179-4902-b8a5-81a8f26d50d1

---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

2N® Access Commander version 3.0.1 Firmware Support & Bugfix (April 2024)


IMPORTANT Due to security reasons this version of Access Commander is not compatible with 2N Intercoms and 2N Access Units running FW 2.37 or older. Access Commander will not manage devices with these FW even with enabled compatibility mode. Please ensure that all devices are running FW 2.38 or newer before upgrading.

Supported device firmware version:


2N® Access Commander version 3.0 (production February 2024)

2N® Access Commander version 3.0 introduces a brand new look and feel. While the look has changed, it's the same trusted Access Commander, now more user-friendly, simplified and intuitive.

Changelog 3.0

New interface

New improvements

Mobile friendly visitor enrolment

Russian language support has been removed from Access Commander 3.0

Access Commander 3.0 includes the ability to toggle back to the old interface. It's worth noting that starting from version 3.1, only the new interface will be available, and the old interface will no longer be supported.

Upgrade to PostgreSQL 15

Supported device firmware version:

* 2N IP intercoms from 2.38.x to 2.42.x
* 2N Access Unit from 2.38.x to 2.42.x
* 2N Indoor Touch 2.0: 4.3.x (devices running versions prior to this will be disabled in Access Commander)

**IMPORTANT**

In May 2023 we announced that the old APIv2 will be retired in place of a more advanced APIv3 and gave a transition period of one year where the two versions run side by side. From Access Commander 3.1 (Q2 2024) APIv2 will be no longer supported, and will be removed completely from Access Commander 3.2 (Q3 2024). 
If you are using Access Commander with a third-party integration, please ensure that this integration is compatible with APIv3 soon to avoid loss of functionality in future versions.
For more information on Access Commander's API see the documentation in the online manual
* Russian language support has been removed from Access Commander 3.0

API changes

* [APIv2 Change log](https://www.2n.com/documents/22902/74426/APIv2+change+log+-+2N%C2%AE+Access+Commander+3.0.md/94202e31-ba91-4b16-9679-a4474581b2a9)
* [APIv3 Change log](https://www.2n.com/documents/22902/74426/APIv3+change+log+-+2N%C2%AE+Access+Commander+3.0.md/d3581281-c2e2-4115-a86a-c64d85d4210f)

---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

2N® Access Commander version 2.7.1 Firmware Support & Bugfix (November 2023)

2N® Access Commander version 2.7.1 supports new version of firmware, that will be released.

Changelog 2.7.1

Supported device firmware version:

2N® Access Commander version 2.7 (August 2023)

2N® Access Commander version 2.7 introduces export of user list and possibility to assign credentials to users in bulk.

Changelog 2.7.0

New Features:

Corrections:

Required device firmware versions for full feature support

Minimum supported firmware versions (devices prior to these versions will not be synchronized with Access Commander)

---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

2N® Access Commander version 2.6.1 Firmware Support & Bugfix (June 2023)

Please note that this version is a minor release, further to the release of version 2.6 in May 2023. It introduces no new feature and only brings a specific bugfix. 

Changelog 2.6.1

Corrections:

2N® Access Commander version 2.6 (May 2023)

2N® Access Commander version 2.6 introduces new API v3.

Changelog 2.6

New features:

Corrections:

Required device firmware versions for full feature support

Minimum supported firmware versions (devices prior to these versions will not be synchronized with Access Commander)

---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

2N® Access Commander version 2.5.1 Firmware Support & Bugfix (February 2023)

Please note that this version is a minor release, further to the release of version 2.5 in December 2022. It focuses on corrections and compatibility with the 2.38 FW version of the 2N OS, it introduces no new feature. 

Changelog 2.5.1

Corrections:

Updates:

2N® Access Commander version 2.5 (Beta November 2022, production December 2022)

2N® Access Commander version 2.5 introduces NTP server functionality whilst work continues on a new API and interface.

Changelog 2.5

New Features:

Corrections:

Required device firmware versions for full feature support

Minimum supported firmware versions (devices prior to these versions will not be synchronized with Access Commander)

---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

2N® Access Commander version 2.4.1 Firmware Support & Bugfix (October 2022)

Changelog 2.4.1

Corrections:

2N® Access Commander version 2.4 (September 2022)

2N® Access Commander version 2.4 makes Attendance Monitoring available even for smaller installations, and introduces some minor features whilst work continues on a new API and interface.

Changelog 2.4.0

New Features:



Corrections:


Required device firmware versions for full feature support

Minimum supported firmware versions (devices prior to these versions will not be synchronized with Access Commander)

---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

2N® Access Commander version 2.3.1 Firmware Support & Bugfix

Changelog 2.3.1

Please note that this version is a minor release, further to the release of version 2.3 in April. It focusses on corrections and introduces no new features.

Corrections:

2N® Access Commander version 2.3

Changelog 2.3 

2N® Access Commander version 2.3 introduces a new access matrix for quick setup and audit of access permissions, allows backup and restore to be managed from the web GUI and introduces new user authorization settings for increased flexibility.

New Features: 



Improvements:

Corrections:

Required device firmware versions for full feature support

Minimum supported firmware versions (devices prior to these versions will not be synchronised with Access Commander)

---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

2N® Access Commander version 2.2

Changelog 2.2

2N® Access Commander version 2.2 (Beta November 2021 - Production December 2021)

2N® Access Commander version 2.2 introduces support of QR codes as a user credential, enables core functions to be set in the GUI and extends the range of ways a door may be controlled.

The maximum PIN code length will change to 9 digits in this version. PIN codes of 10 digits or more will automatically be represented as a QR code after updating, although they may still be entered as PIN codes on a keypad. To avoid this behavior, ensure PIN codes are shorter than 10 digits

Support of QR code reading in IP Style requires firmware version 2.34, which may be released several weeks after Access Commander version 2.2

2N® Access Commander version 2.2 introduces support of QR codes as a user credential, enables core functions to be set in the GUI and extends the range of ways a door may be controlled.

New Features: 






 

Improvements:

 

Corrections:


Required device firmware versions for full feature support:


Minimum supported firmware versions (devices prior to these versions will not be synchronised with Access Commander):

---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

2N® Access Commander version 2.1

Changelog 2.1

2N® Access Commander version 2.1 (Beta August 2021 - Production September 2021)

2N® Access Commander 2.1 introduces powerful new features aimed at user management and controlling the flow of people.

New Features:

Improvements:


Corrections:

Required device firmware versions for full feature support

Minimum supported firmware versions (devices prior to these versions will not be synchronised with Access Commander)

---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

2N® Access Commander version 2.0

Changelog 2.0

2N® Access Commander 2.0 is a major new release which brings great changes to the user interface, as well as powerful new features and improvements. Along with these changes, the license model of Access Commander has also been changed. All users with existing licenses will be migrated to the appropriate new license automatically and free of charge, ensuring you continue to benefit from the same functionality.

WE RECOMMEND EXISTING USERS RENEW THEIR LICENSE WITHIN 5 MINUTES OF UPDATE

 New Features:


Improvements:


Corrections:


Required device firmware versions for full feature support


Minimum supported firmware versions (devices prior to these versions will not be synchronised with 2N® Access Commander)

---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Changelog 1.17.0

## If Access Commander is updated before IP Intercom and Access Unit firmware 2.31.x is available then some newer functions may not be fully supported. Please note the minimum supported firmware in this version is 2.29.x. Please also note that the default 2N SMTP server will no longer be available in version 1.17.0. We suggest you ensure your own SMTP server settings are defined upon update, if you have not already done so, to ensure system and notification messages continue being sent##

New Features:

Improvements:


Corrections:

Required device firmware versions for full feature support

Minimum supported firmware versions (devices prior to these versions will not be synchronised with Access Commander)


Changelog 1.16.0

## Please note that the default 2N SMTP server will no longer be available in version 1.17.0. We suggest you ensure your own SMTP server settings are defined now, if you have not already done so, to ensure system and notification messages continue being sent upon update to 1.17.0 later this year ##

New Features:

Improvements:

Corrections:

Required device firmware versions for full feature support

Minimum supported firmware versions (devices prior to these versions will not be synchronised with Access Commander)

Changelog 1.15.1

## Please note that, due to major improvements in the presentation of logs, direct update update to version 1.15.1 from version 1.14.0 may take longer than usual. These changes mean that logs over a year old may not be retained during the update. We suggest that you export your logs before updating if you wish to archive those older than one year. ##

Improvements:

Corrections:

Changes:

Required device firmware versions for full feature support

Minimum supported firmware versions (devices prior to these versions will not be synchronised with Access Commander)

Changelog 1.15.0

## Please note that, due to major improvements in the presentation of logs, the update to version 1.15 may take longer than usual. Please plan your update accordingly. Please also note that the default 2N SMTP server is to be discontinued in version 1.16.0. We suggest you ensure your own SMTP server settings are defined now to ensure full feature functionality upon update to 1.16.0 later this year. ##

New Features:

Improvements:

Corrections:

Required device firmware versions for full feature support

Minimum supported firmware versions (devices prior to these versions will not be synchronised with Access Commander)

Changelog 1.14.0

New Features:

Improvements:

Corrections:

Required firmware versions for supported devices

Minimum supported firmware versions (devices prior to these versions will not be synchronised with Access Commander)

Changelog 1.13.0

New features in version 1.13.0:

Improvements in version 1.13.0:

Corrections in version 1.13.0:

 Reqired firmware versions for supported devices:

Changelog 1.12.1

Improvements in version 1.12.1:

Corrections in version 1.12.1:

 Reqired firmware versions for supported devices:

Changelog 1.12.0

New features in version 1.12.0:

Improvements in version 1.12.0:

Corrections in version 1.12.0:

 Required firmware versions for supported devices:

Changelog 1.11.1

Improvements in version 1.11.1:

Corrections in version 1.11.1:

 Required firmware versions for supported devices:

Changelog 1.11.0

Features in version 1.11.0:

The Enhanced security or Gold license is required for all border 2N IP intercoms within an area to enable the Anti-passback function.
See https://wiki.2n.cz/acc/latest/en/5-rozsireni/5-7-anti-passback for further details.

Improvements in version 1.11.0:

Corrections in version 1.11.0:

 Required firmware versions for supported devices:

Changelog 1.10.0

Features in version 1.10.0:

Improvements in version 1.10.0:

Improvements in version 1.10.0:

Required firmware versions for supported devices:

SYSTEM UPGRADE - IMPORTANT INFORMATION!

Due to the transition from Linux Debian version 7 to version 9, the online upgrade from 2N® Access Commander version 1.9.1 to the version 1.10.0 is not available. However, you may easily upgrade your system to the latest version following way:

  1. Run your existing 2N® Access Commander system version 1.9.1 as usual
  2. Go to the administration console of (1) and enable the SSH connection. Root password change might be requested.
  3. Install a fresh new 2N® Access Commander system version 1.10.0 (https://www.2n.cz/en_GB/support/documents/software#filter-product-2n-access-commander)
  4. Go to the administration console of (3), login as root (default pass '2n', change required) and choose 'Backup and restore - Import configuration from another Access Commander'
  5. Enter the IP address and root login credentials of (1)
  6. The complete configuration backup gets uploaded to the new 2N® Access Commander, the originating system gets suspended
  7. Keep using (3), uninstall (1).

Changelog 1.9.1

 Improvements in version 1.9.1:

 Corrections in version 1.9.1

 Required firmware versions for supported devices:

Changelog 1.9.0

Features in version 1.9.0:

Improvements in version 1.9.0:

Corrections in version 1.9.0:

Required firmware versions for supported devices:

Changelog 1.8.0

Features in version 1.8.0:

Improvements in version 1.8.0:

Corrections in version 1.8.0:

Changelog 1.7.0

Features in version 1.7.0:


Improvements in version 1.7.0:

Changelog 1.6.1

Improvements in version 1.6.1:

Changelog 1.6.0

Features in version 1.6.0:

Improvements in version 1.6.0:

Changelog 1.5.0

Features in version 1.5.0:

Improvements in version 1.5.0:

Changelog 1.3.3

Changelog 1.3.2

Changelog 1.3.0

Changelog 1.2.2

Changelog 1.2.1

  • Since the upgrade mechanism has been changed in this version, it is necessary to run the upgrade twice. After the first execution, the upgrade mechanism itself gets upgraded and the system will still show the original version number. When the upgrade is run for the second time, a regular upgrade downloads a new system version. We’re sorry for inconvenience.

Changelog 1.2.0