Live data from Hacker News

Kerberos: Open-Source Video Surveillance

kerberos.io

71–80 of 96 posts

Re: Kerberos: Open-Source Video Surveillance

#71
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.

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?

Re: Kerberos: Open-Source Video Surveillance

#72
post #37

Does anyone have some outdoor camera recommendations? The ones I had were very low resolution, I could hardly recognize myself in video.

I ended up getting these Montavue 4k cameras largely because they have really good low light performance. They are ONVIF and work with blueiris, which is good because their NVR sucks for use on a mobile phone.

The hardware is the same as many other cameras, HIKvision also has this hardware but I couldn't get it working with blueiris or the HIKvision NVR.

The cameras are indeed amazing at low light. I felt like that was a good feature, and maybe that was misguided. But I can be fairly dark out, looking out the window, and the cameras are still in color mode and look like it's daytime. Think: Google Night Vision camera mode.

I wish there were a better mobile experience though, that's the only way we use them. Both blueiris and Montavue apps suck. Ubiquiti has the best in class here, but I've been burned by them too many times now. This replaces a unusable Unifi system.

For remote access to BlueIris.i plan to use ZeroTier.

Re: Kerberos: Open-Source Video Surveillance

#73

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. This is a terrible name for an open source project though.

The name is a giant red flag. If someone doesn't care about a giant name conflict of a very uncommon word with a very common project, then they just brush it off with rationalizations, it makes me wonder what other reasonable things they are willing to ignore.

Ah, the reasonableness signaling heuristic.

Re: Kerberos: Open-Source Video Surveillance

#74

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.

It's interesting that the cached summary of the `Kerberos` article on Yahoo search has the text of the disambiguated https://en.wikipedia.org/wiki/Kerberos_(protocol), but it's now a disambiguation page that still doesn't include this Kerberos.

The biggest problem with this name clash for the creators is that help and documentation will be hard to find, which will stymie adoption.

They also lose potential good will with the rest of the tech community.

Re: Kerberos: Open-Source Video Surveillance

#77

Earlier quoted context omitted.

The problem with offloading that to the camera is that onvif doesn't seem to have a standard way to report this. I only need motion detection on one cam so it wasn't an issue. But good point, I wonder how Kerberos does this

It doesn't use the builtin ONVIF motion detection but instead processes every keyframe and does motion detection between the keyframes. So not every frame is being decoded to process, but enough to perform motion capture. There's some interesting work w.r.t motion detection that doesn't actually require decoding the packets but rather looks at the motion vectors to estimate motion. That would save up a lot of resourc…

> motion detection that doesn't actually require decoding the packets but rather looks at the motion vectors to estimate motion.

There's a very cool package for the Raspberry Pi that does this: https://github.com/billw2/pikrellcam

Re: Kerberos: Open-Source Video Surveillance

#78
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.

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.

Re: Kerberos: Open-Source Video Surveillance

#79

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. 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.

Careful with that. Ubiquiti doesn’t support ONVIF (industry standard for triggering motion alerts) and stopped supporting RTSP on their new stuff IIRC.

You’re going to want to do a ton of testing if you’re keeping those cameras.

Re: Kerberos: Open-Source Video Surveillance

#80

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. I've prototyped this but it ended up on my shelf of…

That is all part of ONVIF.
Post reply on HN