> ## 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. # Unico > Connect Unico to KODE OS for electric vehicle charging data > Connect Unico to KODE OS for electric vehicle charging data integration ## Overview Use this integration to connect Unico EV charging to KODE OS. You discover chargers, collect live readings, and ingest related operational records over REST. | Property | Value | | ------------------- | ------------------------- | | **System Type** | Electric Vehicle Charging | | **Communication** | REST | | **Collection** | Pull | | **Collection Mode** | SNAPSHOT | ## Supported Capabilities * Discover Devices & Points * Collect Sensor Data * Collect Non-Sensor Data ## Prerequisites * An active account with Unico and access to their API or developer portal * API key or token from the Unico platform * KODE OS environment with access to Data Sources ## Generate API Credentials 1. Log in to the Unico 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 **Unico** 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 | | **API Key** | Yes | password | The API key for authenticating with the external system | | **Site ID** | Yes | password | The site 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 Unico 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 Unico, KODE OS maps them to the following device types and data points: ### EV Charging Station Canonical Type: `default` | # | Point | Description | Unit | Writable | Ontology Field | Collection | | -- | --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----- | -------- | -------------------- | ---------- | | 1 | `active` | Current activation status | -- | No | `value` | Polling | | 2 | `iMax` | Maximum current limit (A) | A | No | -- | Polling | | 3 | `iMin` | Minimum current threshold (A) | A | No | -- | Polling | | 4 | `state` | **Unknown** -- state cannot be determined / **Unplugged** -- vehicle is not connected / **PluggedIn** -- vehicle is connected but not charging / **Charging** -- vehicle is actively charging / **VentErr** -- ventilation error / **DiodeErr** -- diode check failure / **GfciFault** -- ground fault detected / **NoGround** -- grounding issue / **RelayStuck** -- relay is stuck / **GfciTestFail** -- GFCI self-test failed / **OverTemp** -- over-temperature condition / **EnabledUnknown** -- enabled but state unknown / **SleepTest** -- in sleep/test mode / **Preparing** -- preparing to charge / **Finishing** -- finishing charge session / **Restarting** -- restarting / **UnknownFault** -- unknown fault condition | -- | No | -- | Polling | | 5 | `enabled` | **off** -- disabled / **session** -- enabled for current session only / **always** -- always enabled | -- | No | -- | Polling | | 6 | `boost` | **True** -- boost mode is enabled / **False** -- boost mode is disabled | -- | No | -- | Polling | | 7 | `status` | Current operating status | -- | No | -- | Polling | | 8 | `healthy` | **True** -- device is healthy and operating normally / **False** -- device health issue detected | -- | No | `connection_status` | Polling | | 9 | `current` | Electrical current reading (A) | A | No | `run_current_sensor` | Polling | | 10 | `lastOn` | Timestamp of the last power-on event | -- | No | -- | Polling | | 11 | `lastOff` | Timestamp of the last power-off event | -- | No | -- | Polling | | 12 | `watts` | Power consumption (W) | watts | No | `run_power_sensor` | Polling | ## What Data You Get ### Point History Time-series readings including active, iMax, iMin, state, enabled, boost, status, healthy, and 4 more, collected at regular intervals from connected devices ### Alarms Alert and fault notifications including alarm name, priority, status, timestamps, device association, and acknowledgment state KODE OS maps Unico data to these standard fields: | KODE Field | Source Field | Notes | | --------------- | -------------------------- | ----------- | | **id** | `id` | -- | | **name** | `type` | -- | | **description** | `content` | -- | | **deviceId** | `userUuid` | -- | | **createdAt** | `Instant.parse(creation` | -- | | **updatedAt** | `Instant.parse(expiration` | -- | | **updatedAt** | `Instant.parse(expiration` | conditional | ### Polling Schedule * **Point History** -- Default polling: 5 minutes (min: 5 minutes, max: 1 hours) * **Alarm** -- Default polling: 1 hours (min: 1 hours, max: 1 days) * **ChargePointSessions** -- 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 EV charger availability, session data, and energy delivered * Track charging revenue and utilization across stations * Generate reports on EV infrastructure usage and demand patterns ## Troubleshooting 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 Unico platform. Verify the connector credentials have sufficient permissions in the Unico system to list devices. Run a test connection first to confirm connectivity. Some systems require specific API scopes or roles for device enumeration. 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 Unico API.