Unibandh · Help centre
Recording planSign in
Unibandh · School management for Indian schools · Home
    Help centre/Attendance: daily register, alerts, devices and check-in/Lesson 7

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

    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.

    Open /attendance/devicesRecording script
    10 min6 stepsOwner, Admin, PrincipalDemo: sign in as Owner

    Before you start

    Finish first: Add a biometric, RFID or face terminal

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

    Steps

    0 of 6 done
    1. You should see: 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.

    2. You should see: 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".

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

    3. You should see: The same pipeline processes those events; repeats of the same user and time are ignored.

    4. You should see: 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".

    5. You should see: A table of Time, Device user id, Person, Direction and Result badges for the last 200 punches of this device.

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

    6. You should see: 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.

    What you have now

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

    If something goes wrong

    Last seen stays Never
    Check the serial number matches the terminal exactly, that the server address has no http:// or path, and that the school firewall allows outbound HTTPS. The terminal polls every 10 seconds.
    Every punch shows Unmatched
    The terminal's user ids are not mapped yet. See the mappings lesson; resolving a mapping re-processes waiting punches.
    Punches show Outside window
    Widen Accept punches from / until on the device, or check the terminal's clock and timezone.
    Only ATTLOG is consumed; remote user sync does not work
    By design: Unibandh never pushes commands to terminals. Enrol fingerprints on the terminal itself and map the ids here.

    Related guides

    • Map device user ids to people and resolve unmatched punches
    • Marking rules and the auto-absent sweep
    Add a biometric, RFID or face terminalNext: Map device user ids to people and resolve unmatched punches