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

# Verdigris

> Connect Verdigris to KODE OS for meters, weather data

> Connect Verdigris to KODE OS for meters, weather data integration

## Overview

Use this integration to connect Verdigris electrical metering to KODE OS. You can discover building, panel, breaker, and circuit hierarchies, then pull historical energy metrics (and weather-related context where modeled) for load analysis and efficiency reporting.

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

## Supported Capabilities

* Discover Devices & Points
* Collect Sensor Data

## Prerequisites

* An active account with Verdigris 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 **Verdigris**
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 Verdigris 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    |
| ----------------- | --------------- |
| `temperature`     | temperature     |
| `humidity`        | humidity        |
| `dewPoint`        | dewPoint        |
| `energy`          | energy          |
| `apparent-energy` | apparent-energy |
| `power`           | power           |
| `power-factor`    | power-factor    |
| `thd`             | thd             |
| `current`         | current         |
| `voltage`         | voltage         |

## 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: 15 minutes (min: 5 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:

* 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
* Incorporate external weather conditions into building optimization models

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

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