fix: do not nullify wsConnection in onError handler

The ws library guarantees that a 'close' event always follows an 'error'
event. Eagerly setting wsConnection to null in onError caused the
subsequent onClose handler to emit an 'updated' event with wsState
undefined, making the UI display 'unknown' instead of 'closed'.

diff --git a/src/charging-station/ChargingStation.ts b/src/charging-station/ChargingStation.ts
index 64591099d92f1f692c2eedcacfb9d8726ee62f97..7f9819912585b9a135c45aca052c1bae88d11fd5 100644 (file)
--- a/src/charging-station/ChargingStation.ts
+++ b/src/charging-station/ChargingStation.ts
@@ -2280,7 +2280,6 @@ export class ChargingStation extends EventEmitter {
   }
 
   private onError (error: WSError): void {
-    this.closeWSConnection()
     logger.error(`${this.logPrefix()} ${moduleName}.onError: WebSocket error:`, error)
   }