-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DateTime parsing exception prevents initial EVerest start #678
Comments
I'll have a look at this |
@hikinggrass Did you found something? |
Do you have the ocpp message log? location printed in the line: |
Another thing that might have happended is that the timestamp from the session_event that we parse from the evse_manager is somehow mangled. Can you add a log around these lines in the OCPP201 module so we might see if this timestamp is empty? https://github.com/EVerest/everest-core/blob/40f62a977bd54391d80b7c2774681df40fd59a79/modules/OCPP201/OCPP201.cpp#L640 |
Might be mitigated with EVerest/everest-core#765 . Thanks for identifying the connection @lategoodbye ! |
It seems it can be closed as a dupliacte of #808 ? |
👍 |
OCPP Version
OCPP2.0.1
Describe the bug
We noticed the following issue with our Tarragon platform and EVerest core 2024.05. In case we connect an EV (CP state B) and reboot the charge controller, the following error occurs only once after reboot:
To Reproduce
Configuration:
Anything else?
No response
The text was updated successfully, but these errors were encountered: