node-red-contrib-knx-ultimate 6.0.5 → 6.0.6

package/CHANGELOG.md

@@ -6,8 +6,12 @@
 
 # CHANGELOG
 
-**Version 6.0.5** - July 2026<br/>
+**Version 6.0.6** - July 2026<br/>
 
+- **Matter nodes — cleaner editors**: long pairing, storage, cache and endpoint-structure explanations were removed from the Matter node forms and consolidated in the localized HTML help, keeping the editors focused on fields, actions and live operational status.<br/>
+- **Matter nodes — distinct canvas icons**: Matter Controller and Matter Bridge nodes now use separate compact icons, with `mat` above a large right/left direction arrow, making the two integration directions immediately distinguishable in the palette, workspace and configuration selectors.<br/>
+- **Matter Controller/Bridge — protocol version and portable storage backups**: the Node-RED startup version line now logs the implemented Matter protocol revision (Matter 1.5.1, separately from the matter.js package version). Both Matter configuration editors can export and import a per-instance JSON backup containing the complete persistent Matter storage required to preserve fabrics, private credentials, sessions and commissioned/paired nodes. Import atomically replaces only the selected instance and restarts its engine; backup files contain secrets and must be protected like passwords.<br/>
+- **Homepage — KNX integration engines, MQTT and Matter overview**: the integration-logo heading and Supported technologies section now identify the KNX integration engines and include dedicated MQTT and Matter cards in all six languages (EN/IT/DE/FR/ES/zh-CN), highlighting MQTT/Home Assistant discovery and the bidirectional Matter Controller/Bridge integration for controlling Matter devices and exposing KNX objects to Matter. The feature-request/enterprise-support solicitation, standalone changelog promotion and donation section have been removed.<br/>
 - **Expose KNX to Matter (BETA) — dedup for duplicate Alexa light commands**: same Alexa quirk as the covers below, on lights: a single "turn on" / "set to 50%" voice request could arrive as up to two *identical* cluster commands (two `On`, or `MoveToLevelWithOnOff` + `MoveToLevel` with the same level), making the node emit duplicate raw msgs on `OnOffLightDevice`/`DimmableLightDevice` ([discussion #516](https://github.com/Supergiovane/node-red-contrib-knx-ultimate/discussions/516)). A short leading-edge dedup now forwards the first command immediately (no added latency — lights react instantly) and drops only a command identical to the one just emitted for the same function within the window; any change of value (a real On→Off, or a different brightness) always passes through at once, so genuine commands are never swallowed. The window is exposed in the node's **Advanced** tab as *Alexa duplicate-command window* (default 1.2s, **0 = disabled/raw**), the same approach the Home Assistant Matter Hub adopted for this Alexa behavior. The complementary *ignore brightness after On* option (already present) covers Alexa's other habit of sending a brightness right after On.<br/>
 - **Expose KNX to Matter (BETA) — Home Assistant Matter Hub-style cover compatibility**: `WindowCovering` now exposes **Swap Open / Close** and **Cover slider debounce** in the Advanced tab. Swap reverses the binary KNX Up/Down command and percentage direction symmetrically for Alexa installations that interpret them backwards. Debounce collapses rapid `GoToLiftPercentage` targets into the last KNX command; `0` uses the adaptive Home Assistant Matter Hub windows (400ms first command / 150ms subsequent commands), while `1`–`5000` selects a fixed per-cover window. `StopMotion` remains immediate and cancels every pending movement. Help HTML and Matter Bridge docs were updated in EN/IT/DE/FR/ES/zh-CN.<br/>
 - **Expose KNX to Matter (BETA) — cover "arrived" safety net**: in *Wait for KNX status* mode, if no KNX status telegram confirms the exact requested position within a generous window (45s), the node now falls back to reflecting the requested position to Matter anyway. Without this, a real actuator that never reports back the *exact* requested percentage (positioning tolerance/drift) could leave the Matter device reporting "still moving" forever, since matter.js only clears `OperationalStatus` on an exact match.<br/>

package/README.md

@@ -6,7 +6,7 @@
 
 ## The most popular KNX node for Node-RED
 
-KNX Ultimate is the most advanced KNX integration for Node-RED, providing secure KNX/IP communication, routing, ETS project import, Philips Hue, Matter, MQTT, diagnostics, virtual devices, and powerful automation nodes. Build professional, reliable, and scalable smart home and building automation projects with minimal effort.
+KNX Ultimate is the most advanced KNX integration for Node-RED, providing secure KNX/IP communication, routing, ETS project import, Philips Hue, Matter Controller and Matter Bridge (control matter device via KNX and expose KNX GA via Matter), MQTT, diagnostics, virtual devices, and powerful automation nodes. Build professional, reliable, and scalable smart home and building automation projects with minimal effort.
 
 <br/>
 <br/>

package/nodes/commonFunctions.js

@@ -1043,6 +1043,36 @@ module.exports = (RED) => {
       }
     })
 
