Camera Management

Camera management is performed at runtime via the HTTP API. Settings are saved persistently in BadgerDB.

Basic Settings

When adding or editing a camera, the critical fields include:

• id: A unique string identifier.
• url: The RTSP URL (e.g., rtsp://user:pass@192.168.1.100/stream).
• transport: Specifies tcp or udp for RTSP communication. TCP is recommended for stability.
• tokenAuth: When set to true, the HLS and WebRTC endpoints for this camera will require a one-time stream token to access.

Organization

Cameras can be logically grouped and tagged:

• Tags: A camera can have multiple tags assigned (tags array). Tags have colors and names for UI visualization.
• Folders: A camera can belong to a single folder (folder_id).

Disabling Cameras

A camera can be administratively disabled. When disabled is true, RUSEON Core will disconnect and stop pulling the stream. You can specify a disable_reason:

• Technical Issue
• Requested by User
• Unpaid Bill

The system maintains a disable_history tracking when and why a camera was disabled or enabled.

Cellular & Traffic Limits

For cameras operating over cellular networks (3G/4G/5G), you can track SIM metadata and restrict usage:

• sim_phone and sim_iccid: Metadata for asset tracking.
• traffic_limit: Set a monthly byte limit.
• traffic_used: Counter for bytes consumed.
• last_reset_month: Tracks when the counter was last zeroed.

If traffic_used exceeds traffic_limit, the camera stream can be automatically paused or flagged depending on the integration.

Related Sections

• Camera Overview
• Cameras Configuration