Unibandh · Help centre
Recording planSign in
Unibandh · School management for Indian schools · Home
    Help centre/Attendance: daily register, alerts, devices and check-in/Connect a ZKTeco or eSSL terminal (ADMS) and test it/Script

    Recording script: Connect a ZKTeco or eSSL terminal (ADMS) and test it

    6 shots · about 1 min 03 s of finished video · lesson 7 of Attendance: daily register, alerts, devices and check-in

    Record as

    Owner (demo_owner)

    Sign in at /demo on a demo-mode build

    Screens

    /attendance/devices/[id] /attendance/devices

    Length

    1 min 03 s

    narration at ~150 words/min + screen time

    Status

    Not yet recorded

    Before recording

    • The device is added with the correct serial number.
    • The terminal is on a network with internet access.

    Intro voice-over

    Point the terminal's cloud server setting at Unibandh, confirm Last seen updates, send a test punch through the real pipeline and read the event log.

    #ScreenAction (on screen)Must be visibleVoice-over~s
    1/attendance/devices/[id]Open the device from Attendance → Devices.The header shows type, vendor, location and "SN <serial>". The Connection card reads "ADMS push: the terminal polls this server; no port forwarding needed." with the terminal menu path and the endpoints; a Test card; then Mappings and Events.ADMS means the terminal calls out to the server, so the school needs no fixed IP or router changes.12
    2/attendance/devices/[id]On the terminal go to Menu → Comm. → Cloud Server Setting (older firmware: ADMS). Set Enable domain name on, Server address to your Unibandh host (no path), Server port 443 with HTTPS on (older firmware without HTTPS: 80 behind the school's reverse proxy), Enable proxy server off. Save and reboot the terminal.

    Callout: Set the terminal clock to IST, or set the device's Timezone in Unibandh to match the terminal.

    Within about ten seconds the Connection card's "Last seen" line and the Last seen badge in the device list change from "never" to "Just now".On the terminal itself, point the cloud server setting at Unibandh. No port forwarding is needed.10
    3/attendance/devices/[id]For a generic reader or middleware instead of ADMS, read the "Generic JSON" line: POST to /api/devices/events with Authorization: Bearer <token> and a body like { "events": [{ "userId": "101", "at": "2026-09-01T08:05:00+05:30", "direction": "in" }] }.The same pipeline processes those events; repeats of the same user and time are ignored.Other readers or middleware can push the same punches as JSON with the device token.10
    4/attendance/devices/[id]In the Test card type a Device user id that exists on the terminal (in the demo, 1001), choose Direction In and click Test punch now.A toast: "Punch marked" (mapped and inside the window), "Punch stored as unmatched" (no mapping yet), "Punch ignored as duplicate" (a punch within the duplicate window exists) or "Punch outside window / not markable".The test button sends a real punch through exactly the same rules as the terminal, so you can check mappings and rules without walking to the gate.15
    5/attendance/devices/[id]Scroll to Events and use the filters All, Marked, Unmatched, Duplicate, Outside window.

    Callout: Punches older than 31 days or more than 5 minutes in the future are dropped; the terminal is still acknowledged so it stops resending.

    A table of Time, Device user id, Person, Direction and Result badges for the last 200 punches of this device.The event log shows every punch and what happened to it.8
    6/attendance/devices/[id]Check the student's register: open Attendance for today.A student whose first IN punch arrived before the late cutoff shows P; after it, L. Staff punches write the HR attendance register with in and out times.Back on the Attendance page, the punches have become marks.8

    Outro voice-over

    • The terminal is talking to Unibandh and punches mark the register in real time.

    After the video is published

    Add its YouTube id under attendance-device-adms in src/lib/help/videos.ts, with a chapters map of step number → seconds. The lesson page then shows the video and a “Watch this step” link on every step. See the video production guide.