+    const exportMatterStorage = async (req, res, idKey) => {
+      try {
+        const configNode = RED.nodes.getNode(req.query[idKey])
+        if (!configNode || typeof configNode.exportMatterStorage !== 'function') throw new Error('PLEASE DEPLOY FIRST: then try again.')
+        const backup = await configNode.exportMatterStorage()
+        const stamp = new Date().toISOString().replace(/[:.]/g, '-')
+        res.setHeader('Content-Type', 'application/json; charset=utf-8')
+        res.setHeader('Content-Disposition', `attachment; filename="knx-ultimate-matter-${backup.kind}-${stamp}.json"`)
+        res.send(JSON.stringify(backup, null, 2))
+      } catch (error) {
+        RED.log.error(`Err Matter storage export: ${error.message}`)
+        if (!res.headersSent) res.status(500).json({ error: error.message })
+      }
+    }
+
+    const importMatterStorage = async (req, res, idKey) => {
+      try {
+        const configNode = RED.nodes.getNode(req.query[idKey])
+        if (!configNode || typeof configNode.importMatterStorage !== 'function') throw new Error('PLEASE DEPLOY FIRST: then try again.')
+        await configNode.importMatterStorage(req.body)
+        res.json({ status: 'ok' })
+      } catch (error) {
+        RED.log.error(`Err Matter storage import: ${error.message}`)
+        res.status(400).json({ error: error.message })
+      }
+    }
+
+    RED.httpAdmin.get('/KNXUltimateMatterStorageExport', normalizeAuthFromAccessTokenQuery, RED.auth.needsPermission('matter-config.read'), (req, res) => exportMatterStorage(req, res, 'serverId'))
+    RED.httpAdmin.post('/KNXUltimateMatterStorageImport', RED.auth.needsPermission('matter-config.write'), (req, res) => importMatterStorage(req, res, 'serverId'))
+
     // MATTER BRIDGE: returns the pairing info (QR code, manual code, commissioned fabrics) of a matterbridge-config node
     RED.httpAdmin.get('/KNXUltimateMatterBridgeInfo', RED.auth.needsPermission('matterbridge-config.read'), (req, res) => {
       try {
@@ -1074,6 +1104,9 @@ module.exports = (RED) => {
       }
     })
 
+    RED.httpAdmin.get('/KNXUltimateMatterBridgeStorageExport', normalizeAuthFromAccessTokenQuery, RED.auth.needsPermission('matterbridge-config.read'), (req, res) => exportMatterStorage(req, res, 'configId'))
+    RED.httpAdmin.post('/KNXUltimateMatterBridgeStorageImport', RED.auth.needsPermission('matterbridge-config.write'), (req, res) => importMatterStorage(req, res, 'configId'))
+
     RED.httpAdmin.get('/knxUltimateDpts', (req, res) => {
       try {
         const dpts = Object.entries(dptlib.dpts).filter(onlyDptKeys).map(extractBaseNo).sort(sortBy('base'))

package/nodes/icons/node-matter-bridge-icon.svg

@@ -0,0 +1,6 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<svg width="40" height="60" viewBox="0 0 40 60" xmlns="http://www.w3.org/2000/svg" role="img" aria-label="Matter Bridge">
+  <text x="20" y="21" fill="#ffffff" text-anchor="middle" font-family="Arial, sans-serif" font-size="20" font-weight="700" textLength="38" lengthAdjust="spacingAndGlyphs">mat</text>
+  <path d="M 37 34 H 12 V 29 L 2 38 L 12 47 V 42 H 25"
+    fill="none" stroke="#ffffff" stroke-width="2.6" stroke-linecap="round" stroke-linejoin="round"/>
+</svg>

package/nodes/icons/node-matter-controller-icon.svg

@@ -0,0 +1,6 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<svg width="40" height="60" viewBox="0 0 40 60" xmlns="http://www.w3.org/2000/svg" role="img" aria-label="Matter Controller">
+  <text x="20" y="21" fill="#ffffff" text-anchor="middle" font-family="Arial, sans-serif" font-size="20" font-weight="700" textLength="38" lengthAdjust="spacingAndGlyphs">mat</text>
+  <path d="M 3 34 H 28 V 29 L 38 38 L 28 47 V 42 H 15"
+    fill="none" stroke="#ffffff" stroke-width="2.6" stroke-linecap="round" stroke-linejoin="round"/>
+</svg>

package/nodes/knxUltimate-config.js

@@ -29,6 +29,10 @@ let NODE_VERSION = 'unknown'
 try { NODE_VERSION = require('../package.json').version } catch (e) { /* empty */ }
 let KNX_ENGINE_VERSION = 'unknown'
 try { KNX_ENGINE_VERSION = require('knxultimate/package.json').version } catch (e) { /* empty */ }
+let MATTER_PACKAGE_VERSION = 'unknown'
+let Specification = { REVISION: 'unknown' }
+try { MATTER_PACKAGE_VERSION = require('@matter/main').version } catch (e) { /* empty */ }
+try { Specification = require('@matter/model').Specification } catch (e) { /* empty */ }
 
 // DATAPONT MANIPULATION HELPERS
 // ####################
@@ -193,7 +197,7 @@ const findAutoEthernetInterface = (targetIP) => {
 module.exports = (RED) => {
   // Log node and KNXUltimate engine versions once, at Node-RED startup.
   try {
-    RED.log.info(`KNXUltimate: node-red-contrib-knx-ultimate v${NODE_VERSION} (KNXUltimate engine v${KNX_ENGINE_VERSION})`)
+    RED.log.info(`KNXUltimate: node-red-contrib-knx-ultimate v${NODE_VERSION} (KNXUltimate engine v${KNX_ENGINE_VERSION}, Matter protocol ${Specification.REVISION}, matter.js v${MATTER_PACKAGE_VERSION})`)
   } catch (e) { /* empty */ }
 
   function knxUltimateConfigNode (config) {

package/nodes/knxUltimateMatterBridge.html

@@ -100,7 +100,7 @@
       defaults: gaDefaults,
       inputs: 0,
       outputs: 0,
-      icon: 'node-matter-icon.svg',
+      icon: 'node-matter-bridge-icon.svg',
       label() {
         return this.name || 'Expose KNX to Matter (BETA)';
       },
@@ -337,11 +337,6 @@
     </ul>
 
     <div id="mb-tab-mappings" style="padding-top:12px;">
-      <div class="form-tips" style="display:block; width:100%; max-width:none; box-sizing:border-box; margin-bottom:12px; border-left:4px solid #d9822b;">
-        <i class="fa fa-triangle-exclamation"></i>
-        <span data-i18n="knxUltimateMatterBridge.type_change_warning"></span>
-      </div>
-
       <div id="mb-ga-fields"></div>
 
       <div class="form-row" id="mb-invert-row" style="display:none;">

package/nodes/knxUltimateMatterControllerDevice.html

@@ -125,7 +125,7 @@
       },
       inputs: 0,
       outputs: 0,
-      icon: "node-matter-icon.svg",
+      icon: "node-matter-controller-icon.svg",
       label: function () {
         return this.name || this.matterDeviceName || "Control Matter from KNX (BETA)";
       },
@@ -679,7 +679,6 @@
           const $tabs = $("#tabs");
           const $pinSectionRow = $("#node-input-enableNodePINS").closest('.form-row');
           const $pinSelect = $("#node-input-enableNodePINS");
-          const $pinInfoRow = $pinSectionRow.next('.form-tips');
           let currentMatterCapabilities = parseMatterCapabilities($matterCapabilitiesInput.val() || node.matterDeviceCapabilities);
           $tabs.addClass('hue-vertical-tabs');
           $tabs.tabs(); // Tabs gestione KNX
@@ -984,9 +983,6 @@
             if ($pinSectionRow.length) {
               $pinSectionRow.show();
             }
-            if ($pinInfoRow.length) {
-              $pinInfoRow.show();
-            }
           };
           updateTabsVisibility();
 
@@ -1899,7 +1895,6 @@
           </label>
           <input type="checkbox" id="node-input-updateLocalStateFromKNXWrite" style="display:inline-block; width:auto; vertical-align:top;" />
         </div>
-        <div class="form-tips" style="margin-left:260px;" data-i18n="knxUltimateMatterControllerDevice.update_local_state_from_knx_write_hint"></div><br/>
         <div id ="divBehaviourBrightness">
           <div class="form-row">
             <label for="node-input-specifySwitchOnBrightness" style="width:260px;">
@@ -2116,4 +2111,4 @@ _Non-Hue basic effects_
 The Dimming function works in **KNX mode `start` and`stop` ** . To start dimming, send only one "start" KNX telegram. To stop dimming, send a "stop" KNX telegram. Please**remember that** , when you set your wall swiches properties.
 
 <br/>
-</script>
+</script>

package/nodes/locales/de/knxUltimateMatterBridge.html

@@ -9,6 +9,8 @@ Jeder Expose KNX to Matter Node stellt **ein KNX-Gerät als Matter-Gerät** bere
 
 Das ist die Gegenrichtung zum *Matter Device*-Node: Dort steuert KNX ein Matter-Gerät, hier steuern Matter-Controller KNX.
 
+Das Ändern des Gerätetyps nach der Kopplung der Bridge verändert die Matter-Endpunktstruktur. Controller können den alten Endpunkt als nicht erreichbar behalten; dann die Bridge zurücksetzen/neu koppeln oder ein neues bereitgestelltes Gerät erstellen.
+
 ## Konfiguration
 
 |Feld|Beschreibung|

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

@@ -15,10 +15,14 @@ Der Controller kommuniziert mit den Geräten über das **IP-Netzwerk** (WLAN, Et
 
 Wenn das Gerät fabrikneu ist und nur Bluetooth-Kommissionierung unterstützt, kopple es zuerst mit der Hersteller-App oder einem anderen Matter-Controller (Alexa, Google Home, Apple Home) und nutze dann dessen Funktion **"mit weiterem Hub teilen"**, um einen neuen Kopplungscode für KNX-Ultimate zu erzeugen. So tritt das Gerät mehreren Fabrics gleichzeitig bei.
 
+Bevorzuge den QR-Payload (`MT:...`): Er enthält den vollständigen Diskriminator. Der manuelle Code enthält nur den kurzen Diskriminator und kann bei mehreren identischen Modellen im Kopplungsmodus das falsche Gerät auswählen. Immer nur ein Gerät gleichzeitig koppeln.
+
 ## Speicherung
 
 Die Fabric-Zugangsdaten und die gekoppelten Geräte werden im Ordner `knxultimatestorage/matter` im Node-RED-Benutzerverzeichnis gespeichert. Das Löschen dieses Ordners entfernt alle Kopplungen.
 
+Mit **Exportieren** wird eine vollständige Sicherung dieser Controller-Instanz heruntergeladen. Sie enthält Fabric, private Zugangsdaten, Sitzungen und Daten gekoppelter Geräte. **Die Datei wie ein Passwort schützen.** Der Import ersetzt den Matter-Speicher dieser Instanz und startet den Controller kurz neu. Eine Controller-Sicherung kann nicht in eine Bridge importiert werden.
+
 ## Ein Gerät entfernen
 
 Nutze den Papierkorb-Button in der Liste der gekoppelten Geräte. Der Controller versucht, das Gerät sauber zu dekommissionieren; ist es nicht erreichbar, wird es trotzdem aus der Fabric entfernt (danach kann ein Werksreset des Geräts nötig sein).

package/nodes/locales/de/matter-config.json

@@ -2,7 +2,6 @@
   "matter-config": {
     "properties": {
       "title": "Matter Controller",
-      "intro": "Dieser Node ist ein Matter-Controller (mit eigener Fabric). Kopple hier deine Matter-Geräte und verwende dann den \"Matter Device\"-Node, um sie auf KNX-Gruppenadressen abzubilden. Zuerst deployen, dann hierher zurückkehren, um Geräte zu koppeln.",
       "node-config-input-name": "Name",
       "fabric_label": "Fabric-Bezeichnung",
       "pairing_title": "Neues Gerät koppeln",
@@ -24,7 +23,13 @@
       "pairing_ok": "Gerät erfolgreich gekoppelt!",
       "rename_button": "Umbenennen",
       "rename_prompt": "Neuer Gerätename",
-      "rename_ok": "Gerät umbenannt."
+      "rename_ok": "Gerät umbenannt.",
+      "storage_title": "Sicherung von Fabric und Inbetriebnahme",
+      "storage_export": "Exportieren",
+      "storage_import": "Importieren",
+      "storage_warning": "Die Sicherung enthält Fabric-Zugangsdaten, private Schlüssel und Daten gekoppelter Geräte. Wie ein Passwort schützen. Der Import ersetzt den Matter-Speicher dieses Controllers und startet ihn kurz neu.",
+      "storage_import_confirm": "Matter-Fabric und gekoppelte Geräte dieses Controllers durch die gewählte Sicherung ersetzen?",
+      "storage_import_ok": "Matter-Sicherung importiert. Der Controller wurde neu gestartet."
     }
   }
 }

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

@@ -21,12 +21,16 @@ Dieser Konfigurations-Node ist die **Matter-Bridge selbst**: Er betreibt den Mat
 2. Das Kopplungs-Panel zeigt den **QR-Code** und den **manuellen Code**: scannen oder in Alexa / Google Home / Apple Home eingeben ("Matter-Gerät hinzufügen").
 3. Mehrere Controller können mit derselben Bridge gekoppelt werden (Matter Multi-Fabric).
 
+Um nach dem Ausblenden des QR-Codes einen weiteren Controller hinzuzufügen, den Kopplungsmodus über einen bereits gekoppelten Controller öffnen und dann im neuen Controller ein Matter-Gerät hinzufügen. **Kopplung zurücksetzen** nur verwenden, um alle vorhandenen Controller zu entfernen und neu zu beginnen.
+
 Der Button **Kopplung zurücksetzen** entfernt alle gekoppelten Controller und startet die Kopplungs-Ankündigung neu.
 
 ## Identität und Speicherung
 
 Die Bridge-Identität ist an diesen Konfigurations-Node gebunden und wird in `knxultimatestorage/matter` im Node-RED-Benutzerverzeichnis gespeichert: Re-Deploys (auch mit geändertem Port oder Namen) erfordern **KEINE** neue Kopplung. Nur das Löschen dieses Konfigurations-Nodes und das Anlegen eines neuen ändert die Identität — in dem Fall die alte Bridge aus der Matter-App entfernen und neu koppeln.
 
+Mit **Exportieren** wird eine vollständige Sicherung dieser Bridge-Instanz heruntergeladen, einschließlich Fabrics, privater Zugangsdaten, Sitzungen und Kopplungsdaten. **Die Datei wie ein Passwort schützen.** Der Import ersetzt den Speicher dieser Instanz und startet die Bridge kurz neu. Eine Bridge-Sicherung kann nicht in einen Controller importiert werden.
+
 ## Hinweise
 
 - Der Node-RED-Host muss **IPv6 link-local** aktiviert haben (Standard-Matter-Anforderung) und von den Controllern im lokalen Netzwerk erreichbar sein.

package/nodes/locales/de/matterbridge-config.json

@@ -16,7 +16,10 @@
       "deploy_first": "Bitte zuerst diesen Konfigurations-Node deployen und dann auf Aktualisieren klicken.",
       "reset_button": "Kopplung zurücksetzen",
       "reset_confirm": "ALLE gekoppelten Controller entfernen und die Kopplung neu starten? Die Geräte verschwinden aus Alexa/Google/Apple.",
-      "reset_ok": "Kopplung zurückgesetzt. Die Bridge wartet wieder auf Kopplung."
+      "reset_ok": "Kopplung zurückgesetzt. Die Bridge wartet wieder auf Kopplung.",
+      "storage_title": "Sicherung von Fabric und Kopplung", "storage_export": "Exportieren", "storage_import": "Importieren",
+      "storage_warning": "Die Sicherung enthält Fabric-Zugangsdaten, private Schlüssel und Kopplungsdaten. Wie ein Passwort schützen. Der Import ersetzt den Matter-Speicher dieser Bridge und startet sie kurz neu.",
+      "storage_import_confirm": "Matter-Fabrics und gekoppelte Controller dieser Bridge durch die gewählte Sicherung ersetzen?", "storage_import_ok": "Matter-Sicherung importiert. Die Bridge wurde neu gestartet."
     }
   }
 }

package/nodes/locales/en/knxUltimateMatterBridge.html

@@ -9,6 +9,8 @@ Each Expose KNX to Matter node exposes **one KNX device as a Matter device**: th
 
 This is the opposite direction of the *Matter Device* node: there KNX controls a Matter device, here the Matter controllers control KNX.
 
+Changing the device type after the bridge has been paired changes the Matter endpoint structure. Controllers may keep the old endpoint as unreachable; in that case reset/re-pair the bridge or create a new exposed device.
+
 ## Configuration
 
 |Field|Description|

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

@@ -15,10 +15,14 @@ The controller talks to the devices over the **IP network** (WiFi, Ethernet, or
 
 If the device is brand new and only supports Bluetooth commissioning, first pair it with its vendor app or another Matter controller (Alexa, Google Home, Apple Home), then use that controller's **"share / pair with another hub"** function to generate a new pairing code for KNX-Ultimate. This way the device joins multiple fabrics at once.
 
+Prefer the QR payload (`MT:...`): it contains the full discriminator. A manual code contains only the short discriminator and may select the wrong device when several identical models are in commissioning mode. Pair one device at a time.
+
 ## Storage
 
 The fabric credentials and the paired devices are stored in the `knxultimatestorage/matter` folder inside your Node-RED user directory. Deleting that folder unpairs everything.
 
+Use **Export** to download a complete backup of this controller instance. It includes the fabric, private credentials, sessions and commissioned-device data. **Protect the file like a password.** Import replaces this instance's current Matter storage and briefly restarts the controller. A controller backup cannot be imported into a bridge.
+
 ## Removing a device
 
 Use the trash button in the commissioned devices list. The controller tries to decommission the device properly; if it is unreachable, it is removed from the fabric anyway (a factory reset of the device may then be needed).

package/nodes/locales/en/matter-config.json

@@ -2,7 +2,6 @@
   "matter-config": {
     "properties": {
       "title": "Matter Controller",
-      "intro": "This node is a Matter controller (its own fabric). Pair your Matter devices here, then use the \"Matter Device\" node to map them to KNX group addresses. Deploy the node first, then come back here to pair devices.",
       "node-config-input-name": "Name",
       "fabric_label": "Fabric label",
       "pairing_title": "Pair a new device",
@@ -25,7 +24,13 @@
       "pairing_hint": "Prefer the QR code (MT:…): it carries the full device discriminator. The manual code stores only a short discriminator and can't reliably tell identical devices apart (e.g. several Shelly of the same model), which may pair the wrong one or report it as already commissioned. Pair one device at a time; if it's already paired elsewhere, factory-reset it first.",
       "rename_button": "Rename",
       "rename_prompt": "New device name",
-      "rename_ok": "Device renamed."
+      "rename_ok": "Device renamed.",
+      "storage_title": "Fabric and commissioning backup",
+      "storage_export": "Export",
+      "storage_import": "Import",
+      "storage_warning": "The backup contains fabric credentials, private keys and commissioned-device data. Keep it secret like a password. Import replaces this controller's current Matter storage and briefly restarts it.",
+      "storage_import_confirm": "Replace this controller's Matter fabric and commissioned devices with the selected backup?",
+      "storage_import_ok": "Matter backup imported. The controller has restarted."
     }
   }
 }

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

@@ -21,12 +21,16 @@ This configuration node is the **Matter bridge itself**: it runs the Matter serv
 2. The pairing panel shows the **QR code** and the **manual pairing code**: scan or type it in Alexa / Google Home / Apple Home ("add Matter device").
 3. Multiple controllers can be paired with the same bridge (Matter multi-fabric).
 
+To add another controller after the QR code is hidden, open pairing mode from an already paired controller, then add a Matter device in the new controller. Use **Reset pairing** only to remove every existing controller and start over.
+
 The **Reset pairing** button removes all paired controllers and restarts the pairing advertising.
 
 ## Identity and storage
 
 The bridge identity is tied to this configuration node and stored in `knxultimatestorage/matter` inside the Node-RED user directory: re-deploys (even changing port or name) do **NOT** require a new pairing. Only deleting this configuration node and creating a new one changes the identity — in that case remove the old bridge from the Matter app and pair again.
 
+Use **Export** to download a complete backup of this bridge instance, including fabrics, private credentials, sessions and pairing data. **Protect the file like a password.** Import replaces this instance's storage and briefly restarts the bridge. A bridge backup cannot be imported into a controller.
+
 ## Notes
 
 - The Node-RED host must have **IPv6 link-local** enabled (standard Matter requirement) and be reachable from the controllers on the local network.

package/nodes/locales/en/matterbridge-config.json

@@ -16,7 +16,10 @@
       "deploy_first": "Deploy this configuration node first, then click refresh.",
       "reset_button": "Reset pairing",
       "reset_confirm": "Remove ALL paired controllers and restart pairing? The devices will disappear from Alexa/Google/Apple.",
-      "reset_ok": "Pairing reset. The bridge is now advertising for pairing again."
+      "reset_ok": "Pairing reset. The bridge is now advertising for pairing again.",
+      "storage_title": "Fabric and commissioning backup", "storage_export": "Export", "storage_import": "Import",
+      "storage_warning": "The backup contains fabric credentials, private keys and pairing data. Keep it secret like a password. Import replaces this bridge's current Matter storage and briefly restarts it.",
+      "storage_import_confirm": "Replace this bridge's Matter fabrics and paired controllers with the selected backup?", "storage_import_ok": "Matter backup imported. The bridge has restarted."
     }
   }
 }

