Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 37 Next »

In our platform, we use several objects in the application tree.

Tree items

We currently have the following objects:

  • folder - Folder used to group and structure other nodes. Example:

  • user - Guest user account with defined access rights.

  • camera - AXIS IP camera. The main device.

  • box - Fast local storage and surveillance station in one.

  • audio device - AXIS audio device, used to transmit audio messages to and from a camera.

  • cashdesk - Item to store data from POS system.

  • dashboard - Display several cameras or charts on one screen.

  • device input - Device electric input - IO (doors are open/closed, cash drawer open/closed, …)

  • removed node - A shell containing a removed node. Sometimes needed to preserve access to some of the nodes data.

  • video channel - Video channel of a multichannel or panoramic camera. It works in a similar way as camera. You can fetch live view and recordings.

  • panel - Display statistics in charts.

  • location - Similar as folder with some extra functionality. It represents one site e.g. store.

\uD83D\uDCD8 Tree items

The objects user, camera, electrical input, dashboard, folder and more are nodes in the tree structure. You can find all available types in the generated documentation in API Explorer.


This structure allows:

  1. Get aggregated metrics from multiple objects.

  2. Manage user permissions for a group of objects.

  3. Organizing objects into groups for better clarity in the user interface.

The folder object allows for endless immersion. Some objects, such as the electrical input, are always immersed under the camera object.

Examples with objects:

List of all elements and type

  • No labels