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

# Logic One API

> Connect Logic One API to KODE OS for other data

> Connect Logic One API to KODE OS for other data integration

## Overview

Use this integration to bridge Logic One REST APIs to BACnet-oriented data in KODE OS. You discover devices, poll points, apply schedules, and sync non-sensor metadata for connected networks.

| Property            | Value     |
| ------------------- | --------- |
| **System Type**     | Other     |
| **Communication**   | REST      |
| **Collection**      | Pull      |
| **Collection Mode** | SNAPSHOT  |
| **Schedules**       | Supported |

## Supported Capabilities

* Discover Devices & Points
* Collect Sensor Data
* Collect Non-Sensor Data
* Schedules Support (from enum)

## Prerequisites

* An active account with Logic One API and access to their API or developer portal
* OAuth client credentials (Client ID and Client Secret) from the Logic One API developer portal
* KODE OS environment with access to Data Sources

## Generate API Credentials

1. Log in to the Logic One API developer portal or admin console
2. Navigate to the API or developer settings section
3. Create a new API application or client
4. Note the **Client ID** and **Client Secret** -- you will need these 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 **Logic One API**
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 |
| **Client ID** | Yes      | text     | The OAuth client ID from the vendor's developer portal   |
| **Site ID**   | Yes      | text     | The site identifier in the external system               |

## Discover Devices and Points

After configuring the connector, click **Discover** on the connector detail page. KODE OS will query the Logic One API 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       |
| -------------------- | ------------------ |
| `zone_temperature`   | zone temperature   |
| `fan_status`         | fan status         |
| `heat_anticipator`   | heat anticipator   |
| `control_setpoint_h` | control setpoint h |
| `heat_2`             | heat 2             |
| `limit_status`       | limit status       |
| `scheduled_status`   | scheduled status   |
| `control_setpoint_c` | control setpoint c |
| `output_status`      | output status      |
| `setpoint`           | setpoint           |
| `system_humidity`    | system humidity    |
| `cool_setback`       | cool setback       |
| `cool_1`             | cool 1             |
| `cool_1_2_delay`     | cool 1 2 delay     |
| `cool_anticipator`   | cool anticipator   |
| `load_status`        | load status        |
| `override_status`    | override status    |
| `fan`                | fan                |
| `heat_1`             | heat 1             |
| `heat_3`             | heat 3             |

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

### Building Alarms

Building management system alarms from the Logic One platform

### Polling Schedule

* **Point History** -- Default polling: 5 minutes (min: 5 minutes, max: 1 hours)
* **LogicOneAlarm** -- Default polling: 1 hours (min: 1 hours, max: 1 days)

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

## Schedule Management

This integration supports discovering and managing schedules in the Logic One API system. You can discover existing schedules, create new ones, and sync schedule states between KODE OS and the external system.

For more details, see the [Schedules guide](/products/integrations/capabilities/schedules).

## Use Cases

Once connected, this integration enables you to:

* Centralize Logic One API data in your building operations dashboard
* Correlate data from this system with other building systems for comprehensive analytics

## 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 Client ID and Client Secret match the values from the Logic One developer portal.
  </Accordion>

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