Firmware Release 2.4.2

This page outlines the improved functionality included in the firmware update available on Friday 12th July 2024.

Display IP Address and Firmware version on Login Screen

What have we done?

Updated the login screen of the T2 to display the IP Address and Firmware version of the Device.

Why have we done this?

To make it easier for users to identify the IP Address and Firmware version on the device.

How will you benefit?

This will allow user to identify the Device information quicker.

Details of the change

IP Address and Firmware version now displayed on the Device login screen.

Support for Fingerprint reader hardware

What have we done?

Added additional support in the Firmware around the hardware fix for the Fingerprint sensor.

Why have we done this?

Some users were reporting that in certain environments the fingerprint sensor seemed to be locking. This is temporarily resolved by a reboot of the device.

How will you benefit?

This change will only benefit users with affected terminals.

Details of the change

A hardware change has been made to a small number of affected devices, this Firmware change will support the Hardware fix in place on these devices.

Improved speed of face matching

What have we done?

Improved the speed in the face matching on the device.

Why have we done this?

To increase the speed of facial recognition and clocking using face on the device.

How will you benefit?

End users will benefit from an increase speed in clocking when using facial recognition.

Details of the change

Speed improvements have been made to allow less of a gap between consecutive face matches, allowing a greater throughput of users when clocking with their faces, and less delay between each clocking.

Use default liveness values for users who didn't enrol with face liveness enabled

What have we done?

If face liveness detection is enabled, then all users will be prompted to turn their head when clocking, regardless of whether liveness data was collected when they enrolled their face.

Why have we done this?

To improve security of face clocking, and make it easier to enable liveness detection at a device

How will you benefit?

If your users have already enrolled their faces, you will be able to enable liveness at a device without having to re-enrol the users. Users can still be re-enrolled to collect better liveness data and improve the accuracy of the checks

Details of the change

If face liveness detection is enabled, then all users will be prompted to turn their head when clocking. If they were enrolled without face liveness enabled, then default values will be used to perform the liveness check. The default values are expected to work for the majority of users, but performance will still be improved by enrolling with liveness enabled.

UX Review - Diagnostics Screens

What have we done?

We have continued with a UX Review and have now extended this to the Diagnostics screens of the T2.

Why have we done this?

To improve navigation and usability.

How will you benefit?

Easier to navigate.

Details of the change

Slight changes have been made to the user interface on the T2 devices, which improve the navigation for end users.

Custom hostname

What have we done?

Allow users to enter a custom hostname.

Why have we done this?

To support users wishing to enter a custom hostname.

How will you benefit?

By defining unique hostnames for each device users can more easily monitor device status on their network.

Details of the change

A custom hostname can be defined on the device for both Ethernet and Wi-Fi networks.

Custom DHCP timings

What have we done?

Allow users to enter custom DHCP timings.

Why have we done this?

To support users wishing to amend the DHCP timings.

How will you benefit?

By customising DHCP settings on the device it may be possible to resolve network connectivity issues in some cases.

Details of the change

Custom DHCP retry count and interval can be defined on the device for both Ethernet and Wi-Fi networks.