Local realtime person detection for RTSP cameras

tmjpugh · October 6, 2021, 2:18pm

retained mqtt message?

Frigate turns off clips, detect and record on startup

opened 09:45AM - 11 Sep 21 UTC

closed 10:58AM - 13 Sep 21 UTC

**Describe the bug** Currently i have two camera's configured exactly the same …way, except for the rtmp ip adresses. Both camera's work fine in Frigate, when detect/record/clips are enabled they work as they should do. BUT: every time i restart frigate manually, or restart the server, MQTT turns OFF detect and clips for my oprit (driveway) camera. I changed the configuration for snapshots detect and record to capital letters, saved frigate.yml and restarted. This didn't work. Changed it back to lower case, also dind't work. Even re-installed my camera in HASS, re-configured the one specific (oprit) camera but nothing seems to help. Every time when i restart frigate of Hass, MQTT turns off detection, clips and snapshots. When i manually activate these features they seem to be working just fine. **Version of frigate** 1.13 **Config file** Include your full config file wrapped in triple back ticks. ```mqtt: host: 192.168.2.27 port: 1883 user: ****** password: ****** ########## VOORTUIN CAMERA ########## cameras: voordeur: ffmpeg: inputs: - path: rtsp://******:******@******.200:554/cam/realmonitor?channel=1&subtype=0 roles: - clips #- record - rtmp - path: rtsp://******:******@******.200:554/cam/realmonitor?channel=1&subtype=1 roles: - detect width: 640 height: 480 fps: 5 objects: track: - person - car - cat - dog - bicycle filters: person: threshold: 0.8 snapshots: enabled: true timestamp: false bounding_box: true retain: default: 3 clips: enabled: true pre_capture: 3 post_capture: 3 retain: default: 7 record: enabled: false retain_days: 7 motion: mask: - 428,126,640,148,640,0,323,0,150,0,0,0,0,197,77,149,191,134 zones: zone_voorpad: coordinates: 432,249,433,480,590,480,559,328,523,214,487,130,432,124 zone_oprit_voor: coordinates: 123,280,249,132,106,142,0,240,0,437 ########## OPRIT CAMERA ########## oprit: ffmpeg: inputs: - path: rtsp://******:******@******.201:554/cam/realmonitor?channel=1&subtype=0 roles: - clips #- record - rtmp - path: rtsp://******:******@******.201:554/cam/realmonitor?channel=1&subtype=1 roles: - detect width: 640 height: 480 fps: 5 objects: track: - person - car - bird - cat - dog - bicycle - motorcycle filters: person: threshold: 0.5 snapshots: enabled: True timestamp: false bounding_box: True retain: default: 3 clips: enabled: true pre_capture: 3 post_capture: 3 retain: default: 7 record: enabled: false retain_days: 7 motion: mask: - 0,0,108,0,119,51,0,108 - 508,21,640,23,640,0,640,0,503,0 zones: zone_oprit_achter: coordinates: 520,480,567,343,537,296,425,235,408,253,297,185,218,137,173,148,85,97,10,137,44,248,113,421,150,480 zone_tuinpoort: coordinates: 444,296,540,420,597,250,640,93,529,29 ########## detector toewijzing ########## detectors: cpu1: type: cpu cpu2: type: cpu ``` **Frigate container logs** ``` * Starting nginx nginx ...done. frigate.app INFO : Creating directory: /tmp/cache Starting migrations peewee_migrate INFO : Starting migrations There is nothing to migrate peewee_migrate INFO : There is nothing to migrate frigate.mqtt INFO : MQTT connected frigate.mqtt INFO : Turning off clips for oprit via mqtt frigate.mqtt INFO : **Turning off snapshots for oprit via mqtt** frigate.mqtt INFO : **Turning off detection for oprit via mqtt** detector.cpu1 INFO : Starting detection process: 33 frigate.app INFO : Camera processor started for voordeur: 38 detector.cpu2 INFO : Starting detection process: 34 frigate.app INFO : Camera processor started for oprit: 39 frigate.app INFO : Capture process started for voordeur: 40 frigate.app INFO : Capture process started for oprit: 41 ``` **Frigate stats** ``` Logger: custom_components.frigate.api Source: custom_components/frigate/api.py:172 Integration: Frigate (documentation, issues) First occurred: 11:30:11 (1 occurrences) Last logged: 11:30:11 Error fetching information from http://192.168.2.27:5000/api/stats: 502, message='Bad Gateway', url=URL('http://192.168.2.27:5000/api/stats') **But when i brouwse to ...:5000/api/stats i get the following:** { "detection_fps": 0.0, "detectors": { "cpu1": { "detection_start": 0.0, "inference_speed": 10.0, "pid": 33 }, "cpu2": { "detection_start": 0.0, "inference_speed": 10.0, "pid": 35 } }, "oprit": { "camera_fps": 5.1, "capture_pid": 42, "detection_fps": 0.0, "pid": 39, "process_fps": 0.0, "skipped_fps": 0.0 }, "service": { "storage": { "/dev/shm": { "free": 2053.7, "mount_type": "tmpfs", "total": 2055.0, "used": 1.3 }, "/media/frigate/clips": { "free": 2021463.9, "mount_type": "ext4", "total": 2163762.7, "used": 53932.8 }, "/media/frigate/recordings": { "free": 2021463.9, "mount_type": "ext4", "total": 2163762.7, "used": 53932.8 }, "/tmp/cache": { "free": 1940.6, "mount_type": "tmpfs", "total": 2055.0, "used": 114.4 } }, "uptime": 162, "version": "0.8.4-5043040" }, "voordeur": { "camera_fps": 5.0, "capture_pid": 40, "detection_fps": 0.0, "pid": 38, "process_fps": 5.0, "skipped_fps": 0.0 } } ``` **FFprobe from your camera** Run the following command and paste output below ``` ffprobe <stream_url> ``` **Screenshots** If applicable, add screenshots to help explain your problem. **Computer Hardware** - OS: Windows 10 - Install method: Addon - Virtualization: Virtualbox - Coral Version: none - Network Setup: Wired **Camera Info:** - Manufacturer: Dahua - Model: IPC-HDW4433C - Resolution: 3M - FPS: 5 **Additional context** Add any other context about the problem here.

