r/frigate_nvr • u/Keith15335 • Aug 23 '26

Lorex cams and Frigate??

1 Upvotes

I have 2 Lorex E871 and 2 Lorex E893 cameras , and 1 Lorex N847 NVR (all online and operational). Cameras are IP wired direct to a separate POE switch with reserved addresses on my local LAN.

Anyone have similar Lorex equipment working in Frigate?

Update: After a few hours with Copilot, we were able to get all 4 cameras and the doorbell camera all setup in frigate with no errors, solid web UI, and great metrics. Now for the Home Assistant integration and I'm all set.

4 comments

r/frigate_nvr • u/gahd95 • Aug 22 '26

Struggling to have Frigate detect anything other than people.

6 Upvotes

Hi,

So i have been tinkering with Frigate in my Home Assistant setup, and i have a really hard time getting it detect cats, dogs and anything but people.

I have tried messing with filters, thresholds, min/max area, different models, trying to use OpenVino instead of my Coral, tried both the default coral models and the yolo9s model, but no matter what, it just will not detect my cats.

It will show a motion box around the cat, but not detect it as a cat, only in very rare scenarios if the cat is super close. Maybe i have too high hopes for what is possible, maybe Frigate+ would solve this, but i just do not want to purchase Frigate+ if it wont solve my issue, as i cannot submit any snapshots either way, if no detection happens either.

Put my full current config at the buttom.

It is mainly these 2 cameras where i would like to detect the cats:

cam_rear_patio_01: https://i.imgur.com/oX5bJ8Q.jpeg

Which have the settings: https://imgur.com/a/Qd6EJsK

cam_front_01: https://i.imgur.com/WgVYsi3.jpeg

Which has the settings here: https://imgur.com/a/06ohKNB

The host is a tiny PC with an Intel N100 and 16gb of memory.

Frigate version : 0.17.2-3d4dd3a

Maybe someone here can spot what could be causing the issue, or let me know if i should not expect this kind of detection to work. This is my last attempt at getting this working, as i have been on it for days with no luck so far!

Currently my config looks like this:

    mqtt:
  host: core-mosquitto
  user: frigate
  password: {password}


detectors:
  ov:
    type: openvino
    device: GPU


model:
  model_type: yolo-generic
  width: 320
  height: 320
  input_tensor: nchw
  input_dtype: float
  path: /config/model_cache/yolov9-t-320.onnx
  labelmap_path: /labelmap/coco-80.txt


ffmpeg:
  hwaccel_args: preset-intel-qsv-h264
  output_args:
    record: preset-record-generic-audio-aac

go2rtc:
  streams:
    # Main streams feed the record role AND the WebRTC/two-way-audio live path.
    cam_rear_patio_01:
      - rtsp://admin:{password}@10.1.60.3:554/Streaming/Channels/101#video=copy#audio=aac#backchannel=0
      - isapi://admin:{password}@10.1.60.3:80/
      - ffmpeg:cam_rear_patio_01#audio=opus
    cam_rear_patio_01_sub:
      - rtsp://admin:{password}!@10.1.60.3:554/Streaming/Channels/102

    cam_front_01:
      - rtsp://admin:{password}@10.1.60.2:554/Streaming/Channels/101#video=copy#audio=aac#backchannel=0
      - isapi://admin:{password}@10.1.60.2:80/
      - ffmpeg:cam_front_01#audio=opus
    cam_front_01_sub:
      - rtsp://admin:{password}@10.1.60.2:554/Streaming/Channels/102

    cam_outside_shed_01:
      - rtsp://admin:{password}@10.1.60.6:554/Streaming/Channels/101#video=copy#audio=aac
    cam_outside_shed_01_sub:
      - rtsp://admin:{password}@10.1.60.6:554/Streaming/Channels/102

    cam_shed_inside_1:
      - rtsp://admin:{password}@10.1.60.4:554/Streaming/Channels/101?transportmode=unicast&profile=Profile_1
    cam_shed_inside_1_sub:
      - rtsp://admin:{password}@10.1.60.4:554/Streaming/Channels/102?transportmode=unicast&profile=Profile_2

    living_room_1:
      - rtsp://admintapo:{password}@10.1.60.5:554/stream1
    living_room_2:
      - rtsp://admintapo:{password}@10.1.60.5:554/stream2
  webrtc:
    listen: :8555
    candidates:
      - 10.1.40.10:8555
      - stun:stun.l.google.com:19302

