Why does adding a plate to a Security Center hotlist fail to create hits for older reads?
Answered by ANPR AI·Sourced
Short answer
Hotlist edits affect new reads; retrospective matching is separate.
Explanation
The hotlist editing guide does not promise automatic reprocessing of earlier detections.
Things to check
- Read time
- Hotlist update time
- Available retrospective workflow
What to do
Test a new read and use the product’s documented historical matching or investigation tools when reviewing older data.
Was this answer helpful?
Your vote decides which questions we answer next.
Cloud API
Test plate and vehicle recognition on your own images.
Send a photo or camera frame to our API and get the plate, country, make and model back as JSON. Start free, or run the same models on your own servers.
- 100 free credits every month, no card
- Plates for Saudi Arabia, Qatar, Kuwait, Bahrain and Oman
- Cloud API or on-premise deployment
What to read next
ProductCloud ANPR APISelf-serve plate and vehicle recognition API with a free tier, or run it on-premise.Read GuideConnect an IP camera to ANPRStep-by-step: RTSP streams and snapshots from the cameras you already have, sent to the API.Read ComparisonANPR camera alternativeWhat a dedicated ANPR camera costs against a standard IP camera plus plate-recognition software.Read
Related questions
Why does a SharpV G3 fail when powered by an older SharpV PoE injector?Why do SharpV HTTP events work but HTTPS events fail?Why did SharpV anonymized plate identifiers change after a configuration change?Why are only high-confidence SharpV reads reaching my HTTP receiver?
Browse all ANPR questions
Comments
Add a comment
Share what worked for you, or ask about a detail in this answer.