I have a similar situation (I'm from Belgium, so posting this in English as my German is not sufficient...)
I have a Keba P30 x-series wallbox which is controlled with OpenWB (raspberry pi)
I also own a company car whereby the charging sessions are registered through OCPP to the back-end software of E-flux (
www.e-flux.nl)
I also have a PV installation and want to maximise solar charging.
So my Keba is controlled in 2 ways:
- There is the OCPP connection which controls the Keba. It is however not really controlling it, it is rather monitoring it and passing the data onto the E-flux software. I also registers the RFID card. I can charge with my own card, but the wallbox is also public available for external RFID cards. I can control the cost which is charged in the e-flux software
- At the same time, my raspberry pi/openWB setup controls the Keba and only charges in case of excess PV (in case of PV mode).
It is correct that there is a sort of conflict between both
- In case there is not enough sun, the Keba blinks blue which means the wallbox is not ready for charging. When you swipe with an RFID card, the session is registered, but it decouples again after 1 minute since charging does not start. This also means that - even though my Keba is available publicly - people cannot always charge at all times. The OCPP connection does not overrule the PV loading
- When there is enough sun, it works perfect. The sessions are registered through OCPP, and the OpenWB software adjusts the amperage to maximise own PV consumption
I should not that - even my Keba is publicly available - no one uses this actually. The wallbox is attached to my private home, no-one comes here to charge. The reason why it is available public is because this gives a tax advantage in Belgium
So combining OCPP with PV charging via OpenWB works perfectly for the Keba P30.