Matthias Akstaller

Perfect! The auto-merge from upstream into this branch shows ~2k insertions and ~1k deletions ... I better open a rebased PR

Both scenarios are supported over OCPP: plug in first and authorize first. The transaction eventually starts when both conditions are true, i.e. the cable is plugged and the user is...

Hi @retrocoder-78, sorry, I must somehow missed this issue. The current provisioning scheme is to define factory defaults and then dynamically configuring the connection details via OpenEVSE dashboard or the...

Yes, it is possible. Sorry for the confusing explanation in my previous reply. In SteVe, you can use the ChangeConfiguration operation to update the backend URL and chargeBoxId of the...

Hi @JungHeum-Park, Thanks for reporting this! There is a fix on the way already for that OCTT test case. If you can patch the MicroOcpp sources in your build, comment...

Hi @martamartz, good finding! Let's keep this issue open until I've found a solution to this. As a workaround, you could set the time manually right after `mocpp_initialize()`. Then the...

Checked it again, MicroOcpp will only initiate StatusNotification messages if the clock has been set (except for reporting errors which isn't the case here). Tested it again and couldn't reproduce...

While revisiting the StatusNotification messages I did find a scenario where MicroOcpp would send a message with timestamp 1970-01-01. Error codes which occur before BootNotification were potentially sent without a...

The MCP9808 sensor seems to work and the other device on the I2C bus (PN532) is not disturbed.  Only this line seems to be missed by the dependabot: https://github.com/OpenEVSE/openevse_esp32_firmware/blob/51f1604878a14746053a65a36fcf935d79952a70/platformio.ini#L450

Just updated the missed version number. Hope it won't interfere the workflow.