package/nodes/locales/es/knxUltimateMatterBridge.html

@@ -9,6 +9,8 @@ Cada nodo Expose KNX to Matter expone **un dispositivo KNX como dispositivo Matt
 
 Es la dirección opuesta al nodo *Matter Device*: allí KNX controla un dispositivo Matter, aquí los controladores Matter controlan KNX.
 
+Cambiar el tipo de dispositivo después de emparejar el bridge modifica la estructura del endpoint Matter. Los controladores pueden conservar el endpoint antiguo como no alcanzable; en ese caso, restablece/vuelve a emparejar el bridge o crea un nuevo dispositivo expuesto.
+
 ## Configuración
 
 |Campo|Descripción|

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

@@ -15,10 +15,14 @@ El controlador se comunica con los dispositivos a través de la **red IP** (WiFi
 
 Si el dispositivo es nuevo de fábrica y solo admite emparejamiento por Bluetooth, emparéjalo primero con la app del fabricante o con otro controlador Matter (Alexa, Google Home, Apple Home) y usa después su función **"compartir / emparejar con otro hub"** para generar un nuevo código para KNX-Ultimate. Así el dispositivo se une a varias fabrics a la vez.
 
+Prefiere el payload QR (`MT:...`): contiene el discriminador completo. El código manual solo contiene el discriminador corto y puede seleccionar el dispositivo equivocado si hay varios modelos idénticos en modo de emparejamiento. Empareja un dispositivo cada vez.
+
 ## Almacenamiento
 
 Las credenciales de la fabric y los dispositivos emparejados se guardan en la carpeta `knxultimatestorage/matter` dentro del directorio de usuario de Node-RED. Borrar esa carpeta elimina todos los emparejamientos.
 
+Usa **Exportar** para descargar una copia completa de esta instancia del controlador. Incluye la fabric, credenciales privadas, sesiones y datos de dispositivos vinculados. **Protege el archivo como una contraseña.** La importación reemplaza el almacenamiento Matter de esta instancia y reinicia brevemente el controlador. Una copia de controlador no se puede importar en un bridge.
+
 ## Eliminar un dispositivo
 
 Usa el botón de la papelera en la lista de dispositivos emparejados. El controlador intenta retirar el dispositivo correctamente; si no está accesible, se elimina igualmente de la fabric (puede ser necesario un reset de fábrica del dispositivo).

package/nodes/locales/es/matter-config.json

@@ -2,7 +2,6 @@
   "matter-config": {
     "properties": {
       "title": "Controlador Matter",
-      "intro": "Este nodo es un controlador Matter (con su propia fabric). Empareja aquí tus dispositivos Matter y usa el nodo \"Matter Device\" para mapearlos a direcciones de grupo KNX. Haz deploy primero y vuelve aquí para emparejar dispositivos.",
       "node-config-input-name": "Nombre",
       "fabric_label": "Etiqueta de fabric",
       "pairing_title": "Emparejar un nuevo dispositivo",
@@ -24,7 +23,13 @@
       "pairing_ok": "¡Dispositivo emparejado correctamente!",
       "rename_button": "Renombrar",
       "rename_prompt": "Nuevo nombre del dispositivo",
-      "rename_ok": "Dispositivo renombrado."
+      "rename_ok": "Dispositivo renombrado.",
+      "storage_title": "Copia de fabric y vinculaciones",
+      "storage_export": "Exportar",
+      "storage_import": "Importar",
+      "storage_warning": "La copia contiene credenciales de fabric, claves privadas y datos de dispositivos vinculados. Protégela como una contraseña. La importación reemplaza el almacenamiento Matter de este controlador y lo reinicia brevemente.",
+      "storage_import_confirm": "¿Reemplazar la fabric Matter y los dispositivos vinculados de este controlador con la copia seleccionada?",
+      "storage_import_ok": "Copia Matter importada. El controlador se ha reiniciado."
     }
   }
 }

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