jasonshearer · October 6, 2021, 4:52pm

Oh baby! Loving the new Birdseye feature!

Here is my full working config for reference. Note that I did not do full time recording before or after 2x. I use my Ubiquiti UDMP for long term storage of recordings. I have six cameras being pulled into Frigate but just have the config for one in the code below. I use a NUC with Corals.

detectors:
  coral_pci:
    type: edgetpu
    device: pci
  coral_usb:
    type: edgetpu
    device: usb

mqtt:
  host: core-mosquitto
  port: 1883
  topic_prefix: frigate
  client_id: frigate
  user: XXXXXXX
  password: XXXXXXX
birdseye:
  enabled: True
  width: 1280
  height: 720
  quality: 8
  mode: objects

ffmpeg:
  global_args:
    -hide_banner
    -loglevel warning
  input_args:
    -avoid_negative_ts make_zero
    -fflags +genpts+discardcorrupt
    -rtsp_transport tcp
    -stimeout 5000000
    -use_wallclock_as_timestamps 1
  output_args:
    detect:
      -f rawvideo 
      -pix_fmt yuv420p
    record: 
      -f segment
      -segment_time 60
      -segment_format mp4
      -reset_timestamps 1
      -strftime 1 -c copy -an
    rtmp:
      -c copy
      -f flv
  hwaccel_args:
    - -hwaccel
    - vaapi
    - -hwaccel_device
    - /dev/dri/renderD128
    - -hwaccel_output_format
    - yuv420p

record:
  enabled: true
  retain_days: 0
  events:
    retain:
      default: 30

snapshots:
  retain:
    default: 10
    objects:
      person: 15
      
cameras:
####FRONT DOOR####  
  front_door:
    ffmpeg:
      inputs:
        - path: rtsp://XXXXX
          roles:
            - detect
            - record
            - rtmp
    detect:
      width: 1600
      height: 1200
      fps: 10
    motion:
      mask:
        - 0,411,0,720,670,664,1242,658,1298,559,1600,540,1600,0,0,0
    zones:
      patio:
        coordinates: 1600,1200,1264,934,1285,743,1086,709,966,743,737,763,390,803,0,1116,0,1200
    snapshots:
      enabled: true
      bounding_box: true
      crop: false
      timestamp: false

