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?

  • Shimitar@downonthestreet.euEnglish
    31·
    1 day ago

    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.

    • lemmyvore@feddit.nlEnglish
      1·
      5 hours 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.

      • Shimitar@downonthestreet.euEnglish
        0·
        4 hours ago

        Have you read the readme? There is literally a text config file to fill with the camera info (url of image).

        Feel free to open a ticket on codeberg or DM/PM me for any additional detail.

        Indeed documentation could be better…

        • lemmyvore@feddit.nlEnglish
          0·
          3 hours ago

          This camera (Reolink E330) doesn’t have HTTP (80 or 443), just RTSP (554), ONVIF (8000) and the proprietary interface that their own app uses (9000).

    • lemmyvore@feddit.nlEnglish
      1·
      7 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.

      • trilobite@lemmy.mlOPEnglish
        1·
        2 hours ago

        But if has all these issues, why is it so popular, and more importantly, hoe come the developers are not improving the image? Is it because its too complex?

        • lemmyvore@feddit.nlEnglish
          1·
          19 minutes ago

          It’s popular because it works. You don’t get a lot of choice in the NVR area, most of the other projects are kind of ass too. I’ve been trying lots of them and so far Frigate and Shinobi are the only ones that you can get to show your camera streams, and detecting & recording actually works.

          I also don’t think many people care about the security that much. Either that or they run the container like I do in a completely isolated VLAN with the cameras. Honestly, if it wasn’t for the obscene amounts of RAM, CPU and storage it wastes for no good reason I wouldn’t care that much about the security either.

          hoe come the developers are not improving the image?

          Lots of developers are clueless about Docker. They are used to running their stuff on the metal and piling everything together and they don’t even consider they should clean things up before they ship a docker image.

          Gramps Web for example is another humongous image, and it’s humongous because apparently the developer can’t be arsed to separate the building stage from the production stage in their Dockerfile, so they’re shipping all the build toolchains. People have pointed this out to them and they’re like “eh whatever”.

      • Shimitar@downonthestreet.euEnglish
        1·
        4 hours ago

        Good! I was probably doing something wrong, but in any case seems more logical to leverage the cameras internal detection.

        • lemmyvore@feddit.nlEnglish
          1·
          4 hours ago

          Yeah Frigate devs claim it can’t be done, but it works in other projects like Shinobi.

    • anon_8675309@lemmy.worldEnglish
      1·
      8 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.