For example, in the attached image, we can see that it is already 19h31m and the candle time is still pointing to 19h15m.
The print is divided as follows, the response from the web socket and after the message is, current date - token - the timestamp - conversion from timestamp to date.
"E": 1690481985932 – 2023-07-27 18:19:45.932 UTC – kline generation time
"t": 1690481700000 – 2023-07-27 18:15:00.000 UTC – open time
"T": 1690482599999 – 2023-07-27 18:29:59.999 UTC – close time
Looks pretty consistent with 15-minute interval.
You’re processing it, as appears, on 18:32:08 UTC. So either your clock is running severely ahead by 12 minutes, or you’re processing the events with a 12-minute delay, or they get delivered with that delay.
if you look to the last line on my print, my current date is 19h32h08s and i’m using ‘t’ property from web socket, so i think should be 19h30m.
My clock is ok.
there is any away i check the delay from web socket?