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

# Impark

> Connect Impark to KODE OS for occupancy data

> Connect Impark to KODE OS for occupancy data integration

## Overview

Use this integration to connect Impark parking systems to KODE OS over TCP/IP. You can discover parking assets and points, then pull historical occupancy or availability-style readings so garage and campus views match your other building data.

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

## Supported Capabilities

* Discover Devices & Points
* Collect Sensor Data

## Prerequisites

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

| Field             | Required | Type     | Description                                              |
| ----------------- | -------- | -------- | -------------------------------------------------------- |
| **Host**          | Yes      | text     | The host address for the connection                      |
| **Port**          | Yes      | text     | The port number for connecting to the system             |
| **Database Name** | Yes      | text     | The database name to connect to                          |
| **Schema**        | Yes      | text     | The database schema to use                               |
| **Username**      | Yes      | text     | The username for authenticating with the external system |
| **Password**      | Yes      | password | The password for authenticating with the external system |
| **Lot ID**        | Yes      | text     | The parking lot identifier                               |

## Discover Devices and Points

After configuring the connector, click **Discover** on the connector detail page. KODE OS will query the Impark 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 Impark, KODE OS maps them to the following device types:

* **Presence / Occupancy Sensor** (`presenceDetection`)
* **Traffic Counter** (`trafficCounter`)

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

* Track real-time space utilization rates across floors and zones
* Optimize HVAC and lighting schedules based on actual occupancy patterns
* Generate utilization reports to inform space planning and real estate decisions

## Troubleshooting

<AccordionGroup>
  <Accordion title="Cannot connect to controller">
    Verify the IP address and port are correct. Ensure the Impark 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="Discovery returns no devices">
    Verify the connector credentials have sufficient permissions in the Impark 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 Impark API.
  </Accordion>
</AccordionGroup>