OCPP (Open Charge Point Protocol) enables integration with public charging station networks via OCPP servers (cloud or self-hosted). Authenticate with a valid contract RFID Card, monitor the Charging Points availability and sessions, as well as providing information for billing purposes.
Supports OCPP versions 1.6 and 2.0.1 via secure and unsecure web socket connections (ws:// & wss://).
Miniserver users can be configured with an OCPP Tag ID, which is used for all transactions initiated by them via App or NFC Code Touch.
Local Miniserver authentication is used as fallback when authentication via OCPP Tag ID fails or OCPP Tag ID is not provided.
For the best experience we recommend using the Loxone Wallbox Tree with Energy Meter Tree and NFC Code Touch Tree.
More Information about OCPP can be found here.
Current Miniserver generation required, not supported by Miniserver Gen.1 variants.
Table of Contents
- Initial Setup
- Programming Examples
- Functionality
- Supported OCPP Features
- History
- Wallbox
- Inputs, Outputs, Properties
Initial Setup↑
Add OCPP Server Connector Plugin as Network Device:
Specify settings for OCPP Server Connector plugin and Charging Point. Add a separate Charging Point for each Wallbox:
Programming Examples↑
Wallbox standalone
Connect the Charging Points API Connector to the NFC Code Touch and Wallbox function blocks. When connecting the NFC Code Touch with the Charging Point API Connector, the authentication method will be changed to "OCPP" and Don to 0,7s automatically.
Wallbox with Wallbox Manager
Connect the NFC Code Touch Blocks outputs to either "Ec" or "Ecp" of the Wallbox function block, depending on if Eco or Prio Mode – or both should be usable.
Functionality↑
To start an OCPP charging session, first connect your vehicle, then authenticate. OCPP charging sessions are stopped when the car is disconnected.
Authentication and Charging Processes with OCPP and Local Charging:
Roaming Users (Charging Card) initiate charging sessions using the NFC Code Touch, it reads their charging cards OCPP-Tag-ID and passes it to the OCPP server, which will either accept or reject it. The NFC Code Touch will reflect the decision using its LEDs (red or green).
Miniserver Users can initiate a charging session either via Loxone App or using NFC Code Touch. If an OCPP Tag ID has been configured on the user object, it will be passed to the OCPP server. If no OCPP Tag ID is configured, or it is rejected by the OCPP server, the Miniserver will decide based on the users permissions and may still allow charging. In this case, the Charging Point will be reported as unavailable and no billing information is passed to the OCPP server for that charging session.
Difference Between OCPP and Local Charging:
In both situations the wallbox blocks history will track the charging session. If the OCPP server accepted the charging session, billing information will not be part of the history and the last charging cost will be 0.
Energy Management & OCPP
The charging power set by the energy management on the Miniserver always has priority. If the charging process is deactivated due to local decisions such as "Load Management", "Energy Management", or "Spot Price Management", the charging process will not start or will be stopped. Charging profiles provided by the OCPP server are not used.
Outages (Network or Power)
During network outages, transaction messages are queued and sent once the connection is reestablished. After a reboot (e.g. due to power outages), active transactions are restarted, thus connected cars keep charging. On the OCPP server this will be reflected in two charging sessions, one before and one after the outage.
Supported OCPP Features↑
| Feature | Description | Supported? |
|---|---|---|
| Reset | OCPP 2.0.1 by default hardware reset OCPP 1.6 hard/soft reset |
No |
| Charge point certificate | - | No |
| Offline Behaviour | Messages are queued | Yes |
| Set/Get Variables | OCPP Server can make changes to Charging Point | Yes |
| Remote Start/Stop transaction | - | Not yet supported |
| Authorization | - | Yes |
| Local Authorization | Authorized tokens are cached locally | No |
| Online Transactions | Charging Point reports to OCPP server | Yes |
History↑
The Authentication NFC Code Touch and the Wallbox block show who has been granted access by which authorization (Miniserver or OCPP). The OCPP plugin name is used as the authority's name.
Wallbox↑
Prices are hidden by default in the Wallbox because billing is handled by the OCPP server.
When authorized locally without OCPP servers' approval, the prices configured on the block or provided from a Wallbox Manager are shown in the app.
Standalone (no Wallbox Manager):
Actuators↑
| Summary | Unit |
|---|---|
| API Connector | Text |
Diagnostic Inputs↑
| Summary | Description | Unit | Value Range |
|---|---|---|---|
| Onlinestatus | Indicates whether the device can be reached by the Miniserver. Diagnostics for Air devices Diagnostics for Tree devices Diagnostics for Extensions |
Digital | 0/1 |
Properties↑
| Summary | Description | Default Value |
|---|---|---|
| Server Address | Websocket Address of the OCPP-Server (unsecure or secure).\n e.g.\nws://[address]:[port]/steve/websocket/CentralSystemService\nwss://[address]/ocpp/cp/socket/16\nThis address can be found in your external service portal | - |
| Protocol | Protocol used to communicate with OCPP Server. Applies for all chargepoints. | - |
| Monitor service | If checked, you will be notified by the System Status or Cloud Mailer if this service is no longer available or offline. | - |