Milesight VS133-P: doorway counts with a traceable data route

Research an overhead ToF people counter, its Ethernet reporting route and a fair entrance-counting pilot before using counts in a facility decision.

Offering research · By Admin · Checked 20 October 2026. Official model and configuration references; no installed accuracy, live integration or regional service quote verified.

VS133-P is a model to investigate when the pilot needs an entrance-flow record. A line crossing, a regional count and an inferred room total answer different questions. Define the required record before choosing the application or using a count to change a service.

Start with the entrance and the required record

Exact PoE model

The model documentation describes second-generation time-of-flight sensing and Ethernet communications. Keep VS133-P distinct from other VS13x models; do not borrow a newer model's height, radio or stitching capabilities.

Coverage is site-specific

The quick-start guide distinguishes the monitored view from the usable detection area. Height, target height, placement and surroundings matter. Demonstrate the actual entrance coverage, including accessible routes and ordinary traffic.

Counts need reconciliation

A crossing count is not automatically the number of people now in a room. Record all relevant entrances, starting state, reporting periods, resets and gaps before attempting an occupancy estimate. Keep uncertain totals visibly uncertain.

Follow entrance traffic into an accountable review

1 · Draw the observation boundary

Choose one entrance or a clearly mapped set of entrances. Describe the facility question, time window and decision owner. List routes that bypass the sensor and retain ordinary service arrangements while the pilot is being assessed.

2 · Commission the actual model

The qualified provider checks the supplied hardware, mounting, usable coverage and power/network arrangement against current model documents. The online quick-start and family specification table differ in their named PoE standard; resolve that with the supplier for the supplied revision rather than guessing.

3 · Set a minimal counting rule

Choose the required line or region and retain its identity, direction and configuration. The profile reference documents optional filters and classification settings. Use only settings justified by the facility question and record changes that affect the meaning of the count.

4 · Validate ordinary traffic

Agree an authorised reference-count method and representative periods. Include opposing flows, groups, pauses, U-turns and people using mobility aids. Compare per-direction and per-period results; investigate mismatches rather than accepting a headline accuracy percentage.

5 · Demonstrate the data handover

The configuration reference supports HTTP(S)/MQTT recipients, triggered or periodic reporting and retransmission. Prove the chosen mode with the actual receiver. Keep line/region identity, device time, receipt time, reporting period, resets, gaps and replayed packets distinguishable.

6 · Review before acting

The facility owner reviews count quality and any occupancy calculation with its starting state and reconciliation method. Record uncertainty, changed rules and missing entrances. Any service adjustment needs an agreed fallback for unavailable or implausible records.

Read manufacturer claims in context

The product introduction gives an up-to-99.8% accuracy claim. This page has not independently reproduced that result. Request the relevant test method and demonstrate performance in the proposed entrance before setting an acceptance threshold.

Confirm firmware and interfaces

The official HTTP report-retrieval support article specifies model/firmware prerequisites. A documented interface is not proof that a proposed dashboard, historical export or BMS integration is working. The quick-start reference marks RS485 under development; do not include an assumed working serial integration in the scope.

Minimise joins and optional attributes

A depth-based sensing route does not settle the privacy of the full deployment. Review preview access, stored/exported records, optional classifications and joins to badges, bookings or named accounts. Keep employee monitoring and emergency headcounts outside this pilot.

Scope the operating service explicitly

Request mounting, network/power work, receiver configuration, access control, updates, maintenance, export and recovery responsibilities. Confirm regional supply, qualified installation and written support terms; no current India price, stock or local service is established here.

Use the pilot and a written proposal

Occupancy-aware facilities pilot provides the operating question and evidence record. Prepare a private requirements enquiry for Admin review. An unlisted provider may be named in the non-confidential brief; no provider is contacted automatically.

Sources and independence

Model introduction, quick-start guidance, the development-platform profile and the HTTP retrieval support article support the stated distinctions. Confirm the current installation manual and document revision with the provider for the supplied hardware. Acceptance and reconciliation questions are original editorial guidance; no independent accuracy result, deployed integration, privacy approval or partnership is established.

VS133-P product introduction

VS133-P quick-start reference

VS13x current model table

VS133-P custom profile template

VS13x HTTP report retrieval

Milesight company context