We noticed the following issue with our Tarragon platform and EVerest core 2024.05. After the OCPP client has successful connected to the backend the following opaque warnings are logged:
2024-06-14T14:56:43.327186+0200 tarragon manager[17477]: [INFO] ocpp:OCPP201 :: OCPP client successfully connected to server
2024-06-14T14:56:43.327186+0200 tarragon manager[17477]: [WARN] ocpp:OCPP201 int ocpp::callback_minimal(lws*, lws_callback_reasons, void*, void*, size_t) :: callback_minimal called, but data->owner is nullptr. Reason: 80
2024-06-14T14:56:43.327186+0200 tarragon manager[17477]: [WARN] ocpp:OCPP201 int ocpp::callback_minimal(lws*, lws_callback_reasons, void*, void*, size_t) :: callback_minimal called, but data->owner is nullptr. Reason: 75
2024-06-14T14:56:43.327186+0200 tarragon manager[17477]: [WARN] ocpp:OCPP201 int ocpp::callback_minimal(lws*, lws_callback_reasons, void*, void*, size_t) :: callback_minimal called, but data->owner is nullptr. Reason: 30
To Reproduce
let EVerst connect to gridfluxx.com (OCPP 2.0.1 backend)
OCPP Version
OCPP2.0.1
Describe the bug
We noticed the following issue with our Tarragon platform and EVerest core 2024.05. After the OCPP client has successful connected to the backend the following opaque warnings are logged:
To Reproduce
Configuration:
Anything else?
No response