Hey guys, I been looking recently on car chargers since I might need to develop a binding for one. Since I am still an user of traditional car I have no way to test binding locally beside one remote deployment based on easee I will soon have access. I already managed to setup simulator and mock controller to implement some basic logic related to OCPP conversations on both ends. It let me understand a little bit better protocol and what it allows to do. Now, I start poking around making a basic binding to collect state and some meter values reported by chargers.
It will take me a bit to come with first version hence I would like to collect some additional feedback from you. From my small research it seems that most popular is OCPP-J v1.6. It is being said that VW chargers are supporting OCPP v2, without much of information of what transport it is (JSON or SOAP based).
If you are interested in such binding, could you please post what charger you could test and what OCPP interface it needs?
First release - just allows to connect charging station to openHAB instance using OCPP-J 1.6.
Basically I would be interested in starting/stopping the charging and changing the charging current. I have also solar panels and I have a separate electricity meter so I know the PV power, electricity consumption of our house and how much electricity is put back to the grid. If I could control the ABB charger I would like to optimise the charging current so that all the excess solar electricity could be used for charging up my car. This feature woul dbe really great.
The on, off per connector is rather straight, it will come. Regulation of charging power is also within the range (I aim to achieve it for same reasons as you), however it might require some device specific adjustments. OCPP defines a “smart charging profile” but it seems that not all chargers are compatible with it. There are some device specific extensions and in case of ie. easee, there are constraints of how many updates you can do to charging profiles:
Profiles are stored in non-volatile memory on the chargers, and frequent writes to this memory will cause wear in charger hardware. If on average profiles are updated more than 10 times a day for a longer period of time, the warranty for the charge point is voided.
@jlikonen Can you try to locate ocpp related documentation for your charger?
Hey Jari, I got stuck in stabilization of PV part of the installation and will probably move to billing reporting of electricity meters and not chargers data this week.
I hope to visit a site where I can test ocpp in July, then I will have chance to focus on development of addon.
Łukasz, I wonder whether there has been any progress with this project. Progress on ABB side has also been rather slow; they introduced communication with LAN/WIFI but managed to break this with their latest firmware.
Hello @jlikonen, in the end I haven’t had access to OCPP stations I wished to test stuff with, thus my work on binding got stuck. I was able to test it only with simulator which is… as good as simulator itself.
I gonna publish version which I pictured in April. It works with OCPP-J v 1.6 and allows charging station to connect, but not more.
You could then test if charger is properly connected. I think I will be able to slowly and safely iterate over it until we get “read only” access to charger data.
@jlikonen Which version of OH you are currently using?
Many thanks for the update. I understand that development of new things takes time. I’m running OH3.3 at the moment. I would be interested in testing your binding. Basically I would like to start/stop the charging and set the charging current. I know OCPP has lot more functionalities but I’m not that interested in them.