Connect a device and issue its token

What this achieves

A registered device still has to be pointed at Humavera before it sends anything. The device record carries the address, the token state, and the steps to follow on the terminal itself.

Required role: Administrator.

Before you start

Register the device first, and keep the ingest token issued at that moment. It is displayed once and cannot be shown again.

Steps

Go to Time & Attendance → Attendance Machines and open the device.
Find Device setup.
Under Point the device at this URL, select Copy.
Follow the numbered steps shown there on the terminal itself.
Where a token is required, set the device’s token to the one issued at registration.
Reboot the terminal.
Return to the device record and check Last seen.

What the setup panel gives you

The panel is written to be handed to whoever configures the terminal, which is often not the person who registered it.

Option	Description
Point the device at this URL	The address the terminal sends punches to. Copy it rather than retyping it.
Protocol	The protocol this device is registered for.
Ingest token	Whether a token is required. Where one is, the last few characters are shown so you can confirm you are holding the right one.
Allowed IPs	The source addresses accepted, or Any where none were set.
API key	Whether a key is required.

The numbered steps on the panel cover the terminal side: where to find the server settings in its menu, what to enter, and to reboot afterwards. Follow those rather than a set of instructions written for a different model.

Confirming the token you hold

The panel shows the last few characters of the token rather than the token itself. That is enough to tell one token from another when you are holding several.

If what you hold does not match, you cannot recover the original. Remove the device and register it again to be issued a new one, then reconfigure the terminal with it.

When the address is unavailable

Where the panel shows that the endpoint is unavailable, the server address your workspace publishes has not been configured, so the device address cannot be built.

There is nothing to correct on this screen. Raise it with whoever administers your Humavera deployment — no terminal can be pointed anywhere until it is resolved.

Confirming it worked

A device shows as never connected until its first punch. After that, Last seen carries the time it was last in contact, and Recent punches lists what has arrived from it.

The setup steps say to expect the device to appear within a minute of its first punch. If nothing arrives, the usual causes are a mistyped serial, a token the device is not sending, or a source address outside the allowed list.

Example: a terminal at the Manchester site is configured and rebooted, and Tom Hargreaves punches in. Within a minute the device shows a last-seen time and his punch appears in the recent list.

What happens next

Punches from the device flow into the same attendance days that self-service check-in produces, and are reviewed and approved the same way. Punches arriving under a number Humavera does not recognise are held as unrecognised rather than discarded, so check that list once a device is live.