Get Started
Part 7

Troubleshooting

Expand the item matching your symptom and check the causes in order.

A rule does not run
  1. Confirm the controller is connected and monitoring is started. Nothing is detected while stopped.
  2. Confirm the rule's switch is on.
  3. Check whether any required condition is switched off.
  4. Check whether the schedule includes the current time.
  5. Confirm at least one ordinary condition exists. A rule with only sub conditions never fires.
Changes are not taking effect

The controller operates on the project it received at start time. Stop and start again to send the new configuration.

A rule fires too often
  • Raise Sustained for and Reset after.
  • Raise the confidence or threshold for the analysis.
  • Set a detection zone to exclude traffic outside the area of interest.
Detections are missed
  • Lower the hold time and the threshold.
  • Check whether Detection FPS is so low that brief events fall between analyses.
  • For faces, check whether Min Face Area is excluding people who are far away.
A specific object or plate never matches

Target values are compared as literal strings. Select objects from the list rather than typing them, and check plates for stray spaces.

A person is recognized as someone else

Raise the face Threshold and enroll additional photos of both people. Each analysis keeps its own list, so enrolling on one camera does not affect another.

Notifications do not arrive

First check the events area to confirm the rule fired. If it did, the issue is delivery: the Grablo app must be installed, signed in with the same account, and allowed to send notifications in the phone's settings.

The log is empty

Records are written only by rules with a Logging action. If only older records are missing, they were removed by the retention setting.

A video does not play

Recording… means saving has not finished; wait for it to complete. No video means the file was not saved. If the clip is too large, reduce the pre-event and post-event durations.

One camera shows no picture

The controller cannot reach that camera. Check the camera's power and network, and whether its address or password changed. The camera must be on the same network as the controller.

Overall performance is slow

There are more analyses than the hardware can support. Lower Detection FPS first, then Mode, then delete analyses no rule uses. QR/Barcode, OCR, and Custom Classification have no Mode setting, so for those three only Detection FPS applies.

A rule stopped after deleting an item

Cameras, integrations, and analyses are shared between rules. Deleting one leaves the rules that used it without a target, and those rules stop. Reflex lists where an item is used before deletion, so review that list. If a rule has already stopped, open it and select the target again.

If the problem persists Use Contact Us in the account menu. Include the rule name, the time of occurrence, and the expected versus actual behavior to speed up diagnosis.