Why Is Frigate Audio Not Working in Live View?
- Camera audio codec not browser-compatible (needs AAC)
- Audio not included in the live stream
- go2rtc not passing/transcoding audio
Problem Description
Frigate live view shows video but no audio — the stream is silent in the web UI and Home Assistant. Audio must be enabled on the camera, included in the RTSP stream as AAC, passed through by Frigate's restream configuration, and unmuted in the browser (which auto-mutes video elements by default).
Why This Happens in Real Homes
Audio not working in Frigate live view is usually a codec issue — browsers need AAC audio to play a live stream via MSE/WebRTC, but many cameras output audio in a format (like PCM or G.711) the browser can't play directly. So the video comes through while the audio is silently dropped. The stream also has to actually include audio (sub-streams often don't).
Configure go2rtc to transcode the camera's audio to AAC for the live view, which is the standard fix, and make sure the stream you're viewing carries audio (the high-res main stream, not an audio-less sub-stream), with audio enabled on the camera. Confirm your browser supports the codec being served. Once go2rtc delivers AAC audio in the WebRTC/MSE live stream, sound plays.
Symptoms
- No audio in live view
- Video plays but no sound
- Audio missing from the stream
- No sound in the browser
- Audio not passing through
- Live view silent
- Sound doesn't work
- No audio via go2rtc
Recognize these? Here's what usually causes it.
Common Causes
- Camera audio codec not browser-compatible (needs AAC)
- Audio not included in the live stream
- go2rtc not passing/transcoding audio
- Stream is video-only
- Browser can't play the audio codec
- Audio disabled on the camera
- MSE/WebRTC audio config
- Sub-stream has no audio
Most fixes happen in the first 3 steps.
Avoid forcing unsupported codecs into browser playback paths.
Tools & Requirements
Step-by-Step Solution
Enable audio on the camera stream
Many IP cameras have audio disabled by default. Log into your camera's web interface and check the audio settings: enable audio, set the codec to AAC (most compatible), and set the sample rate to 8000 or 16000 Hz. The audio must be enabled on the specific stream that Frigate uses for the live view (restream role). If audio is only enabled on the main stream but your live view uses the sub stream: you will not hear audio.
Verify audio is included in the RTSP stream
Test if the RTSP stream contains audio: ffprobe rtsp://user:pass@camera-ip/stream. Look for an audio stream entry like 'Stream #0:1: Audio: aac' in the output. If no audio stream is listed: the camera is not including audio in the RTSP output. Re-check camera settings. Some cameras require a firmware update to enable audio over RTSP — older firmware versions only output audio through proprietary protocols.
Configure Frigate to include audio in the restream
Frigate must be configured to pass audio through to the restream. In frigate.yml, check the FFmpeg output args for the restream: if audio is stripped by a -an flag (no audio), remove it. The default Frigate presets should include audio, but custom FFmpeg args may accidentally exclude it. For RTMP restream: audio must be in AAC format. For WebRTC (go2rtc): audio codec must be compatible with the browser (Opus or AAC).
Check browser audio playback settings
Browser live view may have audio muted by default. In the Frigate web UI: look for a speaker/mute icon on the live view player and click to unmute. Chrome and Firefox auto-mute video elements by default (browser policy) — you must click to unmute. If using Home Assistant's Frigate integration: the camera card may not support audio playback. Use the go2rtc WebRTC card instead, which supports audio natively.
Use go2rtc for reliable audio streaming
Frigate uses go2rtc internally for stream management. go2rtc supports multiple streaming protocols (WebRTC, RTSP, MSE, HLS) with audio. Access go2rtc directly at http://frigate-ip:1984. Select the camera and choose WebRTC playback — this provides the lowest-latency stream with audio. If WebRTC audio works through go2rtc but not through the Frigate UI: the issue is in the Frigate UI player, not the stream. Use the go2rtc URL in a Home Assistant iframe or custom card for reliable audio.
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.
Keep a separate low-latency live profile that includes audio.
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.
- Camera audio codec not browser-compatible (needs AAC)
- Audio not included in the live stream
- go2rtc not passing/transcoding audio
- Stream is video-only
- Browser can't play the audio codec
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 Live Audio.
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.