Closed JeremyMahieu closed 1 year ago
Upon further inspection it seems the EV Charger sent a stop transaction with an empty transaction id, and this is required by the protocol. So can't fault the OCPP server.
This is the logging from the EV Charger's perspective. It seems an empty transactionId was sent. So this would probably be a
2023-08-31 11:11:49,933;INFO ;m.websocket : [1002] Communication -out -> [2, "10022f4a-4263-4300-a0f1-32088c7a47cb", "StopTransaction", {"idTag": "REDACTED", "meterStop": 1146195, "timestamp": "2023-08-31T11:11:48Z", "transactionId": "", "reason": "Local"}]
2023-08-31 11:11:50,022;INFO ;m.websocket : [1023] Communication -in -> [4,"10022f4a-4263-4300-a0f1-32088c7a47cb","FormationViolation","",{}]
https://www.oasis-open.org/committees/download.php/58944/ocpp-1.6.pdf
We had this exception in the logging. Not sure what went wrong exactly but the EV charger seems to accept the charing session, then immediatly (about 450ms later) stopped the transaction and while stopping this was logged.