[Support]: "No recordings found for <camera name> during the requested time range" in 0.14 #12809

darmach · 2024-08-07T16:27:49Z

darmach
Aug 7, 2024

Describe the problem you are having

I have one quite active camera (sidewalk) and I noticed that after clicking on some of the detections in the review Panel, a video playback opens - however video never starts to play. Error logged:

Type
error
Timestamp
2024-08-07 18:07:50
Tag
frigate.api.media
Message
No recordings found for cam2 during the requested time range

In similar situation in the morning today, I was able to find the recording on to filesystem and even export in succesfully. Tried to replicate it now, and I can't find the recording for the current detection indeed. Also noticed that directories are not in sequence - like I'm missing no. 15?

root@frigate:/var/lib/frigate/storage/recordings/2024-08-07# tree
.
├── 13
│   └── cam2
│       ├── 31.56.mp4
│       ├── 32.06.mp4
│       ├── 32.17.mp4
│       └── 32.27.mp4
├── 14
│   └── cam2
│       ├── 29.10.mp4
│       ├── 29.20.mp4
│       ...
│       └── 31.11.mp4
└── 16
    ├── cam2
    │   ├── 00.14.mp4
    │   ...
    │   └── 01.25.mp4
    └── cam3
        ├── 05.05.mp4
        ...
        ├── 06.24.mp4

Steps to reproduce

Go to review page, detections panel. Click on detection, some of them are unable to play video. error is logged:
No recordings found for cam2 during the requested time range

Version

0.14.0-7c39b17

Frigate config file

mqtt:
  enabled: True
  host: XXXX
  user: XXXX
  password: XXXX

ui:
  time_format: 24hour

detectors:
  coral:
    type: edgetpu
    device: pci

detect:
  enabled: True
  fps: 10

objects:
  track:
    - person
    - cat
    # - bird
    # - dog
    # - car

record:
  enabled: True

birdseye:
  enabled: True
  mode: continuous
  width: 2560
  height: 1440
  quality: 1

snapshots:
  enabled: true
  bounding_box: true

go2rtc:
  streams:
    cam1:
      - rtsp://192.168.1.101:554/live0.264
    cam2:
      - rtsp://192.168.1.102:554/live0.264
    cam3:
      - rtsp://192.168.1.103:554/live0.264
    cam4:
      - rtsp://192.168.1.104:554/live0.264

# Optional: jsmpeg stream configuration for WebUI
live:
  height: 1080
  quality: 1

cameras:
  cam1:
    enabled: True
    ffmpeg:
      hwaccel_args: preset-vaapi
      inputs:
        - path: rtsp://127.0.0.1:8554/cam1
          input_args: preset-rtsp-restream
          roles:
            - detect
            - record
    motion:
      mask:
        - 1440,0,1920,0,1920,64,1440,64
  cam2:
    enabled: True
    ffmpeg:
      hwaccel_args: preset-vaapi
      inputs:
        - path: rtsp://127.0.0.1:8554/cam2
          input_args: preset-rtsp-restream
          roles:
            - detect
            - record
    motion:
      mask:
        - 1440,0,1920,0,1920,64,1440,64
      threshold: 30
      contour_area: 31
    zones:
      Parcel:
        coordinates: 0,0.362,0.844,0.438,0.999,0.689,0.999,0.846,0.92,0.998,0,0.998
        loitering_time: 0
      Street:
        coordinates: 0,0.358,0.845,0.428,0.873,0.333,0.433,0.214,0,0.168
        loitering_time: 0
      Sidewalk:
        coordinates: 0,0,0.573,0,1,0.265,0.975,0.392,0.876,0.345,0.877,0.325,0.43,0.202,0.003,0.16
        loitering_time: 0
    review:
      alerts:
        required_zones: Parcel
  cam3:
    enabled: True
    ffmpeg:
      hwaccel_args: preset-vaapi
      inputs:
        - path: rtsp://127.0.0.1:8554/cam3
          input_args: preset-rtsp-restream
          roles:
            - detect
            - record
    objects:
      track:
        - person
        - cat
        - dog
    motion:
      mask:
        - 0.75,0,1,0,1,0.059,0.75,0.059
        - 0.619,0.078,0.615,0.096,0.63,0.096,0.631,0.077
    zones:
      Backyard:
        coordinates:
          0.052,0.463,0.186,0.4,0.267,0.42,0.924,0.461,1,0.636,1,1,0.114,1,0.054,0.778,0.015,0.509
        loitering_time: 0
      Tomek:
        coordinates:
          0.253,0.362,0.476,0.297,0.476,0.216,0.513,0.101,0.781,0.105,0.796,0.23,0.789,0.317,0.834,0.323,0.924,0.457,0.286,0.402
        loitering_time: 0
    review:
      alerts:
        required_zones:
          - Backyard
          - Tomek
  cam4:
    enabled: True
    ffmpeg:
      hwaccel_args: preset-vaapi
      inputs:
        - path: rtsp://127.0.0.1:8554/cam4
          input_args: preset-rtsp-restream
          roles:
            - detect
            - record
    objects:
      track:
        - person
        - cat
        - dog
    motion:
      mask:
        - 1440,0,1920,0,1920,64,1440,64
