FAQ

Answers about Frigate versions, camera audio, HTTPS on older Android, push alerts and login security.

Do I need a cloud account?

No. Beacon View connects directly to your Frigate server and cameras, with no cloud relay.

Which Frigate versions are supported?

Frigate 0.14 and newer, tested on 0.14 to 0.18. Adding or editing cameras from the app needs Frigate 0.17+ and an admin account.

Why is there no sound from a camera?

The app plays Opus or AAC audio only. Cameras that send G.711 (PCMA/PCMU) stay silent. In Frigate’s go2rtc config, add an Opus transcode to the sub stream, or switch the camera’s audio to AAC. Main streams usually already have the transcode. Standalone RTSP cameras with G.711 audio stay silent.

"<cam>-sub":
  - "rtsp://…"
  - "ffmpeg:<cam>-sub#audio=opus"

I can’t connect to https://<host>:8971 on Android 7–9

Frigate’s built-in HTTPS port accepts TLS 1.3 only, and Android supports TLS 1.3 from version 10. Use a reverse proxy that allows TLS 1.2, or connect over the HTTP port on your LAN.

Push alerts arrive late or stop (Samsung, Xiaomi and others)

While push is on, the app keeps a direct connection to Frigate with a foreground service. Some phones stop it to save battery. In Android settings, set Beacon View’s battery usage to Unrestricted, or turn off battery optimization for it.

Is my Frigate login safe?

Your login is stored encrypted with the Android Keystore. For self-signed HTTPS certificates, the app shows the certificate and pins it once you approve. Use https:// whenever you connect from outside your LAN.