05-11-2025, 05:53 AM
Hey! You are actually the reason I implemented a softer WebSockets restart as a first line of defense vs the hard reset I had before. I still have subsequent hard resets programmed in if it needs it, but you were right that WebSockets alone is fine for 99% of the problems.
The loop I kept hitting:
Client[0] is connected... X time passes... Client[1] connects! Activate sendPinStatus! It would make it about half way through before one failed. Then it would just be 10 second timeouts until... Client[2] connects! sendPinStatus! Except the WebSockets/Async buffers would all be filled up now without receiving the ACK back. Then Client[3] connects!
Eventually in the mix, clients will drop off. Sometimes Client[0] disconnected within the first seconds of Client[1] connecting, other times I lost it.
Once we got some solid (I say we as in me and Gemini 2.5 Pro) debugging things in place with some client management. It seems Virtuino tries to aggressively reconnect back to the client. I am still not 100% sure if the original client[1] connection is tied to a Client[0] disconnect or if the spurious Client[1] causes the disconnect.
I will PM you the GitHub address in just a bit. I still would prefer a few eyes on it before I make it public. Especially because the library is still a bit of a mess. I have been more in "Debug mode" vs "refine it and make it a cohesive body of code mode". We basically would just shotgun debug messages any and everywhere we could. I am sure there are doubled in there too from different sessions lol.
I don't have a readme or any instructions yet, but there are A LOT of comments all through out. I will try and write you up some basic X does Y notes though!
The loop I kept hitting:
Client[0] is connected... X time passes... Client[1] connects! Activate sendPinStatus! It would make it about half way through before one failed. Then it would just be 10 second timeouts until... Client[2] connects! sendPinStatus! Except the WebSockets/Async buffers would all be filled up now without receiving the ACK back. Then Client[3] connects!
Eventually in the mix, clients will drop off. Sometimes Client[0] disconnected within the first seconds of Client[1] connecting, other times I lost it.
Once we got some solid (I say we as in me and Gemini 2.5 Pro) debugging things in place with some client management. It seems Virtuino tries to aggressively reconnect back to the client. I am still not 100% sure if the original client[1] connection is tied to a Client[0] disconnect or if the spurious Client[1] causes the disconnect.
I will PM you the GitHub address in just a bit. I still would prefer a few eyes on it before I make it public. Especially because the library is still a bit of a mess. I have been more in "Debug mode" vs "refine it and make it a cohesive body of code mode". We basically would just shotgun debug messages any and everywhere we could. I am sure there are doubled in there too from different sessions lol.
I don't have a readme or any instructions yet, but there are A LOT of comments all through out. I will try and write you up some basic X does Y notes though!