question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[Support]: Retain days… how to remove old events?

See original GitHub issue

Describe the problem you are having

Hello,

I read so many articles but i don’t understand how it works…

i have this configuration:

cameras: campianerottolo: ffmpeg: inputs: - path: rtsp://admin:baguzeye256!@10.0.11.31/12 roles:
- detect - rtmp - record detect: width: 640 height: 352 record: enabled: True retain: days: 0 events: retain: default: 5 pre_capture: 5 post_capture: 5

And I think that it will delete my events after 5 days… but it doesnt’t work Why? What i have to do to delete events automatically?

Version

3.0

Frigate config file

mqtt:
  host: 10.0.11.11
  user: mqttilbagatta
  password: passwd 

cameras:
  campianerottolo:
    ffmpeg:
      inputs:
        - path: rtsp://10.0.11.31/12
          roles:        
            - detect
            - rtmp
            - record
    detect:
      width: 640
      height: 352
    record:
      enabled: True
      retain:
        days: 0
      events:
        retain:
          default: 5
        pre_capture: 5
        post_capture: 5
    motion:
      mask:
        - 0,229,382,250,390,132,545,139,640,61,640,0,0,0
    zones:
      porta:
        coordinates: 404,290,577,299,549,162,380,171,367,254,93,241        
  

  camsoggiorno:
    ffmpeg:
      inputs:
        - path: rtsp://10.0.11.33:8554/profile1
          roles:
            - detect
            - rtmp
            - record
    detect:
      width: 640
      height: 360
    record:
      enabled: True
      retain:
        days: 0
      events:
        retain:
          default: 1



  camcameretta:
    ffmpeg:
      inputs:
        - path: rtsp://10.0.11.34/profile1
          roles:
            - detect
            - rtmp
            - record
    detect:
      width: 640
      height: 360
    record:
      enabled: True
      retain:
        days: 0
      events:
        retain:
          default: 1

    motion:
      mask:
        - 608,0,560,141,407,42,351,0

Relevant log output

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[2022-03-03 18:15:51] frigate.app                    INFO    : Starting Frigate (0.10.0-bfecee9)
[2022-03-03 18:15:51] frigate.app                    INFO    : Creating directory: /tmp/cache
Starting migrations
[2022-03-03 18:15:51] peewee_migrate                 INFO    : Starting migrations
There is nothing to migrate
[2022-03-03 18:15:51] peewee_migrate                 INFO    : There is nothing to migrate
[2022-03-03 18:15:51] frigate.app                    INFO    : Output process started: 218
[2022-03-03 18:15:51] frigate.app                    INFO    : Camera processor started for campianerottolo: 220
[2022-03-03 18:15:51] frigate.app                    INFO    : Camera processor started for camsoggiorno: 223
[2022-03-03 18:15:51] detector.cpu                   INFO    : Starting detection process: 217
[2022-03-03 18:15:51] ws4py                          INFO    : Using epoll
[2022-03-03 18:15:51] frigate.app                    INFO    : Camera processor started for camcameretta: 225
[2022-03-03 18:15:51] frigate.edgetpu                WARNING : CPU detectors are not recommended and should only be used for testing or for trial purposes.
[2022-03-03 18:15:51] frigate.app                    INFO    : Capture process started for campianerottolo: 226
[2022-03-03 18:15:51] frigate.app                    INFO    : Capture process started for camsoggiorno: 228
[2022-03-03 18:15:51] frigate.app                    INFO    : Capture process started for camcameretta: 232
[2022-03-03 18:15:51] ws4py                          INFO    : Using epoll
[2022-03-03 18:16:01] ws4py                          INFO    : Managing websocket [Local => 127.0.0.1:5002 | Remote => 127.0.0.1:43514]
[2022-03-03 18:16:12] ws4py                          INFO    : Terminating websocket [Local => 127.0.0.1:5002 | Remote => 127.0.0.1:43514]
[2022-03-03 18:29:57] frigate.mqtt                   INFO    : Turning on snapshots for camcameretta via mqtt
[2022-03-03 18:29:57] frigate.mqtt                   INFO    : Turning on snapshots for campianerottolo via mqtt
[2022-03-03 18:29:57] frigate.mqtt                   INFO    : Turning on snapshots for camsoggiorno via mqtt
[2022-03-03 19:59:29] frigate.mqtt                   INFO    : Turning off recordings for camcameretta via mqtt
[2022-03-03 19:59:29] frigate.mqtt                   INFO    : Turning off snapshots for camcameretta via mqtt
[2022-03-03 19:59:29] frigate.mqtt                   INFO    : Turning off recordings for camsoggiorno via mqtt
[2022-03-03 19:59:29] frigate.mqtt                   INFO    : Turning off snapshots for camsoggiorno via mqtt
[2022-03-03 21:36:11] frigate.object_processing      WARNING : Unable to create jpg because frame 1646339769.940299 is not in the cache
[2022-03-04 02:00:42] frigate.video                  ERROR   : campianerottolo: Unable to read frames from ffmpeg process.
[2022-03-04 02:00:42] frigate.video                  ERROR   : campianerottolo: ffmpeg process is not running. exiting capture thread...
[2022-03-04 02:00:42] watchdog.campianerottolo       ERROR   : Ffmpeg process crashed unexpectedly for campianerottolo.
[2022-03-04 02:00:42] watchdog.campianerottolo       ERROR   : The following ffmpeg logs include the last 100 lines prior to exit.
[2022-03-04 02:00:42] ffmpeg.campianerottolo.detect  ERROR   : Guessed Channel Layout for Input Stream #0.1 : mono
[2022-03-04 02:00:42] ffmpeg.campianerottolo.detect  ERROR   : [segment @ 0x559cb75220] Timestamps are unset in a packet for stream 0. This is deprecated and will stop working in the future. Fix your code to set the timestamps properly
[2022-03-04 02:00:42] ffmpeg.campianerottolo.detect  ERROR   : [flv @ 0x559caeed30] Timestamps are unset in a packet for stream 0. This is deprecated and will stop working in the future. Fix your code to set the timestamps properly
[2022-03-04 02:00:42] ffmpeg.campianerottolo.detect  ERROR   : [swscaler @ 0x559cc4b7c0] deprecated pixel format used, make sure you did set range correctly
[2022-03-04 02:00:42] ffmpeg.campianerottolo.detect  ERROR   : [flv @ 0x559caeed30] Failed to update header with correct duration.
[2022-03-04 02:00:42] ffmpeg.campianerottolo.detect  ERROR   : [flv @ 0x559caeed30] Failed to update header with correct filesize.
[2022-03-04 03:05:05] ws4py                          INFO    : Managing websocket [Local => 127.0.0.1:5002 | Remote => 127.0.0.1:41304]
[2022-03-04 03:05:23] ws4py                          INFO    : Terminating websocket [Local => 127.0.0.1:5002 | Remote => 127.0.0.1:41304]

