Support
Hanwha Motion Detection vs Analytics Setup
Hanwha Analytics Support
Summary
Use this guide when a Hanwha system is creating too many false alarms, not enough useful event clips, or confusion about whether the job is using motion only or a stronger analytics path.
Applies to
- Hanwha cameras and recorders
- Hanwha analytics-enabled cameras
- Wisenet Mobile and WAVE alert workflows
Difficulty and time
Difficulty: Moderate
Estimated time: 20 to 40 minutes
What you will need
- Local access to the recorder or camera
- Camera model details
- Understanding of the required alert outcome
What this guide covers
- Check what event path is active
- Match the mode to the job
- Tune the scene and target area
- Link it properly to recording and alerts
Many Hanwha jobs include stronger analytics capability than the owner ends up using. The support problem then becomes simple: the owner expects human or vehicle-style behaviour from a recorder that is still only using basic motion.
This guide explains when to stay on broad motion detection, when to move to analytics, and how to prove the result locally before trusting app alerts.
Before you start
Decide first whether the owner wants broad movement recording, lower false alarms, or more deliberate analytics events.
- Confirm the camera model actually supports the analytics being discussed.
- Check whether the event lives on the camera, recorder or WAVE layer.
- Pick one camera to tune first.
- Use local testing rather than only a phone notification test.
Analytics still depends on scene design
Bad camera angle, moving trees, headlights and poorly chosen detection zones can still create weak results.
A stronger feature label does not rescue a poor scene or an incomplete recording linkage path.
Step 1: Confirm what event path is active now
Start by checking whether the site is still on basic motion or whether analytics is already enabled but poorly linked.
- Open the event or analytics settings.
- Confirm the current mode on the problem camera.
- Check whether recording and push alerts point to the same event type.
- Record the current settings before changing them.
Step 2: Match the event mode to the real job
Not every camera needs deep analytics. Some scenes only need broad motion, while others benefit from more selective people or vehicle logic.
- Use broad motion where the owner mainly wants movement history.
- Use analytics where the owner wants more selective events.
- Be realistic about model capability and scene complexity.
- Avoid overpromising precision where the scene is messy.
Step 3: Tune the view and target area
False alarms often come from the scene, not from the event label.
- Reduce unnecessary sky, road or tree movement if possible.
- Check the detection area or rules.
- Test in both daytime and night conditions.
- Walk a real person or vehicle through the zone if that is the expected target.
Step 4: Link analytics to recording and alerts properly
A good event path still needs schedule, recording and notification linkage.
- Check the event schedule.
- Check the record linkage or action rules.
- Then test push alerts or WAVE notifications.
- Use local playback to verify the clips first.
Common mistakes
- Calling everything "motion" even when analytics is expected.
- Enabling analytics on unsupported models.
- Ignoring the scene and tuning only the menu.
- Judging the whole result only from phone alerts.
Troubleshooting table
| Symptom | What to check | What to do next |
|---|---|---|
| Too many false alerts | Broad motion or poor scene design | Refine the zone or move to analytics if the model supports it. |
| No useful analytics clips | Unsupported model or missing linkage | Check the model and event linkage path first. |
| Good local result but poor app alerts | Notification or schedule issue | Prove the event locally first, then review the app or WAVE notification path. |
When to contact support
Contact SecurityWholesalers support when you know the exact Hanwha camera and recorder or WAVE workflow, and the site still needs help choosing the right detection path or linking it to recording properly.
Related support guides
- How to Add a Hanwha Recorder to Wisenet Mobile - Useful when app testing is part of the event path.
- Hanwha Wisenet WAVE Recording Not Working - Useful if the recording path is part of the issue.
Related buying guides
- Hanwha Buying Guide - Broader Hanwha planning guide.
Relevant product categories
- Hanwha Vision CCTV Cameras and Security Systems - Hanwha product range.
- Hanwha WAVE Licenses - WAVE category.
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
-
What is the difference between Hanwha motion detection and analytics?
Basic motion looks for movement in an area. Analytics on supported models usually aims to give more selective and useful event behaviour.
-
Should I always use analytics?
Not always. Some scenes still suit broad motion, especially where the owner wants general activity history.
-
Do analytics remove all false alarms?
No. Scene design, angle, target zones and lighting still matter.
-
Should I test on the recorder first?
Yes. Local event proof is more useful than guessing from a phone alert.
-
Can WAVE or app setup affect the outcome?
Yes. Recording linkage and notification workflow still matter even when the camera analytics is good.