In this article, you will learn how to configure your go-e Charger PRO to simultaneously utilize surplus solar power and transmit your charging sessions to a billing backend.
In joint testing with the manufacturer, we confirmed that the go-e Charger PRO can operate two systems in parallel: our energy management (for PV optimization via API) and an OCPP backend (e.g., Rentmywallbox / Neuracharge for billing).
The solution for two vehicles
This setup is ideal if your household charges vehicles with different requirements:
- Company car: Requires precise recording of charged energy for the employer.
- Private car: Should preferably be charged with your own solar power, but does not require billing.
How it works: The "two-way principle"
The go-e Charger PRO is technically designed to communicate via two channels simultaneously:
- API interface: Through this channel, clever-PV dynamically regulates the charging power and controls charging pauses based on your PV system or a dynamic tariff.
- OCPP interface: In parallel, the wallbox sends all relevant data (meter readings, start/stop) to the billing backend.
Test results in detail
Scenario 1: Charging with RFID authorization (e.g., company car)
- Process: The vehicle is plugged in and the charging session is authorized directly at the wallbox using an RFID key.
- Result: Control via clever-PV functioned with 100% reliability. Even during very long interruptions (e.g., overnight or during cloudy periods), the charging session was resumed correctly. The data in the billing backend was complete and accurate.
- Status: ✅ Optimal for billing purposes.
Scenario 2: Charging with app authorization (e.g., private car)
- Process: The vehicle is plugged in and charging is started manually via the go-e app.
- Result: PV control via clever-PV also works perfectly here. Important: Since authorization via the app bypasses the OCPP system, the billing backend often cannot process this session correctly. However, for private vehicles that do not require billing, this is not an obstacle.
- Status: ✅ Successful for purely private charging.
Our recommendation for practical operation
To ensure maximum stability and avoid error messages in the billing system, we recommend the following approach:
- Use RFID keys: Use a separate RFID key for each vehicle.
- Backend registration: Register the key for the private vehicle in the billing backend as well.
- Labeling: Mark the private key in the backend as "not relevant for billing."
The advantage: The billing system recognizes every authorization as a valid session. This prevents conflicts (such as automatic shutdown due to an unknown authorization) while the energy management system retains full control over solar power optimization in the background.
Summary of capabilities
| Function | Status | Detail |
|---|---|---|
| Optimization | ✅ Yes | Dynamic control via API |
| Billing | ✅ Yes | Via OCPP backend and RFID start |
| Simultaneous use | ✅ Yes | API and OCPP work in parallel |
| Charging stability | ✅ Yes | Reliable restart even after 12h pause |