-
-
Notifications
You must be signed in to change notification settings - Fork 129
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
End event not being send after Start event #421
Comments
My config doesn't have a use_fcm=... it only has use_fcmv1=. It looks like fcm is controlled with the enable = no setting in the [fcm] block. weird. FCM disabling works here for me. The logic around this message is unclear. I had put a todo on it and have just now commit a potential fix. Please update and report back. |
I have this in my zmeventnotification.ini file
I did pull the latest change and re-ran the install.sh file. right off the bat, noticed this in the debug log
Looking in ZM, these monitors are not in alarm, and I find those events for those monitors from 12 hours ago, so not sure what's going on there but that's new. As for the original issue, I still get the start event
|
Event Server version
6.1.28
Hooks version (if you are using Object Detection)
app:6.1.28, pyzm:0.3.56
Are you using MLAPI? (Y/N)
No
The version of ZoneMinder you are using:
1.37.23
What is the nature of your issue
Bug
Details
Start event is sent, but End event not sent due to "Not sending event end alarm, as we did not send a start alarm for this, or start hook processing failed". I can see the start message in my MQTT. Note, I have set
It is still showing as enabled, which could be generating an error preventing the start script from running properly.
Also note, I have three camera, two monitors per camera. The one's suffixed with "Motion" are lower resolution and the one's I intend to have trigger, then trigger the higher resolution monitor via Link.
Debug Logs (if applicable)
The text was updated successfully, but these errors were encountered: