Firmware Release 2.3.0

This page outlines the improved functionality included in the firmware update available on Tuesday 16th April 2024.

AI Clocking Analysis improvements

What have we done?

Amended the logic to be more lenient, along with the inclusion of changes for British Summer Time.

Why have we done this?

Allowing the models to be more lenient for device, authentication type and days of the week checks will reduce the number of clockings being flagged. We have also extended the logic to include British Summer Time changes.

How will you benefit?

The AI clocking analysis will continue to use machine learning to identify and flag records, this change will allow the AI clocking analysis learning models to continue to learn behaviours.

Details of the change

All changes have been made to the machine learning models and the end users will not see these changes, they will gain the added support of the models learning behaviours and any British Summer Time changes.

T2 UI Refresh and Logo changes

What have we done?

We have made small improvements to the T2 user interface, this includes a change to the Advanced Logo.

Why have we done this?

To improve user 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 will improve the navigation for end users.

Reboot if fingerprint sensor disappears

What have we done?

We have added additional monitoring of the fingerprint sensor, we periodically check the device and identify if it is not working

Why have we done this?

We have had reports where fingerprint sensors appear to stop working.

How will you benefit?

Increased stability of fingerprint sensors.

Details of the change

Additional monitoring of the fingerprint sensor will now identify if the sensor is no longer working, and will reboot to attempt to re-establish a connection.

Device recovery from Disk Errors

What have we done?

We have added a script to check the status of partitions on boot and repair errors detected.

Why have we done this?

To improve Device stability.

How will you benefit?

Device stability will be improved leading to less Engineer sites visits.

Details of the change

A script has been added to check the status of partitions when the devices boot up and attempt to repair any errors it finds. All results are logged for monitoring.

Reboots from unreliable networks

What have we done?

We have put in changes to resolve reboots that can occur on customers sites where the network connection can be unreliable.

Why have we done this?

To reduce the number of reboots that the device is doing when connecting and disconnecting from the network.

How will you benefit?

Increased Device stability and uptime.

Details of the change

Changes have been made to avoid multiple device reboots, where there are unreliable networks.

Disable connections to open Wi-Fi networks

What have we done?

We have disabled the ability to connect to open Wi-Fi networks.

Why have we done this?

To improve the security around our devices connection to Wi-Fi networks.

How will you benefit?

This change will ensure devices are secure and unable to connect via an open Wi-Fi network.

Details of the change

The list of networks will now exclude any open networks and will not allow these to be selected from the devices by the end users.

Support Wi-Fi connections on channel 12 and 13

What have we done?

Extended our support of Wi-Fi channels to include 12 and 13.

Why have we done this?

These channels were previously not supported as they are allowed in the UK but not in some countries.

How will you benefit?

UK customers will now have access to channel 12 and 13.

Details of the change

Wi-Fi in the UK is allowed to use channel 12 and 13, but in some countries it’s not, this was previously disabled by default. This change will now allow access to channel 12 and 13 for UK.

Disable local Prox reader setting

What have we done?

Allow the local prox reader to be disabled via the Device and Access Manager portal.

Why have we done this?

Previously when the local prox reader had been disabled the prox cards were still being read.

How will you benefit?

Users now have the ability to disable the reader and prox cards will no longer be read from a disabled reader.

Details of the change

Once the local prox reader is disabled via the Device and Access Manager portal, prox card will not longer be read by the reader.