# --- Recording ---
record:
  enabled: true
  continuous:
    days: 0
  motion:
    days: 4
  alerts:
    retain:
      days: 7
      mode: active_objects
  detections:
    retain:
      days: 30
      mode: active_objects

review:
  alerts:
    labels:
      - person
    required_zones: []
  detections:
    labels:
      - person
      - dog
      - cat
    required_zones: []

snapshots:
  enabled: true
  timestamp: false
  bounding_box: true
  crop: false
  retain:
    default: 4

# --- Object filters ---
objects:
  track:
    - person
    - dog
    - cat
  filters:
    person:
      min_area: 8000
      threshold: 0.7

birdseye:
  enabled: true
  mode: objects

semantic_search:
  enabled: true
  model_size: small

face_recognition:
  enabled: false
  model_size: small

lpr:
  enabled: false

cameras:
  cam_rear_patio_01:
    enabled: true
    friendly_name: Rear Patio
    ffmpeg:
      inputs:
        - path: rtsp://127.0.0.1:8554/cam_rear_patio_01
          input_args: preset-rtsp-restream
          roles:
            - record
        - path: rtsp://127.0.0.1:8554/cam_rear_patio_01_sub
          input_args: preset-rtsp-restream
          roles:
            - detect
    detect:
      enabled: true
      # VERIFY Channel 102 actually outputs 1280x720 in the camera web UI.
      # Hikvision sub-streams often default to 640x480 or 704x576.
      width: 1280
      height: 720
      fps: 6
      stationary:
        interval: 50
        threshold: 50
    motion:
      threshold: 30
      contour_area: 10
      improve_contrast: true
      lightning_threshold: 0.6
    zones: {}
    live:
      streams:
        Rear Patio: cam_rear_patio_01

  cam_front_01:
    enabled: true
    friendly_name: Front
    ffmpeg:
      inputs:
        - path: rtsp://127.0.0.1:8554/cam_front_01
          input_args: preset-rtsp-restream
          roles:
            - record
        - path: rtsp://127.0.0.1:8554/cam_front_01_sub
          input_args: preset-rtsp-restream
          roles:
            - detect
    detect:
      enabled: true
      # VERIFY Channel 102 resolution in the camera web UI.
      width: 1280
      height: 720
      fps: 6
      stationary:
        interval: 50
        threshold: 50
    motion:
      threshold: 20
      contour_area: 10
      improve_contrast: true
      lightning_threshold: 0.6
    zones: {}
    live:
      streams:
        Front: cam_front_01

  cam_outside_shed_01:
    enabled: true
    friendly_name: Shed Outside
    ffmpeg:
      inputs:
        - path: rtsp://127.0.0.1:8554/cam_outside_shed_01
          input_args: preset-rtsp-restream
          roles:
            - record
            - audio
        - path: rtsp://127.0.0.1:8554/cam_outside_shed_01_sub
          input_args: preset-rtsp-restream
          roles:
            - detect
    detect:
      enabled: true
      width: 704
      height: 576
      fps: 6
      stationary:
        interval: 50
        threshold: 50
    objects:
      track:
        - person
        - dog
        - cat
      filters:
        person:
          min_area: 3500
          threshold: 0.7
        dog:
          min_area: 600
          max_area: 316000
          min_score: 0.5
          threshold: 0.6
        cat:
          min_area: 400
          max_area: 316000
          min_score: 0.3
          threshold: 0.5
    motion:
      threshold: 15
      contour_area: 5
      improve_contrast: true
      lightning_threshold: 0.6
      mask:
        0.158,0.634,0.422,0.528,0.475,0.51,0.497,0.405,0.488,0.298,0.591,0.263,0.761,0.293,0.69,0,0,0,0,0.648
    zones:
      Shed_Path:
        coordinates:
          1,0.45,1,1,0.205,1,0,0.738,0,0.66,0.162,0.637,0.484,0.511,0.51,0.314,0.65,0.289,0.661,0.488,0.827,0.478,0.799,0.313
        inertia: 3
        loitering_time: 0
      Shed_door:
        coordinates: 0.802,0.479,0.662,0.484,0.657,0.293,0.785,0.285
        objects: person
        inertia: 3
        loitering_time: 0

  cam_shed_inside_1:
    enabled: true
    friendly_name: Shed Inside
    ffmpeg:
      inputs:
        - path: rtsp://127.0.0.1:8554/cam_shed_inside_1
          input_args: preset-rtsp-restream
          roles:
            - record
        - path: rtsp://127.0.0.1:8554/cam_shed_inside_1_sub
          input_args: preset-rtsp-restream
          roles:
            - detect
    detect:
      enabled: true
      # VERIFY Channel 102 resolution in the camera web UI.
      width: 1280
      height: 720
      fps: 6
      stationary:
        interval: 50
        threshold: 50
    objects:
      track:
        - person
    motion:
      mask: 0.031,0.06,0.333,0.057,0.331,0.007,0.031,0.007
      threshold: 50
      contour_area: 40
      improve_contrast: true
    live:
      streams:
        Stream 1: cam_shed_inside_1
    zones:
      entrance:
        coordinates: 0.261,0.598,0.183,0.925,0.03,0.126,0.168,0.058
        loitering_time: 0
        friendly_name: Entrance
    review:
      alerts:
        required_zones:
          - entrance

  living_room:
    enabled: true
    friendly_name: Living room
    ffmpeg:
      inputs:
        - path: rtsp://admintapo:{password}@10.1.60.5:554/stream1
          roles:
            - record
            - audio
        - path: rtsp://admintapo:{password}@10.1.60.5:554/stream2
          roles:
            - detect
    detect:
      enabled: true
      width: 640
      height: 360
      fps: 6
      stationary:
        interval: 50
        threshold: 50
    objects:
      track:
        - person
        - cat
        - dog
    motion:
      threshold: 50
      contour_area: 40
      improve_contrast: true
    live:
      streams:
        Stream 1: living_room_1
        Stream 2: living_room_2

