ESP8266 SocketIO connects and disconnects repeatedly

[GowthamGottimukkala]

A function called connectedtoserver was written and it was called in the CONNECT event which does not seem to fire. But my nodejs server is receiving this connection several times and all of them are disconnecting again showing ping timeout at server end.

I am using 2.3.0.

This is the debug output.
https://www.codepile.net/pile/V0p1DRPp

This is the code I used.
https://www.codepile.net/pile/enkojknz

Any help is appreciated

[Links2004]

Look like your server is using socketIO V3.
for support you need the lib version 2.3.1

[GowthamGottimukkala]

No, my server's socket.io version is 2.3.0

Addition to the above question:
Sometimes it is connecting to the server and staying connected. Then I checked the debug output, it showed that the connection is upgraded to WebSocket from polling. Maybe it is causing the connection to stay? I didn't force connections to happen only for WebSocket in my node server i.e I didn't use any io.set("transports", ["websocket"]);

[Links2004]

upgraded to WebSocket from polling is fine.
the only other hint in the log you posted is that the ESP detects a TCP socket close.
so it looks like your server closes the connection.
this can have many reasons, does your server report anything?

one think to look out for is that the loop is called often.
your log has many lines like lfs_file_close: fd=0x3fff2dfc not sure from what they come and how much time they need.

may add timestamps to you serial terminal to see how often your loop() runs.
if the loop is called to less the connection can not be handled correct, which may lead to the server closing the connecion.

[GowthamGottimukkala]

Thanks for the reply
Are you saying that I need to add some delay in my loop()? If so how will that be helpful?

[Links2004]

do not at a delay, I asked you to check the time Interval in which loop is called.
may it is called to less (you other code takes to much time).
but to see this we need some debug output.

a very simple way is to print millis and substack the values.
a better and way which includes avg's is to count the calles in 1sec and print that value.
basically the same calculation you do to get fps (frames per second) but here we want loop executions per second ;)