[Bug]: Frigate Audio Detection Breaks When Disabling, then Re-enabling Camera #22493
-
Checklist
Describe the problem you are havingFollowing up on this reddit post: https://www.reddit.com/r/frigate_nvr/comments/1r83d9s/audio_debug_stopped_working/, Frigate periodically stops being able to perform audio detection. There is no data shown in the Debug Audio view when this occurs (both 0s), nor does MQTT get updated. Restarting Frigate resolves this issue until the camera is disabled and enabled again, which I believe is the root cause. Steps to reproduce
Version0.17.0-f0d69f7 In which browser(s) are you experiencing the issue with?No response Frigate config fileaudio:
enabled: true
min_volume: 300
listen:
- bark
- scream
- yell
- fire_alarm
- crying
- beep
- car_alarm
- siren
- alarm
- alarm_clock
- buzzer
- smoke_detector
- civil_defense_siren
- ping
- ding
scrypted_camera:
ffmpeg:
inputs:
- path: rtsp://[]
input_args: preset-rtsp-restream
roles:
- detect
- audio
- record
output_args:
record: preset-record-generic-audio-aac
detect:
width: 960
height: 540
fps: 5
objects:
track:
- person
record:
enabled: true
alerts:
retain:
days: 14
detections:
retain:
days: 14
continuous:
days: 0
motion:
days: 2
reolink_camera:
ffmpeg:
inputs:
- path: rtsp://[h264]
input_args: preset-rtsp-restream
roles:
- detect
- path: rtsp://[h264]
input_args: preset-rtsp-restream
roles:
- record
- audio
output_args:
record: preset-record-generic-audio-aac
detect:
width: 640
height: 360
fps: 5
objects:
track:
- person
motion:
mask: 0.285,0.021,0.283,0.1,0.702,0.091,0.702,0.019docker-compose file or Docker CLI commandHome Assistant Add-OnRelevant Frigate log outputNo Frigate logs show any errors related to cameras at issue.Relevant go2rtc log outputNo go2rtc logs show any errors related to cameras at issue.Operating systemHome Assistant OS Install methodHome Assistant Add-on Network connectionWired Camera make and modelMultiple camera brands, although all RTSP streams Screenshots of the Frigate UI's System metrics pagesUpon disable and re-enable immediately after restart (and refreshing page): Any other information that may be helpfulNo response |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
|
This appears to be a legitimate bug where audio detection stops working after disabling and re-enabling a camera via the UI or MQTT. Based on your description, the audio ffmpeg process is not being properly restarted when the camera is re-enabled. A few things to note about the expected behavior: Cameras can be temporarily disabled through the Frigate UI and through MQTT. When disabled, Frigate's ffmpeg processes are terminated — recording stops, object detection is paused, and the Live dashboard displays a blank image with a disabled message. (1) The ffmpeg process for capturing audio will be a separate connection to the camera along with the other roles assigned to the camera. (2) You can monitor the audio stream status via MQTT at Workarounds to try:
Since this behavior is reproducible (disable → re-enable → audio breaks until restart), this does appear to be a bug where the audio ffmpeg process isn't being properly respawned when the camera is re-enabled. The fact that RMS and dBFS both show 0.0 after re-enabling confirms the audio stream isn't being processed at all. This is worth reporting as a bug on the Frigate GitHub repository if you haven't already, as the camera enable/disable functionality should properly restart all associated ffmpeg processes including audio. 📚 Sources: Have another question? Just tag @inkeep. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks, this is fixed in #22495 and will be a part of Frigate 0.17.1. |
Beta Was this translation helpful? Give feedback.


Thanks, this is fixed in #22495 and will be a part of Frigate 0.17.1.