@@ -21,12 +21,16 @@ Este nodo de configuración es el **bridge Matter en sí**: ejecuta el servidor
 2. El panel de emparejamiento muestra el **código QR** y el **código manual**: escanéalo o escríbelo en Alexa / Google Home / Apple Home ("añadir dispositivo Matter").
 3. Se pueden emparejar varios controladores con el mismo bridge (multi-fabric Matter).
 
+Para añadir otro controlador cuando el código QR está oculto, abre el modo de emparejamiento desde un controlador ya vinculado y añade un dispositivo Matter en el nuevo controlador. Usa **Restablecer emparejamiento** solo para eliminar todos los controladores existentes y empezar de nuevo.
+
 El botón **Restablecer emparejamiento** elimina todos los controladores emparejados y reinicia el anuncio de emparejamiento.
 
 ## Identidad y almacenamiento
 
 La identidad del bridge está ligada a este nodo de configuración y se guarda en `knxultimatestorage/matter` dentro del directorio de usuario de Node-RED: los re-deploys (incluso cambiando puerto o nombre) **NO** requieren un nuevo emparejamiento. Solo borrar este nodo de configuración y crear uno nuevo cambia la identidad — en ese caso elimina el bridge antiguo de la app Matter y vuelve a emparejar.
 
+Usa **Exportar** para descargar una copia completa de esta instancia del bridge, con fabrics, credenciales privadas, sesiones y datos de vinculación. **Protege el archivo como una contraseña.** La importación reemplaza el almacenamiento de esta instancia y reinicia brevemente el bridge. Una copia de bridge no se puede importar en un controlador.
+
 ## Notas
 
 - El host de Node-RED debe tener **IPv6 link-local** habilitado (requisito estándar de Matter) y ser accesible desde los controladores en la red local.

package/nodes/locales/es/matterbridge-config.json

@@ -16,7 +16,10 @@
       "deploy_first": "Haz deploy de este nodo de configuración primero y pulsa actualizar.",
       "reset_button": "Restablecer emparejamiento",
       "reset_confirm": "¿Eliminar TODOS los controladores emparejados y reiniciar el emparejamiento? Los dispositivos desaparecerán de Alexa/Google/Apple.",
-      "reset_ok": "Emparejamiento restablecido. El bridge vuelve a estar en espera de emparejamiento."
+      "reset_ok": "Emparejamiento restablecido. El bridge vuelve a estar en espera de emparejamiento.",
+      "storage_title": "Copia de fabric y vinculaciones", "storage_export": "Exportar", "storage_import": "Importar",
+      "storage_warning": "La copia contiene credenciales de fabric, claves privadas y datos de vinculación. Protégela como una contraseña. La importación reemplaza el almacenamiento Matter de este bridge y lo reinicia brevemente.",
+      "storage_import_confirm": "¿Reemplazar las fabrics Matter y los controladores vinculados de este bridge con la copia seleccionada?", "storage_import_ok": "Copia Matter importada. El bridge se ha reiniciado."
     }
   }
 }

package/nodes/locales/fr/knxUltimateMatterBridge.html

@@ -9,6 +9,8 @@ Chaque nœud Expose KNX to Matter expose **un appareil KNX comme appareil Matter
 
 C'est la direction opposée du nœud *Matter Device* : là-bas KNX contrôle un appareil Matter, ici les contrôleurs Matter contrôlent KNX.
 
+Changer le type d'appareil après l'appairage du bridge modifie la structure de l'endpoint Matter. Les contrôleurs peuvent conserver l'ancien endpoint comme injoignable ; dans ce cas, réinitialisez/réappairez le bridge ou créez un nouvel appareil exposé.
+
 ## Configuration
 
 |Champ|Description|

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

@@ -15,10 +15,14 @@ Le contrôleur communique avec les appareils via le **réseau IP** (WiFi, Ethern
 
 Si l'appareil est neuf et ne prend en charge que l'appairage Bluetooth, appairez-le d'abord avec l'app du fabricant ou un autre contrôleur Matter (Alexa, Google Home, Apple Home), puis utilisez sa fonction **« partager / appairer avec un autre hub »** pour générer un nouveau code pour KNX-Ultimate. L'appareil rejoint ainsi plusieurs fabrics à la fois.
 
+Préférez le payload QR (`MT:...`) : il contient le discriminateur complet. Le code manuel ne contient que le discriminateur court et peut sélectionner le mauvais appareil si plusieurs modèles identiques sont en mode appairage. Appairez un appareil à la fois.
+
 ## Stockage
 
 Les identifiants de la fabric et les appareils appairés sont enregistrés dans le dossier `knxultimatestorage/matter` du répertoire utilisateur de Node-RED. Supprimer ce dossier efface tous les appairages.
 
+Utilisez **Exporter** pour télécharger une sauvegarde complète de cette instance de contrôleur. Elle contient la fabric, les identifiants privés, les sessions et les données des appareils associés. **Protégez le fichier comme un mot de passe.** L'import remplace le stockage Matter de cette instance et redémarre brièvement le contrôleur. Une sauvegarde de contrôleur ne peut pas être importée dans un bridge.
+
 ## Supprimer un appareil
 
 Utilisez le bouton corbeille dans la liste des appareils appairés. Le contrôleur essaie de retirer l'appareil proprement ; s'il est injoignable, il est quand même supprimé de la fabric (une réinitialisation d'usine de l'appareil peut alors être nécessaire).

package/nodes/locales/fr/matter-config.json

@@ -2,7 +2,6 @@
   "matter-config": {
     "properties": {
       "title": "Contrôleur Matter",
-      "intro": "Ce nœud est un contrôleur Matter (avec sa propre fabric). Appairez ici vos appareils Matter, puis utilisez le nœud \"Matter Device\" pour les mapper sur des adresses de groupe KNX. Déployez d'abord le nœud, puis revenez ici pour appairer les appareils.",
       "node-config-input-name": "Nom",
       "fabric_label": "Étiquette de fabric",
       "pairing_title": "Appairer un nouvel appareil",
@@ -24,7 +23,13 @@
       "pairing_ok": "Appareil appairé avec succès !",
       "rename_button": "Renommer",
       "rename_prompt": "Nouveau nom de l'appareil",
-      "rename_ok": "Appareil renommé."
+      "rename_ok": "Appareil renommé.",
+      "storage_title": "Sauvegarde de la fabric et des associations",
+      "storage_export": "Exporter",
+      "storage_import": "Importer",
+      "storage_warning": "La sauvegarde contient les identifiants de fabric, les clés privées et les données des appareils associés. Protégez-la comme un mot de passe. L'import remplace le stockage Matter de ce contrôleur et le redémarre brièvement.",
+      "storage_import_confirm": "Remplacer la fabric Matter et les appareils associés de ce contrôleur par la sauvegarde sélectionnée ?",
+      "storage_import_ok": "Sauvegarde Matter importée. Le contrôleur a redémarré."
     }
   }
 }

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

@@ -21,12 +21,16 @@ Ce nœud de configuration est le **bridge Matter lui-même** : il exécute le se
 2. Le panneau d'appairage montre le **QR code** et le **code manuel** : scannez ou saisissez-le dans Alexa / Google Home / Apple Home (« ajouter un appareil Matter »).
 3. Plusieurs contrôleurs peuvent être appairés au même bridge (multi-fabric Matter).
 
