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.
Finish first: Add a biometric, RFID or face terminal
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.
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.
You should see: The same pipeline processes those events; repeats of the same user and time are ignored.
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".
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.
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.