The Device Manager is the central hub for all sensors across all locations. This deep-dive covers the full sensor detail fields, remote connection via reverse proxy, sensor validation, and documentation — essential knowledge for Admins and field engineers.
Path: ⚙ Settings → Devices
Device list filters
Search — by device name, ID, or MAC address
Select Company — dropdown to scope by company
Status — Show all / Online / Offline
Export devices — download full device list as CSV
Columns: Location, Sensor (name + model + internal/external IP + firmware version), Details (MAC address), Features (Entrance, Realtime). Green dot = online, Red dot = offline.
Full sensor detail fields
Click any sensor to open its edit screen. All configurable fields:
Name | Descriptive name for the sensor (e.g. "Entrance North — Xovis") |
Subscription | Shows the linked subscription plan (e.g. VemCount Basic - Pro 42/42) |
Tag data as | How to label counting data (e.g. Visitors entering) |
MAC address | Hardware identifier — used to pair sensor to platform. Lookup vendor button auto-detects manufacturer from MAC prefix |
Vendor | Auto-detected from MAC prefix (Xovis, Milesight, Axis, etc.) |
Is entrance | Checkbox — marks this as a primary entrance sensor (affects footfall calculations) |
Inverted | Checkbox — swaps in/out directions if sensor is mounted facing the opposite direction |
Store zero | Checkbox — whether to store zero-count intervals in the database |
Store events | Checkbox — whether to log sensor events (calibration, firmware updates) |
Exclude from health check | Checkbox — exempts this sensor from health check rules (useful for temporary/test sensors) |
Serial / Version / Firmware | Hardware identifiers (e.g. PC2SEUL / 5.8.3-92cb10c574) |
IP / External IP | Internal network IP and external (public) IP of the sensor |
First seen / Last seen / Last data | Timestamps for sensor activity audit |
Per-sensor three-dot menu
Connect to device | Opens a live reverse-proxy tunnel to the sensor's own web interface (see below) |
Download latest config | Exports the sensor's current configuration as a file |
Create documentation | Opens the sensor documentation builder — attach installation and calibration photos, notes, and audit records |
Sensor details | Opens the Setup Tracking (FW5) dialog with single/multi-sensor JSON sync fields |
Move sensor | Reassign the sensor to a different location without deleting it |
Deactivate / Expire license / Delete | Lifecycle management options |
Connect to device (reverse proxy)
This feature creates a live communication bridge between Vemcount and a physical sensor, allowing remote access to the sensor's own web interface without needing to be on the same network.
Critical: Only GREEN (online) sensors can be connected to. Red (offline) sensors cannot be reached via reverse proxy. The connection dialog shows "Trying to communicate with [MAC address]" followed by "Started a communication bridge with device" when successful.
Through the sensor's own web interface, technicians can:
Adjust counting lines and field of view
Update firmware
Check camera alignment and live video feed
Run onboard diagnostics
Calibrate tracking coordinates
Sensor validation
Sensor validation verifies that a sensor's automated counts match reality. Two methods:
Automated | Health Checks run daily and flag sensors where in/out counts differ by more than the configured threshold (e.g. 10%). See the Health Checks article for rule configuration. |
Manual | A technician physically counts visitors while viewing the sensor's live feed. The system compares manual counts against real-time data (with ~2 second delay). If the difference is below 10%, the sensor passes. Above 10%, the sensor is flagged for recalibration. |
Sensor documentation builder
Use Create documentation from the three-dot menu to build a permanent audit record for each sensor:
Enter the sensor name and mounting height
Upload an installation photo showing the sensor position and mounting
Upload a calibration photo showing the counting zone configuration
Add notes (e.g. installation date, technician name, site conditions)
Click Add sensor to save
This documentation record is stored against the sensor permanently and is invaluable for GDPR compliance audits, insurance, and re-calibration after maintenance.