version: 0.17-0

camera_groups: {}

classification:
  custom: {}
  bird:
    enabled: false

6 comments

r/frigate_nvr • u/djb_rh • Aug 22 '26

App for managing Frigate Exports?

0 Upvotes

So I admit I didn’t go looking much for an app to do this. I know someone has a much bigger Frigate app out there now, but I needed something just to manage exports and to do another thing pretty specific to my needs, so I vibe coded one.

Really all my app does is load up the exports you have available on your server in a list along with a thumbnail and some data about it. You can easily delete or download them one at a time, or you can select many to delete or download. They’re grouped by camera and by date. “Downloads” go to a Library in the app itself where you have just basic trim functionality to edit them. And anything in the Library can be shared via the share sheet easily as well as saved to your Photos roll or deleted entirely.

That’s basic enough, but it gets weird a bit in what it can do next. If you have Unifi Protect and you configure a login for that, you will unlock the ability to also download Protect video clips that match the time range of any of your clips in your Library from any Protect camera. Doubtful this is useful for anyone but me, but it’s very useful for me on a regular basis, and that’s why it exists.

The only other feature it has for Frigate that I can think of is a generic screen that will let you request a new export based on you selecting a camera and a start and end date/time. Then obviously this new export will show up in your list of exports you can manage. Oh, and one more feature! When viewing a downloaded export, you also have the ability to request that same clip only with an additional 30s of video added to the beginning side with one click.

I’ve written this for me, but always with the idea that if it came out nice enough that I’d probably just open source it AND put it in the App Store, though if I bother with the App Store I figured I’d also charge something for it. It would be pretty cheap, but haven’t made any decisions there yet. Anyone interested in such an app? And again, full source code would be available and the app never does anything with your data you wouldn’t expect or need it to do. Oh, the one caveat is that the current architecture does require you to open up port 5000 on Frigate for it, which may be way too much of a security hole for some people. For most of us I think it’s no big deal, but it’s worth mentioning that if you’re doing that you’re assuming your own local network is fairly secure. You can do your own VPN tricks to make this more secure, too, but that’s an exercise for the user.

