Why are VIGI notifications not arriving even though the app is online?

Usually because the event logic, schedule or target filtering is wrong, or because the phone is not the real issue at all.

Should I test on Wi-Fi only?

No. A mobile-data test is much more useful for proving the remote notification path.

Do human and vehicle filters affect whether the notification fires?

Yes. If object classification is enabled, the event must match that logic as well as the detection zone and schedule.

What should I record before changing any settings?

For TP-Link VIGI Notifications Not Working, 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 Notifications Not Working

If VIGI notifications are not arriving, do not start at the phone only. The useful order is event rule first, schedule second, recipient path third, and phone notification settings after that.

VIGI Notification Support

Summary

Use this guide when a VIGI recorder or camera is online but push notifications still do not arrive reliably.

Applies to

VIGI App notifications
VIGI motion and object-classification events
Owner and shared-user mobile alerts

Difficulty and time

Difficulty: Moderate

Estimated time: 20 to 40 minutes

What you will need

Phone with VIGI App
Access to the camera or recorder settings
One test event location
Owner account details

TP-Link's current VIGI app guides make it clear that notifications sit on top of the event logic. In practice, that means the motion or human or vehicle rule has to be working first before the phone can ever be expected to behave.

Before you start

Confirm the device is online and visible in the correct TP-Link ID.
Choose one camera and one event type to prove first.
Turn off any duplicate test rules that make the result confusing.
Make sure the phone allows notifications for VIGI App.

Step 1: Make sure the event itself really works

Open the camera or recorder settings and enable the event you actually want.
For current VIGI app workflows, this often begins from More Settings or the gear icon on the device page.
Confirm the detection zone, sensitivity and target type are sensible.
Run one real walk test or vehicle test.

Step 2: Check schedule and notification toggles together

A lot of VIGI notification complaints come down to a rule that is enabled but not armed when the customer thinks it is.

Check the event schedule.
Check whether push notifications are turned on for that event.
If the site uses object classification, confirm human or vehicle is actually selected rather than assumed.

Useful VIGI app path

More Settings or the gear icon on the Live View page usually leads into the current device settings area.
Motion Detection, Human Detection or Vehicle Detection are the key event paths on current VIGI workflows.
Current TP-Link VIGI guides also expose notification, detection zone and sensitivity controls from those event pages.

Step 3: Confirm the phone and account path

Confirm the phone is logged into the correct TP-Link ID.
Check iPhone or Android notification permissions and battery restrictions.
If a second user expects alerts, confirm whether the device is shared correctly and whether that user should receive them.
Test on mobile data, not only on site Wi-Fi.

Step 4: Reduce noise before expanding the rule

Keep scene motion outside the target area where possible.
Tighten detection zones and lower false triggers before handing over.
Do a second test at night if the customer mainly cares about after-hours alerts.

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.

Worked example

Compare one failing path with one working path

Situation: One device, channel or user failed while another comparable item still worked.

Solution used: The two paths were compared at the local device first, one meaningful difference was corrected, and the original test was repeated.

Why this was chosen: The comparison isolated the affected layer without disturbing the rest of the system.

Installation notes: The final status, screenshot and test time were added to the handover record.

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

Why are VIGI notifications not arriving even though the app is online?
Usually because the event logic, schedule or target filtering is wrong, or because the phone is not the real issue at all.
Should I test on Wi-Fi only?
No. A mobile-data test is much more useful for proving the remote notification path.
Do human and vehicle filters affect whether the notification fires?
Yes. If object classification is enabled, the event must match that logic as well as the detection zone and schedule.
What should I record before changing any settings?
For TP-Link VIGI Notifications Not Working, 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.