You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I dont get 'CALL' response in time its gets timeout error, but soon as I disconnect the charger from the server and when it reconnects on its own the 'CALL' are working fine .
Its happening with some of the charger they send heartbeat at regular interval but don't respond to Call like(remoteStart,clearCache,reset etc.)
It mostly happens after charger is idle for long time , it doesn't respond to any CALL but regularly send heartbeat ,until it reconnects
FYI
This particular vendor don't support ping/pong message so have diasabled them in in web socket. hope that is not causing any issue
I dont get 'CALL' response in time its gets timeout error, but soon as I disconnect the charger from the server and when it reconnects on its own the 'CALL' are working fine .
Its happening with some of the charger they send heartbeat at regular interval but don't respond to Call like(remoteStart,clearCache,reset etc.)
It mostly happens after charger is idle for long time , it doesn't respond to any CALL but regularly send heartbeat ,until it reconnects
FYI
This particular vendor don't support ping/pong message so have diasabled them in in web socket. hope that is not causing any issue
websockets.serve(handler, "0.0.0.0", 9000 subprotocols=["ocpp1.6"], ping_interval=None, ping_timeout=None)
The text was updated successfully, but these errors were encountered: