Closed mckin21 closed 1 year ago
I was not able to reproduce this. Based upon the setting, there is an event gap of 60 seconds and the log shows that Motionplus was triggered to end 48 seconds after the event started.
Can you try to wait the full minute after the motion ends to see if the event end is triggered?
This was the issue. My apologies
Did you read the guide?
Yes
What is the base version number of MotionPlus being used?
0.1.x
What was the install method?
Built from source code
What is base architecture?
ARM-64bit
What is the distro being used?
Raspbian
Disto version number
bullseye
Camera/Sound type(s) being used?
PI camera via libcam
Describe the issue/problem and steps to reproduce
Two week ago, I installed a version of motionplus only my raspberry pi 4. It was working rather smoothly with no issues. In the past two days, I've reinstalled and rebuilt from the source code and ran into an issue where motion is detected by the camera, the camera does not seem to stop detecting motion when there is no motion in view. I have taped the camera just to block out all possible motion events that maybe even I couldn't notice on the web stream. I have tried running motion with a raspberry pi camera module 2 and 3. Both have the same issue though. My pi is running the latest version of bullseye and I have tried both with and without updating/upgrading all packages prior to installing motionplus
Relevant MotionPlus log output (at log_level 8)