From 809f3b8ba959ead5ba5a8fdfd9c70eb826c22082 Mon Sep 17 00:00:00 2001 From: Koushik Dutta Date: Wed, 31 Jul 2024 10:34:39 -0700 Subject: [PATCH] Update troubleshooting.md --- scrypted-nvr/troubleshooting.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/scrypted-nvr/troubleshooting.md b/scrypted-nvr/troubleshooting.md index 24fef42..f81a938 100644 --- a/scrypted-nvr/troubleshooting.md +++ b/scrypted-nvr/troubleshooting.md @@ -141,4 +141,4 @@ Improperly configured systems may not be able to access the GPU when performing ### Camera Activity -Cameras that are actively performing object detection can be viewed in the `Video Analysis Plugin`. If the high cpu usage is persistent, it may be due to cameras that are constantly reporting motion and never going idle. For example, trees blowing in the wind will trigger object detection. To resolve this issue, use motion zones *on the camera* to reduce unimportant motion that is reported to Scrypted. For example, zoning the camera to only perform motion detection on walkways and driveways, rather than on landscaping features. +Cameras that are actively performing object detection can be viewed in the `Video Analysis Plugin`. If the high cpu usage is persistent, it may be due to cameras that are constantly reporting motion and never going idle. For example, trees blowing in the wind will trigger object detection. To resolve this issue, use [motion zones on the camera](/camera-preparation.html#motion-sensor-setup) to reduce unimportant motion that is reported to Scrypted. For example, zoning the camera to only perform motion detection on walkways and driveways, rather than on landscaping features.