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.
Comment on Finally have the stream from my HikVision, now the challenge of Frigate
Shimitar@downonthestreet.eu 3 weeks 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 (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.nl 3 weeks ago
- Shimitar@downonthestreet.eu 3 weeks 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.nl 3 weeks 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).
- Shimitar@downonthestreet.eu 3 weeks ago
That sucks… Maybe a good update to LazyNVR would let grab the RTSP stream…
anon_8675309@lemmy.world 3 weeks ago
Have an i3 8xxx running 7 cams. Avg 35% 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.
- Shimitar@downonthestreet.eu 3 weeks ago
Feels like nextcloud…
tenekev@lemmy.world 2 weeks ago
Nah, not even close. Nextcloud’s attempt to throw in the kitchen sink is what makes it bloated and inefficiant. Frigate on the other hand isn’t like that. The bloat there comes from misconfigured pipelines for your camera feeds. You need some time to dial it down but once you do, it’s literally years between maintenance.
lemmyvore@feddit.nl 3 weeks ago
The Frigate docker image is generally nasty. It’s huge (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
aptso 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.ml 3 weeks 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.nl 3 weeks 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 also don’t think many people care about the security that much. Either that or they run the container like I do in a 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.
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”.
Good! I was probably doing something wrong, but in any case seems more logical to leverage the cameras internal detection.
lemmyvore@feddit.nl 3 weeks ago
Yeah Frigate devs claim it can’t be done, but it works in other projects like Shinobi.