ONVIF Motion Detection: Why the NVR Misses Camera Events

When an NVR shows live video from an ONVIF camera but never records anything on motion, the usual reason is simple: the recorder is taking the video stream and ignoring the camera's events. ONVIF motion detection only works when three things line up: motion detection is switched on in the camera, the NVR is subscribed to the camera's events on that channel, and the channel's recording mode is set to motion or event. If the camera cannot pass its events to your recorder, the fallback is to let the NVR run its own motion detection on the stream.

This article walks through those checks in order, explains what each symptom means, and shows how to test the result. If the camera is not on the NVR yet, start with adding a Yoosee camera to an NVR and come back once you have a live picture.

Video and motion events travel separately

It helps to know why a camera can look "connected" and still be useless for motion recording.

Over ONVIF, a camera offers several separate services. One delivers the video stream. Another delivers events, such as "motion started" and "motion stopped". The recorder has to ask for each one. Many NVRs connect the stream as soon as you add the camera, because that is what live view needs, but they only listen for events if the channel is configured to use them.

So a working live picture proves only that the stream is fine, and the fix is almost always in a settings page on the camera, the NVR, or both.

There are two places motion can be detected:

• In the camera. The camera analyses its own picture and sends an event to the NVR. This is "camera-side" detection.
• In the NVR. The recorder analyses the incoming stream itself. This is often called video motion detection on the recorder's menus.

You need one of these to work. You do not need both, and running both can cause duplicate or confusing event logs.

Step 1: Make sure motion detection is on in the camera

Camera-side events can only reach the NVR if the camera is detecting motion in the first place. On most Yoosee models this is done in the phone app:

1. Open the app and tap the camera.
2. Open its settings (usually a gear icon).
3. Look for an alarm, alert or motion detection section. Menu names differ slightly by app version and model.
4. Switch motion detection on, and set a sensitivity level that suits the scene.

On some models, turning off app alerts or setting the camera to a "disarmed" state also stops it from generating motion events at all, which means nothing is available for the NVR to receive. If you silenced phone alerts to stop notifications, check whether that also switched off detection. The behaviour varies by model, so test it rather than assume.

If the camera triggers on shadows or trees, or misses people walking past, tune the zone and sensitivity first. The guide to motion detection sensitivity and zones covers angle, zones and schedules in detail. An NVR cannot record good motion clips from a camera that detects badly.

Step 2: Check how the camera was added on the NVR

Recorders usually let you add a camera in more than one way, and only some of them carry events.

• Added as an ONVIF device. The NVR logs in to the camera with its username and password and can use the stream, the events and sometimes PTZ control. This is the route you want.
• Added as a plain stream address. Some recorders let you paste a stream address directly, often labelled custom, generic or RTSP. This gives video only. The NVR has no event connection at all, so camera-side motion can never reach it.
• Added with the recorder's own protocol. Some NVRs prefer their own brand protocol for their own cameras. A Yoosee camera should be added as ONVIF instead.

Open the NVR's camera or channel list and look at the protocol column for the channel in question. If it is not ONVIF, delete the channel and add the camera again as ONVIF, using the camera's local IP address and its device password (not your app account password). If the NVR rejects the login, the NVR setup guide explains which password is usually needed.

Also check the camera's time. ONVIF logins can carry a timestamp, and on some recorders a camera whose clock is far off connects for video but fails on events. Set the NVR to sync time to the cameras, or set both to an internet time server, then restart the channel.

Step 3: Set the channel to record on motion

Adding a camera does not tell the NVR when to record. On most recorders, the recording schedule is a separate page:

1. Open the NVR's recording or schedule settings.
2. Select the channel for this camera.
3. Choose the record type. Common labels are continuous, motion, alarm, event or smart. Pick motion or event for the hours you want covered.
4. Save, and copy the schedule to other channels only after it works on one.

Many recorders show this as a weekly grid with a colour per record type. A grid filled in the continuous colour records all the time but does not tag motion; a blank grid records nothing.

Some NVRs also have a pre-record and post-record setting. Pre-record keeps a few seconds before the trigger; post-record keeps recording after motion stops. If clips start after the person has already passed, raise pre-record a little on the NVR. The best value depends on your scene, so try a couple of settings and play back the results.

Step 4: Choose where detection happens

Next, tell the NVR which motion source to use for that channel. This setting is often inside the channel's event or motion page, and it may be split into "camera event" and "NVR detection" options. Wording varies widely between recorders.

Option A: use the camera's events

Look for a setting on the channel such as event source, camera alarm, or ONVIF event. Enable it and link it to recording on that channel. Then check the event or alarm log on the NVR while someone walks in front of the camera. If you see entries appear, the subscription is working.

This option keeps processing on the camera and uses the zones and sensitivity you set in the app. On some models, the camera's human detection may only be reported as plain motion over ONVIF, so the NVR may not know the difference between a person and a moving branch.

Option B: use the NVR's own motion detection

If no events ever appear in the log, the camera may not publish them in a way your recorder understands. In that case, enable motion detection on the NVR for that channel:

1. Open the channel's motion settings on the NVR.
2. Turn motion detection on.
3. Draw the detection area on the NVR's grid. This is independent of any zone you drew in the app.
4. Set the NVR's sensitivity and link the trigger to recording on the same channel.

