Forgive my poor English,After starting frigate, the camera's microphone functions are randomly turned on and off #19820
-
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 6 replies
-
|
Your English is clear! Based on your configuration and the Frigate documentation, the appearance of the microphone button in the UI depends on whether Frigate detects a working audio stream for each camera at startup. Even if both camera configs are the same, the presence of the microphone button can be inconsistent if:
To improve reliability, ensure:
The Frigate documentation also notes that the ffmpeg process for capturing audio is a separate connection from other roles, so using go2rtc restream for audio is recommended for reliability(1). If the problem continues, check your Frigate logs for errors about the audio stream or ffmpeg process when the microphone button is missing. This can help identify whether the issue is with the stream, network, or Frigate startup timing(1). 📚 Sources: Have another question? Just tag @inkeep. |
Beta Was this translation helpful? Give feedback.
-
|
You need to add #backchannel=0 so that the backchannel connection is not opened by default |
Beta Was this translation helpful? Give feedback.
-
|
Setting backchannel=0 does work, the microphone icons for both cameras disappear. However, I'd like the microphone icons to be visible on both cameras, meaning I can choose to start a call. |
Beta Was this translation helpful? Give feedback.
-
|
After I added the timeout parameter, both cameras can show the microphone icon after each restart:timeout=30 c_xi: |
Beta Was this translation helpful? Give feedback.





You need to add #backchannel=0 so that the backchannel connection is not opened by default