I too was noticing the event cut off early. But, it was still working!
Ah, update is showing. Will report back later.
Alarm status is not ended with Norecord
Re: Alarm status is not ended with Norecord
Motion Detection : Always
Analysis FPS : 5.00 ( Camera is 5 FPS )
Recording : On Motion/Trigger/etc
Pre Event count : 25
Post Event count 300
It captured 15 events. They are all exactly 10 seconds long ( either 51 or 52 frames )
One event had 29 Pre Event Frames, 5 alarm frames and 1 post frame.
Also:
The event list shows 52 frames but when I pullup the list of frames there are only 34
I have it set to list 100 rows / page.
Analysis FPS : 5.00 ( Camera is 5 FPS )
Recording : On Motion/Trigger/etc
Pre Event count : 25
Post Event count 300
It captured 15 events. They are all exactly 10 seconds long ( either 51 or 52 frames )
One event had 29 Pre Event Frames, 5 alarm frames and 1 post frame.
Also:
The event list shows 52 frames but when I pullup the list of frames there are only 34
I have it set to list 100 rows / page.
Re: Alarm status is not ended with Norecord
Slightly off topic, but related.
I am noticing a bunch of odd behavior in other places as well as the event recording.
Beginning to wonder if maybe I have database problems.
Is there a good procedure to scrub everything clean and start over?
In particular make sure the database is clean.
BTW, Thanks Connor!!
I am noticing a bunch of odd behavior in other places as well as the event recording.
Beginning to wonder if maybe I have database problems.
Is there a good procedure to scrub everything clean and start over?
In particular make sure the database is clean.
BTW, Thanks Connor!!
-
- Posts: 1322
- Joined: Sat Aug 31, 2019 7:35 am
- Location: San Diego
Re: Alarm status is not ended with Norecord
There are a couple of things you can do, depending. Check out this:
https://wiki.zoneminder.com/MySQL
https://wiki.zoneminder.com/MySQL
Re: Alarm status is not ended with Norecord
Reinstalled from scratch.
Found this in a log file
Found this in a log file
01/21/24 11:33:41.347972 zmc_m2[79319].INF-zm_monitor.cpp/2329 [Susan West LowRes: 838 - Closing event 5, section end forced 1705858421 - 1705858409 = 12 >= 600]
-
- Posts: 27
- Joined: Tue Sep 12, 2023 6:14 pm
Re: Alarm status is not ended with Norecord
Hello,
I updated to 1.37.50 today.
I manually triggered an alarm for a few seconds. After the alarm stops, the monitor will appear as idle. However, the recording continues unnoticed in the background until 10 minutes (maximum section length 600 seconds) are reached.
EVENT_CLOSE_MODE is set to idle for me. I downgrade to version 1.37.48 before January 11th, 2024 and set zoneminder back to apt-mark hold. Until this update, the yellow frame remained around the sub-monitor after an alarm, but recording was stopped. Since the update on January 11, 2024, the frame has disappeared after the alarm, but the recording continues unnoticed. The result is: Zoneminder 1.37x versions after January 11, 2024 are unusable.
Many greetings
Detlef Paschke
I updated to 1.37.50 today.
I manually triggered an alarm for a few seconds. After the alarm stops, the monitor will appear as idle. However, the recording continues unnoticed in the background until 10 minutes (maximum section length 600 seconds) are reached.
EVENT_CLOSE_MODE is set to idle for me. I downgrade to version 1.37.48 before January 11th, 2024 and set zoneminder back to apt-mark hold. Until this update, the yellow frame remained around the sub-monitor after an alarm, but recording was stopped. Since the update on January 11, 2024, the frame has disappeared after the alarm, but the recording continues unnoticed. The result is: Zoneminder 1.37x versions after January 11, 2024 are unusable.
Many greetings
Detlef Paschke
Re: Alarm status is not ended with Norecord
Try the latest please.
-
- Posts: 27
- Joined: Tue Sep 12, 2023 6:14 pm
Re: Alarm status is not ended with Norecord
Hello,
Today I updated from 1.37.48~20240104.28-bookworm to 1.37.50~20240127.87-bookworm and the "10 minute problem" is fixed for me.
The recordings are stopped again after the event and reaching the post-event buffer. Thank you.
Many greetings
Detlef Paschke
Today I updated from 1.37.48~20240104.28-bookworm to 1.37.50~20240127.87-bookworm and the "10 minute problem" is fixed for me.
The recordings are stopped again after the event and reaching the post-event buffer. Thank you.
Many greetings
Detlef Paschke