Why did changing a Milesight camera to HTTP posting break plate search on its NVR?
Answered by ANPR AI·Sourced
Short answer
The recorder expects the camera’s TCP posting mode.
Explanation
The support article explains that the traditional HTTP, TCP and RTSP posting choices are mutually exclusive.
Things to check
- Camera Post Type
- Recorder connection
- Plate receipt
What to do
Restore TCP for the Milesight NVR and verify a new plate in recorder search.
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
Can a Milesight camera send plates to an NVR and also notify an external HTTP service?Why do Milesight MQTT plate notifications fail while HTTP notifications work?Why does a plate added to a Milesight NVR allowlist not appear in the camera’s list?Why does my Milesight NVR omit a plate when the same vehicle returns shortly afterwards?
Browse all ANPR questions
Comments
Add a comment
Share what worked for you, or ask about a detail in this answer.