node-red-contrib-knx-ultimate 4.1.0 → 4.1.6

package/CHANGELOG.md

@@ -6,7 +6,23 @@
 
 # CHANGELOG
 
-**Version 4.1.0** - November 2025<br/>
+**Version 4.1.5** - December 2025<br/>
+- Bump KNX Engine to 5.2.3.<br/>
+<br/>
+
+**Version 4.1.4** - December 2025<br/>
+- KNX config node: cache and force-close the FT1.2 serial driver on deploy/close even when the KNX client instance is already null, preventing orphaned handles from blocking reconnects after a redeploy.<br/>
+<br/>
+
+**Version 4.1.3** - December 2025<br/>
+- KNX config node: strengthened FT1.2 teardown with a direct serial-driver close fallback so the KBerry port is reliably released even if a previous disconnect was in a "disconnected" state; prevents reconnection stalls with "Timeout waiting for FT1.2 ACK (reset)".<br/>
+<br/>
+
+**Version 4.1.2** - December 2025<br/>
+- KNX config node: deploy/disconnect now always tears down the KNX client and clears timers, ensuring Serial FT1.2/KBerry ports are released and can reconnect after configuration changes.<br/>
+<br/>
+
+**Version 4.1.1** - November 2025<br/>
 - KNX config node: Serial FT1.2 now exposes a dedicated **Serial FT1.2 mode** selector with *KBerry/BAOS* vs *Standard FT1.2*; the choice is forwarded to the KNX engine as `serialInterface.isKBERRY` (default: KBerry/BAOS).<br/>
 - KNX config node: when `SerialFT12` is selected, Secure KNX options that only apply to IP tunnelling (manual tunnel IA, tunnel user ID/password, mixed keyring+manual mode) are automatically hidden or disabled to keep the UI focused; help and wiki pages in all languages now clearly state that KNX/IP Secure & Data Secure apply only to IP transports, not to Serial FT1.2.<br/>
 - KNX Device node: the manual command button in the editor is now enabled by default and set to **Toggle boolean (write)**, with the notification message correctly translated in all locales and extended to show the payload value when relevant.<br/>

package/nodes/knxUltimate-config.js

@@ -326,6 +326,7 @@ module.exports = (RED) => {
     node.isKBERRY = parseBoolean(config.isKBERRY, true)
     node.hostProtocol = config.hostProtocol === undefined ? 'Auto' : config.hostProtocol // 20/03/2022 Default
     node.knxConnection = null // 20/03/2022 Default
+    node.serialDriverRef = null // Keep last FT1.2 driver to force-close on redeploy
     node.delaybetweentelegrams = (config.delaybetweentelegrams === undefined || config.delaybetweentelegrams === null || config.delaybetweentelegrams === '') ? 25 : Number(config.delaybetweentelegrams)
     if (node.delaybetweentelegrams < 25) node.delaybetweentelegrams = 25 // Protection avoiding handleKNXQueue hangs
     if (node.delaybetweentelegrams > 100) node.delaybetweentelegrams = 100 // Protection avoiding handleKNXQueue hangs
@@ -1114,6 +1115,11 @@ module.exports = (RED) => {
         node.knxConnection.on(knx.KNXClientEvents.connected, (info) => {
           node.linkStatus = 'connected'
 
+          // Track serial driver for forced close on redeploy
+          if (node.hostProtocol === 'SerialFT12' && node.knxConnection && node.knxConnection._serialDriver) {
+            node.serialDriverRef = node.knxConnection._serialDriver
+          }
+
           // Start the timer to do initial read.
           if (node.timerDoInitialRead !== null) clearTimeout(node.timerDoInitialRead)
           node.timerDoInitialRead = setTimeout(() => {
@@ -2283,20 +2289,66 @@ module.exports = (RED) => {
     }, 10000)
 
     node.Disconnect = async (_sNodeStatus = '', _sColor = 'grey') => {
-      if (node.timerSaveExposedGAs !== null) clearInterval(node.timerSaveExposedGAs)
-      if (node.linkStatus === 'disconnected') {
-        node.sysLogger?.debug('Disconnect: already not connected:' + node.linkStatus + ', node.autoReconnect:' + node.autoReconnect)
-        return
+      if (node.timerSaveExposedGAs !== null) {
+        clearInterval(node.timerSaveExposedGAs)
+        node.timerSaveExposedGAs = null
       }
+      if (node.timerDoInitialRead !== null) {
+        clearTimeout(node.timerDoInitialRead) // 17/02/2020 Stop the initial read timer
+        node.timerDoInitialRead = null
+      }
+
+      const previousStatus = node.linkStatus
       node.linkStatus = 'disconnected' // 29/08/2019 signal disconnection
-      if (node.timerDoInitialRead !== null) clearTimeout(node.timerDoInitialRead) // 17/02/2020 Stop the initial read timer
-      try {
-        if (node.knxConnection !== null) await node.knxConnection.Disconnect()
-      } catch (error) {
-        node.sysLogger?.debug(
-          'Disconnected: node.knxConnection.Disconnect() ' + (error.message || '') + ' , node.autoReconnect:' + node.autoReconnect
-        )
+
+      const connection = node.knxConnection
+      const serialDriver = (node.knxConnection && node.knxConnection._serialDriver) || node.serialDriverRef
+      const isSerial = node.hostProtocol === 'SerialFT12'
+      if (connection) {
+        try {
+          await connection.Disconnect()
+        } catch (error) {
+          node.sysLogger?.debug(
+            'Disconnected: node.knxConnection.Disconnect() ' + (error.message || '') + ' , node.autoReconnect:' + node.autoReconnect
+          )
+          // Extra guard for FT1.2: if Disconnect failed, try closing the serial driver directly
+          if (isSerial && connection._serialDriver && typeof connection._serialDriver.close === 'function') {
+            try {
+              await connection._serialDriver.close()
+              node.sysLogger?.debug('Disconnect: fallback close on serial driver executed')
+            } catch (closeErr) {
+              node.sysLogger?.debug('Disconnect: fallback close on serial driver failed: ' + (closeErr.message || ''))
+            }
+          }
+        } finally {
+          try {
+            connection.removeAllListeners()
+          } catch (error) { /* empty */ }
+          if (isSerial && serialDriver && typeof serialDriver.close === 'function') {
+            try {
+              await serialDriver.close()
+              node.sysLogger?.debug('Disconnect: ensured serial driver close')
+            } catch (closeErr) {
+              node.sysLogger?.debug('Disconnect: ensure serial driver close failed: ' + (closeErr.message || ''))
+            }
+          }
+          node.knxConnection = null
+          node.serialDriverRef = null
+        }
+      } else {
+        if (isSerial && serialDriver && typeof serialDriver.close === 'function') {
+          try {
+            await serialDriver.close()
+            node.sysLogger?.debug('Disconnect: closed cached serial driver without knxConnection')
+          } catch (closeErr) {
+            node.sysLogger?.debug('Disconnect: cached serial driver close failed: ' + (closeErr.message || ''))
+          } finally {
+            node.serialDriverRef = null
+          }
+        }
+        node.sysLogger?.debug('Disconnect: no knxConnection instance. previous status: ' + previousStatus)
       }
+
       node.setAllClientsStatus('Disconnected', _sColor, _sNodeStatus)
       await saveExposedGAs() // 04/04/2021 save the current values of GA payload
       node.sysLogger?.debug('Disconnected, node.autoReconnect:' + node.autoReconnect)
@@ -2304,6 +2356,10 @@ module.exports = (RED) => {
 
     node.on('close', async function (done) {
       try {
+        if (node.timerKNXUltimateCheckState !== null) {
+          clearInterval(node.timerKNXUltimateCheckState)
+          node.timerKNXUltimateCheckState = null
+        }
         await node.Disconnect()
       } catch (error) { /* empty */ }
       node.nodeClients = [] // 05/04/2022 Nullify

package/nodes/locales/de/knxUltimate-config.html

@@ -30,7 +30,7 @@ Dieser Node stellt die Verbindung zu deinem KNX/IP‑Gateway her.
 > **KNX Secure im Überblick** \
 > • _KNX Data Secure_ schützt Gruppenadress-Telegramme und benötigt immer eine Keyring-Datei mit den Gruppenschlüsseln.\
 > • _KNX IP Tunnelling Secure_ schützt den Verbindungsaufbau mittels Commissioning-Passwort. Je nach Modus stammt dieses aus dem Keyring oder wird manuell eingetragen.\
-> • KNX/IP Secure und Data Secure gelten nur für IP-Transporte (Tunnel TCP / sicheres Routing); der Serial-FT1.2-Modus verwendet diese Sicherheitseinstellungen nicht.
+> • KNX/IP Secure (Tunnel-Handshake) gilt nur für IP-Transporte (Tunnel TCP / sicheres Routing). KNX Data Secure schützt Gruppenadress-Telegramme und kann sowohl über IP (Tunneling/Routing) als auch über TP via Serial FT1.2 verwendet werden, sofern ein ETS-Keyring vorhanden ist.
 
 <br/>
 

package/nodes/locales/en/knxUltimate-config.html

@@ -30,7 +30,7 @@
 > **KNX Secure essentials** \
 > • _KNX Data Secure_ protects group-address telegrams and **always** needs a keyring file containing the group keys.\
 > • _KNX IP Tunnelling Secure_ protects the connection handshake with a commissioning password. Depending on the selected mode, the password can come from the keyring or be entered manually.\
-> • KNX/IP Secure and Data Secure apply only to IP transports (Tunnel TCP / secure routing); Serial FT1.2 does not use these secure settings.
+> • KNX/IP Secure (tunnel handshake) applies only to IP transports (Tunnel TCP / secure routing). KNX Data Secure protects group-address telegrams and can be used both on IP (tunnelling/routing) and on TP via Serial FT1.2 when an ETS keyring is provided.
 
 <br/>
 

package/nodes/locales/es/knxUltimate-config.html

@@ -27,7 +27,7 @@
 > ** KNX Secure Essentials** \
 > • _knx data secure_ protege los telegramas de la dirección del grupo y ** siempre** necesita un archivo de llavero que contenga las claves de grupo. \
 > • _knx Tunneling IP Secure_ protege el apretón de manos de la conexión con una contraseña de puesta en marcha. Dependiendo del modo seleccionado, la contraseña puede provenir del llavero o ingresarse manualmente.\
-> • KNX/IP Secure y Data Secure solo se aplican a los transportes IP (Tunnel TCP / routing seguro); el modo Serial FT1.2 no utiliza estas opciones de seguridad.
+> • KNX/IP Secure (handshake del túnel) solo se aplica a los transportes IP (Tunnel TCP / routing seguro). KNX Data Secure protege los telegramas de direcciones de grupo y puede usarse tanto sobre IP (túnel/enrutamiento) como sobre TP vía Serial FT1.2 cuando se proporciona un archivo keyring de ETS.
 
 <br/> **Avanzado** | Propiedad | Descripción |
 

package/nodes/locales/fr/knxUltimate-config.html

@@ -30,7 +30,7 @@ Configuration de la passerelle KNX
 > **KNX Secure Essentials** \
 > • _KNX Data Secure_ protège les télégrammes d'adresses de groupe et **toujours** a besoin d'un fichier de clés contenant les touches de groupe. \
 > • _KNX IP Tunneling Secure_ protège la poignée de main de connexion avec un mot de passe de mise en service. Selon le mode sélectionné, le mot de passe peut provenir du clés ou être entré manuellement.\
-> • KNX/IP Secure et Data Secure ne s’appliquent qu’aux transports IP (Tunnel TCP / routage sécurisé) ; le mode Serial FT1.2 n’utilise pas ces paramètres de sécurité.
+> • KNX/IP Secure (handshake du tunnel) ne s’applique qu’aux transports IP (Tunnel TCP / routage sécurisé). KNX Data Secure protège les télégrammes d’adresses de groupe et peut être utilisé à la fois sur IP (tunneling/routage) et sur TP via Serial FT1.2 lorsqu’un fichier keyring ETS est fourni.
 
 <br/>
 

package/nodes/locales/it/knxUltimate-config.html

@@ -30,7 +30,7 @@ Questo nodo si connette al tuo KNX/IP Gateway.
 > **Nota su KNX Secure** \
 > • _KNX Data Secure_ protegge i telegrammi sugli indirizzi di gruppo e richiede sempre un file keyring con le chiavi di gruppo.\
 > • _KNX IP Tunnelling Secure_ protegge l'handshake della connessione tramite una password di commissioning, che può essere letta dal keyring oppure inserita manualmente in base alla modalità scelta.\
-> • KNX/IP Secure e Data Secure si applicano solo ai trasporti IP (Tunnel TCP / routing sicuro); la modalità Serial FT1.2 non utilizza queste impostazioni di sicurezza.
+> • KNX/IP Secure (handshake del tunnel) si applica solo ai trasporti IP (Tunnel TCP / routing sicuro). KNX Data Secure protegge i telegrammi sugli indirizzi di gruppo e può essere usato sia su IP (tunnelling/routing) sia su TP via Serial FT1.2 quando è presente un file keyring ETS.
 
 <br/>
 

package/nodes/locales/zh-CN/knxUltimate-config.html

@@ -30,7 +30,7 @@
 > **KNX Secure 概览** \
 > • _KNX Data Secure_ 用于保护组地址报文， **始终** 需要包含组密钥的密钥环文件。\
 > • _KNX IP Tunnelling Secure_ 通过调试密码保护连接握手，密码可根据模式从密钥环读取或在界面中手动输入。\
-> • KNX/IP Secure 和 Data Secure 仅适用于 IP 传输（Tunnel TCP / 安全路由）；串口 FT1.2 模式不会使用这些安全参数。
+> • KNX/IP Secure（隧道握手）仅适用于 IP 传输（Tunnel TCP / 安全路由）。KNX Data Secure 用于保护组地址报文，可在 IP（隧道/路由）和 TP（通过串口 FT1.2）上使用，只要提供 ETS 导出的 keyring 文件。
 
 <br/>
 

package/package.json

@@ -3,14 +3,14 @@
   "engines": {
     "node": ">=20.18.1"
   },
-  "version": "4.1.0",
+  "version": "4.1.6",
   "description": "Control your KNX and KNX Secure intallation via Node-Red! A bunch of KNX nodes, with integrated Philips HUE control and ETS group address importer. Easy to use and highly configurable.",
   "dependencies": {
     "binary-parser": "2.2.1",
     "crypto-js": "4.2.0",
     "dns-sync": "0.2.1",
     "js-yaml": "4.1.1",
-    "knxultimate": "5.2.0-beta.0",
+    "knxultimate": "5.2.3",
     "lodash": "4.17.21",
     "mkdirp": "3.0.1",
     "node-color-log": "12.0.1",