Jaburges

is anyone having an issue trying to map the correct folder to ensure enabling tensorflow or face is persistent? /config --> /mnt/user/appdata/shinobipro/config (this contains config, customautoload, database) however the folder that I need to be persistent on the container are `/opt/shinobi` Where the plugins are, but if I map that, i get an error regarding /opt/shinobi/run.sh thoughts?

Replying to my own comment as I've been digging around. It looks like there is more in this docker image than initially thought (even more KUDOS!) i couldnt tell what was GPU enabled and what was not - but running `sh INSTALL.sh` in the `plugins/tensorflow` directory gave me the option on reinstall to optimize for ARM64 (jetson) or for GPU. So did that

Hey folks, Awesome template @SpaceInvaderOne - thank you! Running the `:nvidia' tag as using a 1080 and it works well (RAM usage is a little high, but that's probably my settings, and i'm still tuning it). I used to use Shinobi and switched to Zoneminder as it has the ability to use the GPU for object detection. Coming back to Shinobi i'm using the GPU for hardware acceleration, but it doesn't look like the object vision component (YOLO?) is leveraging the GPU? Is it possible, like dlandon's zoneminder docker, to add the ability for the GPU to use the object vision model (assume due to nvidia licensing we would have to compile openCV ourselves using the CUDA packages?)

I think I might be making progress. There seems to be too many symbolic links to `/var/lib/mysql` and '/config/mysql' weirdly /config/mysql seems to be symbolically linked to /config/mysql so the circular reference maybe causing this? Is there a way to stop the docker restarting due to a SQL issue? i have maybe 9 seconds to connect to the docker and try and explore/fix which i'm not going to lie, is REALLY annoying lol

There are so many of these issues on the Zoneminder forums, but I can't see a single answer - the only answer is to rebuild it?

So weirdly (and annoyingly briefly) as the docker shuts itself down, there is no `mysql.sock` in `/var/run/mysqld` has it been moved in the update? Trying to start the service also confirms this: ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2 "No such file or directory")

HI Folks, Just updated the docker and getting an issue connecting to the internal DB (was humming along nicely previously) not sure what happened: @blaine07 I think this is the same issue you had? Did you find a solution? DBI connect('database=zm;host=localhost','zmuser',...) failed: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111) at /usr/share/perl5/ZoneMinder/Database.pm line 110. DBI connect('database=zm;host=localhost','zmuser',...) failed: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111) at /usr/share/perl5/ZoneMinder/Database.pm line 110. DBI connect('database=zm;host=localhost','zmuser',...) failed: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111) at /usr/share/perl5/ZoneMinder/Database.pm line 110. Can't call method "prepare_cached" on an undefined value at /usr/share/perl5/ZoneMinder/Config.pm line 96. BEGIN failed--compilation aborted at /usr/share/perl5/ZoneMinder/Config.pm line 147. Compilation failed in require at /usr/bin/zmupdate.pl line 73. BEGIN failed--compilation aborted at /usr/bin/zmupdate.pl line 73. Sep 25 07:37:07 62915b1f7bec zmupdate[1187]: ERR [Error reconnecting to db: errstr:Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111) error val:] Sep 25 07:37:07 62915b1f7bec zmupdate[1187]: ERR [Error reconnecting to db: errstr:Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111) error val:] DBI connect('database=zm;host=localhost','zmuser',...) failed: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111) at /usr/share/perl5/ZoneMinder/Database.pm line 110.

Could be a weird quirk as I also had 2 Sandisk USB 3.0 32Gb sticks I was trying - 1 worked one did not. Copying over the files manually didn't work either as wouldn't boot so looked at the one that DID boot and noticed EFI was named differently. I didn't think I had done anything differently, the USB creator tool was the same - but the folder was named `EFI-` on the one that didn't work. renamed that to `EFI` and worked fine. So very odd, sharing in case anyone else had a similar issue. File contents from `unRAIDServer-6.8.3-x86_64.zip`

2 questions when you get a chance: 1. Now I've got OpenCV installed do I need to do anything inform the eventservice workflow to use it? Is it really that simple? 2. Is there much benefit in installing OpenCV >4.2 (in the docs you mention >4.3 to use CSPR over YOLO)

Yep I had the right files in opencv. The build failed previously so I needed to rebuild the container before trying again. Once rebuilt, running the opencv.sh seems to be progressing nicely Fingers crossed EDIT: Build completed successfully!

finally got round to sorting out a GPU so looking at the openCV components. Everything except the CUDNN is reporting as YES and getting this error: Could NOT find CUDNN (missing: CUDNN_LIBRARY CUDNN_INCLUDE_DIR) (Required is at least version "7.5") however the runtime and developer libraries are in the /config/opencv folder and correctly match the name of the entries in opencv.sh

Thanks - done 🙂

Do you have a link to buy beer/coffee? I imagine anyone using your docker would be more than happy to send some $$ :-) we appreciate your hard work and time you invest in this!

Did this update include the JSON changes to MQTT in the ES by any chance?

@turt1e also just noticed I’m getting proper alerts (notifications with images) since I sorted out my token.txt file. have you installed ZMNinja on a mobile device? That helped me narrow down the issue as the logs could be checked for connecting on LAN or WAN. Once ZMNinja is connected you check the folder push and the token.txt file in there. I started with LAN using IP addresses and ports and then slowly moved outward until I found the issue. Once you connect ZMNinja app to Zoneminder and the event service - you’ll get a token in the tokens.txt file (as above I had to edit my txt to include all monitors). anyway just a thought of a systematic way to trouble shoot and find the point of failure. good luck 🙂

no, I don’t get a warning even with self signed certs. I’m using a Synology NAS as a reverse proxy (running NGINX). So I hit the synology box, which has a valid public cert, that then routes internally to my Zoneminder instance. also do you have any form of auth enabled? As I would have thought hitting that url would actually present you with a login screen first?

What happens when you find an event number in the console, and plug that into the URL? can you see the image? i seem to remember I switched out my picture URL for the other one in the ini that was commented out. The rest from memory (I’m AFK right now) looks the same

no - i used default certificates. I did add the IP address of the zoneminder instance to ServerName (it then adds back localhost on the 2nd line). When you say you don't get the alarm pictures do you mean an alert/toast on your phone? or if under 'events list' in ZMNinja you tap the 3 dots, and select 'only detected objects' nothing shows? The best way is to watch the logs when you walk in front of a camera and trigger an alarm as there are quite a few steps to getting it to work. Check the alarm triggers the hook, check the hook finds something, and then the hook sends the alert. Based on that you can narrow down what isn't working.

That’s where I found the answer, was letting you know just in case anyone else has the same issue with the docket/it was the upgrade that had caused the problem/you wanted to add it to any docs? I manually added my extra monitors and the intervals to token.txt <token>:1,2,3,4,5,6,7:0,0,0,0,0,0,0:ios:enabled and it solved the issue

@dlandon not sure if this broke in the update, but my token.txt (despite my iOS device registering and ZMninja showing the logs that iOS is reporting all monitors as included [1,2,3,4,5,6,7) only shows 1 monitor and interval 0, ie: <token>:1:0:ios:enabled

Answering so others can track. Update as per Zoneminder forum and Github issue: https://github.com/pliablepixels/zmeventnotification/issues/206 Using the following URLs, you can send either a video or an image in an iOS notification in HomeAssistant: Image: https://URL/zm/index.php?username=blah&password=blah&action=login&view=image&eid=eventID#&fid=snapshot&width=600 Video: https://url/zm/index.php?username=blah&password=blah&action=login&view=view_video&eid=eventID#&fid=snapshot&width=600 In case anyone finds this useful, I use a really basic Node-Red flow. MQTT input: from "zoneminder#" JSON Node Change Node: (swaps the numbers for the names of the camera location) Function Node: { "data": { "message": "Motion at the {{payload.monitor}}", "data": { "attachment": { "url": "https://url/zm/index.php?username=blah&password=blah&action=login&view=view_video&eid={{payload.eventid}}#&fid=snapshot&width=600", "content-type": "MPEG4", "hide-thumbnail": "false" } } } } Call HA service Node

Since playing with the set up, I wonder if someone could help with 2 questions: 1. How would i change what is sent to MQTT? I'm using Node-red so can parse the JSON pretty easily, but the "name" is a little obscure right now: "name": "CameraName:(413) [s] detected:person:38% Motion mudroom" is it possible to add more lines to the JSON after "hookvalue":"0","eventid":"413","state":"alarm","eventtype":"event_start","monitor":"5" to break out say "object": "person" and "percentage" : "38" 2. Is there a way either in the detection script or via ZM API to save the image or video of a successful detection somewhere (or use its current locaiton)? Ideally I would like to use iOS notification to send the image in an alert in HA.

Just upgraded from 1.32 and upgrade went smoothly. Running 1.34 now and the object vision stuff worked straight away! Solid work - thank you!

confirmed your 1.32 docker update with 5.4 zmeventnotification works using WSS (internally and externally using NGINX) I moved it to a separate VM so could use port 9000. Can't confirm if that was the issue though (even though alt port was set in .ini before) Here is my set up and install with HomeAssistant in case it helps someone else. Thanks for building this!

No luck as of yet. Is there anyway to update zmeventnotification.pl inside the docker to the newer/previous version?