[Bug]: Latest frame API can return code 500 for birdseye #19572
-
Checklist
Describe the problem you are havinghttps://docs.frigate.video/integrations/api/latest-frame-camera-name-latest-extension-get/ Moreover, Frigate produces a massive amount of error logs unrelated to the request when there's such a configuration. Steps to reproduce
Version0.16 In which browser(s) are you experiencing the issue with?No response Frigate config filebirdseye:
enabled: false
restream: true docker-compose file or Docker CLI commandn/a Relevant Frigate log outputToo long, attached as a file Relevant go2rtc log outputn/a Operating systemOther Linux Install methodDocker Compose Network connectionMixed Camera make and modeln/a Screenshots of the Frigate UI's System metrics pages![]() Any other information that may be helpfulFor the request not to return Line 204 in 6840415 But for the error logs, I have no idea. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
This is a configuration issue where you have birdseye disabled but restream enabled, which creates a conflict when the API tries to serve the birdseye latest frame(1)(2). Based on the configuration reference, birdseye has two key settings(2): birdseye:
# Optional: Enable birdseye view (default: shown below)
enabled: True
# Optional: Restream birdseye via RTSP (default: shown below)
# NOTE: Enabling this will set birdseye to run 24/7 which may increase CPU usage somewhat.
restream: False Your configuration has To fix this issue, you have two options:
birdseye:
enabled: true
restream: true
birdseye:
enabled: false
restream: false The documentation notes that enabling birdseye restream will cause birdseye to run 24/7 which may increase CPU usage somewhat(1)(2). If you don't need the birdseye functionality, it's better to disable both settings to avoid the 500 error and excessive logging. 📚 Sources: Have another question? Just tag @inkeep. |
Beta Was this translation helpful? Give feedback.
The AI is correct here, the configuration is problematic.
Nonetheless, this has been improved in #19573