ADRO | Admin Documentation
User Docs Back to App

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).

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

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, 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.
  • 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.