poll() disconnects client about arduinowebsockets HOT 7 CLOSED

omg I'm stupid

Yep, that about sums 1/2 of the problems when being a dev. Cheers!

from arduinowebsockets.

Haven't use this library in a long time but:

You are polling again which is fine but if it's true you again accept the connection, that would be an issue, no?

What happens when you only poll it, does it disconnect again?

from arduinowebsockets.

After accepting the first connection, the result of poll() is false, as expected, so therefore the if block doesn't get executed. Nevertheless the client gets disconnected.

from arduinowebsockets.

Okay, you're connecting first, then you are reading the message in a blocking manner and then you additionally wait one second. I don't see you sending a heartbeat to the server so maybe the server doesn't recognize you as connected anymore? I know that I had an issue like that and I was sending a heartbeat connection every second or so.

I used lambdas to receive messages from the client without actually stopping the main loop. Here's the directory with both my declaration and implementation if that helps/

Edit: Here's my loop as well.

from arduinowebsockets.

Unfortunately I'm not sure how to send a heartbeat and I don't just want to send random garbage. Shouldn't the TCP connection be maintained by the library itself or by an underlying level? Interestingly I can also wait more than 1 second... like 5 or even 10. The client gets only disconnected as soon when I call poll() again.

from arduinowebsockets.

from arduinowebsockets.

omg I'm stupid. I oversaw a websocket.close() in my partly copy and pasted javascript code which was responsible for closing the connection. I got suspicious when I tried to use another arduino library and it still didn't work 🤣. Thanks for help!

from arduinowebsockets.