+Pour ajouter un contrôleur lorsque le QR code est masqué, ouvrez le mode d'appairage depuis un contrôleur déjà associé, puis ajoutez un appareil Matter dans le nouveau contrôleur. Utilisez **Réinitialiser l'appairage** uniquement pour supprimer tous les contrôleurs et recommencer.
+
 Le bouton **Réinitialiser l'appairage** supprime tous les contrôleurs appairés et relance l'annonce d'appairage.
 
 ## Identité et stockage
 
 L'identité du bridge est liée à ce nœud de configuration et enregistrée dans `knxultimatestorage/matter` du répertoire utilisateur de Node-RED : les re-deploys (même en changeant port ou nom) ne nécessitent **PAS** de nouvel appairage. Seule la suppression de ce nœud de configuration et la création d'un nouveau changent l'identité — dans ce cas supprimez l'ancien bridge de l'app Matter et appairez de nouveau.
 
+Utilisez **Exporter** pour télécharger une sauvegarde complète de cette instance du bridge, avec fabrics, identifiants privés, sessions et données d'association. **Protégez le fichier comme un mot de passe.** L'import remplace le stockage de cette instance et redémarre brièvement le bridge. Une sauvegarde de bridge ne peut pas être importée dans un contrôleur.
+
 ## Notes
 
 - L'hôte Node-RED doit avoir **IPv6 link-local** activé (exigence standard de Matter) et être joignable par les contrôleurs sur le réseau local.

package/nodes/locales/fr/matterbridge-config.json

@@ -16,7 +16,10 @@
       "deploy_first": "Déployez d'abord ce nœud de configuration, puis cliquez sur actualiser.",
       "reset_button": "Réinitialiser l'appairage",
       "reset_confirm": "Supprimer TOUS les contrôleurs appairés et relancer l'appairage ? Les appareils disparaîtront d'Alexa/Google/Apple.",
-      "reset_ok": "Appairage réinitialisé. Le bridge attend de nouveau un appairage."
+      "reset_ok": "Appairage réinitialisé. Le bridge attend de nouveau un appairage.",
+      "storage_title": "Sauvegarde de la fabric et des associations", "storage_export": "Exporter", "storage_import": "Importer",
+      "storage_warning": "La sauvegarde contient les identifiants de fabric, les clés privées et les données d'association. Protégez-la comme un mot de passe. L'import remplace le stockage Matter de ce bridge et le redémarre brièvement.",
+      "storage_import_confirm": "Remplacer les fabrics Matter et les contrôleurs associés de ce bridge par la sauvegarde sélectionnée ?", "storage_import_ok": "Sauvegarde Matter importée. Le bridge a redémarré."
     }
   }
 }

package/nodes/locales/it/knxUltimateMatterBridge.html

@@ -9,6 +9,8 @@ Ogni nodo Expose KNX to Matter espone **un dispositivo KNX come dispositivo Matt
 
 È la direzione opposta del nodo *Matter Device*: lì KNX controlla un dispositivo Matter, qui i controller Matter controllano KNX.
 
+Cambiare il tipo dispositivo dopo l'abbinamento del bridge modifica la struttura dell'endpoint Matter. I controller possono conservare il vecchio endpoint come irraggiungibile; in tal caso resetta/riabbina il bridge oppure crea un nuovo dispositivo esposto.
+
 ## Configurazione
 
 |Campo|Descrizione|

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

@@ -15,10 +15,14 @@ Il controller comunica con i dispositivi tramite la **rete IP** (WiFi, Ethernet,
 
 Se il dispositivo è nuovo di fabbrica e supporta solo il commissioning Bluetooth, associalo prima con l'app del produttore o con un altro controller Matter (Alexa, Google Home, Apple Home), poi usa la funzione **"condividi / abbina con altro hub"** di quel controller per generare un nuovo codice di abbinamento per KNX-Ultimate. In questo modo il dispositivo entra in più fabric contemporaneamente.
 
+Preferisci il payload QR (`MT:...`): contiene il discriminatore completo. Il codice manuale contiene solo quello corto e può selezionare il dispositivo sbagliato quando più modelli identici sono in modalità abbinamento. Associa un dispositivo alla volta.
+
 ## Archiviazione
 
 Le credenziali della fabric e i dispositivi associati sono salvati nella cartella `knxultimatestorage/matter` dentro la directory utente di Node-RED. Cancellando quella cartella si perdono tutte le associazioni.
 
+Usa **Esporta** per scaricare un backup completo di questa istanza controller. Include fabric, credenziali private, sessioni e dati dei dispositivi associati. **Proteggi il file come una password.** L'importazione sostituisce lo storage Matter di questa istanza e riavvia brevemente il controller. Un backup controller non può essere importato in un bridge.
+
 ## Rimuovere un dispositivo
 
 Usa il pulsante cestino nella lista dei dispositivi associati. Il controller prova a decommissionare correttamente il dispositivo; se non è raggiungibile, viene comunque rimosso dalla fabric (potrebbe poi servire un reset di fabbrica del dispositivo).

package/nodes/locales/it/matter-config.json

@@ -2,7 +2,6 @@
   "matter-config": {
     "properties": {
       "title": "Controller Matter",
-      "intro": "Questo nodo è un controller Matter (con una propria fabric). Associa qui i tuoi dispositivi Matter, poi usa il nodo \"Matter Device\" per mapparli sugli indirizzi di gruppo KNX. Fai prima il deploy del nodo, poi torna qui per associare i dispositivi.",
       "node-config-input-name": "Nome",
       "fabric_label": "Etichetta fabric",
       "pairing_title": "Associa un nuovo dispositivo",
@@ -25,7 +24,13 @@
       "pairing_hint": "Preferisci il QR code (MT:…): contiene il discriminatore completo del dispositivo. Il codice manuale contiene solo un discriminatore corto e non distingue in modo affidabile dispositivi identici (es. più Shelly dello stesso modello), rischiando di associare quello sbagliato o segnalarlo come già registrato. Registra un dispositivo alla volta; se è già associato altrove, fai prima un factory reset.",
       "rename_button": "Rinomina",
       "rename_prompt": "Nuovo nome dispositivo",
-      "rename_ok": "Dispositivo rinominato."
+      "rename_ok": "Dispositivo rinominato.",
+      "storage_title": "Backup fabric e associazioni",
+      "storage_export": "Esporta",
+      "storage_import": "Importa",
+      "storage_warning": "Il backup contiene credenziali fabric, chiavi private e dati dei dispositivi associati. Proteggilo come una password. L'importazione sostituisce lo storage Matter di questo controller e lo riavvia brevemente.",
+      "storage_import_confirm": "Sostituire la fabric Matter e i dispositivi associati di questo controller con il backup selezionato?",
+      "storage_import_ok": "Backup Matter importato. Il controller è stato riavviato."
     }
   }
 }

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

@@ -21,12 +21,16 @@ Questo nodo di configurazione è il **bridge Matter vero e proprio**: esegue il
 2. Il pannello di abbinamento mostra il **QR code** e il **codice manuale**: scansiona o digita in Alexa / Google Home / Apple Home ("aggiungi dispositivo Matter").
 3. Più controller possono essere abbinati allo stesso bridge (multi-fabric Matter).
 
+Per aggiungere un altro controller quando il QR code è nascosto, apri la modalità di abbinamento da un controller già associato, poi aggiungi un dispositivo Matter nel nuovo controller. Usa **Reset abbinamento** solo per rimuovere tutti i controller esistenti e ripartire.
+
 Il pulsante **Reset abbinamento** rimuove tutti i controller abbinati e riavvia l'advertising di abbinamento.
 
 ## Identità e archiviazione
 
 L'identità del bridge è legata a questo nodo di configurazione ed è salvata in `knxultimatestorage/matter` nella directory utente di Node-RED: i re-deploy (anche cambiando porta o nome) **NON** richiedono un nuovo abbinamento. Solo eliminando questo nodo di configurazione e creandone uno nuovo cambia l'identità — in quel caso rimuovi il vecchio bridge dall'app Matter e riabbina.
 
+Usa **Esporta** per scaricare un backup completo di questa istanza bridge, incluse fabric, credenziali private, sessioni e dati di abbinamento. **Proteggi il file come una password.** L'importazione sostituisce lo storage dell'istanza e riavvia brevemente il bridge. Un backup bridge non può essere importato in un controller.
+
 ## Note
 
 - L'host Node-RED deve avere **IPv6 link-local** attivo (requisito standard Matter) ed essere raggiungibile dai controller sulla rete locale.

package/nodes/locales/it/matterbridge-config.json

@@ -16,7 +16,10 @@
       "deploy_first": "Fai prima il deploy di questo nodo di configurazione, poi clicca aggiorna.",
       "reset_button": "Reset abbinamento",
       "reset_confirm": "Rimuovere TUTTI i controller abbinati e riavviare l'abbinamento? I dispositivi spariranno da Alexa/Google/Apple.",
