this post was submitted on 16 Sep 2023
78 points (100.0% liked)

Privacy

32120 readers
817 users here now

A place to discuss privacy and freedom in the digital world.

Privacy has become a very important issue in modern society, with companies and governments constantly abusing their power, more and more people are waking up to the importance of digital privacy.

In this community everyone is welcome to post links and discuss topics related to privacy.

Some Rules

Related communities

much thanks to @gary_host_laptop for the logo design :)

founded 5 years ago
MODERATORS
 

I couldn't find a post in this community about cameras so I figured I'd make one. Requirements:

  • No "sign up" required to record video
  • Video is stored locally
  • Video is in a non-propriatary format
  • Can work offline

Optional/Discussion Points:

  • Can wireless connectivity be hardware disabled
  • Can auto-update be disabled
  • Does the device try to "phone home" if it is connected to wifi
  • Disk encryption would be nice but I doubt that'll be an option for anything other than self-hosted stuff

Does anyone know about Lorex (it seems more privacy centered)?

I'm highly technical, so feel free to mention self hosted raspberry pi soltuions as well.

you are viewing a single comment's thread
view the rest of the comments
[โ€“] [email protected] 1 points 1 year ago* (last edited 1 year ago) (1 children)

I only use Frigate. All of the Amcrest stuff is turned off.

Each of the cameras have two video streams. The "live" stream is set to 1080p, and the "sub" stream is set to 720p. The sub stream is what Frigate uses for detection. Here is a sample of what a camera config would look like in the frigate.yml file:

cameras:
  back:
    ffmpeg:
      inputs:
        - path: rtsp://camera-username:camera-password@camera-ip-address:554/cam/realmonitor?channel=1&subtype=2
          roles:
            - detect
            - record
    detect:
      width: 1280
      height: 720

My HA runs in a Proxmox VM with 4 vCPUs, 4GB of RAM and 128GB storage. The VM also has access to a network drive, which is where nightly backups are stored.

By default, the HAOS Frigate addon will store recordings on the host machine (you can define any volume if you're running Frigate in docker), and you can set "event" retention in the frigate config file - default is 10 days. You can download any clip or snapshot directly from the Frigate UI to whatever device you are using. OR, if your setup is similar to mine, you can pull from backup.

My nightly backup to my network drive includes the frigate folder with the recordings and snapshots, which is also set to retain 10 days/backups, and finally there is a weekly Borgbase backup of that network folder to a server on another continent, so I don't feel like I need any kind of dedicated storage hardware - normal backup procedures work just fine!

With this setup, CPU usage never goes above around 35% (keep in mind that I have a Coral TPU, which takes all the detection load off of the CPU) and with the configured Frigate retention policy, storage usage for the entire VM never exceeds 50% of the total available space.

This setup has been running flawlessly for almost 3 years now. Detection is immediate, as are the push notifications. Very happy with it!

[โ€“] [email protected] 2 points 1 year ago

Thanks for the breakdown! I've definitely got some research to do.