Supported model families
F18, F22, MA500, MB20, K14, K50, ProFaceX and related LAN TCP-IP terminals, subject to confirming your exact model.
Home / ZKTeco device support
ZKTECO DEVICE SUPPORT
Which ZKTeco models work, and how to check yours.
Almost every "my biometric device is not working" report is a network setting, an unmapped user ID or a clock that has drifted — not a hardware fault. Here are the supported families, the four settings that must be right, and a compatibility check you can run yourself.
What Flowwkkr includes
Explore the product area in more detail and see how it fits into the wider Flowwkkr HR workspace.
Network requirements
LAN or TCP-IP mode, a static device IP, the SDK port reachable, and device time synced to a reliable source.
Fifteen-minute check
Ping the device, open the SDK port, confirm the mode, compare the clock and export a punch list. All five, before any conversation.
Common problems explained
The symptom tells you the cause. Agent cannot find the device, punches with nobody present, times an hour out, hours doubled.
Enrolment quality matters
A terminal that records most staff but not a few is usually an enrolment problem rather than a device fault.
Changing model later
Employee records and history stay in Flowwkkr. A new device only needs its user IDs mapped.
What ZKTeco Device Support actually does
Most "my biometric device does not work" problems are not device faults. They are network reachability, an unmapped User ID, or a device clock that has drifted. This page lists the model families the Flowwkkr agent works with, the network settings that must be right, and a compatibility checklist you can run yourself in fifteen minutes.
ZKTeco Device Support is the set of ZKTeco biometric terminal models, network configurations and enrolment practices that Flowwkkr has been verified to sync with, plus the checks that confirm a given device is compatible.
Supported model families
Device firmware revisions vary within a family. The list above is a guide, not a guarantee, which is why we confirm the exact model on a demo rather than from a datasheet.
| Family | Typical models | Interface | Flowwkkr support |
|---|---|---|---|
| Fingerprint / face LAN terminals | F18, F22, MA500, MB20 | LAN TCP/IP, ZKTeco SDK | Supported |
| Fingerprint + face + card | K14, K50, ProFaceX | LAN TCP/IP, ZKTeco SDK | Supported |
| Time and attendance terminals | u580, u260 | LAN TCP/IP, ZKTeco SDK | Supported — confirm model |
| SpeedFace / face-focused | SpeedFace-V5L, V5L | LAN TCP/IP, SDK | Confirm per model |
| Standalone, no network | e.g. offline-only units | No LAN SDK | Not supported — network required |
| Cloud-hosted terminals | Cloud-managed models | Vendor cloud only | Not supported — check with us first |
Network requirements
Every ZKTeco sync problem is a network problem until proven otherwise. These four settings are the ones that matter.
| Setting | Required value | Why it matters |
|---|---|---|
| Communication | LAN / TCP-IP (not standalone, not cloud-only) | The agent reads the device over the network |
| Device IP | Static, on the same subnet as the agent | A DHCP address can change after a reboot |
| SDK port | 4370, or 80 if the device uses HTTP | Must be reachable and not filtered by a firewall |
| Device time | Synced to a reliable NTP source | Drift corrupts every late and overtime figure |
The fifteen-minute compatibility check
You can confirm most of this yourself, before any conversation with a vendor. From the Windows machine that will run the agent:
- Ping the device IP — it must reply consistently
- Open the SDK port in a browser, for example http://DEVICE_IP:4370 — it should respond rather than time out
- On the device itself, confirm the communication mode is LAN or TCP-IP, not standalone
- Note the device clock and compare it to your PC — flag anything beyond a minute or two
- Export a short punch list from the device and confirm the records include User ID and timestamp
Common problems and what they actually mean
The symptom tells you where to look. Treating the wrong cause is what turns a ten-minute fix into a two-day one.
| Symptom | Most likely cause | Fix |
|---|---|---|
| Agent cannot find the device | Wrong IP, different subnet, or port blocked | Fix the address; open the SDK port |
| Punches arrive but nobody is marked present | Device User IDs not mapped to employees | Bulk-map IDs to employee records |
| Times are hours out | Device clock drift or wrong time zone | Set NTP sync, then re-check |
| Hours look doubled | Same punch relayed twice | Duplicate-safe ingestion prevents this; verify sync settings |
| Night shift staff always absent | Calendar-day logic in the software, not the device | Needs shift-aware calculation, not a device fix |
| A few employees never register | Poor enrolment quality | Re-enrol with a clean, dry finger or a better camera angle |
Enrolment quality is a support issue too
A terminal that records a punch for everyone except a handful of staff is usually an enrolment problem, not a hardware fault. Fingers that are too dry, or enrolled before washing, produce unreliable templates. Re-enrol those staff properly and the reliability improves immediately.
Frequently asked questions
How do I know if my ZKTeco model is supported?
If it is a LAN or TCP-IP terminal exposing the ZKTeco SDK — typically on port 4370 — it is very likely supported. The definitive check takes five minutes: ping the device IP and open port 4370 in a browser. Bring the model number to a demo for a firm confirmation.
Can I use a ZKTeco device if it is in standalone mode?
Not for automatic syncing. A standalone device has no network interface for the agent to read, so punches would have to be exported manually, which is the problem the integration exists to solve. If the device supports LAN mode, switch it.
What happens if we change ZKTeco models later?
Employee records, attendance history and leave balances stay in Flowwkkr. A new device only needs its User IDs mapped, so you are not re-entering historical attendance.
Do you support more than one ZKTeco device at a site?
Yes. Device counts are included per plan, and each device relays through the agent on your network. Additional devices or sites can be covered by additional sync agents.
Can you help if our device is not on the supported list?
Tell us the model on a demo call. Where a device is close to supported, we can usually confirm the interface directly, and we will say plainly if it is not viable rather than selling an integration that will not hold up.
See it against your own requirements
Bring your device model, shift pattern and employee count. We will confirm fit on a private 2-hour demo.
See Flowwkkr in action
Request a private 2-hour live demo and explore the HR workflow.