When analytics appear to do nothing, the algorithm is rarely at fault — one link in the chain is simply not connected.

1. Is the feature enabled? Many devices ship with analytics off. Enable it in the camera's smart settings and select the analysis types you need.
2. Was the rule drawn and deployed? Line-crossing and intrusion rules require drawing the region or line on the image, and confirming the rule was successfully pushed to the device.
3. Is compute oversubscribed? Running several analytics simultaneously on one camera exceeds its compute budget, so some silently drop out. Prioritise the ones that matter.
4. Can the recorder consume it? Camera support does not imply recorder support. Enable smart functions on the recorder channel and configure the linked actions — recording, snapshot, upload, alarm output.
5. Version compatibility: outdated firmware may not recognise protocol fields. Keep front and back end versions aligned with the vendor's recommended pairing.

To verify, walk through the rule region and watch whether the device generates an event and a snapshot. That tells you which link is broken.