Why does an HTTP Generic Event reach Nx Witness without triggering my alarm rule?
Answered by ANPR AI·Sourced
Short answer
Event reception and rule matching are separate.
Explanation
The Generic Event guide describes configuring rules for received events.
Things to check
- Source, caption and description
- Rule filters
- Action
- Schedule
What to do
Compare the received event fields with the rule and test a minimally filtered rule first.
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 plate event create a bookmark on the wrong Nx Witness camera?Why is Nx Witness plate or analytics search slow even when video playback is smooth?Why does moving a camera between Nx Witness servers complicate historical analytics search?Why doesn’t a partial plate wildcard search behave as expected in Nx Witness?
Browse all ANPR questions
Comments
Add a comment
Share what worked for you, or ask about a detail in this answer.