You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
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.
The text was updated successfully, but these errors were encountered: