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

# Hubitat

> Connect Hubitat to KODE OS for controller data

> Connect Hubitat to KODE OS for controller data integration

## Overview

Use this integration to connect Hubitat to KODE OS. You can discover devices and points and collect sensor data from your Hubitat hub alongside your broader building context.

| Property            | Value      |
| ------------------- | ---------- |
| **System Type**     | Controller |
| **Communication**   | REST       |
| **Collection**      | Pull       |
| **Collection Mode** | SNAPSHOT   |

## Supported Capabilities

* Discover Devices & Points
* Collect Sensor Data

## Prerequisites

* An active account with Hubitat and access to their API or developer portal
* API key or token from the Hubitat platform
* KODE OS environment with access to Data Sources

## Generate API Credentials

1. Log in to the Hubitat platform or admin console
2. Navigate to the API settings, developer section, or account settings
3. Generate a new API key or token
4. Copy the key and store it securely -- you will need it when configuring the connector in KODE OS

## Configure Connector in KODE OS

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

| Field       | Required | Type     | Description                                               |
| ----------- | -------- | -------- | --------------------------------------------------------- |
| **Room**    | No       | text     | The specific room this connector is associated with       |
| **URL**     | Yes      | text     | The base URL or IP address of the external system         |
| **API Key** | Yes      | password | The API key for authenticating with the external system   |
| **Token**   | Yes      | password | The API token for authenticating with the external system |

## Discover Devices and Points

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

### Controller

Canonical Type: `default`

| #  | Point                      | Description                             | Unit            | Writable | Collection |
| -- | -------------------------- | --------------------------------------- | --------------- | -------- | ---------- |
| 1  | `Air`                      | Current air temperature reading (°C)    | °C              | No       | Polling    |
| 2  | `Glass`                    | Glass surface temperature reading (°C)  | °C              | No       | Polling    |
| 3  | `Frame`                    | Frame surface temperature reading (°C)  | °C              | No       | Polling    |
| 4  | `Panel`                    | Panel surface temperature reading (°C)  | °C              | No       | Polling    |
| 5  | `Pyranometer`              | Solar irradiance measurement            | solarIrradiance | No       | Polling    |
| 6  | `Solar Cell`               | Solar irradiance measurement            | solarIrradiance | No       | Polling    |
| 7  | `Glass Flux TC`            | Heat flux thermocouple temperature (°C) | °C              | No       | Polling    |
| 8  | `Frame Flux TC`            | Heat flux thermocouple temperature (°C) | °C              | No       | Polling    |
| 9  | `Glass Flux`               | Heat flux measurement (W/m²)            | heatFlux        | No       | Polling    |
| 10 | `Frame Flux`               | Heat flux measurement (W/m²)            | heatFlux        | No       | Polling    |
| 11 | `Wind Speed`               | Wind speed (m/s)                        | windspeed       | No       | Polling    |
| 12 | `Mean Radiant Temperature` | Current temperature reading (W/m²)      | pyrgeometer     | No       | Polling    |
| 13 | `WEMS Film`                | WEMS film temperature reading (°C)      | °C              | No       | Polling    |
| 14 | `Outside Air Temp`         | Outside air temperature (°C)            | °C              | No       | Polling    |
| 15 | `Cloud Coverage`           | Cloud coverage (%)                      | %               | No       | Polling    |
| 16 | `Dew Point`                | Dew point temperature (°C)              | °C              | No       | Polling    |
| 17 | `Outside Air Humid`        | Outside air relative humidity (%)       | %               | No       | Polling    |
| 18 | `Precipitation`            | Current precipitation type or amount    | --              | No       | Polling    |
| 19 | `Outside Air Pressure`     | Atmospheric air pressure (mbar)         | millibars       | No       | Polling    |
| 20 | `Time`                     | Wind speed measurement (m/s)            | metersPerSecond | No       | Polling    |
| 21 | `Wind Angle`               | Wind direction angle (°)                | degrees         | No       | Polling    |

## What Data You Get

### Point History

Time-series readings including Air, Glass, Frame, Panel, Pyranometer, Solar Cell, Glass Flux TC, Frame Flux TC, and 13 more, collected at regular intervals from connected devices

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

* Monitor real-time HVAC, lighting, and building automation data from a single dashboard
* Set up automated alerts when equipment deviates from normal operating parameters
* Track energy consumption and optimize building performance with historical trend data

## 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 API key or token is valid and has not been revoked or expired in the Hubitat platform.
  </Accordion>

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