Claudio Prezzi

We already have a universall set of commands: the lw.comm-server API. The frontend doesn't have to know details about firmware protocoll or specific commands, the server cares about that. By...

That's just my opinion ;)

@DarklyLabs Don't worry, the problem you had with ESP connect should be solved with 4.0.40. I just swapped the check order to smoothie first for the moment (as your users...

I don't realy see how this one big object could simplify the whole thing. If we pack everything in a single websocket event, the client has to parse the object...

I'm not sure yet, if websocket realy is the problem, or just the additional delay the ESP is generating, but you will find out. At least a lower level network...

But could we make sure that unchanged status is not sent again and again (for performance reason)? And what about multiple client connections? I've planned to send the actual job's...

I would still integrate a mini Webpage for mobile / tablet control in the server only version, if possible. Would be cool if you could organize some ESP32s for me....

@openhardwarecoza You should not need a specific socket.io library to talk to the node socket.io port, it should work with other websocket implementations too. At least I was able to...

@jorgerobles I like that approach. The client tells the server at beginning what info/features he likes to subscribe.

But first, the server should tell the client what info/features he has to offer (+server version, protocoll version...) ;)