motioneye-project/motioneye

on_picture_save action and on_movie_end not separated

Open

#2,241 opened on Dec 1, 2021

View on GitHub
 (11 comments) (0 reactions) (0 assignees)Python (3,533 stars) (636 forks)batch import
enhancementfeaturehelp wantedquestion

Description

Hi,

i try to test the configuration of motioneye and i want to have a possibility to set different actions for "picture save" and "movie end". At the end i want to sent the oic when it is saved and i want to send the movie when the movie is save, both via telegram with seprated shell scripts.

In the GUI Setup i found the option "File Storage --> Run a command". But tis option effects "on_picture_save " and "on_movie_end " at the same tiime with the same command.

file_storage camera_config

Is it possible to configure both separatly?

Thanks & best regards

My setup: motionEye Version | 0.42.1 Motion Version | 4.4.0 OS Version | Raspbian 11 on PI4

Contributor guide

Tech stack
pythonjavascriptshell
Domain
frontendbackend
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Familiarity with motionEye's config structureBasic understanding of Python backendFrontend development knowledge
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
Review the 'File Storage' section in the GUI (likely in static/app.js or similar) and the backend command execution logic (probably in motioneye/commands.py or similar). The issue requests separating the 'on picture save' and 'on movie end' actions, which currently share a single command field. You'll need to add separate fields in the UI and handle them separately in the backend when saving config and executing commands. Check existing PRs or discussions for any prior attempts or design considerations.