Release

2023-10-05

New features and improvement

1. Supports Template on Mobile.
2. Improved face anti-spoofing performance when Operation Mode is set to Fusion Matching and Fake Detection is set to Normal.
3. Fixed strings in the Use QR as Card menu.
4. Separated event code for QR authentication.
5. Added Voice Instruction.
6. Updated Japanese regulatory certification electronic notation.

Bug Fixes

1. The Server URL for device's Device ▶ Server Connection in BioStar 2 does not appear on the device configuration. (Affects version: v1.0.1)
2. Authentication result does not appear when authenticating with entering ID followed by an action returning to home screen after entering the menu as an administrator. (Affects version: v1.0.0)
3. The screen overlaps when swiping to scroll the Event Log list screen. (Affects version: v1.0.0)
4. When authenticating with ID + PIN on a device connected as a slave, the user ID is displayed but the user name is not displayed. (Affects version: v1.1.1)
5. Firmware upgrade succeeds with an invalid resource file. (Affects version: v1.0.0)
6. When upgrading firmware, resource file included in the firmware does not get updated. (Affects version: v1.0.0)
7. When user information is sent from BioStar 2 to a master device that does not have 1:N authentication mode, 1:N authentication fails on the device connected as a slave. (Affects version: v1.0.0)
8. Restart log is not logged in the device's Event Log when the master device is restarted. (Affects version: v1.0.1)
9. The device turns off when the user Format Card in BioStar 2. (Affects version: v1.0.0)
10. Device freezes or restarts when continuously authenticating with an EM card. (Affects version: v1.0.0)
11. When devices are connected as a master-slave and the door is deleted and added again, the door does not open even if authentication has succeeded with the device connected as a slave. (Affects version: v1.0.0)
12. Fixed string for scheduled lock zone violation. (Affects version: v1.0.0)
13. Fixed smartcard output byte order setting. (Affects version: v1.1.0)

  • When using Wiegand or OSDP output, it is fixed to be affected by the smartcard output byte order when the Wiegand output information is set to send user ID.