How health is tracked
Heartbeat: each kiosk pings
mc-apievery 30 seconds.Last seen: the dashboard stores the most recent heartbeat time and a history log on each kiosk page.
Self reload: the experience reloads every 15 minutes to pull the latest code and files when online. This does not change status by itself.
Status definitions
Status | What it means | Default rule |
Green | Online now | A valid heartbeat seen in the last 2 minutes |
Yellow | Recently online but not currently connected | No current heartbeat, last seen within 24 hours |
Red | Offline | No heartbeat for 24 hours or more |
Enterprise clients can request different thresholds.
Uptime calculation
Uptime is the percentage of time a device is Green within the selected period.
When a device stops sending heartbeats, time is counted as offline until the next heartbeat arrives.
You can view uptime at organisation, location, and device levels.
Notifications
When alerts fire
On status transitions to Yellow or Red.
Alerts are rate limited to avoid repeat spam. You will be notified again when the status changes.
Channels
Standard: Email, Dashboard alerts, SMS.
Enterprise: Slack and Webhooks are available.
Who receives alerts
Admins and Managers by default. Team routing can be customised for enterprise accounts.
What you can see in the dashboard
Last seen timestamp and heartbeat history per device.
Current status badge and uptime for the selected window.
Any pending content updates that will apply the next time the device is online.
Quick links to device actions such as lock, unlock, ping, and beep. Full details are in Kiosk remote capabilities and actions.
Typical reasons for status changes
Network issues: Wi-Fi drop, captive portal, DNS filtering, strict firewalls.
Power events: device powered off, low battery in sites without constant power.
Local maintenance: deliberate disconnects during store hours.
Large updates: oversized assets can extend fetch times on poor links.
Recommended operating posture
Keep kiosks online daily so health and analytics stay current.
Use compressed media in campaigns and avoid single files over 1 MB where possible.
Prefer stable connectivity over peak speed. 10 Mbps or higher is recommended, 30 Mbps for video heavy sites.
For challenging locations, add a 4G SIM and confirm firewall rules allow outbound HTTPS.
Troubleshooting an offline device
Open the device page and check Last seen and the heartbeat log.
Verify connectivity on site:
Wi-Fi connected with internet access
No captive portal waiting for sign in
Firewall and DNS permit outbound HTTPS
Confirm the device is powered and not in a low battery state. Keep kiosks plugged in where possible.
Check storage headroom so the service worker can cache updates.
If the device just came back online, allow the 15 minute reload cycle to complete.
Use a device action: ping or beep to locate the hardware, then try a screen lock and unlock to confirm control.
If still offline, contact support. We can remotely review logs and help clear cache or reseed content.