Connecting a fingerprint device to a cloud attendance system does not need a technician in every branch, software on a PC or a static IP address. The device sends punches to the system over the internet by itself. These steps are written for ZKTeco devices because they are the most common; menu names can differ a little between models and firmware versions.
Before you start
- Check the device supports cloud push: the communication menu (Comm.) should have a Cloud Server Setting option, also known as ADMS.
- The device’s serial number: under System → Device Info, or on the label on the back. The system identifies the device by this number.
- An internet connection where the device is: a network cable from the router, or Wi-Fi if the device supports it.
Step 1: Add the device to the system
Register the device in the attendance system with its serial number, name and branch. The system then shows the server address and port to enter on the device.
Step 2: Connect the device to the network
Under Comm. → Ethernet:
- Turn on DHCP so the device takes its address from the router automatically; this is the easiest.
- Or enter the IP address, subnet mask, gateway and DNS by hand. Without a working DNS the device cannot find the system’s address.
Step 3: Set the date and time
Under System → Date/Time, check the date, time and time zone. A wrong time records punches on the wrong day or hour, and stops the secure (HTTPS) connection from working.
Step 4: Enter the system’s address
Under Comm. → Cloud Server Setting:
| Setting | Value |
|---|---|
| Server Mode | ADMS (if the option exists) |
| Enable Domain Name | On |
| Server Address | The address the system shows |
| Server Port | 443 with HTTPS on |
| Enable Proxy Server | Off |
Save. Some models ask for a restart.
Step 5: Check and approve the device
Within minutes the device connects and appears in the system. Where the system approves devices before accepting their punches, a company administrator approves it and punches start to arrive. Record a test punch and check that it shows.
Step 6: Match employees to the device
A punch arrives from the device with only a user ID. Each employee’s number on the device must therefore match the number recorded for them in the system, or the punch arrives without being assigned to anyone. Check the numbers when you move employees across, and whenever a new employee is enrolled on the device.
Common problems
| Problem | Likely cause |
|---|---|
| The device never connects | DNS not set, the address mistyped, or the network blocks outgoing connections |
| It connects, then drops with HTTPS | The device’s date or time is wrong |
| It connects but punches are not assigned | User IDs on the device do not match employee numbers in the system |
| The old software stopped receiving | A device sends to one address only, and it now points at the new system |
| Old punches appeared after connecting | Normal: the device sends any stored punches it had not sent yet |
What about Hikvision and Suprema devices?
The idea is the same: the device is set to the system’s address and sends events by itself, but the menus are named differently. Send the device model to the provider for the steps for that model.
IdaraSuite
In the IdaraSuite attendance system you add a device by its serial number and get a setup screen with the address, port and steps, then follow on the devices screen which devices are still sending and when each last did. On ZKTeco devices the system can add new employees to the device and remove leavers, without the fingerprints themselves ever moving. For how cloud connection differs from traditional software, see cloud attendance system: how it works.
This article is general information, not legal advice. Laws and regulations change; refer to the official text in force or to a legal adviser before making a decision.