Events all report continuous even when it is a motion event.

[baudneo]

My custom ml setup checks the cause of the event, ie. Motion|Continuous|Forced web|ONVIF and doesn't run if it isn't a motion or triggered event (skips continuous). I don't know exactly which commit it was, but I compiled on march 2nd around 11AM MDT.

Not a big issue, just thought I would mention it.

Edit: Pretty sure it was this commit: 904f062
The last commit I compiled before that was February 18th @ 10:52 AM MST: def378f

[connortechnology]

I completely refactored the state machine logic... and I've certainly seen similar reports, but thought it resolved in late Feb. Need debug logs around the start of an event that should have been cause=Motion. Also there are new EVENT_CLOSE_MODE settings that may be the issue. It may be incorrectly falling bcak to IDLE instead of Alarm.

[baudneo]

Kk, I'll get some debug logs this evening. Thanks!

[Simpler1]

I'm still seeing this problem also. About 80% of my events show a cause of Continuous even though I only ever record on motion.

[baudneo]

Log file is huge lol, the event starts around 18:21:13. This monitor was a view only monitor, no recording or modect. I turned modect on to create an event and it came out as continuous, so the logging should hopefully show what's up.

zmc_m15.log

[connortechnology]

Latest code may fix this. Please update and report.

[ppnacho69]

I'm at V1.37.55 updated yesterday and I'm also full of Continuous "Cause" events.

More info. As soon a a motion event triggers recording, ZM stays alarming on continuous mode recording10 minutes each event forever.

[connortechnology]

I believe 503b1ae97 fixes this.

[ppnacho69]

Solved, only event triggers are recorded now on V1.37.55. Thank you

[baudneo]

Fixed!

[Simpler1]

Appears to be fixed. Thanks!