How to Fix Frigate Motion Masks Ignoring Actual Motion Areas
- Motion mask covers an area you want detected
- Mask coordinates too large/wrong
- Confusing motion mask with a zone
Problem Description
You added a motion mask in Frigate to block detections in a specific area (trees, road, neighbor's yard), but motion events are still being triggered there. The mask may be the wrong type (motion mask vs. object filter mask), the coordinates may not match the detect stream resolution, the mask may not fully cover the area, or the config was not reloaded after the change.
Why This Happens in Real Homes
A Frigate motion mask ignoring an area you care about is working exactly as designed — a motion mask tells Frigate to NOT look for motion in that region, so if you drew it over an area you actually want monitored, no detection happens there. Motion masks are meant only for constant-noise areas (swaying trees, a timestamp overlay, a busy road) that would otherwise trigger endless detections.
Remove or resize the mask so it no longer covers the area you want detected, keeping motion masks strictly over regions of persistent false motion. If your goal was to define an area of interest (like a driveway) rather than block noise, use a zone instead — zones filter which detections you care about without stopping motion detection. Redraw masks after any camera reposition, and remember: masks block, zones filter.
Symptoms
- Motion mask blocks a real area
- Mask ignoring wanted motion
- No detection where I need it
- Mask over the wrong area
- Missing motion in a masked region
- Mask too large
- Objects missed due to a mask
- Mask covering important zone
Recognize these? Here's what usually causes it.
Common Causes
- Motion mask covers an area you want detected
- Mask coordinates too large/wrong
- Confusing motion mask with a zone
- Mask drawn over the monitored path
- Mask intended for noise blocking real motion
- Overlapping masks
- Mask not updated after moving the camera
- Misunderstanding mask purpose
Most fixes happen in the first 3 steps.
Do not reuse masks across cameras with different fields of view.
Tools & Requirements
Step-by-Step Solution
Understand mask types in Frigate
Frigate has two mask types that work differently. Motion masks: block the motion detector from seeing movement in masked areas — motion is ignored there entirely. Object filter masks: block the object detector from reporting detections in masked areas — motion is still detected but objects are not reported. If you added a motion mask but objects are still being detected: you may need an object filter mask instead, or you used the wrong mask type. Check which type you configured in frigate.yml.
Verify the mask coordinates match the camera view
Masks are defined as polygon coordinates relative to the detect stream resolution. If your detect resolution is 1280x720: the coordinate (640, 360) is the center of the frame. If you copied mask coordinates from a 1920x1080 source but your detect stream is 720p: the mask is in the wrong position. Use the Frigate web UI mask editor to draw masks visually — it automatically uses the correct resolution. Click a camera in the Frigate UI, then click the mask/zone editor icon.
Check if the mask covers the entire motion area
Motion masks must fully cover the area you want to ignore. If a tree branch extends beyond the mask boundary: the portion outside the mask still triggers motion. Frigate's motion detector operates on the full detect frame — any unmasked moving pixels trigger motion detection. Make masks slightly larger than the problem area to account for wind sway, shadow movement, and slight camera angle shifts.
Apply the mask to the correct camera
In frigate.yml, masks are defined per camera. A common error: defining the mask under the wrong camera name, or under a global motion config that does not apply to the specific camera. Verify the mask is indented under the correct camera section: cameras: front_yard: motion: mask: - your_coordinates. If defined under a different camera name: it masks that camera, not the one you intended.
Restart Frigate after mask changes
Mask changes in frigate.yml require a Frigate restart to take effect. Edit the config, save, and restart Frigate (Settings > Add-ons > Frigate > Restart, or docker restart frigate). After restarting, check the Frigate debug view for the camera — the motion overlay should show the masked areas in a different color. If the mask does not appear in the debug view: the config syntax is wrong. Check Frigate logs for YAML parsing errors.
Quick Solutions
Still having issues? This is usually the deeper cause below.
If the sensor still misses events after repositioning, check whether a scheduled 'home' or 'away' mode is overriding the sensitivity setting silently.
Mask tuning should be revisited after camera repositioning.
This issue almost always looks more complex than it is — the majority of cases trace back to a single setting, a stale credential, or a default that shipped wrong.
- Motion mask covers an area you want detected
- Mask coordinates too large/wrong
- Confusing motion mask with a zone
- Mask drawn over the monitored path
- Mask intended for noise blocking real motion
Before you go — try one of these (they fix most cases).
Official Manufacturer Manual
Frigate provides official product documentation through their online manual rather than downloadable PDF. Access setup guides, troubleshooting steps, and product specifications for your Frigate Motion Mask Tuning.
Source: docs.frigate.video
Need More Help? Frigate Support
Note: The contact information below connects you directly to Frigate's official customer support team, not Trunetto. They can help with warranty claims, device replacements, and advanced technical issues.