Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add support for OCPP 2.1 #448

Open
OrangeTux opened this issue Jun 30, 2023 · 2 comments · May be fixed by #457
Open

Add support for OCPP 2.1 #448

OrangeTux opened this issue Jun 30, 2023 · 2 comments · May be fixed by #457
Labels
ocpp2.1 Issues related to OCPP 2.1 support

Comments

@OrangeTux
Copy link
Collaborator

The Open Charge Alliance released a draft version of OCPP 2.1 to it's members.
And this library aims to implement support for this version.
@OrangeTux OrangeTux added the enhancement New feature or request label Jun 30, 2023
@OrangeTux
Copy link
Collaborator Author

Work is tracked in branch https://github.com/mobilityhouse/ocpp/tree/448-ocpp-21

@OrangeTux OrangeTux added ocpp2.1 Issues related to OCPP 2.1 support and removed enhancement New feature or request labels Jul 20, 2023
@OrangeTux OrangeTux linked a pull request Jul 20, 2023 that will close this issue
Open
@gitkh2891
Copy link

gitkh2891 commented Sep 29, 2024 •
edited
Loading

Hi, does the library intelligently handle chargepoints with different versions of OCPP eg. 1.6 vs 2.x when the establishing websocket connections? Or do we need to manually hardcode and check the response body of the "Sec-WebSocket-Protocol" header for the OCPP version and deploy different websocket endpoints for different OCPP versions?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
ocpp2.1 Issues related to OCPP 2.1 support
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add support for OCPP 2.1 mobilityhouse/ocpp
2 participants
@OrangeTux @gitkh2891