Connecting an attendance machine

A ZKTeco machine with the push protocol calls the server itself. Nothing is installed at your office, no port is opened on your network, and no computer has to be left switched on.

What that costs is one setup step at the machine and one here, and they have to match.

Before you start

  • The attendance.configure permission. The Owner and HR roles hold it.
  • A plan that includes devices. The machine counts against the limit from the moment you declare it, not from the moment it first connects.
  • A machine on the published list of verified models. Others use the same protocol and usually work; those are the ones we commit to.

Steps

Declare the machine here first

  1. Open Devices.
  2. Enter the Serial number. On a sticker on the back of the machine, and under Menu → System Info.
  3. Give it a Name — "Front door", "Warehouse" — and choose its Branch.
  4. Press Add device.

Until this is done, everything that machine sends is refused. That is the point: a machine nobody declared is a machine anybody could have put on the network, and punches from it would be attendance nobody authorised.

Then tell the machine where to call

On the machine, go to Comm. → Cloud Server and enter the address and port shown on the screen here. They are plain HTTP on port 80, and that is deliberate — the firmware on many of these machines cannot do TLS at all, and pointing one at an HTTPS address is a machine that silently stops sending.

What you should see

The machine's status changes from Waiting for first contact to Online with the time it last called, usually within a minute.

From then on, a punch appears in the attendance grid in about a minute, and the person who made it gets a message in Telegram saying so — which for somebody standing in front of a machine with no screen of their own is the only confirmation there is.

If something goes wrong

That serial number already belongs to another company. — a serial belongs to one company across the whole platform. A machine that turns up at a second company was moved, sold, or typed in wrong, and all three want the same answer.

The machine stays on Waiting for first contact. Check the address and port at the machine, and that nothing on the way has redirected port 80 to HTTPS. That redirect is the single most common cause, and the machine gives no sign of it.

This machine’s clock is {minutes} minutes off. Every punch it sends is stamped with it. — the machine stamps every punch with its own clock, so a machine running six minutes fast marks everybody six minutes early. Set the time at the machine; the server does not override it.

The machine went Offline. It has said nothing for ten minutes. Power and network are the usual reasons. Punches made while it was offline are not lost: the machine keeps them and sends the backlog when it reconnects.

A punch arrived for a month that is already closed. It is stored and flagged, and the closed month is not recalculated. Nothing is discarded; what a late log cannot do is move a month somebody has already been paid for.

Last checked 19/09/2026