Cameras

Fregata works with anything that exposes RTSP — which is almost every IP camera made. This page is a cheat-sheet of URL patterns by brand, plus the workarounds for cameras that are shy about their streams.

URL shapes by brand

Replace user:pass with your camera’s credentials and IP with the camera’s address. The “main stream” is the high-resolution feed for recording; the “sub-stream” is a lower-resolution feed for detection.

Reolink

Main:  rtsp://user:pass@IP:554/h264Preview_01_main
Sub:   rtsp://user:pass@IP:554/h264Preview_01_sub

For HEVC models, swap h264 for h265. Most modern Reolinks dual- encode — they’ll serve H.264 even when set to H.265 in the app.

Amcrest / Dahua

Main:  rtsp://user:pass@IP:554/cam/realmonitor?channel=1&subtype=0
Sub:   rtsp://user:pass@IP:554/cam/realmonitor?channel=1&subtype=1

Multi-channel NVRs from these brands increment the channel parameter (1, 2, 3…). The sub-stream toggle is subtype.

Hikvision

Main:  rtsp://user:pass@IP:554/Streaming/Channels/101
Sub:   rtsp://user:pass@IP:554/Streaming/Channels/102

The path is 1xx (main) and 1xy (sub-stream); for additional channels, increment the leading digit.

Lorex

Most Lorex models are rebadged Dahua. Try the Dahua URL first.

Ubiquiti UniFi Protect

UniFi cameras have RTSP disabled by default. To turn it on:

1. Open Protect.
2. Cameras → click camera → Settings → Advanced.
3. Under RTSP, enable each stream you want and copy the URL.

The URL UniFi gives you looks like rtsps://192.168.1.1:7441/<random-key> — it’s RTSP-over-TLS, port 7441. Fregata handles rtsps://; just paste the URL as-is.

Ring / Nest / Wyze (cloud-only)

These don’t expose RTSP. Workarounds:

• Ring — no first-party path. Some users run Wyze-Ring-RTSP-style proxies, but they’re brittle.
• Nest — Google killed the SDM API for new accounts; legacy Nest cams have community projects but nothing reliable.
• Wyze — Wyze sells official RTSP firmware for some models. If yours is supported, install that firmware and it becomes a normal RTSP camera.

If “no cloud” matters to you, buy cameras that ship RTSP first-class: Reolink, Amcrest, Dahua, Hikvision, UniFi.

Tapo / TP-Link

Main:  rtsp://user:pass@IP:554/stream1
Sub:   rtsp://user:pass@IP:554/stream2

Tapo cameras require you to enable the camera account in the Tapo app first (Settings → Camera Account → Set Up). The username/password you set there is what RTSP uses, separate from your Tapo account credentials.

Axis

rtsp://user:pass@IP/axis-media/media.amp

Axis URLs accept a videocodec query param if you want to pin the codec. Without it, the camera serves whatever’s negotiated.

Generic ONVIF

Cameras that follow the ONVIF spec (most of them) expose stream URLs via the Media2 service. The easiest discovery tool is ONVIF Device Manager, which connects, lists profiles, and prints the RTSP URL for each.

Webcams (USB or built-in iSight)

USB and built-in cameras don’t speak RTSP. Two options:

1. Run go2rtc with a ffmpeg:device source to fan out a built-in or USB camera as RTSP. go2rtc is already part of Fregata’s bundle; configure it via go2rtc.streams in config.yml. See go2rtc’s README for syntax.
2. Plug in via Continuity Camera — your iPhone’s camera shows up as a webcam to macOS, which go2rtc can then serve. Useful for one-off “what does that camera angle look like” tests.

This isn’t the use case Fregata’s tuned for — single-purpose IP cameras are the boring, reliable choice — but the mechanism works.

Sub-streams: optional power saver

On Linux Frigate, the standard pattern is main stream for recording, sub-stream for detection — sub-streams are usually 640×480, which keeps the CPU detection path tractable. On Fregata you don’t need this. The ANE handles inference at full resolution and full FPS without breaking a sweat, and VideoToolbox decodes the main stream nearly for free. The simpler config is the default:

cameras:
  driveway:
    ffmpeg:
      inputs:
        - path: rtsp://user:[email protected]:554/h264Preview_01_main
          roles: [record, detect]

One stream in, one decode pass, both roles served from the same buffer.

There are still two narrow cases where adding a sub-stream pays:

• Power tuning on a laptop. Decoding a 4K main stream and running ANE inference on every frame draws ~3–6 W more than decoding a 640×480 sub-stream. Not visible on a Mac mini that’s plugged in; meaningful on a battery-only setup.
• Network-constrained installs. If the cameras share a congested Wi-Fi link with the Mac and packet loss is making RTSP brittle, a sub-stream halves the bytes-per-second per camera.

The sub-stream variant looks like this:

cameras:
  driveway:
    ffmpeg:
      inputs:
        - path: rtsp://user:[email protected]:554/h264Preview_01_main
          roles: [record]
        - path: rtsp://user:[email protected]:554/h264Preview_01_sub
          roles: [detect]

If your camera doesn’t expose a separate sub-stream URL, the single-stream default is what you want anyway.

Forcing TCP transport

If detection is choppy and ffprobe shows the camera is reachable over TCP but not UDP (a common Wi-Fi failure mode), pin the transport:

ffmpeg:
  input_args: -avoid_negative_ts make_zero -fflags +genpts+discardcorrupt -rtsp_transport tcp -timeout 5000000 -use_wallclock_as_timestamps 1

This is also Fregata’s default for most camera profiles — you shouldn’t need to set it unless you’ve overridden input_args elsewhere.

What about ONVIF auto-discovery?

Frigate has an onvif config block on each camera for PTZ control and presets. It doesn’t replace the RTSP URL — you still need that. The ONVIF block is for telling Fregata “this camera’s pan-tilt- zoom is at port 8000, and here’s how to authenticate”. See the Frigate ONVIF docs for the details.

Tip

When in doubt, test the URL with ffprobe -rtsp_transport tcp '<url>' before you put it in Fregata’s config. If ffprobe can’t open it, neither can Fregata.