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.

What should I record before changing any settings?

For TP-Link VIGI Human and Vehicle Analytics Setup, record the exact model, firmware if known, current status, precise error wording, screenshots and the last known working condition. Change one item at a time.

Should I factory-reset the equipment while troubleshooting?

Not as an early step. A reset can erase network, recording, user, account or integration settings. Use it only with a configuration backup, known credentials and a model-specific recovery plan.

How do I confirm the problem is genuinely fixed?

Repeat the original test, then check the relevant local and remote paths separately. For an intermittent fault, monitor through the conditions that previously caused it.

What details should I send technical support?

Send the order number if available, exact product models, firmware if known, screenshots or photos, precise error wording, failure times and a short list of completed checks.

Should I change several settings at once?

No. Change one item, repeat the same test and record the result. Multiple simultaneous changes make it difficult to identify the fault or safely reverse the change.

Support

TP-Link VIGI Human and Vehicle Analytics Setup

Human and vehicle analytics only become useful when the rule is aimed at the right area, scheduled properly and tested under the conditions the customer actually cares about. Otherwise the system either misses what matters or bothers everyone with noise.

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.

Worked example

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.

Troubleshooting table

Symptom	What to check	What to do next
The local device also fails	Power, cable, storage or local configuration	Keep the test local and resolve the first failed layer before changing app or cloud settings.
Local operation works but the app fails	Ownership, sharing permission, cloud status or remote network	Keep the proven local setup and compare owner versus shared-user access on mobile data.
Only one channel, zone, door or user fails	Item-specific schedule, permission, wiring or assignment	Compare it side by side with one working item and change only the meaningful difference.
The fault started after another change	Router, password, firmware, account, power or configuration change	Document the last known working state and reverse only the relevant change where safe.
The fault is intermittent	Exact time, logs, signal, load, power and environmental pattern	Capture failure times and screenshots so support can correlate the event instead of guessing.

When to contact support

Contact SecurityWholesalers support when the local result, exact model, firmware or app version and one controlled test are documented but the fault remains. Send the order number if available, screenshots, exact failure time and the checks already completed.

Common mistakes

Changing several unrelated settings before repeating the original test.
Skipping the local device check and relying only on an app symptom.
Resetting, formatting or unbinding equipment without a backup and ownership record.
Escalating without the exact model, version, error text and test time.

Important

Protect the working system before continuing

Do not reset, disconnect, format or overwrite a working path until its current settings, ownership and required evidence have been recorded.

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.

Related buying guides

SecurityWholesalers Buying Guides - Check compatibility and system-design guidance.
Full Store Directory - Find the relevant product family.

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.
What should I record before changing any settings?
For TP-Link VIGI Human and Vehicle Analytics Setup, record the exact model, firmware if known, current status, precise error wording, screenshots and the last known working condition. Change one item at a time.
Should I factory-reset the equipment while troubleshooting?
Not as an early step. A reset can erase network, recording, user, account or integration settings. Use it only with a configuration backup, known credentials and a model-specific recovery plan.
How do I confirm the problem is genuinely fixed?
Repeat the original test, then check the relevant local and remote paths separately. For an intermittent fault, monitor through the conditions that previously caused it.
What details should I send technical support?
Send the order number if available, exact product models, firmware if known, screenshots or photos, precise error wording, failure times and a short list of completed checks.
Should I change several settings at once?
No. Change one item, repeat the same test and record the result. Multiple simultaneous changes make it difficult to identify the fault or safely reverse the change.