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

# Novant

> Connect Novant to KODE OS for controller data

> Connect Novant to KODE OS for controller data integration

## Overview

Use this integration to connect Novant controllers to KODE OS. You can discover devices and points, collect current sensor readings, and pull historical data for trending and analysis.

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

## Supported Capabilities

* Discover Devices & Points
* Collect Sensor Data
* Collect Historical Data

## Prerequisites

* An active account with Novant and access to their API or developer portal
* API key or token from the Novant platform
* KODE OS environment with access to Data Sources

## Generate API Credentials

1. Log in to the Novant platform or admin console
2. Navigate to the API settings, developer section, or account settings
3. Generate a new API key or token
4. Copy the key and store it securely -- you will need it when configuring the connector in KODE OS

## Configure Connector in KODE OS

1. Navigate to **Data Sources** in your building
2. Click **API Catalog** and search for **Novant**
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       |
| **API Key**      | Yes      | password | The API key for authenticating with the external system |
| **Collect Type** | Yes      | dropdown | The data collection method to use                       |

## Discover Devices and Points

After configuring the connector, click **Discover** on the connector detail page. KODE OS will query the Novant 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

| Point  | Display Name |
| ------ | ------------ |
| `enum` | enum         |
| `bool` | bool         |
| `num`  | num          |

## What Data You Get

### Point History

Time-series sensor readings such as temperature, humidity, CO2, occupancy counts, energy consumption, light levels, and other measurable values from physical sensors

### Polling Schedule

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

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 real-time HVAC, lighting, and building automation data from a single dashboard
* Set up automated alerts when equipment deviates from normal operating parameters
* Track energy consumption and optimize building performance with historical trend data

## 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. Ensure the API key or token is valid and has not been revoked or expired in the Novant platform.
  </Accordion>

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