- Reviewed guide and contributing documents? (Yes/No):
- version [x.y.z, hash, other]:
- installed as a package or compiled from sources [deb, rpm, git, other]:
- standalone or part of third party [motion, MotionEyeOS, other]:
- video stream source [V4L (card or USB), net cam (mjpeg, rtsp, other), mmal]:
- hardware [x86, ARM, other]:
- operating system [16.04, Stretch, etc, FreeBSD, other]:
0: Yes and interacted with MrDave via the forums
1: Motion 4.2.1
2. Installed from .deb package
3. Standalone
4. rtsp based netcams ameras
5. Pi 3b+
6. Stretch - Linux motionpi3 4.14.79-v7+ #1159 SMP Sun Nov 4 17:50:20 GMT 2018 armv7l GNU/Linux
As per MrDave and my testing I can no longer use http://localhost:8080/camid/action/quit when using webcontrol_interface 0. This functionality still works with webcontrol_interface 2.
Why do I want the quit function on a camera by camera basis rather than a global quit? I have 4 cameras and 3 are used for motion detection and the 4th is just timelapse. Using automation I would pause motion and then /action/quit 3 of the camera which would significantly reduce the CPU utilization associated with these three cameras. The Pi is used for Pihole and home automation so I am careful with CPU capacity.
Can the functionality for /action/quit be restored in a future release to work as it did in 4.1.1 and still use webcontrol_interface 0. Right now I am using webcontrol_interface 2 to restore the functionality at the cost of no longer having thumbnails available to me.
P.S. Additionally I would like the motion program to continue to run even if I /action/quit all 4 cameras as it did in 4.1.1.
0: Yes and interacted with MrDave via the forums
1: Motion 4.2.1
2. Installed from .deb package
3. Standalone
4. rtsp based netcams ameras
5. Pi 3b+
6. Stretch - Linux motionpi3 4.14.79-v7+ #1159 SMP Sun Nov 4 17:50:20 GMT 2018 armv7l GNU/Linux
As per MrDave and my testing I can no longer use http://localhost:8080/camid/action/quit when using webcontrol_interface 0. This functionality still works with webcontrol_interface 2.
Why do I want the quit function on a camera by camera basis rather than a global quit? I have 4 cameras and 3 are used for motion detection and the 4th is just timelapse. Using automation I would pause motion and then /action/quit 3 of the camera which would significantly reduce the CPU utilization associated with these three cameras. The Pi is used for Pihole and home automation so I am careful with CPU capacity.
Can the functionality for /action/quit be restored in a future release to work as it did in 4.1.1 and still use webcontrol_interface 0. Right now I am using webcontrol_interface 2 to restore the functionality at the cost of no longer having thumbnails available to me.
P.S. Additionally I would like the motion program to continue to run even if I /action/quit all 4 cameras as it did in 4.1.1.