Batch registration of cameras

In environments with many cameras, they can be registered in batches using an Excel template.

<aside> 📘

Key information: Bulk registration processes up to 50 units at a time, and RTSP connection, license, model, and scenario settings are verified for each camera. Start by verifying representative groups and then expand step by step.

</aside>

Register many cameras separately by verification unit

Batch registration reduces input time, but it does not mean that each camera operates normally in the same environment. Even within a single file upload, the RTSP address, license allowance, template name, and model deployment status are verified separately for each camera, so only some may succeed or fail. Therefore, it is better to view batch registration as ‘a task of repeating verification using the same standard’ rather than as a ‘one-time task’.

Set the input values and operating conditions using the pre-upload preparation items below, and after registration, check not only the success, but also the video and notifications from the representative camera. When dealing with a large number of devices, fixing costs can be significantly reduced by registering a small group first to identify problem types and then expanding to the remaining devices.

• Enter camera name, RTSP address, and application scenario template
• Up to 50 registrations per time

The scenario template name must be entered with the same spacing as the name registered in the dictionary. You must also enter the camera RTSP address accurately. If the template name does not match or the RTSP address is incorrect, camera registration will fail.

Preparation before upload

1. Set camera name rules and check for duplicates.
2. Check with representative equipment whether the RTSP address and access account are actually connected on site.
3. Check whether the scenario template and category to be applied are registered in advance.
4. Check whether the number of registration targets is within the remaining number of current licenses.

Check results

• Since the registration operation is processed asynchronously, check the completion status and the reason for success/failure for each camera.
• Failed rows are checked in the following order: RTSP connection, template name, license, and model status.
• Even for successful cameras, do not start full monitoring immediately; check streaming/object boxes/notifications on representative cameras.

Recommended dictionary criteria:

• Camera naming rules