Support
TP-Link VIGI Human and Vehicle Analytics Setup
VIGI Analytics Support
Summary
Use this guide when a VIGI camera or recorder needs cleaner human and vehicle event setup for notifications, recording or deterrence logic.
Applies to
- VIGI cameras that support human or vehicle filtering
- Sites using VIGI App event configuration
- Small business, home and remote-site commissioning jobs
Difficulty and time
Difficulty: Moderate
Estimated time: 20 to 45 minutes
What you will need
- Access to the camera or recorder settings
- One real test area
- Understanding of what counts as a true alarm event on site
- Phone app for final verification
Current TP-Link guidance makes the flow fairly clear: enable the event, choose the object classification, set the zone, then apply the notification or alarm actions. In real support work, the missing piece is usually the discipline to test one rule properly before enabling several overlapping rules.
Before you start
- Choose the one camera and scene that matters most.
- Decide whether the customer wants human, vehicle or both.
- Confirm whether the output is meant to create recording, push alerts, deterrence actions or all three.
- Know whether the site mainly cares about daytime, night-time or after-hours events.
Step 1: Enable the right detection type, not every type
- Start from the device settings area in the VIGI app or supported device UI.
- Enable motion or analytics only where it is required.
- Turn on Human and or Vehicle only if the camera supports them and the site genuinely benefits from them.
Step 2: Draw the detection zone around the event you care about
- Keep public footpaths, moving trees and road glare out of the zone where possible.
- At a front gate, focus on the approach lane rather than the entire frame.
- At a driveway, make sure the target stays large enough in frame to be classified properly.
Step 3: Set schedule, actions and recipients in that order
- Apply the event schedule first.
- Then decide whether the outcome is recording, push, email, light alarm, sound alarm or some mix of those.
- Only then test the owner account and any shared users.
Step 4: Test in the conditions the site actually cares about
- Run a walk test and a vehicle test where relevant.
- Test again at night if the site is mainly an after-hours security job.
- Review the resulting clip, not just the notification banner.
Driveway with regular street traffic nearby
Situation: The customer wanted driveway alerts, but a broad motion zone would also catch traffic and shadows.
Solution used: Vehicle and human filtering were limited to the driveway approach only, with a tighter zone and after-hours schedule.
Why this was chosen: It gave the customer the alert path they wanted without turning the phone into noise.
Installation notes: The final test was done after dark because headlights changed the scene significantly.
Related support guides
Relevant product categories
Still stuck?
Need help choosing or setting up a system? Contact SecurityWholesalers support with your order number, product model and a clear description of the issue.
Frequently asked questions
- Should I enable both human and vehicle for every camera?
Not automatically. Choose the object types that make sense for the scene and the customer's goal.
- Why is my VIGI analytics rule too noisy?
The zone may be too broad, the target types too open, or the scene itself too busy for the current settings.
- What is the best way to prove the rule?
Run a real walk test or vehicle test in the same lighting and approach angle the site actually cares about, then review the resulting clip.