> ## Documentation Index
> Fetch the complete documentation index at: https://docs.spirii.com/llms.txt
> Use this file to discover all available pages before exploring further.

# EVSEs

> Where charging happens, and the object roaming and billing are built on.

An EVSE is the part of a charge box that supplies electricity to one EV at a time.

<Frame>
  <img src="https://mintcdn.com/spirii-7457b714/Hq2YBNx3n8oQoC1s/images/components/evses.png?fit=max&auto=format&n=Hq2YBNx3n8oQoC1s&q=85&s=896df7a9af680fa46480daf5ef28784d" alt="The EVSE detail view in Spirii Connect, showing each connector's standard, power type, and current status" width="1407" height="519" data-path="images/components/evses.png" />
</Frame>

## Overview

EVSE stands for Electric Vehicle Supply Equipment: the component of a charge box that supplies a connected vehicle's battery. It's both the hardware and the software that manage the charging process — the part of the charger that communicates with the vehicle.

A connector is the physical plug a driver attaches to the vehicle. An EVSE usually has a single connector, though it can have more. Spirii models both the EVSE and the connector as levels in the [charger hierarchy](#relationships).

## Context

An EVSE matters on both sides of a charge — it's where charging physically happens, and the object roaming is built on.

### CPO context

For a CPO, the EVSE and its connectors are the charging hardware you model in Connect: their standard, power, and status. The EVSE ID is derived from the [charge box](/components/charging/charge-boxes) it belongs to. The attributes below describe that model.

### eMSP context

For an eMSP, the EVSE is the primary object reached over [roaming](/capabilities/roaming/roaming-connection). Across OCPI, the EVSE is what signals operability to other networks, and what each CDR attaches to for settlement. Complete, correctly formatted connector data is what makes a charger usable over roaming, and the charging status maps to OCPI as shown under States.

## Key attributes

### EVSE

| Attribute | Description                                         | Example            |
| --------- | --------------------------------------------------- | ------------------ |
| EVSE ID   | The unique, eMI3-compliant identifier               | `DE*SPI*E00012345` |
| Status    | The current charging status (see [States](#states)) | `charging`         |

<Note>
  The EVSE ID is derived automatically from the [charge box's](/components/charging/charge-boxes) CBID — you don't assign it yourself.
</Note>

### Connector

| Attribute    | Description                                                                      | Example                            |
| ------------ | -------------------------------------------------------------------------------- | ---------------------------------- |
| Connector ID | The connector number, appended to the EVSE ID                                    | `1` (`DE*SPI*E00012345*1`)         |
| Standard     | The plug type                                                                    | `CCS 2`                            |
| Power type   | AC or DC                                                                         | `DC`                               |
| Max power    | The theoretical maximum power, in kW                                             | `400`                              |
| Max voltage  | The theoretical maximum voltage, in V                                            | `1000`                             |
| Max amperage | The current in A, auto-calculated from power and voltage                         | `400`                              |
| Error        | Error codes and information reported by the charger                              | `UnderVoltage`, `NO_VOLTAGE_L2_L3` |
| Availability | Whether the connector is temporarily disabled, via the `SetAvailability` command | `Unavailable`                      |

## States

An EVSE's charging status follows OCPP 1.6 and maps to OCPI 2.1.1 for roaming:

| Status (OCPP)   | OCPI mapping  | Meaning                                                                 |
| --------------- | ------------- | ----------------------------------------------------------------------- |
| `Available`     | `Available`   | No vehicle is plugged in; the EVSE is ready to start a session          |
| `Preparing`     | `Charging`    | A session is being prepared, e.g. after a valid token is presented      |
| `Charging`      | `Charging`    | The vehicle is actively charging                                        |
| `Finishing`     | `Charging`    | The flow of electricity has stopped and the transaction is concluding   |
| `SuspendedEV`   | `Blocked`     | The vehicle stopped the transaction but is still plugged in             |
| `SuspendedEVSE` | `Blocked`     | The charger stopped the transaction but the vehicle is still plugged in |
| `Faulted`       | `OutOfOrder`  | The charger registered an error                                         |
| `Unavailable`   | `Inoperative` | The EVSE is temporarily out of service                                  |

Spirii doesn't use OCPP's `Reserved` status.

## Relationships

An EVSE and its connectors sit at the bottom of the charger hierarchy. The EVSE inherits its charge box's connectivity; box-level commands such as `reboot` are issued on the charge box and affect the EVSEs it contains.

```mermaid theme={null}
flowchart TD
    L("Location") --> CB1("Charge box\nAC")
    L --> CB2("Charge box\nDC")
    CB1 --> E1("EVSE")
    CB2 --> E2("EVSE")
    CB2 --> E3("EVSE")
    E1 --> C1("Connector\nType 2")
    E2 --> C2("Connector\nCCS")
    E2 --> C3("Connector\nCHAdeMO")
    E3 --> C4("Connector\nCCS")
```

## Used in

<CardGroup cols={3}>
  <Card title="Roaming connection" icon="globe" href="/capabilities/roaming/roaming-connection">
    Publish your EVSEs to other networks over OCPI.
  </Card>

  <Card title="Charge boxes" icon="box" href="/components/charging/charge-boxes">
    The unit an EVSE belongs to, and where its ID comes from.
  </Card>

  <Card title="EVSEs API" href="https://docs.spirii.com/api-reference/evses-v2/fetches-a-single-evse">
    Retrieve EVSE and connector data programmatically.
  </Card>
</CardGroup>