Introduction

❗️
Disclaimer: OCPP is currently in beta release with firmware version >= 328. We strongly recommend using this beta release exclusively in test environments. Your feedback is greatly appreciated and will help us improve the final offering of OCPP. Other features of firmware version 328 can be used in production safely.

OCPP Implementations in Easee

Easee offers two distinct implementations of OCPP 1.6J, each with its own operational model:

Cloud-emulated OCPP
Operation: The charger communicates with the Easee Cloud, which then interfaces with a 1.6J compatible back-office. Key feature: Proxied communication through Easee Cloud, allowing a higher level of support from Easee, more functionality.
OCPP
Operation: This is the native version where the charger communicates directly with a compatible 1.6J server / back-office. Key feature: No intermediary Easee Cloud proxy is required, meaning a lower level of support from Easee.

Comparison
Both implementations have their own set of advantages and disadvantages some of which are listed below.

Feature	Cloud-Emulated OCPP	OCPP
Latency	Slightly higher (due to proxy)	Lower
Easee Cloud Dependency	Yes	No
Implementation Complexity	Lower	Higher

Note: The benefits and drawbacks of each implementation may evolve as new features are added to OCPP.

Future developments

As OCPP continues to evolve, we anticipate further enhancements to both implementations. Developers should stay updated with our documentation for the latest features and best practices.

How to provide feedback to us

If you have any questions or would like to provide us with some feedback on our OCPP implementation please contact us via Easee Connect or email via [email protected]

Note: Since the charger primarily connects to a server other than Easee Cloud, support is limited due to the reduced diagnostics and telemetry available. Therefore, Easee Connect is the primary support channel for our initial native OCPP offering.