Alarm status is not ended with Norecord

[Detlef Paschke]

Hello,

I noticed with ZM 1.37.48 that a sub-stream monitor with Analysis Always and without recording, the alarm status is no longer completely ended. Even after the event, the sub-stream monitor remains in alarm status but with a yellow border and yellow writing in the Montage. The connected main stream monitor goes idle.

If the Sub-Stream Monitor is switched to Record On Motion, it goes idle after an event.

Many greetings
Detlef Paschke

[MohanDavid]

You're right, the yellow alarm state with Analysis Always for sub-streams seems like a new quirk introduced in ZM 1.37.48.

Here are some things to explore:

Possible explanation: It might be a bug where the alarm doesn't properly clear in Analysis Always mode for sub-streams. Some users have reported similar issues on the ZoneMinder forums.
Troubleshooting:
Check the debug logs for any clues related to the persistent alarm state.
Try manually triggering and clearing the alarm to see if it behaves differently.
Experiment with different Analysis Always settings (e.g., minimum detection score) to see if it influences the issue.
As you mentioned, switching to Record On Motion seems to clear the alarm as expected. This could be a temporary workaround while waiting for a potential fix.

[iconnor]

Fix pushed. Packages building.

[Detlef Paschke]

Hello,

sorry but I think it's even worse now.

The main stream does not stop recording at all or only after the set maximum section length.
The "Record on Motion" Monitor is displayed as "idle" after an event, but the recording continues to run unnoticed in the background until the set maximum section length (standard 600 seconds) is reached.
You notice it when suddenly several hundred MB are added in just a few events.

Many greetings
Detlef Paschke

[Detlef Paschke]

The main stream does not stop recording at all or only after the set maximum section length.
The "Record on Motion" Monitor is displayed as "idle" after an event, but the recording continues to run unnoticed in the background until the set maximum section length (standard 600 seconds) is reached.

This also seems to be the case if the sub-stream is also set to Record on Motion. After the event, both monitors continue to record in the background until the maximum sector length is reached. However, both monitors are shown as idle.

Just tested again with a manually triggered alarm.

[bbunge]

I've just noticed the events are going to 10 minutes in most cases even with a 5 alarmed frames event.

Debian 12 system

I check for updates daily

[iconnor]

@bbunge what is your EVENT_CLOSE_MODE set to? If it's TIME then yeah the expectation is to run out the clock.

I've just done a huge revamp of this code, trying to make it easier to understand. WIll do a bit more testing before pushing though.

[bbunge]

Idle

[bbunge]

1.37.50 - Events still not closing when motion ends. Events going until Section length time is reached.

[Burtski]

1.37.50. Same issue.
EVENT_CLOSE_MODE = idle.
I have set the section length to 30 seconds for now.
I have 10 High Resolution monitors all linked to the Low resolution Mocord monitors.
This eats up a lot of disk space fast recording 100 minutes of high resolution for a 15 second event.

[iconnor]

Today I pushed my revamp of the state code.... please test with todays packages.

[bbunge]

Initial test shows it is working now. Will see what it does over night. Expecting snow and that usually results in lots of events.

FYI - I had gone back to 1.36 from the Debian repo. Upgraded to the 1.37.50 from the zmrepo with no apparent issues. Have not checked all the settings yet... May have to redo the zones.

[iconnor]

If there are no issues... that would be a first for this ZM dev team (me).

This is a fairly major code change... but I think in terms of structure and long term maintainability, a huge step forward.

1 item off the todo list towards 1.38.

[Burtski]

I let it run over night.
It appears the event is ending too soon now.
( camera is set to 5fps )
Pre Event Frames = 25
Post Event Frames = 150
Section Length = 600

The last event only captured 47 frames.
It captured 25 Pre Event frames.
Then 19 alarm frames.
But only 3 frames after the last alarm frame.

Another event on the same camera:
Pre Event frames : 29
Alarm frames : 6
Post Event frames: 1

[iconnor]

Todays build might better