[Support]: Object Detection Periodically Stops for Particular Cameras #15746
Replies: 7 comments 4 replies
-
What specifically makes you think object detection is not running? |
Beta Was this translation helpful? Give feedback.
-
Well I swear I have simply turned object detection on or off to fix it, but it didn't work this time. I also have HASS scripts to turn all cameras off/on (motion, recording, snapshots, object detection) via MQTT that I sometimes use--maybe that was it. Anyways, this time I rebooted Frigate to get it working again. |
Beta Was this translation helpful? Give feedback.
-
In the logs I only notice things about the doorbell camera and, separately, CAM11/CAM12 having non-monotonic timestamps or something. I'm not sure what those issues are (separate concern for me ATM). I would expect they are unrelated to CAM1 having object detection stop since CAM2 was still detecting objects (not a system-wide object detection issue). |
Beta Was this translation helpful? Give feedback.
-
Below are the only logs since this morning and CAM1 is not detecting objects again. This is very interesting though: I went to the motion tuner to see what it was seeing for CAM1 while I walked around and it only saw motion for my head (dark hair on bright background). I lowered the threshold, contour area, and turned off the improve contrast setting. Of course, it saw more motion due to the increased sensitivity. Then I reset it all back to what I had it at (60, 30, on, respectively) originally. I went back to view the camera and it (with the old settings again) was detecting both me and the car in the scene again. I never saved the settings nor restarted Frigate. It may or may not matter, but I do notice the light to dark transition due to a shadow over my car is very distinct. Maybe this passing by affects detectability? See image below. This issue might actually be limited to this camera the more that I think about it.
|
Beta Was this translation helpful? Give feedback.
-
Here’s an example of how turning object detection off and on fixes the issue. ScreenRecording_12-31-2024.16-13-01_1.mov |
Beta Was this translation helpful? Give feedback.
-
Here’s another example video where there are no relevant errors in the logs and turning off and on object detection (in Frigate but not via MQTT) fixes the issue. https://ln5.sync.com/dl/09e6a5f50#juzv5r94-8sxvnkbr-yeyvbkvp-s6ny8qve Or https://mega.nz/file/rI1QXQyZ#iQNaa_JSc6LxPMZU7RyMl8enBlAArEtHYrkP032Kj8o |
Beta Was this translation helpful? Give feedback.
-
@blakeblackshear, the last video summarizes the issue. Any thoughts? |
Beta Was this translation helpful? Give feedback.
-
Describe the problem you are having
I have 8 outdoor cameras of the same type. A few should continuously see some cars due to their position. I notice that occasionally the cars are no longer detected (and car count in Home Assistant goes to zero) on CAM1 and CAM2. If I walk in front of the camera it doesn't detect me. It is obvious it is no longer detecting objects. Object detection on the Frigate page for the camera settings says it is on. It also shows as on via the Home Assistant sensor. If I turn off object detection and back on (in Frigate or HA) it works again. After a while it will stop working again. I haven't seen any relevant information in the logs as to why this is happening. My system has ample resources (CPU averages 5-6% and GPU 3-4%).
Version
0.14.1-f4f3cfa
What browser(s) are you using?
No response
Frigate config file
Relevant Frigate log output
Relevant go2rtc log output
FFprobe output from your camera
Frigate stats
Install method
Docker Compose
docker-compose file or Docker CLI command
Object Detector
Coral
Network connection
Wired
Camera make and model
Amcrest IP8M-2779EW-AI
Screenshots of the Frigate UI's System metrics pages
Any other information that may be helpful
No response
Beta Was this translation helpful? Give feedback.
All reactions