OCPP server and client doesn't include all atributes (GARO EVCS example)

[tomazbu]

We are trying to connect GARO charger using our device as a proxy with ChargeTimeEU OCPP library where our device then sends forward messages to GARO backend.

OCPP server and client need to have access to read and write data of the following attributes on Web Socket connection:

Did anyone implement this to the library? @TVolden I saw you made the last changes. Do you have any idea regarding that?

[TVolden]

Hi @tomazbu,

I'm not sure which changes you are referring to? My engagement these days mostly concerns code review and merging pull requests. I haven't implemented a new feature for a long time.

That said, it looks like the websocket connection was successfully established. I'm too rusty to tell if the syntax is correct. I'm also not familiar with the CARO charger. Do you get any error messages?

[tomazbu]

Hello @TVolden

I am referring to you because I saw you made some reviews and pull requests, and I wondered if you have had similar issues anywhere else already.

It is GARO: https://www.garo.co.uk/EVCharging

That charger can communicate with their Mobile APP (backend cloud) they are using OCPP with additional parameters for authentification where this OCPP library has been implemented only on the side of the Server but not on the Client Side.

We have a DLM device which is used as a proxy in between the charger and GARO back-end. But when charger connects to our device, communication is lost with the GARO back-end becuase we are not sending forward the auth part descibed on my initial message.

Do you know who would be the best person to add this to this library?

Thank you!

[TVolden]

Hi @tomazbu,

I don't know if anyone knows how to address this very specific problem. You are welcome to give it a go. I can recommend the gitter channel if you're looking for implementation guidance.

Just to clarify, this is a server and client implementation of the OCA specified OCPP 1.6 soap, JSON, and 2.0.