version: 0.14

Relevant log output

2024-08-07 15:49:24.273520428  [INFO] Preparing Frigate...
2024-08-07 15:49:24.318391842  [INFO] Starting Frigate...
2024-08-07 15:49:26.053507659  [2024-08-07 17:49:26] frigate.app                    INFO    : Starting Frigate (0.14.0-7c39b17)
2024-08-07 15:49:26.053534824  [2024-08-07 17:49:26] frigate.util.config            INFO    : Checking if frigate config needs migration...
2024-08-07 15:49:26.074444038  [2024-08-07 17:49:26] frigate.util.config            INFO    : frigate config does not need migration...
2024-08-07 15:49:27.983606831  [2024-08-07 17:49:27] frigate.util.services          INFO    : Automatically detected vaapi hwaccel for video decoding
2024-08-07 15:49:32.941717297  [2024-08-07 17:49:32] peewee_migrate.logs            INFO    : Starting migrations
2024-08-07 15:49:32.941772697  [2024-08-07 17:49:32] peewee_migrate.logs            INFO    : There is nothing to migrate
2024-08-07 15:49:32.959443536  [2024-08-07 17:49:32] frigate.app                    INFO    : Recording process started: 492
2024-08-07 15:49:32.959502505  [2024-08-07 17:49:32] frigate.app                    INFO    : Recording process started: 494
2024-08-07 15:49:32.962088838  [2024-08-07 17:49:32] frigate.app                    INFO    : go2rtc process pid: 94
2024-08-07 15:49:32.982788225  [2024-08-07 17:49:32] detector.coral                 INFO    : Starting detection process: 521
2024-08-07 15:49:32.984851450  [2024-08-07 17:49:32] frigate.app                    INFO    : Output process started: 523
2024-08-07 15:49:32.988369147  [2024-08-07 17:49:32] frigate.detectors.plugins.edgetpu_tfl INFO    : Attempting to load TPU as pci
2024-08-07 15:49:33.030896984  [2024-08-07 17:49:33] frigate.app                    INFO    : Camera processor started for cam1: 549
2024-08-07 15:49:33.031055504  [2024-08-07 17:49:33] frigate.app                    INFO    : Camera processor started for cam2: 552
2024-08-07 15:49:33.031151509  [2024-08-07 17:49:33] frigate.app                    INFO    : Camera processor started for cam3: 553
2024-08-07 15:49:33.031280566  [2024-08-07 17:49:33] frigate.app                    INFO    : Camera processor started for cam4: 565
2024-08-07 15:49:33.036820897  [2024-08-07 17:49:33] frigate.app                    INFO    : Capture process started for cam1: 579
2024-08-07 15:49:33.040742424  [2024-08-07 17:49:33] frigate.detectors.plugins.edgetpu_tfl INFO    : TPU found
2024-08-07 15:49:33.044863142  [2024-08-07 17:49:33] frigate.app                    INFO    : Capture process started for cam2: 595
2024-08-07 15:49:33.050166699  [2024-08-07 17:49:33] frigate.app                    INFO    : Capture process started for cam3: 599
2024-08-07 15:49:33.058317075  [2024-08-07 17:49:33] frigate.app                    INFO    : Capture process started for cam4: 614
2024-08-07 16:07:49.145668153  [2024-08-07 18:07:49] frigate.api.media              ERROR   : No recordings found for cam2 during the requested time range
2024-08-07 16:07:50.184187807  [2024-08-07 18:07:50] frigate.api.media              ERROR   : No recordings found for cam2 during the requested time range
2024-08-07 16:11:49.149223894  [2024-08-07 18:11:49] frigate.api.media              ERROR   : No recordings found for cam2 during the requested time range

Operating system

Debian

Install method

Docker Compose

Network connection

Wired

Camera make and model

Besder

Any other information that may be helpful

I noticed that yesterday, afterwards redeployed frigate just to be sure. I will do some more testing/trying to replicate and will update here.

Answered by NickM-27

Aug 7, 2024

probably because that's the only video that exists in the hour that the detection exists.

