How to Fix Frigate Birdseye Not Showing One Camera
- Birdseye mode set to motion/objects (camera idle)
- Birdseye disabled for that camera
- No motion/objects on the camera (in those modes)
Problem Description
One of your cameras does not appear in Frigate's Birdseye combined overview while other cameras show up normally. The camera may not be enabled for Birdseye in your frigate.yml config, the Birdseye mode may be set to 'objects' (hiding the camera when no detection is active), or the camera's RTSP stream may not be connecting.
Why This Happens in Real Homes
A camera not appearing in Frigate Birdseye is usually the Birdseye mode doing its job — in the default "motion" or "objects" mode, Birdseye only shows cameras that currently have motion or detected objects, so an idle camera won't appear. It's an activity-based overview, not a fixed grid, unless you set it to "continuous."
If you want a camera always visible, set the Birdseye mode to continuous (globally or per camera). Otherwise, the camera will appear when there's motion or objects. Also confirm Birdseye is enabled for that camera, its stream is actually working (no "no frames" issue), and the go2rtc restream backing Birdseye is functioning. For a fixed always-on overview, continuous mode is the setting you want.
Symptoms
- Camera not in Birdseye
- Birdseye missing a camera
- Camera never appears in Birdseye
- Birdseye blank for a camera
- Only some cameras in Birdseye
- Camera absent from the overview
- Birdseye not displaying a feed
- Missing camera tile
Recognize these? Here's what usually causes it.
Common Causes
- Birdseye mode set to motion/objects (camera idle)
- Birdseye disabled for that camera
- No motion/objects on the camera (in those modes)
- Camera stream/role issue
- go2rtc restream for birdseye not working
- Config excludes the camera
- Camera offline/no frames
- Birdseye layout/limit
Most fixes happen in the first 3 steps.
Do not assume Birdseye inclusion defaults match per-camera intent.
Tools & Requirements
Step-by-Step Solution
Check that the camera is enabled in Birdseye config
Birdseye is Frigate's combined overview display that stitches multiple camera feeds into one view. Each camera must be explicitly enabled for Birdseye in your frigate.yml config. Under the camera section, add or verify: birdseye: enabled: true. If the camera has birdseye: enabled: false or the birdseye key is missing entirely: that camera does not appear in the Birdseye view. After changing the config, restart Frigate for the setting to take effect.
Set the Birdseye mode
Each camera's Birdseye mode controls when it appears in the overview. Options: 'continuous' (always shows), 'objects' (shows only when an object is detected), 'motion' (shows only during motion), 'static' (shows a static image). If set to 'objects' and no object is detected: the camera disappears from Birdseye until the next detection. Set mode to 'continuous' if you want the camera always visible: birdseye: mode: continuous. The 'objects' mode is useful for reducing Birdseye clutter — only active cameras appear.
Verify the camera stream is working
If the camera's RTSP stream is not connecting in Frigate: Birdseye has nothing to display. Check the Frigate logs for FFmpeg errors related to that camera (connection refused, timeout, authentication failure). Go to the camera's individual view in the Frigate web UI — if it shows 'No stream available' or a black rectangle: fix the camera stream first. Common fixes: verify the RTSP URL is correct, check camera credentials, confirm the camera is online and accessible from the Frigate server.
Check Birdseye resolution and layout
Birdseye arranges cameras in a grid. If you have many cameras (8+), some may be too small to see or may be pushed off the visible area. The Birdseye resolution is set globally: birdseye: width: 1920, height: 1080 (default). With 12 cameras, each gets approximately 480x360 pixels. If a camera appears but is tiny or partially visible: increase the Birdseye resolution to 2560x1440 or 3840x2160 (requires more CPU/GPU to render). Individual camera order in the grid follows the order in frigate.yml.
Restart Frigate after config changes
Birdseye configuration is read on Frigate startup — changes to frigate.yml do not take effect until you restart. Restart Frigate through the Home Assistant add-on page (Settings > Add-ons > Frigate > Restart), or 'docker restart frigate' if running in Docker. After restarting, check the Birdseye view in the Frigate web UI (typically at http://your-ip:5000). The camera should appear within 10-30 seconds of the stream connecting.
Quick Solutions
Still having issues? This is usually the deeper cause below.
Camera issues that start suddenly almost always trace back to an upload bandwidth drop — run a speed test before assuming hardware failure.
Use consistent camera naming to avoid layout filter mistakes.
Live view problems that start suddenly usually trace back to an upload speed drop — the camera itself is fine, the bandwidth path to the cloud isn't.
- Birdseye mode set to motion/objects (camera idle)
- Birdseye disabled for that camera
- No motion/objects on the camera (in those modes)
- Camera stream/role issue
- go2rtc restream for birdseye not working
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 Birdseye Layout.
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.