Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature] Option to manually start and stop recording? #229

Open
TimAEllis opened this issue Jun 16, 2016 · 26 comments
Open

[Feature] Option to manually start and stop recording? #229

TimAEllis opened this issue Jun 16, 2016 · 26 comments
Labels

Comments

@TimAEllis
Copy link

The title says it all but is there any feature that allows the user to essentially press a record button on one or all webcams at any given time.

Say, for example, I don't have motion detected recording enabled but whilst viewing, I want to manually record a block of time; be it 5 minutes or 2 hours. Is there any support for this?

I would assume it would just be a pop-up menu item like viewing photos and videos where I can simply press record to start recording and then stop to stop it.

@TimAEllis
Copy link
Author

Actually just noticed something very similar on the road map. Any idea on when you think the feature will be implemented?

@ccrisan
Copy link
Collaborator

ccrisan commented Jun 16, 2016

There are plans in this direction but no work has been done yet.

@yanoschik
Copy link

I'm interested in this feature too... would appreciate if there were buttons to manually: A) take a picture, and B) start/stop recording. Thanks

@dintid
Copy link

dintid commented Jul 14, 2017

Any news on this?
It's a bit of a bother (a large bit) having to change a setting and apply in order to manually record something and stop it again.
Thanks

@Shaka-60hp
Copy link

I'm interested too, this post is rather old , Any news on this?

@TopperBG
Copy link

TopperBG commented Dec 4, 2017

Following

@WaGi-Coding
Copy link

still not possible? :/

@GrahamDB
Copy link

GrahamDB commented Dec 5, 2018

I am also interested in this feature. Perhaps a command line script as a short term work around until this can be put in the web interface?

@DaafSamson
Copy link

+1 would like to see this feature!

@crahlfs
Copy link

crahlfs commented Feb 18, 2019

+1 me too. I need to send start / stop from with http request! Perfect for home automation

@EJNash1
Copy link

EJNash1 commented Apr 20, 2019

+1 Any update on this. Is this project still ongoing as of Q2 2019?

@jasaw
Copy link
Contributor

jasaw commented Apr 23, 2019

As a workaround for now, you could start/stop recording by enabling motion detection, then sending a HTTP request to trigger motion detection.
http://localhost:7999/1/config/set?emulate_motion=1 to force trigger motion detection.
http://localhost:7999/1/config/set?emulate_motion=0 to disable forced motion detection.

@ualex73
Copy link
Contributor

ualex73 commented Apr 23, 2019

The http request with eventstart and eventend should also work.

@karthickshiva18
Copy link

As a workaround for now, you could start/stop recording by enabling motion detection, then sending a HTTP request to trigger motion detection.
http://localhost:7999/1/config/set?emulate_motion=1 to force trigger motion detection.
http://localhost:7999/1/config/set?emulate_motion=0 to disable forced motion detection.

in which version this works...Please answer.

@jasaw
Copy link
Contributor

jasaw commented Aug 29, 2019

@karthickshiva18 Emulate motion has been in motion for a long time. Any version should work.

@colinlgray
Copy link

@jasaw is there any more information how to send those commands via http request? I got a 404 error when sending both get and post requests. Screenshots attached from my terminal and motioneye.log

Screen Shot 2020-07-04 at 10 09 36 AM

Screen Shot 2020-07-04 at 10 10 09 AM

@davebdb
Copy link

davebdb commented Jul 5, 2020

@colinlgray is motion running under port 80? You need to specify the port
http://host:port/1/config/set?emulate_motion=1

port 7999 is the default "command/control" port for motion. Your examples are going against port 80 so you must have some other webserver (or motioneye set) on that port.

here is my sample of my script for on and for off

$ cat light_on_1
#!/bin/sh
/usr/bin/curl "http://localhost:7999/1/config/set?emulate_motion=1"
$ cat light_off_1
#!/bin/sh
/usr/bin/curl "http://localhost:7999/1/config/set?emulate_motion=0"

Let me know if that resolves your issue.

BTW: the "light_on_#" and "light_off_#" is for setting control buttons on the cameras on the motioneye interface, if you didn't already know that. You put them in your motioneye config directory, default of /etc/motioneye

One other note, you need to be on the local system that your motioneye is running on for this to work, so its best to use localhost in this instance. If you want to allow access from another system, you will need to set the permissions in the config for motion to accept non localhost (127.0.0.1) connections for command/control. I don't have that off the top of my head, but its in the configuration.

@colinlgray
Copy link

Thanks for the clarification there. This was my bad, I am running motion via motioneyeos. It sets up a web interface on your local network and I was trying to send requests to that interface. I need to see how it exposes this interface

@lcleve
Copy link

lcleve commented Jul 29, 2020

I need to record sleep, e.g. 8 hour sessions. A start/stop button would be very useful so that unskilled users could operate the soft ware. Even a toggle switch connected with one of the GPIO pins would be desirable. Currently, it looks like I will write a script to control rasspivid.

In any case the ease of installing and setting up MotionEyeOS is a welcome relief from software like BlueIris.

Many thanks,

lcleve

@jasaw
Copy link
Contributor

jasaw commented Jul 29, 2020

@lcleve If you use a toggle switch, you should be able to use this script by just changing the GPIO pin: motioneye-project/motioneyeos#842 (comment)

@lcleve
Copy link

lcleve commented Jul 29, 2020

Thanks.
I'll look into it.

lcleve

@rateur42
Copy link

+1 would like to see this feature!

@WattageGuy
Copy link

WattageGuy commented May 4, 2022

+1

@MichaIng MichaIng added feature and removed Stale No Activity 60 Days To be marked closed labels May 5, 2022
@MichaIng
Copy link
Member

MichaIng commented May 5, 2022

A reasonable feature indeed, I would find it helpful for testing as well.

@filip-strelec
Copy link

filip-strelec commented Dec 25, 2023

+1

@KodeMunkie
Copy link

+1 as it's a fairly easy feature to add to the ui

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

No branches or pull requests