Interesting. I’ve been building a home camera network and the state of this space (the nvr software) is pretty abysmal: zoneminder, blueiris, shinobi, etc… gonna take this for a spin.<p>This is a terrible name for an open source project though.
Frigate is another open-source object detection engine that works amazingly well with Home Assistant: <a href="https://github.com/blakeblackshear/frigate" rel="nofollow">https://github.com/blakeblackshear/frigate</a>
This post couldn't have come at a more perfect time. I recently got a call from a client who couldn't access their Unifi Cameras remotely anymore. Apparently the EOL for the self-hosted Unifi Video was was announced last year.<p>And the replacement solution is no longer self-hosted and is a hardware solution that costs a few hundred dollars to keep the system up to date.
How this could be named open source but actually be licensed under a creative commons non comercial license (BY-NC-SA 4.0)<p><a href="https://doc.kerberos.io/opensource/license/" rel="nofollow">https://doc.kerberos.io/opensource/license/</a>
Anyone know how this compare to MotionEyeOS? MotionEye is great but have some limitations like no audio, no way to separate users/camera permissions
I'm surprised more video surveillance software does not leverage the APIs of the cameras. Network cameras have built in motion, object, line cross, and facial detection. The work is done in the camera and the APIs allow you to subscribe through call backs or server side events.
You could support event recording for at least a half dozen cameras with a raspberry pi.<p>I've prototyped this but it ended up on my shelf of incomplete hobbies. Given that many camera brands are white label products made by the same manufacturer, I would think you could cover several brands with just the first API client implementation. Or maybe this is also covered with onvif?
Interesting! I was just setting up Shinobi but this looks really good too.<p>I don't like the idea of having one docker per camera though.. But I'll give it a try.
docker pull kerberos/kerberos<p>Should I trust a whole image from docker hub with access to a security camera?<p>No. I'd rather trust a Linux distribution to do a reproducible build.
Choosing a name like "Kerberos" for a new project will make it very difficult to search for anything related to it. Kerberos is an old concept in many operating systems with 8.4 million google search results(and none of them are related to this video product). Pick a new name IMO.
> Single camera per instance (e.g. One Docker container per camera).
One camera per Docker instance? This is going to eat up hardware resources like Fat Albert.