Feature Request: OCPP Forwarding / Proxy

[mtobehn]

As an increasing number of charging stations support connectivity exclusively via OCPP, users who need to submit the electricity charged at home for reimbursement by their employer currently lack the possibility to integrate a suitable billing backend.

At present, I am using a wallbox that allows EVCC to communicate via TCP Modbus while the billing backend is connected through OCPP. However, since I will be replacing this unit with an Autel Maxicharger Single AC in the coming days, I will unfortunately no longer be able to use EVCC until further notice.

Several other manufacturers, such as Energielenker and Cfos, address this use case by implementing OCPP forwarding or an OCPP gateway. This enables users to directly configure the connection parameters of their billing backend and ensures seamless data passthrough.

cfos

Energielenker

It would be highly appreciated if a similar integration could be considered for future releases, as this would significantly improve compatibility with modern charging infrastructure and support a broader range of professional billing workflows.

[andig]

The real question here is how this is supposed to work. Most specifically: what interaction is expected? How should evcc handle upstream requests and responses? Which messages need to be handled at all?

[premultiply]

And should that be a general feature for all loadpoints (like SMA SEMP) or should it only proxy OCPP-connected chargers or should there be a kind of opt-in for each device?

[mtobehn]

in the first step it should be enough only to adapt this feature for OCPP-connected devices since others could still use the legacy TCP Modbus connection to EVCC and OCPP for the billing backend.

In case of Energielenker and cfos the whole OCPP trafic is proxied