We have a testing room that is used at irregular intervals. Because record on motion has failed to capture questionable activity in the past, I created two User defined events - one to start continuous recording and one to stop continuous recording with the expectation that the test proctors would activate the start event at the beginning of the exam and would activate the stop event and the end of the exam.
However, I don’t want to depend on them activating the stop event and would rather not find out later that weeks of recording of an empty room had been stored.
I was looking for a way to just set the camera to a ‘record on motion’ state at a specific time every day - perhaps 3 AM - in order to limit the number of potential hours continuously recorded in the event that the stop event was not activated.
However I could not find this in the rule set and the support agent I spoke with could not think of a way to do that either.
Does anyone have any ideas on how to do this? I’m open to installing and learning the SDK.
The way I understand your situation you would like to do something that will automatically stop whatever has been started, specifically that a user-defined event to start recording has been sent and a user-defined event to stop recording has not been sent.
The easiest way is to send the user-defined event to stop recording.
The easiest way to do this is to make a new rule looking something like this:
--
Perform an action that Occurs every day at 03:00
On site DKWS-BA-05 trigger user-defined event StopRecording_UserDefinedEvent
--
I have to admit that my brain is coming up with a lot of ideas for advanced control by developing an application or Event Server plugin, so if the solution above is too simple or not what you had in mind, please let me know and please try to outline what you think an ideal solution would look like.
No, you are correct - I see now that I was over-thinking the problem.
I was thinking that I had to activate a new stopping process when all I had to do was activate the already created event that would stop the original process.
Yes I think rules with “Perform an action on a recurring time” was that introduced later than 2018R3.
I think your rule will work, perhaps you can make a test to make sure it works as intended. Please do and please let me know if it works as I do not have a test system of this old version presently.