the easiest way to get things working for your use case would be to enable continuous recordings with active objects as the retention mode. That would only record when objects are detected

record:
  enabled: true
  retain:
    days: 10
    mode: active_objects

View full answer

darmach · 2024-08-07T16:28:37Z

darmach
Aug 7, 2024
Author

Just a small update - I just realized that it might be only this particular camera. Will try to confirm that, please don't bother with this issue for now I don't want to be the nuisance!

0 replies

NickM-27 · 2024-08-07T16:32:59Z

NickM-27
Aug 7, 2024
Collaborator Sponsor

you don't have continuous recording enabled, so naturally if no objects in the required zones are detected during an hour (like 15 in your case) then the directory won't be created because there are no recordings saved during that time

6 replies

darmach Aug 7, 2024
Author

Hmm, the objects were detected - just not alerted on them (objects detected in the zone that is not alerting).
So not having a directory is all right, I assume that still if I have the video snapshot shown on the detections tab, I should be able to play the full related video?

NickM-27 Aug 7, 2024
Collaborator Sponsor

not necessarily, you have not configured continuous recording and you only have required zones for alerts, so recordings will only be saved for alerts

    review:
      alerts:
        required_zones: Parcel

darmach Aug 7, 2024
Author

All right! Right now I have two new detections to be reviewed. I'm clicking on each of them, and video starts playing right away.... ...it's wrong, it's the video of me from 56 minutes ago (on both of the new ones). That I am sure of - different people on the video, and timestamp from the camera.

NickM-27 Aug 7, 2024
Collaborator Sponsor

probably because that's the only video that exists in the hour that the detection exists.

the easiest way to get things working for your use case would be to enable continuous recordings with active objects as the retention mode. That would only record when objects are detected

record:
  enabled: true
  retain:
    days: 10
    mode: active_objects

Answer selected by darmach

darmach Aug 7, 2024
Author

Will give this a try! Thank you!

Just to make sure @NickM-27 so now:

New detection happens (not alert as it's wrong zone and it's not triggering alert)
I get a notification that there are new detections to be reviewed on the page
I click on that new, fresh, detection
I see old video

So if I would like to see the actual detection I either have to retain everything as advised above, or just make everything alerting?
I.e. in case of not alerting detections, I don't have any option to actually review them (as the recordings are not there), unless I start retaining all active_objects ? Maybe it would be good to change the default then?

EDIT: Just to make sure, reading this part of docs - Events are in recent version Alerts?

NickM-27 Aug 7, 2024
Collaborator Sponsor

Maybe it would be good to change the default then?

that would be a major breaking change for every user that intentionally did not enable continuous recording on purpose. Detections is a new concept in 0.14 and in 0.13 they would not be recorded if a user had a config like yours. So the behavior remains consistent between versions.

EDIT: Just to make sure, reading this part of docs - Events are in recent version Alerts?

there are some caveats but yes in most cases that is correct

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Uh oh!

[Support]: "No recordings found for <camera name> during the requested time range" in 0.14 #12809

Uh oh!

{{title}}

Uh oh!

Replies: 2 comments 6 replies

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{editor}}'s edit

{{editor}}'s edit

Uh oh!

Uh oh!

{{title}}

Uh oh!

Select a reply

Uh oh!

Uh oh!

[Support]: "No recordings found for <camera name> during the requested time range" in 0.14 #12809

Uh oh!

darmach Aug 7, 2024

Describe the problem you are having

Steps to reproduce

Version

Frigate config file

Relevant log output

Operating system

Install method

Network connection

Camera make and model

Any other information that may be helpful

Replies: 2 comments · 6 replies

Uh oh!

darmach Aug 7, 2024 Author

Uh oh!

NickM-27 Aug 7, 2024 Collaborator Sponsor

Uh oh!

darmach Aug 7, 2024 Author

Uh oh!

NickM-27 Aug 7, 2024 Collaborator Sponsor

Uh oh!

darmach Aug 7, 2024 Author

Uh oh!

NickM-27 Aug 7, 2024 Collaborator Sponsor

Uh oh!

Uh oh!

darmach Aug 7, 2024 Author

Uh oh!

NickM-27 Aug 7, 2024 Collaborator Sponsor

darmach
Aug 7, 2024

Replies: 2 comments 6 replies

darmach
Aug 7, 2024
Author

NickM-27
Aug 7, 2024
Collaborator Sponsor

darmach Aug 7, 2024
Author

NickM-27 Aug 7, 2024
Collaborator Sponsor

darmach Aug 7, 2024
Author

NickM-27 Aug 7, 2024
Collaborator Sponsor

darmach Aug 7, 2024
Author

NickM-27 Aug 7, 2024
Collaborator Sponsor