ADRO | Admin Documentation

Kiosk Devices & Offline Alerts

Get a text message when a site kiosk goes offline and when it comes back, and see what happened on the device.

How Offline Detection Works

Every kiosk checks in with ADRO once a minute. If a kiosk stops checking in for a few minutes (3 by default), it is marked offline. This happens when the site loses internet, the kiosk loses power, or the device is switched off.

  • You get one SMS when the kiosk goes offline, with the time it was last seen
  • You get one SMS when it is back online, saying how long it was down
  • No repeated messages while it stays offline

Scans made while a kiosk is offline are saved on the device and sent automatically once it reconnects, so no check-ins are lost.

Choosing Who Gets the Alerts

Alerts go to users whose role has the receive device status notifications permission and who have a mobile phone number on their account.

  • Go to Admin → Configuration → Roles
  • Edit or create a role and enable receive device status notifications under the Notifications group
  • Assign the role to a user's project profile to get alerts for that project's kiosks, or to a company-wide profile to get alerts for every kiosk in the company
  • You can also turn the permission on or off for a single user from Users → Profile → Permissions

The Company Admin role has this permission by default. Remove it from the role if company admins should not receive kiosk texts.

On the Kiosk Screen

The bottom of the kiosk's main screen shows how long the device and the app have been running, and the most recent check-in: the camera snapshot, the worker's name, whether it was a check-in or check-out, and the time. Waiting to sync means the scan was saved while offline and will be sent when the connection returns.

When the kiosk is offline, the red banner says why: No internet connection (the site network is down) or Server is not reachable (the internet works but ADRO cannot be reached).

Card + Face Verification

A kiosk can require both the worker's card and their face before it records a check-in. On the kiosk, open Admin → Tools, turn on Face Scanner, then tap Require Card + Face (tap again to turn it off). Workers can present either one first; the kiosk tells them by voice what to do next and has 10 seconds to receive the other.

  • Access granted: the face matches the card holder. The entry is recorded as Card + Face Scan with the camera photo, and the gate opens
  • Access denied: a different face, no face on camera, no card scanned within 10 seconds of the face, a card that doesn't belong to the person on camera, or a worker with no enrolled face photo. Nothing is recorded and the denied relay pulses
  • Face light (night): a light wired to the kiosk (GPIO 19 by default, changeable under Admin → Tools → Relay Pins → Light) switches on after a card scan so the camera can see the worker's face, and switches off as soon as the check ends or the 10 seconds run out — it can never stay on. Test it from Admin → Test
  • Camera fault: if the kiosk's face service or camera is down, cards are accepted on their own so the gate keeps working. The journal notes each card accepted this way

Device Journal

Each kiosk keeps a journal of important events, kept even through restarts and power cuts:

  • Internet lost, server not reachable, and back online (with how long it was down)
  • Reboots, including whether it was a clean shutdown or a power loss
  • App restarts, updates, sync problems, and camera or face scanner problems
  • Every scan

A worker is checked in at most once a minute: after a check-in by card or face, the kiosk refuses the same worker for 60 seconds, whether they scan the card again, look at the camera after scanning the card, or scan the card after the face. The kiosk screen shows Already Checked In and how many seconds are left; refused tries do not restart the wait. A repeated card scan or face match still pulses the door relay, so a worker who did not hear the first click can scan again to open the door, but they are not checked in a second time. A worker who stays in front of the camera opens the door again about every 5 seconds until the minute is up. In Card + Face mode the face alone never opens the door (kiosk app 2.16.9 or newer). A refused card appears in History as an early scan with the reason Already checked in less than 60 seconds ago and a photo from every camera (kiosk app 2.16.4 or newer).

Each pulse keeps the door relay on for 3 seconds by default, whether it comes from a scan or from the admin panel. To change it, open Admin → Tools → Relay Pins on the kiosk, enter a number of seconds in Hold (seconds) (0.1 to 30, e.g. 1.5) and tap Save. The denied relay uses the same time. Each kiosk keeps its own setting (kiosk app 2.16.10 or newer). A card tapped again while the door is still unlocked restarts the time instead of adding to it, so the door always locks that many seconds after the last tap, however often the card is tapped (kiosk app 2.16.11 or newer).

When a face is on camera but doesn't match any enrolled worker, the journal records Face not recognized (at most once every 10 seconds) together with the camera photo. Denied Card + Face scans keep the photo too. Tap View photo on the entry to see who was at the kiosk. The photos stay on the kiosk and are deleted when the journal is cleared. The kiosk never throws away anything it has not sent to the server yet: journal entries, History rows and photos waiting for upload are all kept until they arrive, however long the kiosk is offline (only a nearly full disk, or weeks offline, makes it drop the oldest). Of what the server already has, the kiosk keeps the newest 5,000 journal entries, 5,000 History rows and 300 photos (kiosk app 2.16.6 or newer).