-      "reset_ok": "Abbinamento resettato. Il bridge è di nuovo in attesa di abbinamento."
+      "reset_ok": "Abbinamento resettato. Il bridge è di nuovo in attesa di abbinamento.",
+      "storage_title": "Backup fabric e associazioni", "storage_export": "Esporta", "storage_import": "Importa",
+      "storage_warning": "Il backup contiene credenziali fabric, chiavi private e dati di abbinamento. Proteggilo come una password. L'importazione sostituisce lo storage Matter di questo bridge e lo riavvia brevemente.",
+      "storage_import_confirm": "Sostituire le fabric Matter e i controller abbinati di questo bridge con il backup selezionato?", "storage_import_ok": "Backup Matter importato. Il bridge è stato riavviato."
     }
   }
 }

package/nodes/locales/zh-CN/knxUltimateMatterBridge.html

@@ -9,6 +9,8 @@
 
 这与 *Matter Device* 节点方向相反：那里是 KNX 控制 Matter 设备，这里是 Matter 控制器控制 KNX。
 
+桥接器配对后更改设备类型会改变 Matter 端点结构。控制器可能会将旧端点保留为不可达；此时请重置并重新配对桥接器，或创建新的公开设备。
+
 ## 配置
 
 |字段|说明|

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

@@ -15,10 +15,14 @@
 
 如果设备是全新的且仅支持蓝牙配对，请先用厂商 App 或其他 Matter 控制器（Alexa、Google Home、Apple Home）配对，然后使用其**"与其他中枢共享/配对"**功能为 KNX-Ultimate 生成新的配对码。这样设备可以同时加入多个 fabric。
 
+优先使用二维码 payload（`MT:...`），因为它包含完整的鉴别码。手动配对码只包含短鉴别码；当多个相同型号同时处于配对模式时，可能会选错设备。请一次只配对一个设备。
+
 ## 存储
 
 Fabric 凭据和已配对设备保存在 Node-RED 用户目录下的 `knxultimatestorage/matter` 文件夹中。删除该文件夹将移除所有配对。
 
+使用 **导出** 下载此控制器实例的完整备份，其中包含 Fabric、私有凭据、会话和已配网设备数据。**请像密码一样保护此文件。** 导入会替换此实例当前的 Matter 存储并短暂重启控制器。控制器备份不能导入网桥。
+
 ## 移除设备
 
 使用已配对设备列表中的垃圾桶按钮。控制器会尝试正确地解除设备调试；如果设备无法访问，仍会从 fabric 中移除（之后可能需要对设备进行恢复出厂设置）。

package/nodes/locales/zh-CN/matter-config.json

@@ -2,7 +2,6 @@
   "matter-config": {
     "properties": {
       "title": "Matter 控制器",
-      "intro": "此节点是一个 Matter 控制器（拥有自己的 fabric）。在此配对您的 Matter 设备，然后使用 \"Matter Device\" 节点将其映射到 KNX 组地址。请先部署该节点，然后回到这里配对设备。",
       "node-config-input-name": "名称",
       "fabric_label": "Fabric 标签",
       "pairing_title": "配对新设备",
@@ -24,7 +23,13 @@
       "pairing_ok": "设备配对成功！",
       "rename_button": "重命名",
       "rename_prompt": "新的设备名称",
-      "rename_ok": "设备已重命名。"
+      "rename_ok": "设备已重命名。",
+      "storage_title": "Fabric 和配网备份",
+      "storage_export": "导出",
+      "storage_import": "导入",
+      "storage_warning": "备份包含 Fabric 凭据、私钥和已配网设备数据。请像密码一样妥善保管。导入会替换此控制器的 Matter 存储并短暂重启。",
+      "storage_import_confirm": "要用所选备份替换此控制器的 Matter Fabric 和已配网设备吗？",
+      "storage_import_ok": "Matter 备份已导入，控制器已重启。"
     }
   }
 }

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

@@ -21,12 +21,16 @@
 2. 配对面板显示**二维码**和**手动配对码**：在 Alexa / Google Home / Apple Home 中扫描或输入（"添加 Matter 设备"）。
 3. 多个控制器可以与同一个桥接器配对（Matter 多 fabric）。
 
+二维码隐藏后如需添加其他控制器，请从一个已配对的控制器开启配对模式，然后在新控制器中添加 Matter 设备。仅在需要移除所有现有控制器并重新开始时使用**重置配对**。
+
 **重置配对**按钮会移除所有已配对的控制器并重新开始配对广播。
 
 ## 身份与存储
 
 桥接器身份与此配置节点绑定，保存在 Node-RED 用户目录的 `knxultimatestorage/matter` 中：重新部署（即使更改端口或名称）**不**需要重新配对。只有删除此配置节点并新建一个才会改变身份——此时请从 Matter App 中移除旧桥接器并重新配对。
 
+使用 **导出** 下载此网桥实例的完整备份，其中包含 Fabric、私有凭据、会话和配对数据。**请像密码一样保护此文件。** 导入会替换此实例的存储并短暂重启网桥。网桥备份不能导入控制器。
+
 ## 说明
 
 - Node-RED 主机必须启用 **IPv6 link-local**（Matter 标准要求），并且控制器可在本地网络访问到它。

package/nodes/locales/zh-CN/matterbridge-config.json

@@ -16,7 +16,10 @@
       "deploy_first": "请先部署此配置节点，然后点击刷新。",
       "reset_button": "重置配对",
       "reset_confirm": "移除所有已配对的控制器并重新开始配对？设备将从 Alexa/Google/Apple 中消失。",
-      "reset_ok": "配对已重置。桥接器重新进入配对模式。"
+      "reset_ok": "配对已重置。桥接器重新进入配对模式。",
+      "storage_title": "Fabric 和配网备份", "storage_export": "导出", "storage_import": "导入",
+      "storage_warning": "备份包含 Fabric 凭据、私钥和配对数据。请像密码一样妥善保管。导入会替换此网桥的 Matter 存储并短暂重启。",
+      "storage_import_confirm": "要用所选备份替换此网桥的 Matter Fabric 和已配对控制器吗？", "storage_import_ok": "Matter 备份已导入，网桥已重启。"
     }
   }
 }

package/nodes/matter-config.html

