This fork seems slow to connect the websockets.

[FOHJimJohnson]

I just converted some of my projects over to this fork. Previously I used the me-no-dev version. I'm running it on both esp8266's and esp32's. since changing over I've noticed that the Web sockets take a long time (5-10 seconds) to connect after the page loads. Once it connects it responds quick as usual. I'm wondering if there is something that I should be doing (either in the HTML or the ESP) that would speed this process up? the users of the web page are not tech savvy and the delay may turn them into "button mashers"

[mathieucarbou]

the fork is used in many projects I know of also using websocket and this behaviour is not seen, so I don't know what to advise.

[proddy]

trace it in the browser, devTools (F12 on windows), Network tab, then ctrl-R to capture and see where the delay actually is.

[mathieucarbou]

Hello @stefan-wr , I will open a new issue referencing this one.
Could you please tell us if you tested with latest versions also ?
And would you be able to test with previous ones ? There has been many foxes in the com stack lately.
I will be able to try reproduce tomorrow morning.
Thanks!

@vortigont : fyi

[mathieucarbou]

#176

[mathieucarbou]

@stefan-wr : fyi, @vortigont did a fix and I added a commit to verify the use case works.
See: #179
I will release immediately once merged.

[mathieucarbou]

Fixed in v3.4.4

[stefan-wr]

Thank you! I can confirm 3.4.4 fixed it for me. Now the new client receives the message too.