On the kiosk, open Admin → Journal and tap a category to filter. The journal is also uploaded to ADRO, where support staff can review it and request the device's full technical logs.

A kiosk that starts without internet may show the wrong time until its clock syncs. Those journal entries are marked kiosk clock not synced. Kiosks on app 2.15 or newer note how long they had been running when each entry was recorded, so when the entry reaches ADRO before the kiosk restarts, the server works out the real time and shows it, with the time the kiosk clock showed next to it (time corrected by the server). Otherwise the entry says time may be off, and times far in the past or future are moved to the nearest sensible date.

Devices Page (Super Admins)

  • Fetch full logs asks the kiosk for its technical logs with its next check-in. If no logs arrive within 15 minutes, the request expires and the page shows Expired, no answer (the kiosk may be offline or on an older app). You can Cancel request while waiting, or ask again at any time.
  • The device page has four tabs under the status cards: Journal, History, Debug and System Logs.
  • Journal: everything the kiosk recorded. Entries with a camera photo (unrecognised faces, face and Card + Face scans) show a thumbnail; click it to see the photo full size. The type buttons work as a multi-select: click a type to show or hide it, or use All and None. Every type except face (unrecognised faces, which can be many) is shown when the page opens.
  • History: every scan the kiosk handled — accepted, refused and early scans — with the worker, the card, the scan type, whether it reached the server, the reason a scan failed (e.g. unknown card, face does not match the card holder) and the camera photos. On a kiosk with more than one camera, a card scan and a refused Card + Face scan keep a photo from every camera, the one showing the worker's face first, so the person at the kiosk is always on one of them (kiosk app 2.15 or newer). Under the scan time each row shows Uploaded (when the row reached the server). A scan made before the kiosk's clock synced is marked: the time is corrected from the kiosk's uptime and the note shows what its clock said, or says the time may be off when the kiosk restarted before uploading (kiosk app 2.16 or newer). No note is shown when the kiosk's clock turned out to be within a minute of the real time. A name followed by (card not on the kiosk yet) was filled in by the server: the card belongs to that worker, but the kiosk did not have it in its card list when it was scanned (for example, the card was added while the kiosk was offline). The failure reason has its own Error column, and a worker's name links to their user page in the admin when the card belongs to a user on the project. Pick an error in the All errors dropdown to see only those scans: it lists every error the kiosk can give (unknown card, already checked in within 60 seconds, card does not belong to the person on camera, face does not match the card holder, face could not be verified, no enrolled face, no card within 10 seconds), plus any other the kiosk has reported, with the number of scans that had it in the picked days, tick Problems only to see just the failed scans, or search by name or card. Searching a card number (or part of it) also lists that worker's face check-ins, and searching a name also finds the scans the kiosk sent without one. Use Today, Yesterday, This week (from Monday), This month or the two date boxes to limit the list to some days (in the project's timezone); All days clears them. The list shows 50 scans a page with the total above it; use the arrows at the bottom to move between pages. Export CSV downloads every row matching those filters (the last 30 days), with times in the project's timezone. On a phone each scan is shown as a card.
  • Report on the History tab downloads a PDF for the client covering the picked days (today when none are picked): a plain-language summary, how many check-ins were accepted and for how many workers, who scanned again within 60 seconds (not counted twice), which cards were not found on the project, which workers used a card the kiosk had not received yet, and any other refused scans with their reason.
  • The Device card shows the kiosk's RAM in use, its storage (used and free), load and operating system from the last full system report (every 5 minutes). Peak RAM is the highest RAM use the kiosk has seen and when; the kiosk checks every 10 seconds, keeps the peak across restarts and sends it with every heartbeat (kiosk app 2.16.7 or newer).
  • Debug: the same records as the kiosk's own Admin → Debug list (scans, relay, face service, sync, uploads), sent after every check-in and kept for 7 days. Tick Problems only for warnings and errors, or search.
  • System Logs: the kiosk's full technical logs, including every network (HTTP) request. Use Fetch full logs to get the latest.
  • Kiosks send their journal, history, photos and debug records after every check-in (about once a minute while online); a kiosk that was offline catches up when it reconnects. History and photos are kept on the server for 30 days, like the journal.
  • Load older entries at the bottom of the journal shows the next 50 entries without repeating any.
  • Searching for devices or journal messages matches the text exactly as typed, including % and _.
  • When a kiosk moves to a location that already has a device, the location's device keeps its name and takes over the kiosk's journal. No "back online" text is sent for the move.
  • The Last Command column shows the relay pulse result. A red failed badge means ADRO's real-time server could not be reached, so the door was not opened. Try again in a moment. A pulse the kiosk did not confirm within 30 seconds shows as expired.