Matthias Akstaller

Update: #682 resolves the LITTLEFS issue.

A further outstanding issue on Windows is the upload command in the platformio.ini (env:openevse_wifi_v1): ``` upload_command = curl -F firmware=@$SOURCE http://$UPLOAD_PORT/update --progress-bar | cat ``` This only works on Linux....

Good tip, the extra debug port would be very handy and I will change my dev setup then. Apart from that line in the platformio.ini I did not face any...

The function `endTransaction()` terminates the currently active transaction immediately. It is declared in MicroOcpp.h: https://github.com/matth-x/MicroOcpp/blob/d486288d5a151d271bf4e78a534eda8231e99381/src/MicroOcpp.h#L152 After the transaction process has been ended, the library is ready to begin a new...

In case the OCPP lib forgets about the current transaction after the ESP has reset, then most likely the filesystem access doesn't work. Are there suspicious log messages about this?

Before the ESP restarts, at the time when the power loss occurs, it's complicated. The typical approach is more to terminate any active transaction when the ESP boots up again...

The library will fetch the energy register from the EnergyMeterInput once it creates the StopTransaction request. In the initialization phase of the charger you need to set the callback function...

Hi Madison, I'm not sure I understand how you want to use MicroOcpp in this case. Can you explain your goals a little more? Generally, MicroOcpp is an OCPP client....

Okay, I see. I think that starting with the RequestQueue is a good idea. But first things first: The Operation classes (e.g. Authorize, BootNotification, ...) included in MicroOcpp don't contain...

Hi @flyrobot, Actually OpenEVSE does not stop the transaction when the controller is reset. Charging will be resumed with the same transaction once the power supply is up again. "DeAuthorized"...