-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[zoneminder] Motion detection is slow #3730
Comments
There are performance improvements in https://github.com/openhab/openhab2-addons/pull/3583. Perhaps you can help @Mr-Eskildsen testing it? |
Thank you for the quick respone. Unfortunately this version does not seem to enable the detection motion faster. |
Your Zoneminder Server seems to be pretty loaded. Cpuload is over 3. You should also consider how long time it takes in ZoneMinder before ZoneMinder reports motion. Typically ZoneMinder looks at a number of frames. Another reason for the 18 seconds might be that the listener isn't working correct (You should be able to start a telnet on port 6902,), That could cause some problems. My guess is that the cause is one of / or a combination:
|
Thank you for your help. I've installed the .jar which you link in the #3583 post, because i realizied the 2.3.0 Version from the PaperUI did not have an Image channel, so i've found out it's not the same version. I didn't test out the performance with the new version jet, but if i hit trigger the alarm in ZoneMinder it seems to work faster. I will run some more test to confirm this. The other thing i've noticed is that the function channel is no longer avaliable. So i can't switch between Monitor and Motion through openHAB. Is it correct that way? I'm running ZoneMinder Server in Virtualbox with 2 Processor and 4GB of RAM. Is not that enough? At the moment one IP-Camera "Wansview W2" is connected over RTSP at 1080p@25fps. I've activated the "OPT_TRIGGERS" option in ZoneMinder so that openHAB can recive the informations, so telnet on port 6902 should work right?! |
closed due to inactivity |
Hey,
I’ve installed Zoneminder on my Debian-System and got the Zoneminder Binding working in openHAB 2.3.
The problem that i have is that the EventState takes too long to change from OFF to ON.
My Camera is above my front door. So if I close the door (time 16:13:34.861) the system recognizes a motion about 6 seconds later Received forceAlarm (16:13:40.713). This would be fine, but the state of the EventState changes 18 seconds after I’ve closed the door (16:13:52.607). This works too slow for my project, because I created a rule that checks if a motion gets detected in case the lock on the door changes from OPEN to CLOSED.
I don’t want to wait for 18 seconds after I closed the door to lock my house. 6 Seconds would be totally fine.
So is there a way that the system sets the EventState faster? Or can I check the Received forceAlarm from Zoneminder? The motion gets detected fast enough from Zoneminder and technically also from openHAB.
zoneminder.things
zoneminder.items
The text was updated successfully, but these errors were encountered: