OCPP 2.0.1 support

[munterkalmsteiner]

Are there any plans already to support OCPP 2.0.1? I'm planning to buy a DEFA Power which implements v2.0.1.

[lbbrhzn]

No plans yet... perhaps we should. OCPP 2.0 is not backwards compatible with OCPP 1.6

[tobsys]

+1, that would be awesome.

[JoaoPedroBelo]

any news on this?

[magnushacker]

I have a DEFA power and can confirm that it does not work. Also, you need to contact their support to get the charger configured, there's no way to do it by yourself.

The Python OCPP library claims to support 2.0.1 so why doesn't this integration?

[piomark]

any update/plans about ocpp 2.0.1 support?

I see more and more newly released chargers drop support for previous protocols and implement only 2.0.1

[bobcov]

Does OCPP exist because these devices don't speak MQTT? Otherwise, could MQTT handle what this is doing with chargers, etc?

[piomark]

Well, those are completely different things.
MQTT is communication protocol that defines pub/sub communication mechanism. It does not define what kind of information is transferred.

OCPP is an application protocol (using REST/HTTP as communication protocol), and as such it defines how a charger talks with a charging station management system to control it (it defines all messages structure and data that is transferred in between).

[bobcov]

But there are charging stations which speak MQTT and seem to do just fine, no?

…

On 07/19/2024 5:17 PM CEST piomark ***@***.***> wrote: Well, those are completely different things. MQTT is communication protocol that defines pub/sub communication mechanism. It does not define what kind of information is transferred. OCPP is an application protocol (using REST/HTTP as communication protocol), and as such it defines how a charger talks with a charging station management system to control it (it defines all messages structure and data that is transferred in between). — Reply to this email directly, view it on GitHub #983 (reply in thread), or unsubscribe https://github.com/notifications/unsubscribe-auth/AJAII4YTRNBUOOJNMAQX7GLZNEUY5AVCNFSM6AAAAAA7YGRDJSVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTAMBZGY4TAOA. You are receiving this because you commented.Message ID: ***@***.***>

[magnushacker]

What kind of effort would be involved in adding support for ocpp 2.0.1? I understand some parts need to be reimplemented, but I cannot judge how much work would be needed. Perhaps it could be worthwhile reaching out the community for assistance in case the maintainers do not have time?

[piomark]

I created a fork of this project to see what can be done. I don't have much time right now therefore the progress is really slow.
The only thing that I managed to do is to replace all references/data structures from 1.6 to 2.0.1.
The charger is connecting to the server (so there is a small success) but no logic is implemented.

Regarding the effort, it's a complete re-work of OCPP layer. 2.0.1 is completely different than 1.6 when it comes to messages and communication.

When (and if) I have time I will continue the work on the project. In my free time I'm digging through 2.0.1 spec.

[quokkapatrik]

What are your plan for letting version 1.6 co-exist with version 2.0.1?

[piomark]

For the moment it's proof of concept ;) I was not intending to preserve 1.6, I am working on a fork so nothing will change here.
If I succeed then ofc it can be done, for the moment I have no clue when I will find sufficient time to do it.
Anyway my goal is not to reproduce the functionality as in this repo. I am only interested in get/set charging current/power and get some basic statistics (at least for now).

[magnushacker]

Are there even chargers that talk both 1.6 and 2.0.1? Maybe there won't be much of an issue if users had to choose between two separate HACS repos depending on which charger they have.

…

On Tue, 24 Sept 2024 at 09:29, piomark ***@***.***> wrote: For the moment it's proof of concept ;) I was not intending to preserve 1.6, I am working on a fork so nothing will change here. If I succeed then ofc it can be done, for the moment I have no clue when I will find sufficient time to do it. Anyway my goal is not to reproduce the functionality as in this repo. I am only interested in get/set charging current/power and get some basic statistics (at least for now). — Reply to this email directly, view it on GitHub <#983 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA73OUWDYHZDHNTCG2X2F43ZYEIHPAVCNFSM6AAAAAA7YGRDJSVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTANZTGUZDSMQ> . You are receiving this because you commented.Message ID: ***@***.***>