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

# Enertiv

> Connect Enertiv to KODE OS for meters data

> Connect Enertiv to KODE OS for meters data integration

## Overview

Use this integration to connect Enertiv to KODE OS. You can discover meters, pull scheduled point history (for example power usage), ingest non-sensor records, and collect meter-bill data so operations, submetering, and finance views share the same source of truth.

| Property            | Value      |
| ------------------- | ---------- |
| **System Type**     | Meters     |
| **Communication**   | REST       |
| **Collection**      | Pull       |
| **Collection Mode** | HISTORICAL |

## Supported Capabilities

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

## Prerequisites

* An active account with Enertiv 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 **Enertiv**
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 Enertiv 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 Enertiv, KODE OS maps them to the following device types and data points:

### Meter

Canonical Type: `default`

| # | Point         | Description                    | Unit | Writable | Collection |
| - | ------------- | ------------------------------ | ---- | -------- | ---------- |
| 1 | `power_usage` | Current power consumption (kW) | kW   | No       | Polling    |

## What Data You Get

### Point History

Time-series readings including power\_usage, collected at regular intervals from connected devices

### Meter Bills

Utility meter billing data including consumption, rates, and billing period details

### Polling Schedule

* **Point History** -- Default polling: 1 days (min: 1 days, max: 1 days)
* **MeterBill** -- Default polling: 1 days (min: 1 days, max: 1 days)

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:

* Aggregate utility consumption data (electricity, gas, water, steam) in a unified dashboard
* Detect abnormal consumption patterns and potential waste or leaks
* Generate utility cost reports and benchmark buildings in your portfolio

## 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 Enertiv platform.
  </Accordion>

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