Support
HiLook Motion Detection or Push Notifications Not Working
Events and Notifications
Summary
Follow the four stages below to diagnose HiLook motion recording or phone notifications are missing or unreliable without losing evidence, configuration or device ownership.
Applies to
- HiLook NVR motion events
- HiLookVision/Hik-Connect mobile notifications
Difficulty and time
Difficulty: Moderate
Estimated time: 20 to 40 minutes
What you will need
- The exact model and current firmware or app version
- Administrator access where authorised
- A photo or screenshot of the current status
- One controlled test case and its exact time
What this guide covers
- Preserve and reproduce the fault
- Open the correct diagnostic screen
- Correct the proven cause
- Verify and document the result
Use this page when HiLook motion recording or phone notifications are missing or unreliable. It includes the menu or screen to look for, the status that matters and a repeatable proof test.
Exact labels can differ between recorder, controller, app and firmware versions. If the named screen is not present, do not guess at destructive options; note the model and current version for support.
Before you start
Protect the current system and record a baseline before changing anything.
- Write down the exact symptom: motion occurs but no event marker, clip or push notification appears.
- Photograph the current status, error text, wiring or timeline as applicable.
- Record the last known working time and anything changed immediately before the fault.
- Photograph the current event schedule, area and linkage before changing it.
A phone notification is not proof of recording
Prove the event and clip locally first. App reinstallation cannot recreate missing event recording.
If the required option is missing or the result does not match this guide, stop and identify the exact model before continuing.
What usually causes this
- Motion area or schedule is wrong
- Recording linkage is missing
- App event subscription is off
- Phone background/battery rules suppress pushes
Step 1: Preserve the current state and reproduce the fault
Begin with a repeatable baseline so you know whether a later change genuinely helped.
- Reproduce the problem once and record: motion occurs but no event marker, clip or push notification appears.
- Note whether every device or user is affected, or only one.
- Compare one working path with the failing path if a comparison exists.
- Photograph the current event schedule, area and linkage before changing it.
Step 2: Open the correct screen and inspect the evidence
The primary diagnostic location is NVR Main Menu > Event > Basic Event > Motion Detection, then app > Settings > Notifications. Do not change anything until the displayed state is recorded.
- Open NVR Main Menu > Event > Basic Event > Motion Detection, then app > Settings > Notifications. Menu wording can vary by model and firmware; use the nearest equivalent label.
- Select one camera and confirm motion detection is enabled for that channel.
- Check its arming schedule, detection area and linkage/recording channel.
- Confirm a walk test creates a local event marker before changing phone settings.
Step 3: Correct only the cause you proved
Use the matching correction below. Make one change, save it, then repeat the same test.
- Enable and draw the required detection area with a realistic sensitivity.
- Set the active schedule and link the event to the correct recording channel.
- Enable Notify Surveillance Centre or the model-equivalent push linkage if required.
- In the app and phone OS, enable event notifications, background activity and the correct device schedule.
Step 4: Verify, monitor and document the handover
A saved setting is not proof. Test the real outcome locally first, then test any app, cloud or client path separately.
- Run a time-coded walk test in the detection area.
- Find the event in local NVR playback or event search.
- Lock the phone and confirm one push arrives with the expected channel/time.
- Repeat after-hours if the real schedule differs from the test period.
Controlled support test
Situation: The reported symptom was: motion occurs but no event marker, clip or push notification appears.
Solution used: The current state was recorded in NVR Main Menu > Event > Basic Event > Motion Detection, then app > Settings > Notifications, one matching correction was made, and the same test was repeated.
Why this was chosen: This separated the proven cause from unrelated settings.
Installation notes: The final screenshot and test time were saved with the handover record.
Official reference used for this guide
Menu names differ between releases. Confirm model-specific behaviour in Hikvision NVR User Manual before firmware, reset, storage or security-sensitive work.
Common mistakes
- Changing several settings before repeating the original test.
- Using a factory reset, initialise or format option as an early troubleshooting step.
- Treating an app symptom as proof that the local hardware or recording has failed.
- Failing to record the model, version, exact error and test time before escalation.
- Assuming similar-looking models use identical menus or features.
Troubleshooting table
| Symptom | What to check | What to do next |
|---|---|---|
| motion occurs but no event marker, clip or push notification appears | event disabled, wrong schedule/area, missing record linkage, app subscription off or phone OS suppression | Open the named diagnostic screen, record the displayed state and use the matching correction above. |
| The named menu is not visible | Different firmware, permissions or model capability | Do not substitute a destructive menu. Capture the model and version and use its official manual. |
| The change saves but the fault remains | The selected cause was not the root cause | Undo the change if appropriate, return to the baseline and compare the failing path with a working one. |
| Local test works but app or client test fails | Account, permission, cloud or remote-network path | Keep the proven local configuration and diagnose the remote path separately. |
| Problem returns later | Intermittent power, cable, storage, network or schedule condition | Record the new failure time and status; correlate it with logs, events and the last known working interval. |
When to contact support
Contact SecurityWholesalers support when a local event and clip are proven but the owner app receives no push after account, app and phone-permission checks.
Send the order number if available, exact model, firmware or app version, screenshot of NVR Main Menu > Event > Basic Event > Motion Detection, then app > Settings > Notifications, the failure time, and the result of the local proof test.
Related support guides
- HiLook Support Guides - Browse every guide in this support area.
- All Technical Support Guides - Return to the complete support library.
Related buying guides
- HiLook Buying Guide - Broader HiLook planning guide.
- NVR Buying Guide - Recorder planning guide.
Relevant product categories
- HiLook CCTV Products - HiLook products.
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
-
Where should I click first for HiLook notifications not working?
Start at NVR Main Menu > Event > Basic Event > Motion Detection, then app > Settings > Notifications. Record the existing state before changing it because labels and available options can vary by model and firmware.
-
What should I look for on that screen?
Look for Enable Motion, detection grid/area, arming schedule, linkage action/record channel and app notification subscription.
-
What must I avoid changing during the first check?
Prove the event and clip locally first. App reinstallation cannot recreate missing event recording.
-
How do I prove the correction worked?
A controlled walk test should create a local event/clip and one correctly timed push while the phone is locked.
-
Why might my menu names look different?
Recorder, controller, camera, app and firmware releases can use different labels. Use the closest equivalent only when its function is clear; otherwise record the model and version for support.
-
Should I factory-reset the device?
Not as an early step. A reset may erase users, network settings, recording configuration, licences or cloud ownership. Back up the configuration and confirm the recovery plan first.
-
What should I send technical support?
Send the exact model and version, screenshot of NVR Main Menu > Event > Basic Event > Motion Detection, then app > Settings > Notifications, exact error text, failure time, what changed before the fault and the result of the controlled local test.
-
Can configuration changes recover data or events that were never recorded?
No. A correction can restore future operation, but it cannot recreate footage, alarm events or access transactions that were never stored.