External trigger of Motion to Start a Event, not Start the Event

[BLLuis]

I need an external way to trigger motion to let motion start the event and stop the event when no more motion is detected.
At the moment I start the event but I HAVE to stop the event, I need a way to trigger motion so the event is started when I call the trigger and stopped when no more motion is detected without calling eventend.

Im not asking for: http://motionsrv:8000/00105/action/eventstart
Because I have to: http://motionsrv:8000/00105/action/eventend

Any clue is this is already implemented? Im asking because I got very confused about versions/docs/pr and new things that I can't find in documents.

Or is there any way to do it?

Just joking, my possible solutions: Open a water conduct directed to the cam, turn on a motor that move a tree in front of the camera, Turn on a laser beam or a flashlight directed to the cam.

Besides Jokes (used as examples), need a way to fire motion calling a function or url.
Maybe related to: #1627

[BLLuis]

Well, I put some code inside:

First I cloned url management for eventstart and make my own eventfire url
In my eventfire a put 100 into emulate_motion (I know emulate_motion is for configuration but now I'm using to make my own test without modify too much code).

in webu.c

 (mystreq(webui->uri_cmd2,"eventfire")) {
        if (webui->thread_nbr == 0 && webui->cam_threads > 1) {
            while (webui->cntlst[++indx]) {
                webui->cntlst[indx]->conf.emulate_motion = 100;
            }
        } else {
			webui->cnt->conf.emulate_motion = 100;
        }

Then in mlp_actions, after checking emulate_motion (old code) if this variable is greater than 0, I decrement, so, it works like a temporal emulate_motion.

in motion.c

if ((cnt->conf.emulate_motion || cnt->event_user) && (cnt->startup_frames == 0)) {
		if(cnt->conf.emulate_motion > 0)
		{
			MOTION_LOG(DBG, TYPE_ALL, NO_ERRNO
                        ,_("Emulated motion fired"));

			cnt->conf.emulate_motion--;
		}

Still have to test if real motion is detected into this time frame (about 8 seconds using a value of 100) the event keep fired besides emulate_motion already reach value of 0.

In a future, what I need to reach is:
Detect motion by motion itself and the help of an external sensor (partial atm because I have to call eventend when I have called eventstart).

Disable motion detection, trigger motion by external sensor, but let motion determine when the motion ends (Maybe having motion paused, then on sensor signal, resume motion, fire motion and pause motion again, don't know if motion keep the already fired event in case of motion pause).

[BLLuis]

Seems to be working:
If I fire motion using my code, the event is started, if no real motion is detected the event stop by itself.
If I fire motion using my code, the event is started, if real motion is detected the event keep running until motion ends.
If the event is already fired and I call my code, the event take longer time to finish (if called almost at the end) because the emulate_motion still have a non zero value, I like this, because if the sensor trigger again the event keep running.

Hope somebody else can test this and add to the motion code using a more suitable way, maybe adding another variable to the context structure and not using the emulate_motion like my test.

Still have to test another approach, have motion paused and call this code, then test if motion is detected, anyway for this I can resume motion detection by api call, then call my code and in the eventend call pause motion again using an external script, so, I reach a goal, fire motion using an external sensor, then let motion detect when to finish the event and if the sensor triggers again keep the event running.

A more suitable way:

Create a config parameter for fire timeout
Implement fire api, like /action/eventfire
Add fire timeout value to context struct.
When eventfire is called, put the value from config parameter to the new variable
Check in motion loop if fire timeout variable have a non zero value, if non zero, act like emulate_motion, then check if the timeout has elapsed reset the variable with zero.

I'm available to do it but need instructions and know if anybody think this will be useful or not. also need that somebody else check if this approach is correct, atm is working here.