Health Checks are monitoring rules set per company. They run on a schedule and send an email when sensors or data fall outside the limits you set. A good setup stops silent data loss.
See open health issues
Path: Settings (cogwheel) > Health Issues
This list shows active device issues. You can filter by company and issue type. Columns: Health Issue type, Error Started, Last Checked, and Health Issue Item (MAC address or location).
Set up a health check
Path: Settings (cogwheel) > Companies > [Company] > Health Checks > + Add check
Name: give the check a clear name, for example "Daily offline check, all locations".
Source: choose Source Type Locations (pick specific locations) or All.
Notifications: enter the email addresses that should get the alerts. You can tick Group notifications by location and Notify users connected to the location.
Rules: pick a rule, an operator, a value and a % limit. Use + Add rule to add more rules to the same check.
Schedule: select the days the check runs and the time zone.
Tick Send notification once to avoid repeat emails for an issue that is already known.
Save.
All 13 rule types
No data: the sensor is online but sends no count data. Often a setup problem or a blocked data push.
Offline: the sensor has stopped talking to the platform. Network, power or hardware problem.
Difference between In and Out: entries and exits differ by more than your limit (for example 10 %). Points to a counting line problem or sensor drift.
Wrong sensor time: the sensor clock is out of sync, so hourly data lands in the wrong hour. Check the NTP settings (ntp.vemcount.com, UDP 123).
No realtime data: the sensor sends history but no live feed. Affects Live Inside and queue widgets.
No visitors: zero visitors during opening hours. Can be a quiet period or a silent sensor failure.
No sales data imported: POS or turnover data has not arrived by the check time.
No screen sync: a connected display screen is not syncing.
Privacy level: the sensor's privacy setting is outside the allowed level. Check the anonymisation settings.
Metric: a general rule that fires when a chosen metric goes above or below a value.
Realtime data monitoring: flags unusual spikes or drops in the live data.
Difference between In and Out per location: the same as the In/Out rule, but calculated per location so problems are not hidden in combined totals.
Daily difference between In and Out: runs once at the end of the day and flags locations where the full-day In/Out balance is over the limit.
Recommended minimum setup
Create at least two health checks per company: one for Offline / No data (daily, all locations, email to an admin) and one for Difference between In and Out (10 % limit, daily, all locations). These two catch most real-world sensor problems.
Acknowledging issues
In the Health Issues list, click an active issue to see the details and the recommended action. Use Acknowledge to mark an issue as known while it is being fixed, so you do not get repeat notifications.
When to contact support
A sensor stays offline after you have checked power and network and restarted it.
An In/Out difference stays high for several days, or started after a change at the entrance.
You get many alerts and are not sure which rules or limits to use.
Email support@vemcogroup.com with the location, the sensor name or MAC address, and the dates of the alerts.