flyrobot

This is the further message after DeAuthorized : Received: [2,"1000004","StopTransaction",{"meterStop":54,"timestamp":"2024-01-15T13:23:28.057Z","transactionId":347,"reason":"DeAuthorized"}] Sending: [3,"1000004",{}] [chargeBoxId=xxxxx, sessionId=6dc2a837-5faa-8495-3417-8e5507c9bf00] Received: [2,"1000005","StatusNotification",{"connectorId":1,"errorCode":"NoError","status":"Finishing","timestamp":"2024-01-15T13:23:28.666Z"}] And do you need OpenEVSE to stop transactions after power outages? Im using openevse...

[chargeBoxId=xxxxx, sessionId=d620d3d6-f21c-0cb3-d60d-236758494982] Received: [2,"1000035","StatusNotification",{"connectorId":1,"errorCode":"NoError","status":"Preparing","timestamp":"2024-01-15T15:59:20.563Z"}] [chargeBoxId=xxxxx, sessionId=d620d3d6-f21c-0cb3-d60d-236758494982] Sending: [3,"1000035",{}] [chargeBoxId=xxxxx, sessionId=d620d3d6-f21c-0cb3-d60d-236758494982] Sending: [2,"f8407a95-bf6d-463f-8226-2070458d3720","RemoteStartTransaction",{"connectorId":1,"idTag":"2DA7CD6C"}] [chargeBoxId=xxxxx, sessionId=d620d3d6-f21c-0cb3-d60d-236758494982] Received: [3,"f8407a95-bf6d-463f-8226-2070458d3720",{"status":"Accepted"}] [chargeBoxId=xxxxx, sessionId=d620d3d6-f21c-0cb3-d60d-236758494982] Received: [2,"1000036","StartTransaction",{"connectorId":1,"idTag":"2DA7CD6C","meterStart":54,"timestamp":"2024-01-15T15:59:35.770Z"}] [chargeBoxId=xxxxx, sessionId=d620d3d6-f21c-0cb3-d60d-236758494982] Sending: [3,"1000036",{"transactionId":352,"idTagInfo":{"status":"Accepted","expiryDate":"2024-01-31T00:00:00.000Z"}}] [chargeBoxId=xxxxx, sessionId=d620d3d6-f21c-0cb3-d60d-236758494982] Received: [2,"1000037","StatusNotification",{"connectorId":1,"errorCode":"NoError","status":"SuspendedEVSE","timestamp":"2024-01-15T15:59:36.517Z"}] [chargeBoxId=xxxxx, sessionId=d620d3d6-f21c-0cb3-d60d-236758494982]...

> Can you post the preceding Authorize and StartTransaction messages? > > Okay, perhaps the blackout behavior is not tested at all. To my understanding the OCPP specs leave this...

Yes i can compile the source. give the result here

on Last report above im using openevse_wifi_v1 using stock firmware, now I compile using nodeMCU-32S (why LCD become dark ???) with ocpp.cpp edited, the moment charging transaction is in progress...

i tried to turn off power while in charging status (in transaction) The user with idTag '2DA7CD6C' is ALREADY in another transaction(s). [chargeBoxId=xxxxx, sessionId=6c7b491d-f1ea-8775-4c4d-c153931b403b] Sending: [3,"1000001",{"transactionId":377,"idTagInfo":{"status":"ConcurrentTx","expiryDate":"2024-01-17T06:15:25.817Z"}}] [chargeBoxId=xxxxx, sessionId=6c7b491d-f1ea-8775-4c4d-c153931b403b] Received: [2,"1000002","StatusNotification",{"connectorId":0,"errorCode":"NoError","status":"Available","timestamp":"2024-01-17T05:15:13.535Z"}]...

> Before the StopTransaction with reason DeAuthorized I would expect an Authorize response or StartTransaction response with idTagInfo, status Invalid (or anything but Accepted). The logs from above look okay....

Yes this is a mandatory to comply in backend. they also have some charger and i see they do not have this issue.

 do you mean become like this ?

i try this config above, still doesn't work. may be im wrong add a new declareConfiguration, please advice.