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

# Point Grab

> Connect Point Grab to KODE OS for occupancy, indoor environmental quality data

> Connect Point Grab to KODE OS for occupancy, indoor environmental quality data integration

## Overview

Use this integration to connect PointGrab space analytics to KODE OS. You can discover zones and sensors, poll utilization and IEQ-related points on a schedule, and register webhooks so occupancy updates arrive when conditions change.

| Property            | Value                                   |
| ------------------- | --------------------------------------- |
| **System Type**     | Occupancy, Indoor Environmental Quality |
| **Communication**   | REST + Webhook                          |
| **Collection**      | Pull                                    |
| **Collection Mode** | SNAPSHOT                                |

## Supported Capabilities

* Discover Devices & Points
* Collect Sensor Data
* Collect Non-Sensor Data
* Receive Webhook Data

## Prerequisites

* An active account with Point Grab and access to their API or developer portal
* OAuth client credentials (Client ID and Client Secret) from the Point Grab developer portal
* KODE OS environment with access to Data Sources

## Generate API Credentials

1. Log in to the Point Grab developer portal or admin console
2. Navigate to the API or developer settings section
3. Create a new API application or client
4. Note the **Client ID** and **Client Secret** -- you will need these when configuring the connector in KODE OS

## Configure Webhook

This integration uses webhooks for real-time data delivery. After creating the connector in KODE OS:

1. Copy the webhook URL provided on the connector detail page
2. In the Point Grab platform, navigate to the webhook or notification settings
3. Add a new webhook endpoint using the KODE OS URL
4. Configure the authentication header as specified on the connector detail page
5. Save and enable the webhook

## Configure Connector in KODE OS

1. Navigate to **Data Sources** in your building
2. Click **API Catalog** and search for **Point Grab**
3. Click **+ Add Datasource**
4. Fill in the fields below and complete the three-page setup flow

| Field               | Required | Type     | Description                                                |
| ------------------- | -------- | -------- | ---------------------------------------------------------- |
| **URL**             | Yes      | text     | The base URL or IP address of the external system          |
| **Client ID**       | Yes      | text     | The OAuth client ID from the vendor's developer portal     |
| **Client Secret**   | Yes      | password | The OAuth client secret from the vendor's developer portal |
| **Site ID**         | Yes      | text     | The site identifier in the external system                 |
| **API Building ID** | Yes      | text     | The building or source identifier in the external system   |

## Discover Devices and Points

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

### Air Quality Sensor

Canonical Type: `airQuality`

| # | Point              | Description                        | Unit     | Writable | Ontology Field                    | Collection |
| - | ------------------ | ---------------------------------- | -------- | -------- | --------------------------------- | ---------- |
| 1 | `pressure`         | Static air pressure (pascals)      | pascals  | No       | `zone_air_static_pressure_sensor` | Webhook    |
| 2 | `humidity`         | Relative humidity level (humidity) | humidity | No       | `zone_air_humidity_sensor`        | Webhook    |
| 3 | `temperature`      | Current temperature reading (°C)   | °C       | No       | `zone_air_temperature_sensor`     | Webhook    |
| 4 | `connectionStatus` | Device connectivity status         | --       | No       | `connection_status`               | Webhook    |

### Traffic Counter

Canonical Type: `trafficCounter`

| # | Point       | Description                         | Unit  | Writable | Ontology Field            | Collection |
| - | ----------- | ----------------------------------- | ----- | -------- | ------------------------- | ---------- |
| 1 | `inNumber`  | Cumulative count of people entering | count | No       | `people_entering_counter` | Webhook    |
| 2 | `outNumber` | Cumulative count of people exiting  | count | No       | `people_leaving_counter`  | Webhook    |

### Presence / Occupancy Sensor

Canonical Type: `presenceDetection`

| # | Point   | Description                                 | Unit  | Writable | Ontology Field    | Collection |
| - | ------- | ------------------------------------------- | ----- | -------- | ----------------- | ---------- |
| 1 | `count` | Number of people/objects currently detected | count | No       | `occupancy_count` | Webhook    |

## What Data You Get

### Point History

Time-series readings including pressure, humidity, temperature, connectionStatus, inNumber, outNumber, count, collected at regular intervals from connected devices

### Polling Schedule

* **Point History** -- Default polling: 1 minutes (min: 1 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:

* 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
* Monitor air quality metrics (CO2, VOC, humidity, temperature) across all occupied spaces

## 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. Ensure the Client ID and Client Secret match the values from the Point Grab developer portal.
  </Accordion>

  <Accordion title="Webhook data not arriving">
    Verify the webhook URL is correctly registered in the Point Grab platform. Check that the authentication header matches the value from the KODE OS connector detail page. Ensure the Point Grab system can reach the KODE OS webhook endpoint over the network.
  </Accordion>

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