I've now managed to get the stream of my HiWatch Series, model HWI- T641H-Z 2.8-12 mm by accessing via browser to rtsp://USERNAME:PASSWORD@192.168.30.50:554/Streaming/Channels/101. Working nice. But on its own, very unusful unless I get storage and image detection going. So, I need something like Frigate.

I believe the Frigate docs suggest running in a docker container installed on a VM. Very convienient as I have Proxmox (installed on a optiples 7070 micropc with 32MB ram) running a VM on which i have a few containers. The idea is to mount a "frigate" dataset created on my Truenas server on Proxmox which is then mounted to the VM. Lots of layers but hoping it should be ok.

I heard that the Google Coral TPU is not sold anymore. Is this going to be a problem for Frigate image recognition? Are there alternatives to the Coral TPU?

you are viewing a single comment's thread
view the rest of the comments
[–] 2 points 21 hours ago (3 children)

In my experience frigate is quite CPU intensive. I have 10 cameras and my old I7-8700 would die trying to have frigate process them all.

I opted for a different approach with LazyNVR (https://codeberg.org/LazyNVR/lazynvr-sources) leveraging the capability of the camera to perform motion detection and video recording directly. This offloaded my CPU and now I can record all 10 cameras on a OPi3.

  • source
  • hideshow 3 child comments
  • [–] 1 point 1 hour ago

    I've tried LazyNVR but I couldn't figure out how to make it work with my cameras. There seem to be no real instructions. I don't even get how it's supposed to find the cameras, there's no place to put an IP.

  • source
  • parent
  • [–] 1 point 3 hours ago*

    The Frigate docker image is generally nasty. It's humongous (5.5 GB), bundles and runs a ton of different things whether you use them or not, uses s6 as init and supervisor which is a piece of crap, and it cannot be secured – it won't run as a non-privileged user, it won't drop caps, you can't make it read-only because some genius configured nginx to put temporary files in with the app files, it conveniently includes apt so the attacker can install anything they might want inside the container, and in fact recommends running in privileged mode(!).

    I think it's the most security-hostile docker image I have ever seen.

  • source
  • parent
  • [–] 1 point 3 hours ago* (last edited 3 hours ago)

    Have an i3 8xxx running 7 cams. Avg 15% detection CPU.
    Took a while to get my config right.

    My complaint isn’t that frigate is inefficient it’s that it’s way too easy to make it inefficient.

  • source
  • parent