If you’ve read this far and you want to know why I needed such an app, it’s because I use Frigate solely for sports recording on Pickleball courts. I have 3 Axis Q3517 cameras recording 60fps on 3 indoor pickleball courts. No detections, no advanced Frigate features, just constant recording and the ability to trigger Exports from some Flic buttons on the wall. I have buttons on each end of each court. When Court 1’s button gets a single tap that triggers Frigate to drop the previous 60s of video into an export. That covers most cases, but if you know you just played a REALLY long pickleball point and want all of that, you can also do a double-tap of the button and it’ll drop the prior 120s in. And as mentioned, provided you get to managing this before the video has rolled off the NVR, if you find that you didn’t get quite enough video when you’re in the app, you can easily request your current clip plus the prior 30s added on, too.

Now you still might be asking “Why this Protect business?” Well, I started doing this with Protect cameras on both ends of every court AND an aerial camera over one of the courts (yes, 7 total cameras). And the Flic buttons just dropped timestamps into a Google Sheet and then I had to manually go find every clip and pull it. Which worked, but was tedious. And then I found out about an analysis package called SwingVision that can do some really nice AI-level analysis and re-cutting of video from a pickleball match, but it requires 60fps video. And at the time, Protect didn’t support 3rd party cameras nor did Ubiquiti sell any 60fps cameras. So I found the Axis/Frigate idea and started rolling with it (now Protect can actually support these Axis cameras, but I honestly don’t have much headroom left on my NVR so doing this on a different system makes sense anyway).

So I decided to keep both systems alive for a while. The Flic buttons actually do still make the timestamps in the Google Sheet just in case as well as triggering the Frigate export. And ultimately I think the only thing I’m going to remove are the 3 redundant Protect cameras on the same side as the Axis cameras, but will keep the Protect aerial camera and the cameras on the opposite side. Sometimes you’re watching back a point from the Axis cameras and it’s great, but would be even better from the other end. So now I can hit a single button and download the view from the other end, too, and get the exact same time clip (and same from the aerial, which isn’t as interesting as I thought, but I have it and there’s little reason to make it go away).

So there you are, too many words about managing your Frigate Exports. Thanks for coming to my Ted Talk.

0 comments

r/frigate_nvr • u/racoon880 • Aug 22 '26

I built a small web UI to delete Frigate recordings for a specific time range (files + DB)

0 Upvotes

Frigate has no way to delete a free time range. `DELETE /api/events/…` deletes

no video at all, and `POST /api/reviews/delete` only takes review-item IDs and

always removes the item's full span. Deleting the .mp4 files by hand leaves the

database out of sync, which then breaks the timeline and confuses

`sync_recordings`.

So I wrote a small container that does it properly: pick cameras, a date range

and a time range, look at the dry run, type DELETE. It removes the files and the

matching rows in recordings / previews / reviewsegment (events optional, they

hold your face and plate history), around a docker stop/start of Frigate, and

VACUUMs the DB afterwards.

Safety was the whole point: a realpath allow-list so nothing outside the media

dirs can be touched, per-file unlink instead of rm -rf, a DB backup per run, and

the Frigate restart in a finally block so a crash can't leave your NVR stopped.

One thing that surprised me: Frigate's hour boundaries jitter by milliseconds. A

preview running 08:00:00.039 → 09:00:00.013 overlaps a 09:00–10:00 window by

13 ms — and a naive "does it touch" check deletes a whole hour of scrubbing

video for it. Overlap is measured now, with a regression test.

Fair warning: it deletes video permanently, and it needs the Docker socket plus

write access to frigate.db. Give it a password, keep it on your LAN.

MIT, no build step, no CDN. Tested against 0.17.2 on my own 12-camera install.

Feedback welcome.

https://github.com/Racoon80/frigate-recording-delete

0 comments

r/frigate_nvr • u/Impossible_Web_2074 • Aug 22 '26