lorenzodonini

``` INFO[2022-08-21T16:42:25+05:30] ocpp message (2596996162): GenericError - request timed out, no response received from server ``` if I understand this right, the charge point sent a request to the CSMS,...

The issue described in #141 is completely separate and not linked to this at all. #133 might indeed be related though. I'll look into this further and hopefully find a...

@utsavanand2 The error you're seeing occurs when a charging station connects to the server, while the server already holds an open connection with the same charging station. The error occurs...

@utsavanand2 Thanks for collecting some debug logs. Feel free to upload them to any cloud and either send me a link via email or paste it here (maybe obfuscate sensitive...

Quick question regarding the timeout: do you expect a use-case, in which this would be useful? The `TimeoutConfig` should already set timeouts, so having a double timeout seems like overkill....

> I think the `TimeoutConfig` just leads to the client disconnecting, leading to the scenario I mentioned where a request effectively might never time out. Not exactly. If the client...

I stand corrected: the timeout policy on the dispatcher currently doesn't use the value from the `TimeoutConfig`. It uses a default 30 seconds timeout value, with the option of [setting...

> once it's paused, both a request waiting in the dispatcher queue and AFAICT an already dispatched request will never time out. Correct. The idea was to give some support...

Hello, interesting question and not completely unexpected. If you take a look at all the messages in the callbacks, you'll realize that most of the messages and/or attributes are different...

Hey Had, you make a good point there. I originally thought of keeping the included batteries to a minimum and enforce the specifications, which clearly say that: - ISO 8601...