Your ZKTeco terminal can already send every punch to the cloud on its own. It just has not been told where. On most ZKTeco models that instruction lives in one menu, usually called Cloud Server or ADMS, and filling it in takes a few minutes. Most failed setups come down to two settings, not the hardware.
This guide walks through connecting a ZKTeco terminal to Wurxa over ADMS push, step by step, exactly as the Add device flow in Wurxa runs it. It also covers the four things that stop a terminal connecting, so you can fix them before you call anyone.
What ADMS push is, in one paragraph
ADMS is the protocol ZKTeco terminals use to talk to a server. With it switched on, the terminal calls out over the internet to the address you give it, sends each punch as it is recorded, and checks in regularly for commands such as "enrol this person" or "send me last month's punches". The terminal starts the connection, so you need no static IP, no port forwarding and no PC on site. If the internet drops, the terminal keeps the punches in its own memory and sends them when it reconnects. We go into the detail in what happens to attendance when the internet goes down.
Before you start: a five-minute checklist
The terminal is usually the quick part. The wait is getting the right person and the right password to the device, so line these up first:
Wurxa is confirmed on the SpeedFace V4L, V4L Pro, V5L, F18 and K40. Other ZKTeco terminals that support ADMS push connect the same way; the Add device flow has a "Not sure which model" option that lists the common menu paths.
Step 1: Find the serial number
Wurxa claims each terminal by its serial number, so it knows the punches are yours. On the terminal, go to Menu > System Info > Device Info and read the Serial Number. It is also printed on a label on the back or side, marked S/N, but reading it on screen saves taking a wall-mounted unit down.
Step 2: Start Add device in Wurxa
Wurxa now shows the exact menu path for your model and the settings to type in. Keep this screen open beside you at the terminal.
Step 3: Enter the cloud server settings on the terminal
The menu path depends on the model and its firmware:
Some builds label the same screen ADMS or ADMS Settings. On it, set:
Save, and back out of the menu.
Step 4: Test the connection
Back in Wurxa, click I've entered the settings, test connection, then Start test. Wurxa waits for that exact serial number to call in, so a different terminal on the same network cannot be mistaken for yours.
Most terminals check in within a minute or two. If nothing arrives after three minutes, Wurxa says so and shows the likely causes. Jump to the troubleshooting section below.
Step 5: Name the terminal and give it a site
When the terminal connects, give it a Device name and choose its Site. The site is required, and it matters: it decides whose punches this terminal accepts and whose working hours, rest days and time zone they are measured against. Choose the site the terminal is physically at.
Direction (entry only, exit only or both) and Location in building are optional. Click Save & confirm device.
Step 6: Do a test punch
Walk to the terminal and tap it as Wurxa asks. When you see Device setup complete, the terminal is live, and every punch from now on lands on the Time board as it happens.
Step 7: Bring in the history and the people
Two things make the first month useful rather than empty:
When the terminal will not connect
The Wurxa test screen lists these, in the order they usually turn up:
And check HTTPS once more. It is the setting most often left on.
After setup: knowing it stays connected
A connected terminal is not the end of the job. Power gets cut, cables get moved, a router gets replaced, and a terminal that stops sending looks exactly like a quiet day.
Wurxa decides a terminal's health from the last time it actually made contact, not from what the terminal last said about itself. A terminal is Online if it checked in within the last 15 minutes and is marked Offline after two hours of silence, with a warning in between. If it goes quiet for over an hour, the owner and IT admin get an alert in the app and by email. When it is back, Pull data collects what it stored while it was away. Nothing is lost as long as the terminal kept power to its memory.
Connect your first terminal today
Wurxa is cloud attendance software built around the ZKTeco terminals UAE businesses already own: no server on site, no CSV exports, punches arriving live, and lateness, overtime at 125% and 150%, rest days and public holidays worked out from the raw punches for every site. Read how it works on the Wurxa for ZKTeco page, or see the full Wurxa Attendance product.
Wurxa is free for up to 5 employees on one site, and every new workspace starts with a 14-day trial with every feature and no card. Create your workspace, add your site, and have your first terminal sending punches before lunch.
Put the workflow into practice.
Start with every Wurxa feature for 14 days. No credit card required.
