Integration Options
Pleevi supports multiple ways to integrate with your charging infrastructure. Depending on your setup, you can choose one or combine several of these methods.
Overview
| Integration Method | Capabilities | Data Flow | Schedule Delivery | Best For |
|---|---|---|---|---|
| MQTT | Ingress, Egress | You publish measurements & transactions to our MQTT broker | Subscribe to MQTT topics | Local controllers, EMS platforms, real-time bidirectional communication |
| API | Configuration, Driver I/O | Manage sites, topologies, and optimization settings via REST API | Driver-facing endpoints for session input and schedules | Site setup and management, driver-facing applications |
| OCPP Broker | Driver Identification | Automatic, we read the badge from OCPP start messages | / | Linking charging sessions to drivers, no code changes needed |
| Eniris Smart Grid One | Ingress, Egress | Automatic, Eniris reports device metrics to Pleevi | Sent directly to the Eniris controller | Sites with Eniris hardware, fully managed integration |
| MINT | Ingress | Automatic, MINT reports energy measurements to Pleevi | / | Sites with MINT smart energy meters |
| OCPI | Ingress, Egress | Via OCPI protocol from your CPMS | Smart Charging commands via OCPI | CPMSs with OCPI support |
| WithTheGrid | Coming soon | Coming soon | Coming soon | Sites using WithTheGrid teleport controller |
| Custom | Depends on your setup | Depends on your setup | Depends on your setup | Have a different system? Contact us, we're always open to discuss new integrations |
- Ingress: Sending measurement data and transactions to Pleevi.
- Egress: Receiving optimized charging schedules from Pleevi.
- Configuration: Creating and managing sites, topologies, and optimization settings.
- Driver I/O: Driver-facing endpoints for session input (departure time, energy needs) and retrieving personal schedules.
- Driver Identification: Identifying drivers via badge ID (RFID token) from charging sessions.
The API does not support data ingress or egress — use MQTT or Eniris for sending measurements/transactions and receiving schedules. Use the API or Portal to manage site configuration.
Combining Integration Methods
These methods are not mutually exclusive. Common combinations include:
- MQTT + OCPP Broker: Use MQTT for data ingress and schedule delivery, while using the OCPP broker to identify drivers via the badge ID in their OCPP start messages. See OCPP Broker for details.
- API + MQTT: Use MQTT for real-time data ingress and schedule egress, while using the API for site configuration, activation, and management.
- Eniris + OCPP Broker: Use the Eniris controller for local energy management and charging, while using the OCPP broker for driver identification.
Getting Started
Choose the integration method that fits your infrastructure:
- MQTT Integration, Connect to our MQTT broker to send data and receive schedules in real time.
- API Integration, Configure sites, manage topologies, and access driver-facing endpoints.
- OCPP Broker, Point your charging stations at our WebSocket endpoint to link charging sessions to drivers.
- Eniris Smart Grid One, If you have Eniris hardware on-site, we integrate directly with it.
- MINT, Integrate MINT smart energy meters for site-level measurements.
- OCPI, Connect your CPMS via the OCPI protocol.
- WithTheGrid, Teleport integration (coming soon).
Not sure which integration method to use? If you have an Eniris Smart Grid One, that requires the least integration effort. If you need more control or want to send additional site data, combine it with the API or MQTT integration. Add the OCPP Broker to link charging sessions to drivers.