@@ -3,6 +3,7 @@
 <script type="text/javascript">
     RED.nodes.registerType('matter-config', {
         category: 'config',
+        icon: 'node-matter-controller-icon.svg',
         defaults: {
             name: { value: "Matter Controller" },
             fabricLabel: { value: "KNX-Ultimate" }
@@ -20,6 +21,23 @@
             var $devicesBody = $("#matter-devices-body");
             var $refreshDevices = $("#matterRefreshDevices");
             var $pairSpinner = $("#matterPairSpinner");
+            var $storageExport = $('#matter-storage-export');
+            var $storageImport = $('#matter-storage-import');
+            var $storageFile = $('#matter-storage-file');
+
+            function storageExportUrl() {
+                var adminRoot = (RED.settings && typeof RED.settings.httpAdminRoot === 'string') ? RED.settings.httpAdminRoot : '/';
+                adminRoot = String(adminRoot || '/').trim();
+                adminRoot = adminRoot === '/' ? '' : '/' + adminRoot.replace(/^\/+|\/+$/g, '');
+                var params = new URLSearchParams();
+                params.set('serverId', node.id);
+                params.set('_', String(Date.now()));
+                try {
+                    var tokens = (RED.settings && typeof RED.settings.get === 'function') ? RED.settings.get('auth-tokens') : null;
+                    if (tokens && typeof tokens.access_token === 'string' && tokens.access_token.trim() !== '') params.set('access_token', tokens.access_token.trim());
+                } catch (error) { }
+                return adminRoot + '/KNXUltimateMatterStorageExport?' + params.toString();
+            }
 
             function notifyPairingError(msg) {
                 var text = RED._("node-red-contrib-knx-ultimate/matter-config:matter-config.properties.pairing_failed") + ': ' + (msg || '');
@@ -148,6 +166,32 @@
             });
 
             loadDevices();
+
+            $storageExport.on('click', function () {
+                window.location = storageExportUrl();
+            });
+            $storageImport.on('click', function () { $storageFile.trigger('click'); });
+            $storageFile.on('change', function () {
+                var file = this.files && this.files[0];
+                this.value = '';
+                if (!file || !window.confirm(RED._('node-red-contrib-knx-ultimate/matter-config:matter-config.properties.storage_import_confirm'))) return;
+                var reader = new FileReader();
+                reader.onload = function () {
+                    var backup;
+                    try { backup = JSON.parse(reader.result); } catch (error) { RED.notify(error.message, { type: 'error' }); return; }
+                    $storageImport.prop('disabled', true);
+                    $.ajax({
+                        url: 'KNXUltimateMatterStorageImport?serverId=' + encodeURIComponent(node.id),
+                        method: 'POST', contentType: 'application/json', data: JSON.stringify(backup)
+                    }).done(function () {
+                        RED.notify(RED._('node-red-contrib-knx-ultimate/matter-config:matter-config.properties.storage_import_ok'), { type: 'success' });
+                        loadDevices();
+                    }).fail(function (xhr) {
+                        RED.notify((xhr.responseJSON && xhr.responseJSON.error) || xhr.statusText, { type: 'error', fixed: true });
+                    }).always(function () { $storageImport.prop('disabled', false); });
+                };
+                reader.readAsText(file);
+            });
         },
         oneditsave: function () {
             // Return to the info tab
@@ -167,7 +211,6 @@
   </div>
 
   <div class="form-row">
-    <b><span data-i18n="matter-config.properties.title"></span></b>
     <p align="center" style="margin:8px 0;">
       <svg width="70" height="77" viewBox="0 8 40 44" xmlns="http://www.w3.org/2000/svg" aria-label="Matter" style="vertical-align:middle;">
         <g fill="currentColor" stroke="none">
@@ -187,9 +230,8 @@
         </g>
       </svg>
       <br/>
-      <span style="font-size:18px; font-weight:600; letter-spacing:1px;">matter</span>
+      <span style="font-size:18px; font-weight:600; letter-spacing:1px;" data-i18n="matter-config.properties.title"></span>
     </p>
-    <p><span data-i18n="matter-config.properties.intro"></span></p>
   </div>
 
   <div class="form-row">
@@ -210,9 +252,17 @@
 
   <hr/>
 
+  <div class="form-row">
+    <b><i class="fa fa-database"></i>&nbsp;<span data-i18n="matter-config.properties.storage_title"></span></b>
+    <button type="button" id="matter-storage-export" class="red-ui-button" style="margin-left:8px;"><i class="fa fa-download"></i>&nbsp;<span data-i18n="matter-config.properties.storage_export"></span></button>
+    <button type="button" id="matter-storage-import" class="red-ui-button"><i class="fa fa-upload"></i>&nbsp;<span data-i18n="matter-config.properties.storage_import"></span></button>
+    <input type="file" id="matter-storage-file" accept="application/json,.json" style="display:none;">
+  </div>
+
+  <hr/>
+
   <div class="form-row">
     <b><i class="fa fa-qrcode"></i>&nbsp;<span data-i18n="matter-config.properties.pairing_title"></span></b>
-    <p><span data-i18n="matter-config.properties.pairing_help"></span></p>
   </div>
 
   <div class="form-row">
@@ -236,15 +286,6 @@
     </label>
     <input type="text" id="matter-pairing-name" placeholder="Kitchen plug" style="width:250px;">
   </div>
-  <div class="form-tips" style="margin: 4px 0 8px; font-size:12px;">
-    <i class="fa fa-circle-info" style="color:#1b7d33; margin-right:4px;"></i>
-    <span data-i18n="matter-config.properties.pairing_hint">Prefer the QR code (MT:…): it carries the full device discriminator. The manual code
-    stores only a short discriminator and cannot reliably tell identical devices apart
-    (e.g. several Shelly of the same model), which can pair the wrong one or report it as
-    already commissioned. Pair one device at a time; if a device is already paired
-    elsewhere, factory-reset it first.</span>
-  </div>
-
   <hr/>
 
   <div class="form-row">
@@ -270,9 +311,9 @@
   </div>
 
   <br/>
-   <br/>
-    <br/>
-    <br/>
-   <br/>
-    <br/>
+  <br/>
+  <br/>
+  <br/>
+  <br/>
+  <br/>
 </script>

package/nodes/matter-config.js

@@ -1,5 +1,8 @@
 /* eslint-disable max-len */
 const path = require('path')
+const { exportMatterStorage, importMatterStorage } = require('./utils/matterStorageBackup')
+const matterPackageVersion = require('@matter/main').version
+const { Specification } = require('@matter/model')
 
 // 10/09/2024 Setup the color logger
 const loggerSetup = (options) => {
@@ -18,6 +21,7 @@ module.exports = (RED) => {
     node.sysLogger = null
     node.matterManager = null
     node.timerMatterConfigCheckState = null
+    node.storageOperation = null
     try {
       node.sysLogger = loggerSetup({ loglevel: node.loglevel, setPrefix: 'matter-config.js' })
     } catch (error) { console.log(error.stack) }
@@ -190,6 +194,35 @@ module.exports = (RED) => {
       if (node.matterManager === null) throw new Error('Matter controller not started')
       return node.matterManager.renameNode(_nodeId, _label)
     }
+
+    const withStoppedController = async (operation) => {
+      if (node.storageOperation !== null) throw new Error('Another Matter storage operation is already running')
+      node.storageOperation = (async () => {
+        if (node.matterManager !== null) await node.matterManager.close()
+        node.matterManager = null
+        try {
+          return await operation()
+        } finally {
+          await node.initMatterConnection()
+        }
+      })()
+      try { return await node.storageOperation } finally { node.storageOperation = null }
+    }
+
+    node.exportMatterStorage = () => withStoppedController(() => exportMatterStorage({
+      storagePath: node.matterStoragePath,
+      instanceId: node.matterInstanceId,
+      kind: 'controller',
+      protocolVersion: Specification.REVISION,
+      packageVersion: matterPackageVersion
+    }))
+
+    node.importMatterStorage = (backup) => withStoppedController(() => importMatterStorage({
+      storagePath: node.matterStoragePath,
+      instanceId: node.matterInstanceId,
+      kind: 'controller',
+      backup
+    }))
     // END functions called from the nodes -------------------------------------------------------------
 
     node.addClient = (_Node) => {

package/nodes/matterbridge-config.html

@@ -3,6 +3,7 @@
 <script type="text/javascript">
     RED.nodes.registerType('matterbridge-config', {
         category: 'config',
+        icon: 'node-matter-bridge-icon.svg',
         defaults: {
             name: { value: '' },
             bridgeDeviceName: { value: '' },
@@ -15,6 +16,21 @@
             var $pairingBody = $('#mbc-pairing-body');
             var $refreshPairing = $('#mbc-refresh-pairing');
             var $resetButton = $('#mbc-factory-reset');
+            var $storageFile = $('#mbc-storage-file');
+
+            function storageExportUrl() {
+                var adminRoot = (RED.settings && typeof RED.settings.httpAdminRoot === 'string') ? RED.settings.httpAdminRoot : '/';
+                adminRoot = String(adminRoot || '/').trim();
+                adminRoot = adminRoot === '/' ? '' : '/' + adminRoot.replace(/^\/+|\/+$/g, '');
+                var params = new URLSearchParams();
+                params.set('configId', node.id);
+                params.set('_', String(Date.now()));
+                try {
+                    var tokens = (RED.settings && typeof RED.settings.get === 'function') ? RED.settings.get('auth-tokens') : null;
+                    if (tokens && typeof tokens.access_token === 'string' && tokens.access_token.trim() !== '') params.set('access_token', tokens.access_token.trim());
+                } catch (error) { }
+                return adminRoot + '/KNXUltimateMatterBridgeStorageExport?' + params.toString();
+            }
 
             var t = function (key) {
                 return RED._('node-red-contrib-knx-ultimate/matterbridge-config:matterbridge-config.properties.' + key);
@@ -37,7 +53,6 @@
                         info.fabrics.forEach(function (f) {
                             $pairingBody.append($('<div style="margin-left:10px;"></div>').text('• ' + (f.label || 'Controller') + ' (vendor ' + f.vendorId + ')'));
                         });
-                        $pairingBody.append($('<p style="max-width:760px; margin:14px auto 0; color:#777;"></p>').text(t('commissioned_hint')));
                         $resetButton.show();
                         return;
                     }
@@ -69,6 +84,26 @@
                     loadPairingInfo();
                 }).always(function () { $resetButton.prop('disabled', false); });
             });
+            $('#mbc-storage-export').on('click', function () {
+                window.location = storageExportUrl();
+            });
+            $('#mbc-storage-import').on('click', function () { $storageFile.trigger('click'); });
+            $storageFile.on('change', function () {
+                var file = this.files && this.files[0];
+                this.value = '';
+                if (!file || !window.confirm(t('storage_import_confirm'))) return;
+                var reader = new FileReader();
+                reader.onload = function () {
+                    var backup;
+                    try { backup = JSON.parse(reader.result); } catch (error) { RED.notify(error.message, { type: 'error' }); return; }
+                    $('#mbc-storage-import').prop('disabled', true);
+                    $.ajax({ url: 'KNXUltimateMatterBridgeStorageImport?configId=' + encodeURIComponent(node.id), method: 'POST', contentType: 'application/json', data: JSON.stringify(backup) })
+                        .done(function () { RED.notify(t('storage_import_ok'), { type: 'success' }); loadPairingInfo(); })
+                        .fail(function (xhr) { RED.notify((xhr.responseJSON && xhr.responseJSON.error) || xhr.statusText, { type: 'error', fixed: true }); })
+                        .always(function () { $('#mbc-storage-import').prop('disabled', false); });
+                };
+                reader.readAsText(file);
+            });
 
             loadPairingInfo();
         },
@@ -87,8 +122,27 @@
   </div>
 
   <div class="form-row">
-    <b><span data-i18n="matterbridge-config.properties.title"></span></b>
-    <p><span data-i18n="matterbridge-config.properties.intro"></span></p>
+    <p align="center" style="margin:8px 0;">
+      <svg width="70" height="77" viewBox="0 8 40 44" xmlns="http://www.w3.org/2000/svg" aria-label="Matter" style="vertical-align:middle;">
+        <g fill="currentColor" stroke="none">
+          <circle cx="20" cy="30" r="4.5"/>
+          <g>
+            <rect x="18.4" y="9" width="3.2" height="11"/>
+            <path d="M 14.5 18.5 L 25.5 18.5 L 20 25.5 Z"/>
+          </g>
+          <g transform="rotate(120 20 30)">
+            <rect x="18.4" y="9" width="3.2" height="11"/>
+            <path d="M 14.5 18.5 L 25.5 18.5 L 20 25.5 Z"/>
+          </g>
+          <g transform="rotate(240 20 30)">
+            <rect x="18.4" y="9" width="3.2" height="11"/>
+            <path d="M 14.5 18.5 L 25.5 18.5 L 20 25.5 Z"/>
+          </g>
+        </g>
+      </svg>
+      <br/>
+      <span style="font-size:18px; font-weight:600; letter-spacing:1px;" data-i18n="matterbridge-config.properties.title"></span>
+    </p>
   </div>
 
   <div class="form-row">
@@ -109,6 +163,15 @@
 
   <hr/>
 
+  <div class="form-row">
+    <b><i class="fa fa-database"></i>&nbsp;<span data-i18n="matterbridge-config.properties.storage_title"></span></b>
+    <button type="button" id="mbc-storage-export" class="red-ui-button" style="margin-left:8px;"><i class="fa fa-download"></i>&nbsp;<span data-i18n="matterbridge-config.properties.storage_export"></span></button>
+    <button type="button" id="mbc-storage-import" class="red-ui-button"><i class="fa fa-upload"></i>&nbsp;<span data-i18n="matterbridge-config.properties.storage_import"></span></button>
+    <input type="file" id="mbc-storage-file" accept="application/json,.json" style="display:none;">
+  </div>
+
+  <hr/>
+
   <div class="form-row">
     <b><i class="fa fa-qrcode"></i>&nbsp;<span data-i18n="matterbridge-config.properties.pairing_title"></span></b>
     <button type="button" id="mbc-refresh-pairing" class="red-ui-button" style="margin-left:6px; color:#1b7d33; border-color:#1b7d33;">
@@ -119,4 +182,11 @@
     </button>
   </div>
   <div class="form-row" id="mbc-pairing-body" style="text-align:center;"></div>
+
+  <br/>
+  <br/>
+  <br/>
+  <br/>
+  <br/>
+  <br/>
 </script>

package/nodes/matterbridge-config.js

@@ -1,5 +1,8 @@
 /* eslint-disable max-len */
 const path = require('path')
+const { exportMatterStorage, importMatterStorage } = require('./utils/matterStorageBackup')
+const matterPackageVersion = require('@matter/main').version
+const { Specification } = require('@matter/model')
 
 // 10/09/2024 Setup the color logger
 const loggerSetup = (options) => {
@@ -39,6 +42,7 @@ module.exports = (RED) => {
     let startupTimer = null
     let reconcileTimer = null
     let closing = false
+    let storageOperation = null
 
     Object.defineProperty(node, 'linkStatus', {
       get: function () {
@@ -193,6 +197,40 @@ module.exports = (RED) => {
       await node.matterBridge.factoryReset()
       notifyClientsStatus()
     }
+
+    const withStoppedBridge = async (operation) => {
+      if (storageOperation !== null) throw new Error('Another Matter storage operation is already running')
+      storageOperation = (async () => {
+        const engine = node.matterBridge
+        if (engine !== null) {
+          engine.removeAllListeners()
+          await engine.close()
+          runningBridges.delete(node.id)
+          node.matterBridge = null
+        }
+        try {
+          return await operation()
+        } finally {
+          await ensureEngineStarted()
+        }
+      })()
+      try { return await storageOperation } finally { storageOperation = null }
+    }
+
+    node.exportMatterStorage = () => withStoppedBridge(() => exportMatterStorage({
+      storagePath: node.matterStoragePath,
+      instanceId: node.matterInstanceId,
+      kind: 'bridge',
+      protocolVersion: Specification.REVISION,
+      packageVersion: matterPackageVersion
+    }))
+
+    node.importMatterStorage = (backup) => withStoppedBridge(() => importMatterStorage({
+      storagePath: node.matterStoragePath,
+      instanceId: node.matterInstanceId,
+      kind: 'bridge',
+      backup
+    }))
     // END functions called from the device nodes -------------------------------------
 
     node.on('close', (removed, done) => {

package/nodes/utils/matterStorageBackup.js

@@ -0,0 +1,100 @@
+const fs = require('fs/promises')
+const path = require('path')
+
+const BACKUP_FORMAT = 'knx-ultimate-matter-storage'
+const BACKUP_VERSION = 1
+const MAX_BACKUP_BYTES = 64 * 1024 * 1024
+
+const instancePath = (storagePath, instanceId) => path.join(storagePath, instanceId)
+
+const listFiles = async (root, current = root) => {
+  const entries = await fs.readdir(current, { withFileTypes: true })
+  const files = []
+  for (const entry of entries) {
+    if (entry.isSymbolicLink()) throw new Error('Matter storage contains an unsupported symbolic link')
+    const absolute = path.join(current, entry.name)
+    if (entry.isDirectory()) files.push(...await listFiles(root, absolute))
+    else if (entry.isFile()) files.push(path.relative(root, absolute).split(path.sep).join('/'))
+  }
+  return files.sort()
+}
+
+const exportMatterStorage = async ({ storagePath, instanceId, kind, protocolVersion, packageVersion }) => {
+  const root = instancePath(storagePath, instanceId)
+  let names
+  try {
+    names = await listFiles(root)
+  } catch (error) {
+    if (error.code === 'ENOENT') names = []
+    else throw error
+  }
+  const files = []
+  let totalBytes = 0
+  for (const name of names) {
+    const content = await fs.readFile(path.join(root, ...name.split('/')))
+    totalBytes += content.length
+    if (totalBytes > MAX_BACKUP_BYTES) throw new Error('Matter backup exceeds the 64 MB safety limit')
+    files.push({ path: name, content: content.toString('base64') })
+  }
+  return {
+    format: BACKUP_FORMAT,
+    version: BACKUP_VERSION,
+    kind,
+    createdAt: new Date().toISOString(),
+    sourceInstanceId: instanceId,
+    matterProtocolVersion: protocolVersion,
+    matterPackageVersion: packageVersion,
+    files
+  }
+}
+
+const validateRelativePath = (name) => {
+  if (typeof name !== 'string' || name === '' || name.includes('\\')) return false
+  const normalized = path.posix.normalize(name)
+  return normalized === name && !path.posix.isAbsolute(name) && name !== '..' && !name.startsWith('../')
+}
+
+const importMatterStorage = async ({ storagePath, instanceId, kind, backup }) => {
+  if (!backup || backup.format !== BACKUP_FORMAT || backup.version !== BACKUP_VERSION) throw new Error('Unsupported Matter backup file')
+  if (backup.kind !== kind) throw new Error(`This is a Matter ${backup.kind || 'unknown'} backup, not a ${kind} backup`)
+  if (!Array.isArray(backup.files)) throw new Error('Invalid Matter backup: files are missing')
+
+  const decoded = []
+  const seen = new Set()
+  let totalBytes = 0
+  for (const file of backup.files) {
+    if (!file || !validateRelativePath(file.path) || seen.has(file.path) || typeof file.content !== 'string') throw new Error('Invalid Matter backup file entry')
+    const content = Buffer.from(file.content, 'base64')
+    totalBytes += content.length
+    if (totalBytes > MAX_BACKUP_BYTES) throw new Error('Matter backup exceeds the 64 MB safety limit')
+    seen.add(file.path)
+    decoded.push({ path: file.path, content })
+  }
+
+  await fs.mkdir(storagePath, { recursive: true })
+  const target = instancePath(storagePath, instanceId)
+  const temporary = `${target}.import-${process.pid}-${Date.now()}`
+  const previous = `${target}.previous-${process.pid}-${Date.now()}`
+  await fs.mkdir(temporary, { recursive: true })
+  try {
+    for (const file of decoded) {
+      const destination = path.join(temporary, ...file.path.split('/'))
+      await fs.mkdir(path.dirname(destination), { recursive: true })
+      await fs.writeFile(destination, file.content, { mode: 0o600 })
+    }
+    let hadTarget = true
+    try { await fs.rename(target, previous) } catch (error) { if (error.code === 'ENOENT') hadTarget = false; else throw error }
+    try {
+      await fs.rename(temporary, target)
+    } catch (error) {
+      if (hadTarget) await fs.rename(previous, target)
+      throw error
+    }
+    if (hadTarget) await fs.rm(previous, { recursive: true, force: true })
+  } catch (error) {
+    await fs.rm(temporary, { recursive: true, force: true })
+    throw error
+  }
+}
+
+module.exports = { exportMatterStorage, importMatterStorage, BACKUP_FORMAT, BACKUP_VERSION, MAX_BACKUP_BYTES }

package/package.json

@@ -3,7 +3,7 @@
   "engines": {
     "node": ">=20.18.1"
   },
-  "version": "6.0.5",
+  "version": "6.0.6",
   "description": "Control your KNX and KNX Secure intallation via Node-Red! A bunch of KNX nodes, with integrated Philips HUE control, ETS group address importer, KNX AI for diagnosticsand KNX routing between interfaces. Easy to use and highly configurable.",
   "files": [
     "nodes/",

package/resources/htmlUtils.js

@@ -1,6 +1,17 @@
 /* global window, document, MutationObserver, $, jQuery */
 /* eslint-disable camelcase */
 
+// Keep informational tips aligned with the full width of our Node-RED editor forms.
+// Node-RED applies a max-width to .form-tips by default, which otherwise leaves
+// inconsistent empty space in wider edit dialogs.
+;(function ensureKnxUltimateEditorStyles () {
+  if (document.getElementById('knx-ultimate-editor-styles')) return
+  const style = document.createElement('style')
+  style.id = 'knx-ultimate-editor-styles'
+  style.textContent = '.form-tips { width: 100% !important; max-width: none !important; box-sizing: border-box !important; background-color: #e8f5e9 !important; }'
+  document.head.appendChild(style)
+})()
+
 // 31/03/2020 Search Helper
 function htmlUtilsfullCSVSearch (sourceText, searchString) {
   let aSearchWords = []