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

# PME

> Connect PME to KODE OS for meters data

> Connect PME to KODE OS for meters data integration

## Overview

Use this integration to connect Schneider Electric Power Monitoring Expert (PME) to KODE OS over TCP/IP. You can ingest sensor data from your PME deployment so critical-facility electrical monitoring, historical intervals, and power-quality context are available in the same model as your other integrations.

| Property            | Value      |
| ------------------- | ---------- |
| **System Type**     | Meters     |
| **Communication**   | TCP/IP     |
| **Collection**      | Pull       |
| **Collection Mode** | HISTORICAL |

## Supported Capabilities

* Collect Sensor Data

## Prerequisites

* Network access to the PME controller or device
* The IP address and port of the on-site system
* Login credentials for the PME system
* 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 **PME**
3. Click **+ Add Datasource**
4. Fill in the fields below and complete the three-page setup flow

| Field                  | Required    | Type     | Description                                                      |
| ---------------------- | ----------- | -------- | ---------------------------------------------------------------- |
| **Auth Type**          | Yes         | dropdown | The authentication method to use                                 |
| **IP Address**         | Yes         | text     | The IP address of the on-site controller or device               |
| **Port**               | Yes         | text     | The port number for connecting to the system                     |
| **Username**           | Yes         | text     | The username for authenticating with the external system         |
| **Password**           | Conditional | text     | The password for authenticating with the external system         |
| **Read Path**          | Yes         | text     | The path for reading data from the external system               |
| **Meter Organization** | Yes         | text     | The organization identifier for the meter in the external system |
| **Meter Location**     | Yes         | text     | The location identifier for the meter in the external system     |

## Devices and Points

When you discover devices from PME, KODE OS maps them to the following device types and data points:

### Meter

Canonical Type: `default`

| # | Point               | Description                                                           | Unit | Writable | Collection |
| - | ------------------- | --------------------------------------------------------------------- | ---- | -------- | ---------- |
| 1 | `connection_status` | **True** -- device is connected / **False** -- device is disconnected | --   | No       | Polling    |

## What Data You Get

### Point History

Time-series readings including connection\_status, collected at regular intervals from connected devices

### Polling Schedule

* **Point History**

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="Cannot connect to controller">
    Verify the IP address and port are correct. Ensure the PME controller is powered on and connected to the network. Check that firewalls allow inbound connections on the configured port from the KODE OS server.
  </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 PME API.
  </Accordion>
</AccordionGroup>