flay

WebSocket connections do support status codes for all kinds of disconnects, however the most common one you'll see is probably 1006. Unlike most other codes, this code does not originate...

Ok, I must amend my previous comment. It is also possible for the RPCClient or RPCServerClient to call terminate() on the Websocket instance due to a ping timeout. (This is...

You can log successful ping/pong responses initiated from your side of the connection. However, this does not allow you to monitor unsuccessful ping/pongs (i.e. a ping without a response) nor...

If you really absolutely need to log each ping sent from your RPCServer and log the corresponding response, you could take the following monkey-patch approach: ```js server.on('client', (client) => {...

Hi @KlajdiTolis , I could probably help you debug this if you can show me the code (- or better yet, a simple example that demonstrates the same error).

Refer back to [my earlier post](https://github.com/mikuso/ocpp-rpc/issues/80#issuecomment-2555084759) regarding close code 1006. Does the disconnect only happen after ping/pong? If you disable the ping timeout behaviour, does this prevent the disconnect? Do...

Sounds like something is going wrong with your code there then. Add a try/catch block around it like this to see if you can avert a failure: ```js //++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ client.handle('Heartbeat',...

This makes sense, as `'message'` is not a valid member of that schema. If the charger performs strict validation, then this is a likely outcome. Glad you figured it out.