From f9acca43755ddb79c21d1c05a74b0c02f3059da3 Mon Sep 17 00:00:00 2001
From: =?utf8?q?J=C3=A9r=C3=B4me=20Benoit?= <jerome.benoit@sap.com>
Date: Sat, 2 May 2026 23:21:24 +0200
Subject: [PATCH] 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'.
---
 src/charging-station/ChargingStation.ts | 1 -
 1 file changed, 1 deletion(-)

diff --git a/src/charging-station/ChargingStation.ts b/src/charging-station/ChargingStation.ts
index 64591099..7f981991 100644
--- 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)
   }
 
-- 
2.43.0