detection and alert via mqtt with zmeventnotifierįrenck’s integration allows for viewing the camera frame and works well but no camera controlsįrenck had developed an integration for this but dropped it in favor of Motioneye because the Shinobi development was too progressing slow Works very well, camera views and camera controls, even obj.
Abode iota zoneminder manual#
Manual SQL: mysqldump, mysql redirect importīutton to save and restore to tar.gz file, works great!Īttempted json export, setup new docker instance use import and it failed
Abode iota zoneminder full#
I think performance was good but I couldn’t tell if trigger/detection was working until my disk was full of recordings of nothing Copy option tree to other cameras is a VERY nice feature.ĥ.5 load average (full-res 2.8-3MP 10fps)ģ.5 load average (all cameras scaled down to 1024x768 10fps) - CPU overrun at full-res Power video viewer for recordings is terrible. Lots of options but layout, navigation, and feel is terrible. Various ways to review recordings.Ĭlean and snappy! Well organized option set, but limited configuration options. Front page shows all camera’s states at a glance. Tons of options because ZM has been around a long time. Supports zones but not advanced triggering like ZM Terrible trigger support: front-edge one-shot trigger only, then timer-based video recording. Mediocre support for triggering has object detection OOTB but requires significant CPU (had to reduce resolution)
Abode iota zoneminder license#
Must pay for license to use – didn’t evaluateĮxcellent support -advanced zoning config, alarmed/filtered/blobed - capturing depends on trigger Motion Eye - look and feel just like web app ZmNinja - fully functional - different interface Works well, found all my cameras but used rtsp stream instead of rtmp Not really, weekly nag screen to dismiss, also riddled with licensing options After I created the table, I decided I’d tabulate where I thought each package performed well and see how they measured up. I put together this table of my experiences so I could try to record the things I found good and bad for each package. In fact, I ran Motioneye on the machine for the last week but ended up switching back to ZM today because it isn’t as feature-rich. I’m going to come out and say: I’m probably biased to ZM since I’ve used it for so long but I did try to give each package a fair shake because I was fully intending to switch to something else. I think ZM probably still wins at this point even though I spent a good chunk of today trying to get it working without success. Well, eventually I realized that was a fruitless endeavor. Primarily, I was interested in seeing if I could find something else that was also docker-based but would work quickly/easily with GPU and/or TPU offloading. Anyway, I’ve run it with dlandon’s object detection docker and recently he deprecated the docker image I was using so I took the opportunity to fully evaluate other options. They’re hooked to a beastly computer (6-core E5-2620 with 128GB of ram) so I have no problem scaling up the shared memory area so ZM can do its thing. I have a set of seven Reolink security cameras that I’ve used with Zoneminder for a long time.
0 kommentar(er)
