Hi. Did you finally found a solution?
I have the same issue and can't see it solved. My websocket-zwave-client is initiating a connection to a websocket server but closing down immediately again. My code devices looks like this right now (including a ping and settimeout) but no effect....
Any ideas?
Meanwhile I found, that I get a step further, if I remove the whole "protocol" definition. (Of course this is not my solution, but at least I get a properly connect and ping etc.)
Unfortunately yes, because the websocket server is ignoring requests without protocol definition.
(In this case it's a Knaus camper that allows dimming lights etc. via websocket connection. Actually a cool thing putting zwave into a camper and do all the nice stuff).
Right now I am kind of stuck here, because without this, the project is in a dead end...
Can you send us in PM or by mail a sniplet of code to test it (if possible with access to that server) and a demo with correctly working handshake form a browser WS? We will then check our code
Direct access is probably difficult, because it's a camper. I'll try to copy the websocket server (raspberry based) and make some tests tomorrow. Will keep you informed.