Health Checks are company-level monitoring rules that run on schedule and alert recipients when sensors or data fall outside defined thresholds. The platform has 7,403 active health issues platform-wide. Proactive configuration prevents silent data loss.
Health Issues overview
Path: ⚙ Settings → Health Issues
Shows all active device issues across all companies. Filters: company, issue type. Columns: Health Issue type, Error Started, Last Checked, Health Issue Item (MAC address / location).
Configuring health checks per company
Path: ⚙ Settings → Companies → [Company] → Health Checks → + Add check
Each check has:
Name — descriptive label (e.g. "Daily offline check — all locations")
Source type — Locations (specific) or All
Source — multi-select location picker
Notifications — recipient email addresses, option to group by location, option to also notify users assigned to that location
Rules — one or more rule conditions with operator, value, and % threshold
Schedule — which days to run, timezone
Send notification once — checkbox to avoid repeat alerts for persistent issues
All 13 health check rule types
No data | Sensor is connected and online but sending no count data at all. Usually indicates a misconfiguration or blocked data push endpoint. |
Offline | Sensor has stopped communicating with the platform entirely. Network issue, power failure, or hardware fault. |
Difference between In and Out | Entry and exit counts differ beyond the configured threshold (e.g. 10%). Indicates a counting line issue or sensor drift. |
Wrong sensor time | Sensor's internal clock is out of sync. Causes timestamps to misalign with actual traffic, corrupting hourly data. Check NTP settings (ntp.vemcount.com, UDP 123). |
No realtime data | Sensor is sending historical data but not the live real-time feed. Affects Live Inside and queue widgets. |
No visitors | Sensor data shows zero visitors during configured opening hours. Could be a genuine quiet period or a silent sensor failure. |
No sales data imported | POS or turnover data has not been submitted for this location. Triggers when the expected data feed has not arrived by the check time. |
No screen sync | A connected display screen is not syncing with the platform. Affects digital signage and in-store display systems. |
Privacy level | Sensor's privacy compliance threshold has been breached. Check sensor anonymisation settings. |
Metric | Generic metric-based threshold — triggers when any selected metric exceeds or drops below a defined value. Flexible catch-all rule. |
Realtime data monitoring | Live data stream anomaly detection — flags unusual spikes or drops in real-time data that may indicate sensor tampering or misconfiguration. |
Difference between In and Out per location | Same as the In/Out difference rule but calculated individually per location rather than aggregated. Catches per-location issues hidden in combined totals. |
Daily difference between In and Out | Daily aggregated in/out difference check — runs once at end of day and flags locations where the full-day entry/exit balance exceeds the threshold. |
Recommended minimum setup: Create at least two health checks per company — one for Offline / No data (runs daily, all locations, email to Admin) and one for Difference between In and Out (10% threshold, daily, all locations). These two rules catch 90% of all real-world sensor issues.
Acknowledging issues
In the Health Issues overview, click any active issue to see the error detail and recommended action. Use the Acknowledge button to mark an issue as known while it is being resolved — this prevents repeat notifications while the fix is in progress.