> ## Documentation Index
> Fetch the complete documentation index at: https://documentation.kodelabs.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Avigilon ACC (Avigilon Control Center)

> Connect Avigilon ACC (Avigilon Control Center) to KODE OS for camera, video data

> Connect Avigilon ACC (Avigilon Control Center) to KODE OS for camera, video data integration

## Overview

Use this integration to connect Avigilon Control Center (ACC) to KODE OS. You can discover cameras and devices, receive webhook events, stream video, and collect camera and video telemetry through REST.

| Property            | Value          |
| ------------------- | -------------- |
| **System Type**     | Camera, Video  |
| **Communication**   | REST + Webhook |
| **Collection**      | Pull           |
| **Collection Mode** | SNAPSHOT       |

## Supported Capabilities

* Discover Devices & Points
* Collect Sensor Data
* Receive Webhook Data
* Video Streaming

## Prerequisites

* An active account with Avigilon ACC (Avigilon Control Center) and access to their API or developer portal
* Username and password credentials for the Avigilon ACC (Avigilon Control Center) system
* KODE OS environment with access to Data Sources

## Configure Webhook

This integration uses webhooks for real-time data delivery. After creating the connector in KODE OS:

1. Copy the webhook URL provided on the connector detail page
2. In the Avigilon ACC (Avigilon Control Center) platform, navigate to the webhook or notification settings
3. Add a new webhook endpoint using the KODE OS URL
4. Configure the authentication header as specified on the connector detail page
5. Save and enable the webhook

## Configure Connector in KODE OS

1. Navigate to **Data Sources** in your building
2. Click **API Catalog** and search for **Avigilon ACC (Avigilon Control Center)**
3. Click **+ Add Datasource**
4. Fill in the fields below and complete the three-page setup flow

| Field           | Required | Type     | Description                                              |
| --------------- | -------- | -------- | -------------------------------------------------------- |
| **URL**         | Yes      | text     | The base URL or IP address of the external system        |
| **Username**    | Yes      | text     | The username for authenticating with the external system |
| **Password**    | Yes      | password | The password for authenticating with the external system |
| **User Nonce**  | Yes      | password | The user nonce value for authentication                  |
| **User Key**    | Yes      | password | The user-specific key from the vendor platform           |
| **Client Name** | Yes      | password | The client application name registered with the vendor   |

## Discover Devices and Points

After configuring the connector, click **Discover** on the connector detail page. KODE OS will query the Avigilon ACC (Avigilon Control Center) system and return a list of available devices and their data points.

Review the discovered items and select the devices you want to register in KODE OS.

For more details on the discovery process, see the [Discovery guide](/products/integrations/capabilities/discovery).

## Devices and Points

When you discover devices from Avigilon ACC (Avigilon Control Center), KODE OS maps them to the following device types and data points:

### Camera

Canonical Type: `camera`

| # | Point       | Description                                                                  | Unit | Writable | Ontology Field      | Collection |
| - | ----------- | ---------------------------------------------------------------------------- | ---- | -------- | ------------------- | ---------- |
| 1 | `Active`    | **True** -- camera is active and streaming / **False** -- camera is inactive | --   | No       | `run_status`        | Webhook    |
| 2 | `Connected` | Device connectivity status                                                   | --   | No       | `connection_status` | Webhook    |

## What Data You Get

### Point History

Time-series readings including Active, Connected, collected at regular intervals from connected devices

### Event Logs

System and security event records with timestamps, event types, and associated devices

KODE OS maps Avigilon ACC (Avigilon Control Center) data to these standard fields:

| KODE Field       | Source Field              | Notes                |
| ---------------- | ------------------------- | -------------------- |
| **id**           | `id`                      | --                   |
| **category**     | `EventCategory.CAMERA`    | --                   |
| **customFields** | `(custom fields)`         | custom fields object |
| **name**         | `event.activity`          | --                   |
| **description**  | `event.analyticEventName` | --                   |
| **location**     | `event.location`          | --                   |
| **deviceId**     | `event.cameraId`          | --                   |
| **status**       | `event.type`              | --                   |
| **createdAt**    | `event.timestamp`         | transformed          |
| **createdAt**    | `time`                    | transformed          |
| **name**         | `event.activity`          | conditional          |
| **createdAt**    | `time`                    | conditional          |

### Polling Schedule

* **Point History** -- Default polling: 30 seconds (min: 30 seconds, max: 1 hours)
* **EventLog**

For more details on collection modes, see the [Data Collection guide](/products/integrations/capabilities/data-collection).

## Use Cases

Once connected, this integration enables you to:

* Integrate video surveillance feeds into the building operations dashboard
* Correlate camera events with access control and alarm data for incident review
* Monitor high-traffic areas and verify occupancy data against video feeds
* Integrate video surveillance feeds into the building operations dashboard

## Troubleshooting

<AccordionGroup>
  <Accordion title="Authentication or connection error">
    Verify that the credentials are correct and have not expired. Check that the URL is reachable from the KODE OS environment. Verify the username and password are correct and the account has not been locked in the Avigilon ACC (Avigilon Control Center) system.
  </Accordion>

  <Accordion title="Webhook data not arriving">
    Verify the webhook URL is correctly registered in the Avigilon ACC (Avigilon Control Center) platform. Check that the authentication header matches the value from the KODE OS connector detail page. Ensure the Avigilon ACC (Avigilon Control Center) system can reach the KODE OS webhook endpoint over the network.
  </Accordion>

  <Accordion title="Discovery returns no devices">
    Verify the connector credentials have sufficient permissions in the Avigilon ACC (Avigilon Control Center) system to list devices. Run a test connection first to confirm connectivity. Some systems require specific API scopes or roles for device enumeration.
  </Accordion>

  <Accordion title="Data collection stops or gaps appear">
    Check the connector status on the Data Sources page. If the status shows an error, review the error logs on the connector detail page. Common causes include expired credentials, network changes, or rate limiting by the Avigilon ACC (Avigilon Control Center) API.
  </Accordion>
</AccordionGroup>