FFprobe output from your camera

Ffprobe Not found

Frigate stats

No response

Operating system

HassOS

Install method

HassOS Addon

Coral version

CPU (no coral)

Network connection

Wired

Camera make and model

SriHome

Any other information that may be helpful

No response

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Comments:32 (1 by maintainers)

github_iconTop GitHub Comments

2reactions
ilbagattacommented, Mar 29, 2022

so, I added that code and the events desappeared!!!

Thank you, now I have understood!

Only a question… what you say on point 2 is right (because now It deleted them), but they were available… I expect that I wasn’t able to play them…

haha, i’m going to comment the new code only to try 😃

Thank you @NickM-27 , i’m trying to fix it for a long time and now I have a “human-readable” list of events!

1reaction
NickM-27commented, Mar 29, 2022

another question and i can close all… sorry

If I put a number of snapshot smaller then events days what happens? must they have the same value? I tried but nothing seems happening

For an event to be in the events page and not cleaned up it needs a snapshot or a clip.

So as long as either exists the event will stay. The numbers can be different without issue.

For example: if the snapshot is smaller than the event days then the clip will remain and the snapshot will be deleted. Once the event days is hit the clip will be deleted and the event will be removed.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Delete or hide a calendar event on iCloud.com - Apple Support
Delete an event you're invited to: Double-click the event to select it, then decline the event. Set Calendar to automatically hide past events:...
Read more >
Remove items from your calendar - Microsoft Support
In the folder list, click Calendar. ... In the Archive items older than list, select the date that you want. To archive everything,...
Read more >
How can I delete an Event? | Keep&Share Support
Once you've opened your Event, just click the "Delete" button on the right side of your Event Editor, and a pop-up dialog will...
Read more >
Cancel or transfer calendar events before deleting a user
Under Events of deleted users, select Silently cancel future events of deleted users. Click Save. For this feature to work, you must opt...
Read more >
Delete old tasks, events and statistics data in vCenter Server 5 ...
In this KB we will use scripts to help with this operation and keep vCenter Server's database healthy. Avoiding to do this can...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found