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

# WOHR API

> Connect WOHR API to KODE OS for parking data

> Connect WOHR API to KODE OS for parking data integration

## Overview

Use this integration to stream WOHR bike-silo data into KODE OS over MQTT. You receive bay status and assignment updates, optionally linking Avigilon ACM so permitted riders stay aligned with physical access.

| Property            | Value   |
| ------------------- | ------- |
| **System Type**     | Parking |
| **Communication**   | MQTT    |
| **Collection**      | Push    |
| **Collection Mode** | DELTA   |

## Supported Capabilities

* Collect Sensor Data
* Collect Non-Sensor Data
* MQTT Data Collection

## Prerequisites

* Access to the MQTT broker used by WOHR API
* Broker hostname, port, and credentials
* 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 **WOHR API**
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             |
| **Username**               | Yes      | text     | The username for authenticating with the external system |
| **Password**               | Yes      | password | The password for authenticating with the external system |
| **Path**                   | Yes      | text     | The API path or resource path on the external system     |
| **Plant Name**             | Yes      | text     |                                                          |
| **Avigilon Datasource ID** | No       | text     |                                                          |

## Devices and Points

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

### Parking Sensor

Canonical Type: `default`

| # | Point        | Description                       | Unit | Writable | Collection |
| - | ------------ | --------------------------------- | ---- | -------- | ---------- |
| 1 | `Bay Status` | Current status of the parking bay | --   | No       | MQTT       |
| 2 | `Bay User`   | User assigned to the parking bay  | --   | No       | MQTT       |

## What Data You Get

### Point History

Time-series readings including Bay Status, Bay User, 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:

* Monitor real-time parking space availability across facilities
* Track occupancy trends to optimize parking allocation and signage
* Generate utilization reports for parking revenue and capacity planning

## Troubleshooting

<AccordionGroup>
  <Accordion title="No data arriving from MQTT broker">
    Verify the MQTT broker hostname, port, and credentials. Check that the topic patterns match the topics being published by the WOHR devices. Ensure the MQTT client has subscribe permissions.
  </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 WOHR API.
  </Accordion>
</AccordionGroup>