NVR-side detection works with any camera that streams video, so it is the dependable fallback. The trade-off is that it uses the recorder's processing power. Some recorders limit how many channels can run their own detection, or only offer it on the sub-stream. Check the NVR's manual for its limits.

Step 5: Test it properly

A quick live view check is not a test. Do this instead:

1. Have someone walk across the detection area at a normal pace, at the distance where you most care about catching people.
2. Wait a minute, then open playback on the NVR.
3. Search by event or motion type for that channel, not just by time.
4. Confirm the clip exists, starts before the person is fully in frame, and covers them leaving.
5. Repeat after dark if the camera covers an outdoor area, because night detection behaves differently.

If the event search shows nothing but a time search shows footage, the NVR is recording continuously and not tagging motion. Go back to Step 3 and Step 4. If neither search shows anything, the problem may be the drive or the schedule rather than motion. The guide to playback not working on a recorder covers drive, clock and schedule checks.

Camera IP PoE ONVIF setups: wired cameras on the NVR

People searching for a camera IP PoE ONVIF setup often plug wired cameras straight into the PoE ports on the back of an NVR. The same logic applies to those cameras: the PoE port supplies power and a network link, but the event connection still has to be set up on the channel.

A few points specific to wired setups:

• Plug-and-play may not mean ONVIF. Some NVRs add a camera on a PoE port automatically using their own protocol. If that fails, or the channel shows no events, switch that channel to ONVIF and enter the camera's login.
• Check the camera supports PoE. Not every model does. Confirm it on the label or in the manual for your model before you rely on the NVR to power it.
• Power budget matters. An NVR's PoE ports share a limited amount of power. If a camera reboots when its night lights come on, the ports may be overloaded. The NVR's manual lists its budget.

For outdoor work, switch off power before running or reconnecting cables, use a stable ladder, and have a qualified electrician handle any mains wiring. If your cameras run on solar and batteries, many of them sleep between events and drop off the NVR entirely; the solar camera NVR guide explains which types can stay connected.

Reading the symptoms

• Live view works, no motion recordings at all. Channel is set to continuous or blank, or the event source is not linked to recording. Check Step 3 and Step 4.
• Event log empty, but the app sends motion alerts. The camera is detecting, but the NVR is not receiving. The camera may have been added as a plain stream, or its events are not compatible with your recorder. Re-add as ONVIF, or use NVR detection.
• Events appear, but no clips. Recording is not linked to the event, or the drive is full or unformatted.
• Clips start late. Pre-record is too short, or detection is slow at night. Raise pre-record on the NVR and check the camera's night settings.
• Too many clips. Zone or sensitivity is too broad, or both camera and NVR are triggering. Narrow the zone and pick one source.
• Events stopped after a power cut. The camera may have a new IP address, so the channel is offline. Reserve its address in the router.
• Motion clips at the wrong times. Clocks are out of sync between camera and NVR. Set both to the same time source.

When to get help

Contact the seller of your camera or your NVR when:

• The channel is added as ONVIF, the camera detects motion in the app, but the NVR's event log never shows anything even after you restart both devices.
• The NVR offers no motion setting at all for third-party channels.
• You need to know whether your exact model publishes motion events over ONVIF. This varies by model and firmware, and the seller can confirm it for the units you have.

Install or resell cameras?

For installers and shops, motion recording is the part customers notice when it fails, usually after an incident. A few habits help:

• Test events per model with each recorder you sell or install. Note whether camera-side events arrive, or whether you need NVR-side detection for that combination.
• Do a walk test with the customer and show them how to search playback by motion, not by time.
• Write down the channel settings you used, including record type and event source, so a later visit starts from known settings.
• Turn off duplicate detection before handover, so customers do not see double events.

If you install or sell cameras and want information about the dealer program, see the Yoosee business page.

Frequently asked questions

Why does my NVR show "video loss" or "offline" events instead of motion events?

Those entries mean the NVR lost its connection to the camera, not that motion was detected. Common causes are a changed IP address, a changed password, or a weak WiFi link. Fix the connection first; motion recording cannot work on an offline channel.

Will the NVR use the detection zone I drew in the Yoosee app?

Only when the NVR uses the camera's own events. In that case, the camera decides what counts as motion, using its app settings. If you switch to the NVR's own motion detection, you need to draw a new area on the NVR, because the recorder analyses the picture separately.

Can I get phone alerts and NVR motion recording at the same time?

Usually yes. The app alert and the ONVIF event are separate outputs from the camera, so both can work together. On some models, turning off app alerts also turns off detection, so check the NVR log after changing alert settings.

Does ONVIF send person detection to the NVR?

Sometimes, but often not. Many recorders only understand the plain motion event over ONVIF, so a camera's person detection may arrive as ordinary motion or not at all. If you need person-based recording, check whether your NVR offers its own person detection for third-party channels.

Is it better to record continuously and just search for motion later?

It is the safest backup, because nothing is lost if detection fails, but it fills the drive faster, so old footage is overwritten sooner. If your recorder allows continuous recording and motion tagging on the same channel, using both gives you full coverage and quick searching.