Energy management systems
A home battery, a heat pump and a car all want the same connection at the same moment. An energy management system decides who gets what, and it needs the charger to obey. There are exactly two ways that conversation can run, and which one a system uses changes what it can do.
REST API: the EMS asks Plugchoice
The charger stays connected to Plugchoice and nothing about its configuration changes. The energy management system calls our API to set a limit, pause a session or read what the charger is drawing, and we translate that into the OCPP calls the hardware understands. Sessions, RFID rules, tariffs and invoicing all keep running in Plugchoice, and if the EMS goes offline the charger simply carries on at its normal limit.
| System | Vendor | Status |
|---|---|---|
| Greenchoice EMS | Greenchoice | Supported |
| Slimmie | Eco-Tronic | Verified |
| Powerland | Powerland | Supported |
| Equans | Equans | Supported |
| Energiemanagers | Energiemanagers | Verified |
| Dijkman | Dijkman Zonne-Energie | Supported |
| AX Core HEMS app | a-TroniX | Supported |
| Eneco Slimme Thuisbatterij | Eneco | Vendor restricted |
| Next Source EMS | Next Source | Supported |
| Eniris | Eniris | Verified |
| evcc | evcc | Verified |
| GridSense | GridSense | Supported |
| Envitron | Envitron | Supported |
OCPP proxy: the session is forwarded
Some platforms want to speak OCPP to the charger themselves. Rather than reconfigure the hardware and lose it from your own portal, Plugchoice keeps the charger's connection and forwards a copy of the OCPP session onward. The other platform sees a charger it can command; you keep the charger in Plugchoice at the same time. One charger, one backend URL, two systems watching it.
| System | Vendor | Status |
|---|---|---|
| Driivz | Driivz | Supported |
| Fuuse | Fuuse | Supported |
| GreenFlux | GreenFlux | Verified |
| Monta | Monta | Verified |
| Maxem Energy Cloud | Maxem Energy | Verified |
| Wevo Energy Platform | Wevo Energy | Supported |
| Lynkwell Energy Platform | Lynkwell | Supported |
| EDGE Smart Charging | Noodoe | Supported |
| EV.Energy | EV.energy | Supported |
The same mechanism is what lets you move between platforms without an installer visit. How the OCPP proxy works
Picking a route
The API route is the lighter one. Nothing on the charger changes, the integration is a handful of calls, and the failure mode is harmless: no answer from the EMS means no limit, and charging continues. Use it when the EMS only needs to steer power.
The proxy route is the one to pick when the other platform needs the full protocol: its own transaction records, its own firmware updates, its own charging profiles. It costs a little more latency and you now have two systems that can both send a command, so agree up front which one owns the limit.
Related
About this page
All names, logos and trademarks on this page are the property of their respective owners. This page is published independently by Plugchoice and is not affiliated with, endorsed by or sponsored by any of the companies listed. Every detail was taken from publicly available sources and from our own testing, and was accurate to the best of our knowledge on the date shown. Specifications and features change often, so please confirm the current details with the manufacturer before relying on them.