ZoneMinder Forums

Ok, so the filter approach does seem to be working, with the caveat that all the videos seem to be cut off after a couple of minutes. Is there any chance that the filter runs before the event is complete? EDIT: Just confirmed this is the case. Event ID 1629259 is a currently recording event, but my ...

Nope, I can see in the other thread that "the event will be marked that it has ben processed". That neither says or implies that it won't do it again - especially when the "list matches" button continually returns the same list, implying that it WILL do them again. I'll take your...

Good thought, but doesn't seem to work. Apparently that field needs things in key=value format, not command line args for one thing. I tried using tag:v=hvc1, but that didn't work, so it seems it's not just a format thing. That said, after some more digging, I found this thread: https://forums.zonem...

I have a camera set up in zone minder that streams video in h.265 format. The camera is set up with a source type of "Ffmpeg" and a rtsp:// url. This all works as expected, I can view the camera live and it creates events, but when I download the event video (on my Mac) I can't play it in ...

Looks good, thanks!

I owe you an apology. When I submitted this issue, I approached it from the mindset that I approach all the programing bugs I deal with every day - debug the code and see what it is actually doing vs what it is supposed to be doing. I then made the assumption that you would - and should - approach t...

AND, most significantly we can also see that the problem is a mismatch between the mlapiconfig.ini file, where (in my case) the resize option was set to 1024 (thereby returning scaled polygons), and the /etc/zm/objectconfig.ini used on line 174 of zm_detect.py, where (again, in my case obviously) r...

OR, we could do the smart thing and look at the code that draws the polygons, where we see that: a) there is no relevant logging around the code that draws the polygons on the image (pyzm/helpers/utils.py draw_bbox, or the place in zm_detect.py it is called from) b) you get the newh,neww of the imag...

See the attached image for an example - the polygon drawn in the image should be covering the yard (the cutout goes around the bush), and I'm fairly certain the "dog" detection box should be around the bee. It appears as though the polygon/detection box is drawn on the full-size image, but...

Looks good now. Even after filtering, on the next run the original polygon list showed the full list, and as such filtered correctly. Thanks!

It looks like that did it about halfway. The first time looks correct: May 28 2021 11:25:26.073179 [DBG 2] Only filtering polygon names that have Motion Driveway-Front May 28 2021 11:25:26.073258 [DBG 2] Original polygons being used: [{'name': 'driveway-back', 'value': [(0, 602), (1193, 562), (1522,...

For what it's worth, disabling the "only_triggered_zm_zones" option (but leaving the "import_zm_zones" option enabled) appears to resolve the issue - with the obvious caveat that it will detect objects in any of my defined zones, not just the alarmed zone. Still better than detec...

Ok, it started acting up again last night. Looking at the logs generated when running the test shows this line in the "bad" run that is not present in the "good" run: May 26 05:53:29 watchman mlapi[2305103]: May 26 2021 05:53:29.135784 [DBG 2] No polygons, adding full image polyg...

Ok, now I'm really confused. I re-started MLAPI to get the logs from when it gives the incorrect results, only now it's working perfectly. I guess I'll keep an eye on it, and update this thread if/when it mis-behaves again. Thanks anyway!

I just completed a wholesale update of my zoneminder/zmeventnotification/mlapi system (I was several versions behind), and now MLAPI is detecting objects outside of my zones, even though I have both the `import_zm_zones` and `only_triggered_zm_zones` options set to `yes` in the mlapiconfig.ini file ...