> ## 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.

# Trellix

> Connect Trellix to KODE OS for lighting data

> Connect Trellix to KODE OS for lighting data integration

## Overview

Use this integration to connect Trellix to KODE OS. You can discover WaveLinx-connected lighting devices and points, pull snapshot supervisory data over REST, and monitor portfolio-level lighting state from Data Sources.

| Property            | Value    |
| ------------------- | -------- |
| **System Type**     | Lighting |
| **Communication**   | REST     |
| **Collection**      | Pull     |
| **Collection Mode** | SNAPSHOT |

## Supported Capabilities

* Discover Devices & Points
* Collect Sensor Data
* Collect Non-Sensor Data

## Prerequisites

* An active account with Trellix and access to their API or developer portal
* KODE OS environment with access to Data Sources

## Configure Connector in KODE OS

1. Navigate to **Data Sources** in your building
2. Click **API Catalog** and search for **Trellix**
3. Click **+ Add Datasource**
4. Complete the three-page setup flow using the credential prerequisites for this integration

<Note>
  Connector field metadata is not exposed in code for this integration. Configure the connector using your standard credentials and endpoint details shown in the prerequisites and vendor onboarding references.
</Note>

## Discover Devices and Points

After configuring the connector, click **Discover** on the connector detail page. KODE OS will query the Trellix 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 Trellix, KODE OS maps them to the following device types and data points:

### Lighting Fixture

Canonical Type: `lighting`

| # | Point               | Description                      | Unit | Writable | Ontology Field           | Collection |
| - | ------------------- | -------------------------------- | ---- | -------- | ------------------------ | ---------- |
| 1 | `selectedScene`     | Currently active lighting scene  | --   | No       | `scene_command`          | Polling    |
| 2 | `zoneDimmableLight` | Output level command (%)         | %    | No       | `run_percentage_command` | Polling    |
| 3 | `deviceStatus`      | **BAD** / **GOOD** / **UNKNOWN** | --   | No       | `fault_label`            | Polling    |

## What Data You Get

### Point History

Time-series readings including selectedScene, zoneDimmableLight, deviceStatus, collected at regular intervals from connected devices

### Alarms

Alert and fault notifications including alarm name, priority, status, timestamps, device association, and acknowledgment state

KODE OS maps Trellix data to these standard fields:

| KODE Field       | Source Field       | Notes                |
| ---------------- | ------------------ | -------------------- |
| **id**           | `id`               | --                   |
| **name**         | `errorCode`        | --                   |
| **description**  | `description`      | --                   |
| **status**       | `status.name(`     | --                   |
| **deviceId**     | `sourcePublicId`   | --                   |
| **deviceName**   | `sourceName`       | --                   |
| **location**     | `physicalLocation` | --                   |
| **createdAt**    | `createdTime`      | --                   |
| **updatedAt**    | `updatedTime`      | --                   |
| **customFields** | `(custom fields)`  | custom fields object |

### Polling Schedule

* **Point History** -- Default polling: 30 minutes (min: 30 minutes, max: 1 hours)
* **Alarm**

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:

* Monitor lighting system status, energy usage, and occupancy-driven behavior
* Coordinate lighting schedules with HVAC and building automation systems
* Track lighting energy consumption and identify optimization opportunities

## 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. Double-check all credential fields match the values from the Trellix platform.
  </Accordion>

  <Accordion title="Discovery returns no devices">
    Verify the connector credentials have sufficient permissions in the Trellix 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 Trellix API.
  </Accordion>
</AccordionGroup>