How-to guides Biometric devices

Troubleshoot a biometric device that will not connect

A checklist for a terminal that shows Offline, or scans that do not turn into attendance.

By Aajar team · · 3 min read

Most connection problems come down to a few causes. Work through them in this order. Everything below happens on Biometric Devices (Business plan), and the device row tells you what Aajar last heard.

The device shows Offline or never came online

  1. Internet on the terminal. Check the WiFi, LAN cable or SIM. Try opening any website from the same network.
  2. Address and port. Press Setup on the device row and type the server address and port into the terminal exactly as shown, without https:// or a slash. If port 443 does not work on your model, try port 80.
  3. Serial number. It must match the label on the terminal exactly.
  4. Comm Key. If the terminal asks for one, type the key from Setup. If it was changed, press New key and type the new one.
  5. Paused. A device you paused is ignored. Press Resume.
  6. Hikvision and Matrix COSEC. These use a secret link instead of a serial number. If it was copied wrongly or has leaked, press New link and paste the new one into the device.

The device says Online but the Latest scan is "No scan yet"

Online only means the terminal can reach Aajar. It does not mean it has sent any scans. Check these on the terminal, then open Setup → Messages received on its row and scan once:

  1. Cloud Server / ADMS must be ON (Menu → Comm. → Cloud Server Setting). Some eSSL models also have Upload on real time or Realtime upload; turn it on.
  2. Scan after it is online. Press Refresh on Messages received. A row starting Scans uploaded means the scan arrived. If you only see Handshake rows, the terminal is not sending scans: re-save the Cloud Server settings, restart the terminal, and check its date and time.
  3. Same serial number on the terminal label and in Aajar. Two terminals need two rows.
  4. Enrolled users. A scan only counts when the person has been enrolled on that terminal. A "not registered" scan on the terminal is never sent.
  5. After the fix is applied, the terminal sends the scans it still holds (including earlier ones) within a few minutes. Anything from a number nobody has yet is kept as Unmatched until you set that Biometric ID on the person.

Also fill each person's Biometric ID (the number they were enrolled with on the terminal) under Employee biometric IDs. Without it scans are kept as Unmatched and attendance does not appear for the person.

The device is online but attendance is missing

  • Unmatched scans. Open Punch log and tick Show only unmatched. A scan from a number nobody has yet waits there. Set that number on the right person under Employee biometric IDs and it is applied straight away.
  • Wrong time. Check the terminal's date and time, and the Timezone under Settings → Work Hours. Scans are read in that time zone.
  • Days off. A scan on a holiday or week off counts as extra hours, not as a working day.
  • Days corrected by hand. Imports never overwrite them.

The model has no push setting

Export the log and upload it under Import a device's log. Choose the raw punch or transaction report, one line per scan, not a daily summary.

Still stuck?

Open Messages received on the device (see "Read the Messages received log") and look at the last few rows. Every device type now shows it.