jruss · October 7, 2021, 3:09am

New image pushed to docker (stable-amd64) yesterday, container now cannot start. I’m looking through docs saw there were some breaking changes so I made the adjustments in my config. Still no go.

Looking at the container logs I see its having issues hitting run.sh:

[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.
ifelse: fatal: unable to exec /run.sh: No such file or directory
[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.
[s6-finish] sending all processes the KILL signal and exiting.

I’m running it with docker-compose on a separate box from my HA. It had been running successfully for months. Absolutely love this project and greatly appreciate the work and effort that goes into it.

ukro · October 7, 2021, 9:46pm

I cant watch clips. On two differwnt HA servers and through app and webbrowser pwa mobile. After 2.0 update. Was working perfectly before update

Eoin · October 7, 2021, 11:06pm

I had the same error, for me a HA restart fixed it.

blakeblackshear · October 7, 2021, 11:58pm

You probably have a warning message in your logs about not having the record role assigned to an input with recording enabled. You need add record where you removed clips.

ukro · October 8, 2021, 7:23am

Top of config:

detectors:
  coral_pci:
    type: edgetpu
    device: pci


    
ffmpeg:
  # Optional: global ffmpeg args (default: shown below)
  global_args: -hide_banner -loglevel warning
  # Optional: global hwaccel args (default: shown below)
  # NOTE: See hardware acceleration docs for your specific device
  hwaccel_args:
    - -hwaccel
    - qsv
    - -qsv_device
    - /dev/dri/renderD128
  # Optional: global input args (default: shown below)
  input_args: -avoid_negative_ts make_zero -fflags +genpts+discardcorrupt -rtsp_transport tcp -stimeout 5000000 -use_wallclock_as_timestamps 1
  # Optional: global output args
  output_args:
    # Optional: output args for detect streams (default: shown below)
    detect: -f rawvideo -pix_fmt yuv420p
    # Optional: output args for record streams (default: shown below)
    #longloading-record: -f segment -segment_time 60 -segment_format mp4 -reset_timestamps 1 -strftime 1 -c:v libx264 -an
    #longloading-clips: -f segment -segment_time 10 -segment_format mp4 -reset_timestamps 1 -strftime 1 -c:v libx264 -an

    record: -f segment -segment_time 60 -segment_format mp4 -reset_timestamps 1 -strftime 1 -c copy -an
    # Optional: output args for clips streams (default: shown below)
    #clips: -f segment -segment_time 10 -segment_format mp4 -reset_timestamps 1 -strftime 1 -c copy -an

and Each cam have same setup on one server 11cams other server 11cams

  CAM_garaz:

    ffmpeg:
      inputs:
        - path: rtsp://xxx:xxxx@192xxxx:554/cam/realmonitor?channel=1&subtype=0&authbasic=xxxx
          roles:
            - detect
            #- clips


    zones:
      zone_0:
        coordinates: 0,1080,1388,1080,1920,1080,1920,660,1792,476,1412,110,581,47,309,161,0,386
    detect:
      enabled: True
      max_disappeared: 25
      width: 1920
      height: 1080
      fps: 5
      #best_image_timeout: 60

    record:
      enabled: True
      retain_days: 0
      events:
        post_capture: 10
        pre_capture: 5
        objects:
          - person
        retain:
          default: 5
    
    rtmp:
      enabled: False
    snapshots:
      enabled: True
      timestamp: False
      bounding_box: True
      crop: False
      retain:
        default: 5
        #objects:
          #person: 15
    mqtt:
      enabled: False
      timestamp: True
      bounding_box: True
      crop: True
      height: 270
    objects:
      track:
        - person
      filters:
        person:
          min_area: 1000
          max_area: 100000
          min_score: 0.5
          threshold: 0.77

@blakeblackshear

ukro · October 8, 2021, 7:24am

same after restart

ukro · October 8, 2021, 7:25am

Some other settings are broking on update?

[2021-10-08 07:28:42] frigate.video                  INFO    : CAM1: ffmpeg sent a broken frame. memoryview assignment: lvalue and rvalue have different structures
[2021-10-08 07:28:42] frigate.video                  INFO    : CAM1: ffmpeg process is not running. exiting capture thread...
[2021-10-08 07:28:52] watchdog.CAM1                  ERROR   : FFMPEG process crashed unexpectedly for CAM1.
[2021-10-08 07:28:52] watchdog.CAM1                  ERROR   : The following ffmpeg logs include the last 100 lines prior to exit.
[2021-10-08 07:28:52] watchdog.CAM1                  ERROR   : You may have invalid args defined for this camera.

@blakeblackshear

sender · October 8, 2021, 1:51pm

Sorry, I also update and got erros… and I don’t know where to start…

cameras -> schuurachter -> ffmpeg -> inputs -> 0 -> roles -> 1
  value is not a valid enumeration member; permitted: 'record', 'rtmp', 'detect' (type=type_error.enum; enum_values=[<CameraRoleEnum.record: 'record'>, <CameraRoleEnum.rtmp: 'rtmp'>, <CameraRoleEnum.detect: 'detect'>])
cameras -> schuurachter -> clips
  extra fields not permitted (type=value_error.extra)
cameras -> schuurachter -> fps
  extra fields not permitted (type=value_error.extra)
cameras -> schuurachter -> height
  extra fields not permitted (type=value_error.extra)
cameras -> schuurachter -> width
  extra fields not permitted (type=value_error.extra)
cameras -> parkeerplaats -> ffmpeg -> inputs -> 0 -> roles -> 1
  value is not a valid enumeration member; permitted: 'record', 'rtmp', 'detect' (type=type_error.enum; enum_values=[<CameraRoleEnum.record: 'record'>, <CameraRoleEnum.rtmp: 'rtmp'>, <CameraRoleEnum.detect: 'detect'>])
cameras -> parkeerplaats -> clips
  extra fields not permitted (type=value_error.extra)
cameras -> parkeerplaats -> fps
  extra fields not permitted (type=value_error.extra)
cameras -> parkeerplaats -> height
  extra fields not permitted (type=value_error.extra)
cameras -> parkeerplaats -> width
  extra fields not permitted (type=value_error.extra)
cameras -> voortuin -> ffmpeg -> inputs -> 0 -> roles -> 1
  value is not a valid enumeration member; permitted: 'record', 'rtmp', 'detect' (type=type_error.enum; enum_values=[<CameraRoleEnum.record: 'record'>, <CameraRoleEnum.rtmp: 'rtmp'>, <CameraRoleEnum.detect: 'detect'>])
cameras -> voortuin -> clips
  extra fields not permitted (type=value_error.extra)
cameras -> voortuin -> fps
  extra fields not permitted (type=value_error.extra)
cameras -> voortuin -> height
  extra fields not permitted (type=value_error.extra)
cameras -> voortuin -> width
  extra fields not permitted (type=value_error.extra)
cameras -> terras -> ffmpeg -> inputs -> 0 -> roles -> 1
  value is not a valid enumeration member; permitted: 'record', 'rtmp', 'detect' (type=type_error.enum; enum_values=[<CameraRoleEnum.record: 'record'>, <CameraRoleEnum.rtmp: 'rtmp'>, <CameraRoleEnum.detect: 'detect'>])
cameras -> terras -> clips
  extra fields not permitted (type=value_error.extra)
cameras -> terras -> fps
  extra fields not permitted (type=value_error.extra)
cameras -> terras -> height
  extra fields not permitted (type=value_error.extra)
cameras -> terras -> width
  extra fields not permitted (type=value_error.extra)
[cmd] python3 exited 1
[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.

ukro · October 8, 2021, 1:57pm

those are easy, you need to rewrite your config, move as per documentation. I was also shocked at first but after 30minutes all fixed.
Remove all mention on clips.
Add record True with retention false (if you don’t use 24/7 recording) and move your settings frrom clips to record

tmjpugh · October 8, 2021, 1:57pm

sender:

 value is not a valid enumeration member; permitted: 'record', 'rtmp', 'detect' (type=type_error.enum; enum_values=[<CameraRoleEnum.record: 'record'>, <CameraRoleEnum.rtmp: 'rtmp'>, <CameraRoleEnum.detect: 'detect'>])
cameras -> parkeerplaats -> clips

clips is no longer a valid role and should be removed

FPS not needed

sender · October 8, 2021, 1:59pm

This is an example of 1-5 cams:


cameras:
# FRONT Camera ########################################################################################################
  voordeur:
    ffmpeg:
      inputs:
        - path: rtsp://admin:[email protected]:554/Streaming/Channels/101/
          roles:
            - detect
            - clips
#            - rtmp
    width: 2560
    height: 1440
    fps: 6
    snapshots:
      enabled: true
      crop: false
      bounding_box: True
    objects:
      track:
        - person
        - dog
        - cat
    motion:
      mask:
        - '1090,81,1216,0,1382,34,1532,99,1518,259,1426,363,1123,247'
        - '1766,498,1753,669,1778,722,1829,773,1863,825,1906,884,1924,955,1953,1065,2237,1169,2255,1128,2295,1046,2338,946,2378,841,2410,743,2215,647,2190,582,2138,512,2010,402,1859,351'
    clips:
      # Required: enables clips for the camera (default: shown below)
      # This value can be set via MQTT and will be updated in startup based on retained value
      enabled: True
      # Optional: Number of seconds before the event to include in the clips (default: shown below)
      pre_capture: 2
      # Optional: Number of seconds after the event to include in the clips (default: shown below)
      post_capture: 2
      # Optional: Objects to save clips for. (default: all tracked objects)
      objects:
        - person
        - dog
        - cat
      # Optional: Restrict clips to objects that entered any of the listed zones (default: no required zones)
      required_zones: []
      # Optional: Camera override for retention settings (default: global values)
      retain:
        # Required: Default retention days (default: shown below)
        default: 10
        # Optional: Per object retention days
        objects:
          person: 200
          dog: 20
          cat: 200

What should I do with the “clips” section then?

mikey62831 · October 8, 2021, 1:59pm

Frigate Integration will not connect after update and followed the new config based on item 3 in new document.

`Frigate
URL you use to access Frigate (ie. http://frigate:5000/)

If you are using HassOS with the addon, the URL should be http://ccab4aaf-frigate:5000/

Home Assistant needs access to port 5000 (api) and 1935 (rtmp) for all features.

The integration will setup sensors, cameras, and media browser functionality.

Sensors:

Stats to monitor frigate performance
Object counts for all zones and cameras
Cameras:

Cameras for image of the last detected object for each camera
Camera entities with stream support (requires RTMP)
Media Browser:

Rich UI with thumbnails for browsing event clips
Rich UI for browsing 24/7 recordings by month, day, camera, time
API:

Notification API with public facing endpoints for images in notifications
Failed to connect
 
URL
http://ccab4aaf-frigate:5000
`
New  Config.yml Frigate

URL you use to access Frigate (ie. `http://frigate:5000/`)

If you are using HassOS with the addon, the URL should be `http://ccab4aaf-frigate:5000/`

Home Assistant needs access to port 5000 (api) and 1935 (rtmp) for all features.

The integration will setup sensors, cameras, and media browser functionality.

Sensors:

* Stats to monitor frigate performance
* Object counts for all zones and cameras

Cameras:

* Cameras for image of the last detected object for each camera
* Camera entities with stream support (requires RTMP)

Media Browser:

* Rich UI with thumbnails for browsing event clips
* Rich UI for browsing 24/7 recordings by month, day, camera, time

API:

* Notification API with public facing endpoints for images in notifications

Failed to connect

URL

SUBMIT
```
mqtt:
  host: 192.168.0.74
  topic_prefix: frigate
  client_id: frigate
  user: mikey
  password: xxxxxx


detectors:
  cpu1:
    type: cpu
    num_threads: 3

cameras:
    camera1:front_driveway:
    ffmpeg:
      inputs:
        - path: rtsp://admin:[email protected]:554/h264Preview_01_sub
          roles:
            - detect
    width: 1280
    height: 720
````
 Any idea where i am  going wrong as  i am trying to setup agin in HASSO

ukro · October 8, 2021, 2:02pm

  CAM_obyvak:

    ffmpeg:
      inputs:
        - path: rtsp://xxxx:xxxx@xxxx:554/cam/realmonitor?channel=1&subtype=0&authbasic=xxxxx
          roles:
            - detect



    zones:
      zone_0:
        coordinates: 0,1080,1429,1080,1855,583,1876,490,1309,380,1333,0,0,0
    detect:
      enabled: True
      max_disappeared: 25
      width: 1920
      height: 1080
      fps: 5
      #best_image_timeout: 60

    record:
      enabled: False
      retain_days: 0
      events:
        post_capture: 10
        pre_capture: 5
        objects:
          - person
        retain:
          default: 5
    rtmp:
      enabled: False
    snapshots:
      enabled: True
      timestamp: False
      bounding_box: True
      crop: False
      retain:
        default: 5
        #objects:
          #person: 15
    mqtt:
      enabled: False
      timestamp: True
      bounding_box: True
      crop: True
      height: 270
    objects:
      track:
        - person
      filters:
        person:
          min_area: 1000
          max_area: 100000
          min_score: 0.5
          threshold: 0.77

No 24/7 recording

sender · October 8, 2021, 2:19pm

I totally do not get this:

cameras:
# FRONT Camera ########################################################################################################
  voordeur:
    ffmpeg:
      inputs:
        - path: rtsp://admin:[email protected]:554/Streaming/Channels/101/
          roles:
            - detect
            #- clips
#            - rtmp
    detect:
      width: 2560
      height: 1440
#    fps: 6
    snapshots:
      enabled: true
      crop: false
      bounding_box: True
    objects:
      track:
        - person
        - dog
        - cat
    motion:
      mask:
        - '1090,81,1216,0,1382,34,1532,99,1518,259,1426,363,1123,247'
        - '1766,498,1753,669,1778,722,1829,773,1863,825,1906,884,1924,955,1953,1065,2237,1169,2255,1128,2295,1046,2338,946,2378,841,2410,743,2215,647,2190,582,2138,512,2010,402,1859,351'
#    clips:
      # Required: enables clips for the camera (default: shown below)
      # This value can be set via MQTT and will be updated in startup based on retained value
#      enabled: True
      # Optional: Number of seconds before the event to include in the clips (default: shown below)
#      pre_capture: 2
      # Optional: Number of seconds after the event to include in the clips (default: shown below)
#      post_capture: 2
      # Optional: Objects to save clips for. (default: all tracked objects)
#      objects:
#        - person
#        - dog
#        - cat
      # Optional: Restrict clips to objects that entered any of the listed zones (default: no required zones)
#      required_zones: []
      # Optional: Camera override for retention settings (default: global values)
#      retain:
        # Required: Default retention days (default: shown below)
#        default: 10
        # Optional: Per object retention days
#        objects:
#          person: 200
#          dog: 20
#          cat: 200

with this errors:

[services.d] starting services


[services.d] done.


[2021-10-08 16:15:28] frigate.app                    INFO    : Starting Frigate (0.9.1-800f33e)


Error parsing config: 26 validation errors for FrigateConfig


ffmpeg -> output_args -> clips


  extra fields not permitted (type=value_error.extra)


cameras -> voordeur -> ffmpeg -> inputs -> 0 -> roles -> 1


  value is not a valid enumeration member; permitted: 'record', 'rtmp', 'detect' (type=type_error.enum; enum_values=[<CameraRoleEnum.record: 'record'>, <CameraRoleEnum.rtmp: 'rtmp'>, <CameraRoleEnum.detect: 'detect'>])


cameras -> voordeur -> clips


  extra fields not permitted (type=value_error.extra)


cameras -> voordeur -> fps


  extra fields not permitted (type=value_error.extra)


cameras -> voordeur -> height


  extra fields not permitted (type=value_error.extra)


cameras -> voordeur -> width


  extra fields not permitted (type=value_error.extra)

what’s wrong there?

tmjpugh · October 8, 2021, 2:24pm

did you save the config before restart? maybe save and restart again

Its still saying you have clips as a role and heig tht/width/fps under FFMPEG section but above looks correct so I thinking it not saved before you try restart

sender · October 8, 2021, 2:26pm

I really did… Not

sender · October 8, 2021, 2:57pm

Another question. How do I delete all recordings? and database?

ukro · October 8, 2021, 6:07pm

If its a one time thing just delete the db file in config and remove all the media files?