chargepi / chargepi-go

ChargePi is a charge point framework/project for Linux devices with OCPP support, API and a management UI

⚡ ChargePi-go

ChargePi is an open-source, Linux based ⚡Charging Point🔌 "framework". It makes your EV charging station smart by abstracting and unifying the hardware components into a customizable, modular Charge Point with OCPP 1.6 and 2.0.1 support, an intuitive UI for easy management and an API for custom integrations. It is highly customizable, simple to make and supports both off-the-shelf and commercial hardware.

Concepts

A charge point is a device, consisting of multiple EVSEs, that is capable of delivering energy to an electric vehicle. Each EVSE has a connector, an EV Charge Controller and a Power Meter. Optionally, the charge point can have an RFID/NFC reader as an authentication mechanism, a display as a user interface, a status indicator and a communication module for connecting to the backend.

🔌 Charge point software specification

OCPP version	Core functionalities	Reservations	LocalAuthList	SmartCharging	FirmwareUpdate	Security Extension	ISO 15118 (Plug and Charge)
1.6 JSON/WS	✔️	✔️	✔️	Planned	✔️ (partial)	Planned	Planned
2.0.1 JSON/WS	Planned	Planned	Planned	Planned	Planned	Certificate management included	Included

📦 Features

• OCPP 1.6 with planned 2.0.1 support - ChargePi supports OCPP 1.6, the most common protocol for EV charging stations. OCPP 2.0.1 support is planned.
• Easily configurable - ChargePi is easy to configure and customize. It comes with default settings that require minimal configuration.
• Easy replication - ChargePi is easy to replicate. It can be deployed on a Raspberry Pi or any other Linux-based device. Configurations can be easily exported from an existing device to other devices.
• Mix and match hardware - ChargePi supports a variety of hardware components. You can mix and match the hardware components to create a charging station that suits your needs.
• Customizable UI - ChargePi comes with a customizable UI that allows you to easily manage your charging station.
• API for custom integrations - ChargePi comes with an API that allows you to integrate it with other systems.

🔌 Hardware support

All contributions for hardware support are welcome. If you want to add support for a new hardware component, please check out the hardware support guide. The more hardware is supported, the more customizable the ChargePi is.

RFID/NFC readers

Reader	Is supported
PN532	✔

Display

Display	Is supported
HD44780	✔

Power Meters

Power meter	Is supported
CS5460A	✔
ETI	Planned

EVCC

EVCC	Is supported
Relay	✔
Phoenix Contact EVSEs	Planned

LED indicators

Indicator	Is supported
WS2812b	✔
WS2811	✔

⚡ Quickstart

1. Choose the desired functionality and hardware.

2. Wire your hardware according to the provided schematics (if the hardware is supported - otherwise, seek professional guidance or contribute to the project!).

   [!CAUTION] The hardware part of the project requires fairly good electrical knowledge. Make at your own risk or seek professional guidance. The project is not responsible for any damage caused by the hardware and will not take responsibility for any software misconfiguration or misbehavior.

3. Configure the settings files according to the hardware and desired functionality:

   • client configuration
   • OCPP configuration

4. Run the client. ChargePi-go can be deployed/run in multiple ways:

   • standalone (host machine)
   • Docker 🐳 and docker-compose

Details on how to run the client on are described in the client startup guide.

🛠️ Configuration and settings

To configure the ChargePi, check out the configuration guide. Client comes with default settings which require minimal configuration.

Contributing

Contributions are welcome! Please check out the contributing guide for more information.

License

ChargePi-go is licensed under the MIT License.

chargepi-go's Issues

ConnectorData DataTransfer payload

TLDR; Create a custom DataTransfer payload that will notify the backend of connector (and/or charge point)details, such as: charge point max current, connector type, max current per connector, etc.

This is useful for backends to automatically detect the number and type of connectors the charge point has available.

HTTP Basic Auth OCPP-J login

Is it possible to use HTTP BasicAuth to authenticate the ChargePoint?

It is supported by the library used to handle websocket connections, see https://github.com/lorenzodonini/ocpp-go/blob/master/ws/websocket.go#L707 but I don't know how it's exposed in the ocpp lib.

WebUI for V2

Need help with the design and implementation of the Web UI, which would be statically served within the application. The WebUI is currently written with Tailwind, Svelte and DaisyUi.

The list of WebUI tabs/elements:

• Login
• Logs
• Card reader settings
  • tag management
• Display settings
• OCPP settings
  • Connection
  • Variables
  • Charge point details
• EVSE view (list of EVSEs)
  • Status
  • Settings for EVCC, Power Meter, LED indicator

The rough representation of the layout should be available here.

API for V2

Need help with creating a gRPC/HTTP API for Charge Point configuration and user access management with operation monitoring.

Features:

• EVSE management - adding, removing and updating evses (EVCC and PowerMeter types, connections, etc),
  • monitoring - displaying current consumption/session details on the EVSE/connector
• User and access management - manage users that have access to the application.
• Connectivity setting management - configure the OCPP version, backend url, operation details
  • OCPP configuration variables management
  • OCPP information management (serials, etc)
• Peripherals management
  • Display settings management
  • RFID reader management
  • LED indicator settings management
• Log monitoring and exporting