Cameras and edge nodes
You manage cameras in the dashboard's Cameras & Edge Nodes tab. Everyone can see the tab, but only admins can add or change cameras. Changes are picked up by the edge nodes within about 10 seconds, with no restart.
Before you start
- The edge node that will process the camera must be able to reach the camera's stream over the network. The site node must reach it too, because it opens the stream for Test Connection, snapshots, the zone editor and the Dashboard tab's camera view. See Cameras and network.
- Have the camera's stream URL ready, for example
rtsp://192.168.1.100:554/stream. Check your camera's manual for the exact path. - At least one edge node must be running. Running edge nodes register themselves and show up under Edge Nodes.
- Every camera belongs to an organization. Create one first if your site has none.
Add a camera
- Open Cameras & Edge Nodes and click Add Camera.
- Under Add New Camera, pick the organization the camera belongs to.
- Enter a Camera Name. Names must be unique within an organization. Rules and the Copilot refer to cameras by name, so give every camera at the site its own name, one people will recognise, such as
loading-bayorcam-07. - Enter the Source URI. Use an
rtsp://orrtsps://URL, or anhttp://orhttps://video stream. - Pick a Detection Profile. The profile decides which detections count for this camera. See Detection profiles.
- Pick the Assigned Edge Node that will process the camera.
- Click Test Connection. The site node grabs one frame from the stream and shows it as a snapshot. If it can't open the stream or read a frame, you see an error instead.
- Click Save Camera.
The assigned edge node starts processing the camera on its next check, within about 10 seconds.
The first frame of an RTSP stream can take a while to arrive. If Test Connection is slow, wait before you retry.
A camera that is Unassigned is saved but not processed. No edge node picks it up until you assign one. Argus does not move cameras between edge nodes on its own. If an edge node goes offline, reassign its cameras by hand.
Find cameras with Scan network
If your cameras support ONVIF, an edge node can look for them on its own network, so you don't have to type the stream URL. You need the admin role, and your administrator must first put the edge node on the camera network. Until then, the scan says that discovery is not available on that node. See Camera discovery (ONVIF).
- Open Cameras & Edge Nodes, click Add Camera, and in Add New Camera click Scan network.
- Under Edge node, pick the node that sits on the cameras' network, then click Scan. The scan takes about 5 seconds.
- The list shows each camera that answered, with its name, manufacturer, model and IP address. Cameras that allow it also show their stream URL. Click Select next to the camera you want.
- If the camera needs a login, enter the Camera username and Camera password under Camera login, then click Get stream URL.
- If the camera offers more than one stream, pick one under Stream.
- Click Use this camera. The camera's name and Source URI are filled in, with the login written into the URL.
- Check or change the fields, then go on from step 5 of Add a camera: pick a profile and an edge node, test the connection and save.
What to know about the scan:
- The scan only asks which cameras are there. It never sends a camera login, because anything on the network can answer it. The login you enter goes only to the camera you selected.
- The login is not logged or stored unless you save the camera. It is then part of the camera URL, like any camera credentials.
- The scan only finds cameras on the edge node's own network segment. Cameras on another subnet, or without ONVIF, are added by URL as before. Video is still read over RTSP.
- If nothing answers, the dialog says No ONVIF cameras answered. Check that ONVIF is turned on in the camera and that it is on the same subnet as the edge node.
- Every scan and stream lookup is recorded in the audit log.
Camera credentials
If your camera needs a user name and password, you write them into the source URL, for example rtsp://user:password@192.168.1.100:554/stream.
Only admins see the full URL, in the camera's edit form. Operators, the Copilot, error messages and the audit log never show the user name and password. The URL is stored in the site database as you enter it, so use a camera account that can only view the stream.
Edge nodes
An edge node is a server that runs the edge-node container. Each edge node registers itself under its node name and sends a heartbeat every 10 seconds. A node shows as online when its last heartbeat is less than 30 seconds old.
To spread load, run edge nodes on several servers at the site and assign each camera to one of them. Each camera runs on exactly one edge node. See Install for how to add an edge node.
The Edge Nodes card shows the state of each node:
| State | What it means |
|---|---|
| Online | The node checks in and delivers detections. |
| Redis unreachable (amber) | The node runs and checks in, but can't reach the site's event streams. Its cameras' detections are dropped, and the card shows how many. It recovers by itself when Redis is back. See If the edge node can't reach Redis. |
| Offline | No check-in for 30 seconds. |
The System Health box in the sidebar also turns amber and names the node.
The card also lists every node with the stream address the Live wall uses for it. Nodes register this address themselves, by default /edge/<node name>. An admin can click Edit to set a different address, for example when browsers reach a node through another proxy path. Click Use node's own to go back to the address the node registers.
Change a camera
Each camera has a card in the tab:
- Profile. Pick another detection profile, or + Create New Profile....
- Node. Move the camera to another edge node, or set it to Unassigned.
- Enabled. Turn processing on or off. A disabled camera keeps its history.
- Edit Zones. Draw the areas that zone rules and profiles use. See Zones.
- Delete Camera. Remove the camera.
Rules can filter by camera name. If you rename a camera through the API, update any rules that use the old name.
Delete a camera
You can delete a camera only while it has no detections or events. Once a camera has history, deleting it fails so its events stay queryable. Disable the camera instead. Deleting a camera also deletes its zones.
Organizations
Organizations group cameras, for example by building, tenant or area. Every camera belongs to one organization.
- Open Organizations to see each organization with its cameras. Click View Cameras to work with one organization's cameras, including adding a camera to it.
- Admins can click Create Organization, and edit or delete an organization from its card. An organization that still has cameras can't be deleted. Move or delete its cameras first.
- In Cameras & Edge Nodes, pick an organization at the top to show only its cameras.
Organizations help you find cameras. They don't change who can see what: every user can see every organization.
Detection classes
The edge node uses a YOLO detector. The default model detects the 80 everyday object classes of the COCO dataset, such as person, car, truck, bus, motorcycle, bicycle, backpack, handbag and suitcase. The full list for your model is shown when you create a detection profile, and from the detection profiles API.
Camera view
The Dashboard tab shows a picture from your cameras, and the Live Wall shows every enabled camera at once. See The dashboard and Live wall.