How to make permanent motion detection in Zoneminder when there is motion?

Question

linux

I noticed an unpleasant thing in Zoneminder, in the presence of a long movement, it generates only one event and, accordingly, it is not possible to record all the events that have occurred.
For example, the camera is on the stairs, people come and walk back and forth for 2 minutes, but in zoneminder there will be only one event with the duration specified in the Buffering section of the camera (now it is set to 15 seconds). Despite the fact that the movement continues, zoneminder still does not want to react to it.
How to make zm record an event (well, or several in a row) while there is movement?

Answer 1

We set the Modect mode, select exactly the area in which the recording is of interest.
Most likely you have done this and it should already write the entire movement.
There is a suspicion that the camera simply does not give, or ZM does not take.
This happened to me with some. The solution is simple: take everything from the camera yourself.
For example, for D-Link 920, the path was something like this: web.cam.ip/VIDEO.CGI
This is the most correct decision that we came to by experience.

Answer 2

That's the way it should be.
The fact is that ZM does not write the usual AVI or any other file.
He writes the events that we observe in the above picture.
Here www.samag.ru/archive/article/2077 the "Event Handling" section will help you.
As I understand it, in your case it only writes the first 15 seconds and then nothing, but now it turns out that the recording is normal, but you just didn’t understand it =)
The whole feature is that these are small events that happened on a trigger (modect - also a trigger, only global).
Further, in the filters, we indicate to collect the archive every day and get daily archives.
After that (for example) we poison ffmpeg for a daily archive and at the output we get a video file.
If you need to fully view not fifteen or twenty seconds, then when viewing, select the checkboxes of those events that interest you, click "play marketed" and watch everything that was marked with checkboxes in one tape.

Answer 3

So you either radically installed it incorrectly, or you configured it incorrectly.

Answer 4

If still relevant, I recently encountered the same problem FreeBSD 9.1 Zoneminder 1.25.0_2
Need to recreate the MySQL database Zoneminder. Or with a high degree of probability only the Monitors table. Of course, everything will have to be set up again.
The following may lead to problems with the database:
1. When creating a motion detection zone, when dragging the corner of the zone with the mouse, you drag the corner out of the border of the edit zone and you can return it back only through editing points. Here it is possible that some records in the database are corrupted.
2. It is possible that incorrect data stream from the IP camera leads to problems, lost frames - this happened when using the rtsp stream via udp (by default). If you run ffmpeg separately and see what's going on with the stream, then there were constant frame drops and even ffmpeg crashes. Zoneminder uses ffmpeg by default. It's a camera problem. Moreover, in my case, the old firmware worked almost without problems, and it worked with the new ones via udp for several seconds, then the zmc process was restarted. Take the stream via tcp, for this add '?tcp' to the end of the stream query string from the IP camera. Example: rtsp://username:[email protected]:554/video.h264?
tcp try to re-create the zm database or rather just the Monitors table and add '?tcp' to the end of the IP camera stream address