c-jimenez

Hi, I'm not sure you have to send an idTag in this case since no user has presented physically nor remotely an idTag to stop the transaction. The StopReason::PowerLoss should...

Hi, In your case, you must call the `ChargePoint::stopTransaction()` method with an empty string for the `id_tag `parameter and `Reason::PowerLoss` for the `reason` parameter.

Hi, It is not yet compatible, I am currently preparing the development branch to support OCPP2.0 => For now, I have moved OCPP1.6 specific code in dedicated namespaces/directories. I am...

Sorry for the late response. The following branch contains all the necessary base classes to start working with OCPP 2.0.1 => https://github.com/c-jimenez/open-ocpp/tree/dev/ocpp20 A first ChargePoint20 class has been written to...

Hi @jorisoffouga, I won't have much time in the next few months to work on OCPP2.0.1. What I have planned in the next weeks: - Generate a 1.6.0 release based...

@jorisoffouga : The develop branch is now the reference for OCPP2.X developments. Thanks for your collaboration.

Hi, If you want to test the local authorization for your specific charge point implementation: - Connect your charge point to your CSMS - Configure the local authorization (local list,...

Hi, The stack should automatically do the following actions when the connection has been lost with the CSMS: - Store the last notified connector statuses - Store all transaction related...

Hi, The requirement in the whitepaper says: ``` 5. The Central System sends the certificate it has acquired from the CA to the Charge Point, using the CertificateSigned.req message. 6....

Ok it's fine for me. Sorry for the delay.