Replies: 5 comments
-
I'll take a few additional comments on this but am pretty sure that this will be get classified as invalid and it is working entirely as I intended it to when I added it. I know for certain that the title of this issue is precisely what I intended. |
Beta Was this translation helpful? Give feedback.
-
For me there is 3 scenarios :
How can we achieve the last scenario in the actual version : an eventstart action trigger only one motion detection ? |
Beta Was this translation helpful? Give feedback.
-
I'm thinking that isn't supported. The result prior to the commit referenced invoked new events at the end of the maximum movie time. This wasn't a correct approach. Per all the documentation from the origins of Motion, the event was to continue regardless of the movie time. Additionally, this resulted in a different behavior depending upon whether movies were requested or not. i.e. If no movies were created, each event would last until the gap occurred. In the method before the commit, multiple events would be triggered based upon the maximum movie time. The desired effect being requested (I think) is to have user event only invoke an event until the maximum time is reached for a movie. (i.e. Tying together a maximum movie duration and a maximum event time) |
Beta Was this translation helpful? Give feedback.
-
Yes, setting a maximum time length for an event could achieve the requested functionality. |
Beta Was this translation helpful? Give feedback.
-
One question : why there is the possibility to take a snapshot independently of an event (using the |
Beta Was this translation helpful? Give feedback.
-
Did you read the guide?
Yes
What is the base version number of Motion being used?
4.3.x
What was the install method?
Built from source code
What is base architecture?
ARM-32bit
What is the distro being used?
Raspbian
Disto version number
buster
Camera type(s) being used?
Network camera with HTTP
Describe the issue/problem and steps to reproduce
I need to manually start recording movies using actions via an external trigger.
I use the eventstart and eventend actions :
wget -O- http://127.0.0.1:7999/1/action/eventstart
This works with motion 4.3.2 till this commit b2726fa821db3903328fca06260078ee175fb132.
Since this commit 262b6b0ac62f92fa2410bdc556a10daacb28e7f3 it doesn't work as expected because eventstart action makes motion create records continuously as if the parameter
emulate_motion
is set toTrue
(but it is not).The log above is for the
262b6b0
commit.Relevant Motion log output (at log_level 8)
Beta Was this translation helpful? Give feedback.
All reactions