2N Access Commander version 3.6.2 (July 2026)
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.
Changes and bugs fixed in 3.6.2
- Adds support for 2N OS firmware 3.3.0.
- Supports the new Axis A9210, A9910 and A9920 relays via 2N OS devices for lift access control.
- Fixes an issue where warning logs in the Call logs may fill up disk space.
Bugs fixed in 3.6.1
Addresses a critical bug that affects a small number of Access Commander Box installations and My2N app pairing.
New Features in 3.6
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.x
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