Skip to main content

Device Manager & reverse-proxy sensor connection

Vemcount Device Manager — sensor list, all edit fields, the per-sensor menu, the reverse-proxy 'Connect to device' bridge (online sensors only), and automated/manual sensor validation. Internal reference.

V
Written by Vemco Group

Internal reference — super-admin and partner functions. Not for end customers.

Device Manager overview

Path: Settings gear > Devices. Filters: search, company dropdown, status (all / online / offline), per-page. Columns: Location, Sensor (name + model + internal/external IP + firmware), Details (MAC), Features (Entrance, Realtime). Green dot = online, red = offline. "Export devices" downloads the list.

Sensor detail fields (Edit Sensor)

  • Name, Subscription, Tag Data As (e.g. Visitors entering), MAC address + Lookup vendor

  • Vendor (auto-detected from MAC prefix), Is entrance, Inverted, Store zero, Store events, Exclude from health check

  • Import sensor id, Serial, Version, Firmware, Custom sensor id, IP, External IP, First seen, Last time seen, Last data

Per-sensor menu (three-dot)

  • Connect to device — opens a live reverse-proxy tunnel to the sensor's own web interface

  • Download latest config — exports the sensor's current configuration

  • Create documentation — installation documentation builder (name, height, install photo, calibration photo)

  • Sensor details — Setup Tracking (FW5) dialog with sync-from-sensor and single/multi-sensor JSON

  • Move sensor, Deactivate, Expire license, Delete

Connect to device (reverse proxy)

Creates a live bridge between Vemcount and a physical sensor, giving remote access to the sensor's own web interface for configuration, firmware updates and calibration. The dialog shows "Trying to communicate with [MAC]" then "Started a communication bridge with device" on success.

Only online (green) sensors can be connected to. Offline (red) sensors cannot be reached via the reverse proxy. Through the bridge, technicians can adjust counting lines and field of view, update firmware, check camera alignment, run diagnostics, and calibrate tracking coordinates.

Sensor data validation

  • Automated — Health Checks run daily and flag sensors where in/out counts differ beyond the configured threshold (e.g. 10%).

  • Manual — an admin physically counts visitors while viewing the live feed and compares against the platform's real-time data (~2s delay). Under threshold passes; over flags for recalibration.

  • Documentation — attach install pictures, calibration screenshots and validation reports to each sensor for audit compliance.

Did this answer your question?