ZoneMinder Forums

In 1.37, this is doable.

We have filters at the top now with which you can tell it to show only events with either something in the notes column, or now we have a new Tags feature.

Turn on debug logging, it should log the values being sent.

Just pushed a fix.

In Filter.pm, around line 164 we force the op to EXISTS. Need to instead restrict it to valid values like NOT EXISTS etc.

We are grateful for any amount! I think $25 is around the average donation. Lots of $10. Anything less really isn't worth it as transaction fees leave not much.

Some wonderful people donate a lot more.

You can add an exists in filesystem rule to only delete accessible events.

sgzoneminder.readthedocs.io is generated from someone else's fork and hasn't been updated in years.

zoneminder.readthedocs.io is our docs, and has a nice getting getting started section:
https://zoneminder.readthedocs.io/en/la ... arted.html

The logic goes both ways. Some people just want the event to disappear and get deleted later in the background. When you get into s3fs filesystems, etc the performance of deleting is so bad, that you just want to delete from the db anyways. We take the view that the video has the greatest value, and...

We run 1.37 in production. Yeah sometimes things break, but we fix them fairly quickly.

I believe it works. I have not tested extensively with a ton of models, but so far every reolink has worked for me.

Yes you need 1.37.

Is there some reason you need something newer?

Arm builds aren't automated unfortunately

I never implemented the rest of the operators for this. I'll try to get to it soon.

We definitely do see some weird behaviours, but it almost always is because something can't keep up and people ignore their logs which are screaming full of warnings and errors.

Each event has a StorageId to tell it where it is. The Storage entry has a ServerId field which can be empty, but can also specify the server that it actually exists on, so that we can ask that server for the content. If you aren't using storage areas.. then all events are stored in /var/cache/zonem...

Effect can also be caused by decoding thread falling behind, or not enough buffers. In which case your logs will be filled with errors. Check your logs.