You’re fully right @bertreb, a propper boot often helps …, mostly at Win systems
I will do this directly and test tomorrow!
Thanks!
Which Cam do you use?
You’re fully right @bertreb, a propper boot often helps …, mostly at Win systems
I will do this directly and test tomorrow!
Thanks!
… well, my wife and me tested it today after the yesterday’s evening reboot.
My tests have been successful, the other ones not …
However we will continue to test …
What I recognized unsatisfying was, that motioneye didn’t keep the customized file store path after the reboot.
… but I know, this is not the motioneye forum here
yes, I would say they do, as my two tests, in the early morning and the early evening, have been successful.
I will do a longer test tomorrow morning over 30 minutes, if detection really stays on pause and doesn’t reactivate itself.
What I’m wondering about: Is it correct, that the respective button in the motioneye gui doesn’t switch to ‘off’ when I send the ‘pause’ command?
I have no clue what happened when my wife tested and motion detection continued…!?
Maybe she didn’t hit the button propperly, however …
This one:
Ok, that the button for enabling the whole motion detection function.
There buttons for video streaming, text overlay, etc.
I wasn’t aware that a motion command will switch a the MotionEye option.
well I’m not that deep in the technical stuff, but I thought, that if the command would really switch ‘off’ the whole motion detection functionallity, then further detection definitely should not happen.
However, the ‘start/pause’ commands seems to influence other parameters deeper in motioneye …
So I can stop wondering
Thanks for taking that up!
After another check it becomes clear why we saw different results.
After deactivating motion detection by the ‚pause‘ command, it seems to reactivate itself after ~5-10minutes.
Crucial is, that it continues to respond with ‚… Cam is on PAUSE‘ by using the respective http-link to motioneye.
I will check out for this directly in the motioneye forum this evening…
… now motioneye issue #2311 on Github, let‘s see …
https://github.com/ccrisan/motioneyeos/issues/2311