node-red-contrib-knx-ultimate 7.1.4 → 8.0.2

package/nodes/locales/en/knxUltimateStaircase.json

@@ -1,62 +0,0 @@
-{
-  "knxUltimateStaircase": {
-    "title": "Staircase light",
-    "paletteLabel": "Staircase (deprecated)",
-    "node-input-server": "KNX Gateway",
-    "node-input-name": "Name",
-    "node-input-outputtopic": "Topic for emitted events",
-    "trigger": "Trigger GA",
-    "output": "Output GA",
-    "status": "Status GA",
-    "override": "Override GA",
-    "block": "Block GA",
-    "node-input-timerSeconds": "Timer duration (seconds)",
-    "node-input-extendMode": "On new trigger",
-    "extend_restart": "Restart timer",
-    "extend_extend": "Extend remaining time",
-    "extend_ignore": "Ignore the trigger",
-    "node-input-triggerOffCancels": "0 command cancels the cycle",
-    "opt_yes": "Yes",
-    "opt_no": "No",
-    "node-input-blockAction": "When blocked",
-    "block_off": "Force light OFF",
-    "block_keep": "Leave current state",
-    "node-input-preWarnEnable": "Send pre-warning before timeout",
-    "node-input-preWarnSeconds": "Pre-warning offset (seconds)",
-    "node-input-preWarnMode": "Pre-warning mode",
-    "prewarn_status": "Toggle status GA",
-    "prewarn_flash": "Flash output",
-    "node-input-preWarnFlashMs": "Flash duration (ms)",
-    "node-input-emitEvents": "Emit events on node output",
-    "help": {
-      "intro": "Implements a staircase light logic with KNX integration, handling timer, pre-warning, manual override and blocking.",
-      "trigger": "Triggers",
-      "trigger_ga": "A rising edge (value = 1) on the trigger GA starts the timer. If enabled, a value of 0 will immediately cancel the cycle.",
-      "extend": "The \"On new trigger\" option controls how subsequent pulses behave: restart the timer, extend the remaining time or ignore the pulse.",
-      "off": "When override is active the timer is paused and the light stays on. Blocking disables new pulses and optionally forces the output off.",
-      "outputs": "Group addresses",
-      "output_ga": "Output GA is driven with DPT 1.001 by default. Configure other DPTs if required.",
-      "status_ga": "Status GA mirrors the stair light state (and the pre-warning flag when enabled).",
-      "override_ga": "Override GA keeps the light on while true and suspends the timer.",
-      "block_ga": "Block GA prevents new activations. When false, normal behaviour resumes.",
-      "prewarn": "Pre-warning",
-      "prewarn_desc": "Enable a pre-warning to alert occupants before the light turns off. You can either flash the output or toggle the status GA.",
-      "events": "Node output",
-      "events_desc": "When enabled the node emits structured events (trigger, extend, prewarn, timeout, override, block) with the remaining time and state information."
-    },
-    "placeholders": {
-      "outputtopic": "Optional topic for node events",
-      "ga": "e.g. 1/1/5",
-      "triggerName": "Trigger device name",
-      "outputName": "Output actuator name",
-      "statusName": "Status feedback name",
-      "overrideName": "Override channel name",
-      "blockName": "Block command name"
-    },
-    "section_commands": "Command group addresses",
-    "section_inputs": "Input group addresses",
-    "legacy_notice": "This node is deprecated and remains supported for existing flows. Use KNX Utility for new flows. The button below converts all compatible legacy KNX utility nodes in every flow and subflow.",
-    "migration_button": "Convert all compatible legacy KNX nodes",
-    "migration_button_title": "Convert every compatible legacy KNX utility instance in all editor flows and subflows to KNX Utility"
-  }
-}

package/nodes/locales/en/knxUltimateWatchDog.html

@@ -1,244 +0,0 @@
-<script type="text/markdown" data-help-name="knxUltimateWatchDog">
-### Upgrade to KNX Ultimate 8
-
-Version 7 shows a compact **Upgrade to v8** button at the top of this editor. It downloads a flow backup, installs the required HUE/Matter packages, converts compatible nodes, performs a full Deploy, verifies the saved flows and installs version 8. Restart the Node-RED service when prompted; reloading only the browser is not enough. Legacy KNX AI nodes stop the automatic operation.
-
-[Full upgrade guide](https://supergiovane.github.io/node-red-contrib-knx-ultimate/wiki/Upgrade-to-v8)
-
-<br/>
-
-**Deprecated:** This dedicated node remains supported for existing flows. Use **KNX Utility** for new flows and select the matching function. The legacy node is hidden from the palette and marked `(deprecated)` on the canvas. Its editor offers a button to convert all compatible legacy KNX utility nodes in every flow and subflow after confirmation. Conversion happens locally in the browser, preserves IDs, settings, connections and groups, and supports Undo. Confirming closes the current node editor and discards unsaved edits. Review the result before Deploy.
-
-<p>Checks the connection to the Gateway or to a specific KNX device</p>
-
-# WatchDog
-
-**What does it do?**
-
-1. Checks for the healty of KNX BUS communication/connection by sending a telegram at regular intervals, watching for a response and sends a msg to the flow if a connection to KNX Bus is broken. Two check levels, see below.
-2. Programmatically changes the Configuration Node parameters, thus the connection to your KNX/IP Router/Interface (for example, if you have 2 KNX/IP Routers and you want to switch between the two for connection backup).
-3. Forces the gateway's connection/disconnection from/to the KNX BUS.
-
-## Ethernet level and KNX Twisted Pair level checks
-
-The WatchDog has two check levels.
-
-The first, checks only the connection between knx-Ultimate and the KNX/IP Interface.
-
-The second one, checks the entire route, from knx-Ultimate Gateway node to ethernet, then to KNX TP media and vice versa; this implies the use of a physical device, responding to a read requests.
-
-The WatchDog node is a powerfull node for signalling errors and connection problems. <br />
-
-You can send an Email to the KNX installer responsible to your Building, or you can automatically switch to a backup KNX/IP Router/Interface in your installation.
-
-## SETTINGS
-
-| Property | Description |
-| ----------------------------- | --------------------------------------------------------------------------------------------------- |
-| Gateway | Selected KNX gateway. |
-| Group Address to monitor | The node will send a telegram to this address and monitors the message flowing through the KNX BUS. The Datapoint must be DPT 1.x (boolean).|
-| Node Name | Node Name |
-| Auto start the watchdog timer | The watchdog timer starts automatically on deploy or on node-red start. |
-| Listen to KNX-Ultimate node errors | Enabled by default. Outputs a `NodeError` when a KNX-Ultimate node associated with the selected gateway, including KNX Device, reports a red error status. Disabling it suppresses only those `NodeError` messages; the WatchDog's own bus checks and control messages remain active. |
-| Check level (please see the wiki) | See below |
-
-**Check level** > _**Ethernet**_: Checks the connection between knx-ultimate Gateway in unicast mode and your KNX IP Interface.<br />
-
-<img src="https://raw.githubusercontent.com/Supergiovane/node-red-contrib-knx-ultimate/master/img/wiki/WatchDogEthernetLevel.png"
- width="90%"><br />
-
-> _ **Ethernet and KNX TP** _ : Complete check. It works either with KNX/IP Routers and KNX/IP Interfaces (as well as
-
-address set), it checks the connection between KNX-Ultimate and this physical KNX device, by issuing a read request and by awaiting a response telegram from this device. Any error on the ethernet trunk or on the KNX Twisted Pair trunk will be notified. To setup this check level, you need to reserve a Group Address and add it to a "Status" output of your KNX Actuator. For example, if you have a light actuator, it has for sure a "light status" output that can **respond** to a **read request**.
-
-About this picture, in ETS, assign an Output of this Gira KNX Actuator to a Light **Status** (for example 12/0/0). Everytime the Watchdog node asks for the status, the Gira KNX Actuator will respond. The WatchDog then know, that your KNX
-
-Twisted Pair connection is up and running.
-
-<img src="https://raw.githubusercontent.com/Supergiovane/node-red-contrib-knx-ultimate/master/img/wiki/WatchDogEthernetKNXTPLevel.png"
- width="90%"><br />
-
-## ADVANCED OPTIONS
-
-| Property | Description |
-| -------- | ----------- |
-| Retry interval (in seconds) | The node sends a telegram to the KNX bus at this time interva, in seconds. |
-| Number of retry before giving an error |After the telegram has been sent for this amount of times, without any response from KNX Bus, the node throws an error. |
-
-# MESSAGE OUTPUT FROM THE WATCHDOG
-
-The WatchDog always outputs its own bus-check and control messages. When **Listen to KNX-Ultimate node errors** is enabled, it also outputs errors reported by KNX-Ultimate nodes, including KNX Device, associated with the selected gateway.<br />
-
-**In case of Watchdog self connection problem**
-
-<a href="https://supergiovane.github.io/node-red-contrib-knx-ultimate/wiki/WatchDog-Configuration"
- target="_blank">Please see here.</a>
-
-```javascript
-
-msg = {
-type:"BUSError"
-checkPerformed: "Ethernet" for basic check, or "Eth+KNX" for full check.
-nodeid: "23HJ.2355" // (The node ID causing the error, so you can find it using node-red "search" funtion)
-payload: true
-description: // (whatever error description)
-}
-
-```
-
-<br />
-
-**When KNX-Ultimate node error listening is enabled and one of your nodes is in trouble**
-
-```javascript
-
-msg = {
-type:"NodeError"
-checkPerformed: "Self KNX-Ultimate node reporting a red color status"
-nodeid: "23HJ.2355" // (The node ID causing the error, so you can find it using node-red "search" funtion)
-payload: true
-description: // (KNX-Ultimate node reports his error here)
-completeError:{
-nodeid: "23HJ.2355" // (The node ID causing the error, so you can find it using node-red "search" funtion)
-topic: "0/1/1" // (or the custom topic you set in the knx-ultimate node)
-devicename: "Kitchen Light"
-GA: "0/1/1"
-
-}
-}
-
-```
-
-<br />
-
-**In case of a new gateway configuration is called via setGatewayConfig**
-
-```javascript
-
-msg = {
-type:"setGatewayConfig"
-checkPerformed: "The Watchdog node changed the gateway configuration."
-nodeid: "23HJ.2355" // (The node ID issuing the setGatewayConfig, so you can find it using node-red "search" funtion)
-payload: true
-description: "New Config issued to the gateway. IP:224.0.23.12 Port:3671 PhysicalAddress:15.15.1
-BindLocalInterface:Auto"
-completeError:""
-}
-
-```
-
-<br />
-
-**Forced connection/disconnection**
-
-```javascript
-
-msg = {
-type:"connectGateway"
-checkPerformed: "The Watchdog issued a connection/disconnection to the gateway."
-nodeid: "23HJ.2355" // (The node ID issuing the connection/disconnection request, so you can find it using node-red
-"search" funtion)
-payload: true // true if you requested the connection, false if you requested the disconnection
-description: "Connection"
-completeError:""
-}
-
-```
-
-<br />
-
----
-
-# INPUT FLOW MESSAGE
-
-The WatchDog node accepts flow's input and transmits flow's output. Below, an explanation of the message's format to be sent to or trasmitted from the node.
-
-## START AND STOP THE WATCHDOG
-
-To start and stop the watchdog, you can pass this as message to the node<br />
-
-**START WATCHDOG** <br />
-
-```javascript
-
-// Start the WatchDog
-msg.start = true;
-return msg;
-
-```
-
-**STOP WATCHDOG** <br />
-
-```javascript
-
-// Start the WatchDog
-msg.start = false;
-return msg;
-
-```
-
-## CHANGE THE KNX/IP ROUTER/INTERFACE SETTINGS ON THE FLY
-
-With **msg.setGatewayConfig** , you can change the IP, Port, Physical Address, Protocol and so on of your KNX/IP Interface or Router, previously set in the Config-Node<br />
-
-The Config-Node will change the settings and reconnect with new parameters.<br />
-
-Be careful, if you restart node-red, the new settings are reverted to the settings specified in the Config-Node.<br />
-
-**ALL parameters are OPTIONAL** <br />
-
-```javascript
-
-// IP: IP of your KNX/IP Router or Interface
-// Port: Port of your KNX/IP Router or Interface
-// PhysicalAddress: Physical address your KNX/IP Router or Interface (this is not a Group Address, this is a physical address indicating the physical device in your KNX installation)
-// BindToEthernetInterface: "Auto" (for automatic detection) or the ethernet interface name, for example "en0".
-// Protocol: "TunnelUDP" or "TunnelTCP" or "Multicast"
-// importCSV: the ETS exported CSV or ESF. Please see the text format in the Gateway Config Wiki Page and in the youtube
-video.
-// All these parameters are optional
-
-msg.setGatewayConfig={IP:"224.0.23.12",Port:3671,PhysicalAddress:"15.15.1",BindToEthernetInterface:"Auto",
-Protocol:"Multicast", importCSV:`"Group name" "Address" "Central" "Unfiltered" "Description" "DatapointType" "Security"
-"Attuatori luci" "0/-/-" "" "" "" "" "Auto"
-"Luci primo piano" "0/0/-" "" "" "" "" "Auto"
-"Luce camera da letto" "0/0/1" "" "" "" "DPST-1-1" "Auto"};`}
-
-return msg;
-
-```
-
-All properties are optional. For example, to only change the IP:
-
-```javascript
-
-// IP: IP of your KNX/IP Router or Interface
-msg.setGatewayConfig={IP:"224.0.23.12"};
-return msg;
-
-```
-
-**FORCE GATEWAY'S DISCONNECTION AND DISABLE AUTO RECONNECTION ATTEMPTS** <br />
-
-```javascript
-
-// Force the gateway's disconnection from the BUS and stop the reconnection's attempts.
-msg.connectGateway = false;
-return msg;
-
-```
-
-**FORCE GATEWAY'S CONNECTION AND ENABLE THE AUTO RECONNECTION ATTEMPTS** <br />
-
-```javascript
-
-// Force the gateway's connection to the BUS and activate the reconnection's attempts.
-msg.connectGateway = true;
-return msg;
-
-```
-
-## SEE ALSO
-
-[Sample WatchDog](https://supergiovane.github.io/node-red-contrib-knx-ultimate/wiki/-Sample---WatchDog)
-</script>

package/nodes/locales/en/knxUltimateWatchDog.json

@@ -1,27 +0,0 @@
-{
-    "knxUltimateWatchDog": {
-        "paletteLabel": "KNX WatchDog (deprecated)",
-        "title": "Watchdog",
-        "properties": {
-            "node-input-server": "Gateway",
-            "node-input-checkLevel": "Check level (please see the wiki)",
-            "node-input-topic": "Group Address to monitor",
-            "node-input-name": "Node Name",
-            "node-input-autoStart": "Auto start the watchdog timer",
-            "node-input-listenToKnxUltimateNodeErrors": "Listen to KNX-Ultimate node errors",
-            "advancedOptionsAccordion": "Advanced Options",
-            "node-input-retryInterval": "Retry interval (in seconds)",
-            "node-input-maxRetry": "Number of retry before giving an error"
-        },
-        "placeholder": {
-            "monitor": "Ex: 12/0/0. For 'Only Ethernet' checks, please use a non existent Group Address."
-        },
-        "selectlists": {
-            "Ethernet": "Only Ethernet unicast (Default), using ping. Works ONLY with KNX Interfaces (not routers)",
-            "EthKNX": "Ethernet + KNX Twisted Pair, using a real KNX device"
-        },
-        "legacy_notice": "This node is deprecated and remains supported for existing flows. Use KNX Utility for new flows. The button below converts all compatible legacy KNX utility nodes in every flow and subflow.",
-        "migration_button": "Convert all compatible legacy KNX nodes",
-        "migration_button_title": "Convert every compatible legacy KNX utility instance in all editor flows and subflows to KNX Utility"
-    }
-}

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

@@ -1,47 +0,0 @@
-<script type="text/markdown" data-help-name="matter-config">
-### Upgrade to KNX Ultimate 8
-
-Version 7 shows a compact **Upgrade to v8** button at the top of this editor. It downloads a flow backup, installs the required companion packages, converts compatible nodes, performs a full Deploy, verifies the saved flows and installs version 8. Restart the Node-RED service when prompted; reloading only the browser is not enough. Legacy KNX AI nodes stop the automatic operation.
-
-[Full upgrade guide](https://supergiovane.github.io/node-red-contrib-knx-ultimate/wiki/Upgrade-to-v8)
-
-<br/>
-
-# Matter Controller
-
-## Overview
-
-This configuration node is a full **Matter controller**: it creates its own Matter *fabric* and commissions (pairs) your Matter devices into it. The paired devices are then available to the **Matter Device** nodes, which map them to KNX group addresses.
-
-The controller talks to the devices over the **IP network** (WiFi, Ethernet, or Thread through a border router). Bluetooth commissioning is not supported: the device must already be reachable on the network.
-
-## Pairing a device
-
-1. **Deploy** this configuration node first (the controller must be running).
-2. Open the node again and enter the **pairing code**: either the 11-digit manual code (e.g. `3497-011-2332`) or the QR code content (`MT:....`).
-3. For a manually entered code, click **PAIR**. A QR read with **Webcam** or **Image** starts pairing automatically. Commissioning can take up to a minute.
-
-Instead of typing the QR payload, click **Webcam** to scan it live or **Image** to read it from a local picture. Both standard dark-on-light and inverted white-on-dark QR codes are supported. Decoding takes place entirely in the browser; after a valid Matter QR is read, the editor fills the pairing-code field and immediately starts pairing. Enter the optional device name before scanning if desired. A manually typed code still starts only when you click **PAIR**. Live webcam access requires the editor to be opened over HTTPS or from `localhost`; when that is not possible, the editor explains the limitation and image loading remains available.
-
-While commissioning is in progress, a blocking panel covers the editor and prevents further clicks until the operation succeeds or fails. Its progress bar follows the actual matter.js milestones and shows the current operation in English. When the device exposes its product identity, the panel also shows its product name, Vendor ID and Product ID.
-
-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).
-
-The list contains one row for every node currently stored in this controller's Matter fabric. Node IDs are unique within that fabric; endpoints exposed by one commissioned bridge are not listed as separate devices. The state column reports whether each node is connected, disconnected, reconnecting or waiting for discovery.
-
-The controller keeps command order separately for each commissioned device. A slow, offline or removed device cannot block commands for other devices. Controller device nodes that still reference a removed Node ID reject new commands immediately and display **Device no longer commissioned**.
-
-When a device becomes unavailable, its Controller nodes stay blocked and ignore further commands until that device reports `connected` again. Recovery is automatic; opening the device-node editor also clears the block for a manual retry.
-</script>

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

@@ -1,48 +0,0 @@
-{
-  "matter-config": {
-    "properties": {
-      "title": "Matter Controller",
-      "node-config-input-name": "Name",
-      "fabric_label": "Fabric label",
-      "pairing_title": "Pair a new device",
-      "pairing_help": "Enter the 11-digit manual pairing code (e.g. 3497-011-2332) or the QR code content (MT:....). The device must be reachable on the IP network (WiFi/Ethernet or Thread via border router). If the device is already paired with another controller (Alexa, Google, Apple), use its \"share/pair with another hub\" function to obtain a new pairing code.",
-      "pairing_code": "Pairing code",
-      "pairing_name": "Device name",
-      "pair_button": "PAIR",
-      "qr_acquire": "Read QR code",
-      "qr_scan_camera": "Webcam",
-      "qr_scan_image": "Image",
-      "qr_stop_camera": "Stop camera",
-      "qr_camera_insecure": "The browser cannot use the webcam because the Node-RED editor is not open over HTTPS or localhost. Reopen it over HTTPS, or use Image.",
-      "qr_camera_unsupported": "This browser cannot access a webcam. Use a supported browser or load an image.",
-      "qr_camera_permission_denied": "Webcam permission was denied. Allow camera access in the browser, or load an image.",
-      "qr_camera_failed": "Unable to start the webcam",
-      "qr_image_failed": "No readable QR code was found in the selected image",
-      "qr_invalid_matter": "The QR code is not a Matter pairing code (MT:…).",
-      "qr_found": "Matter QR code read. Pairing starts automatically.",
-      "qr_decoder_unavailable": "The QR decoder could not be loaded.",
-      "devices_title": "Commissioned devices",
-      "col_name": "Name",
-      "col_product": "Product",
-      "col_state": "State",
-      "no_devices": "No devices paired yet.",
-      "unpair_confirm": "Remove (decommission) the device",
-      "unpair_ok": "Device removed.",
-      "deploy_first": "Deploy this configuration node first, then try again.",
-      "pairing_code_missing": "Please enter a pairing code.",
-      "pairing_wait": "Pairing in progress. It can take up to a minute...",
-      "pairing_failed": "Pairing failed",
-      "pairing_ok": "Device paired successfully!",
-      "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.",
-      "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

@@ -1,45 +0,0 @@
-<script type="text/markdown" data-help-name="matterbridge-config">
-### Upgrade to KNX Ultimate 8
-
-Version 7 shows a compact **Upgrade to v8** button at the top of this editor. It downloads a flow backup, installs the required companion packages, converts compatible nodes, performs a full Deploy, verifies the saved flows and installs version 8. Restart the Node-RED service when prompted; reloading only the browser is not enough. Legacy KNX AI nodes stop the automatic operation.
-
-[Full upgrade guide](https://supergiovane.github.io/node-red-contrib-knx-ultimate/wiki/Upgrade-to-v8)
-
-<br/>
-
-# Matter Bridge
-
-## Overview
-
-This configuration node is the **Matter bridge itself**: it runs the Matter server that Alexa, Google Home, Apple Home (or any Matter controller) commission **once**. Every **Matter Bridge device** node in your flows points here and appears in the apps as one bridged device.
-
-## Configuration
-
-|Field|Description|
-|--|--|
-| Name | The name of this configuration node in Node-RED |
-| Matter bridge name | How the bridge itself is named in the Matter apps. **Leave it empty to reuse this node's Name.** |
-| Port | UDP port of the Matter server (default 5540). Each bridge needs its own port, so you can run **multiple independent bridges** |
-
-## Pairing
-
-1. **Deploy**, wait a few seconds, then open this node again.
-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.
-- Device nodes added/renamed/removed are picked up by the paired controllers within seconds, without re-pairing.
-- **Naming:** Alexa and Google Home honor the names you set here (bridge name and device node names). **Apple Home ignores them and asks you to name each accessory manually during setup** — this is an Apple limitation, not a bridge issue.
-</script>

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

@@ -1,25 +0,0 @@
-{
-  "matterbridge-config": {
-    "properties": {
-      "title": "Matter Bridge",
-      "intro": "This configuration node is the Matter bridge itself: Alexa, Google Home, Apple Home (or any Matter controller) pair it once and see every KNX device you attach to it. Add \"Matter Bridge device\" nodes across your flows and point them here. Deploy first, then reopen to get the pairing code.",
-      "node-config-input-name": "Name",
-      "bridge_name": "Matter bridge name",
-      "bridge_name_ph": "Leave empty to use the node name",
-      "port": "Port",
-      "pairing_title": "Pairing (Alexa, Google Home, Apple Home...)",
-      "not_running": "The Matter bridge is not running yet. Deploy, wait a few seconds, then click refresh.",
-      "commissioned": "Bridge paired with these controllers:",
-      "commissioned_hint": "The QR code is hidden because the bridge is already paired. To add Alexa as another Matter controller, open pairing mode from one of the controllers listed above (for example Apple Home or Google Home), then add a Matter device in Alexa. Use Reset pairing only if you want to remove all existing controllers and start from scratch.",
-      "awaiting": "Awaiting pairing. Scan the QR code or enter the manual code in your Matter app:",
-      "qr_link": "Open the QR code in the browser",
-      "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.",
-      "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/hue-config.html

@@ -1,31 +0,0 @@
-<script type="text/markdown" data-help-name="hue-config">
-### Actualizar a KNX Ultimate 8
-
-La versión 7 muestra un pequeño botón **Actualizar a v8** en la parte superior de este editor. Descarga una copia de los flujos, instala los paquetes HUE/Matter necesarios, convierte los nodos compatibles, realiza un Deploy completo, verifica los flujos guardados e instala la versión 8. Reinicia después el servicio Node-RED cuando se indique; recargar solo el navegador no es suficiente. Los nodos antiguos KNX AI detienen la operación automática.
-
-[Guía completa de actualización](https://supergiovane.github.io/node-red-contrib-knx-ultimate/wiki/es-Upgrade-to-v8)
-
-<br/>
-
-<h1> <p Align = 'Center'> Philips Hue Nodos </p> </h1>
-<br/>
-<P align = 'Center'> <img src = 'https://raw.githubusercontent.com/supergiovane/node-red-contrib-knx-ultimate/master/img/huehub.jpg' width = '40%'> </p>
-
-Este nodo registra Node-RED en el puente Hue y ahora realiza automáticamente el proceso de emparejamiento.
-
-Introduce la IP del puente (o elige una de las detectadas automáticamente) y pulsa **CONNECT**. El editor seguirá consultando el puente y cerrará la ventana de espera en cuanto pulses el botón físico de enlace. Usa **CANCEL** si necesitas cancelar la espera y probar más tarde. Los campos de Nombre de usuario y Client Key permanecen editables para que puedas copiar o pegar las credenciales en cualquier momento.
-
-¿Ya tienes las credenciales? Haz clic en **YA TENGO LAS CREDENCIALES** para mostrar los campos al instante e introducirlas manualmente sin esperar al botón del puente.
-
-**General**
-
-| Propiedad | Descripción |
-|-|-|
-| IP | Introduce la IP fija de tu puente Hue o selecciona uno de los puentes detectados automáticamente. |
-| CONECTAR | Inicia el registro y espera al botón de enlace del puente. La ventana se cierra automáticamente cuando lo pulsas; utiliza **CANCEL** para detener la espera. |
-| Nombre | Nombre del puente leído desde la Hue Bridge después de una conexión correcta. |
-| Nombre de usuario | Nombre de usuario devuelto por la Hue Bridge tras el emparejamiento. El campo permanece editable para poder copiar, pegar o escribir el valor manualmente. |
-| Clave del cliente | Clave del cliente devuelta por la Hue Bridge tras el emparejamiento. El campo permanece editable para poder copiar, pegar o escribir el valor manualmente. |
-
-![Image.png](../ img/hude-config.png)
-</script>

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

@@ -1,21 +0,0 @@
-{
-  "hue-config": {
-    "properties": {
-      "title": "Puente de Hue Philips",
-      "host": "IP",
-      "host_placeholder": "Escriba la IP del puente Hue, luego haga clic en Conectar",
-      "node-config-input-name": "Nombre",
-      "getinfocam": "Regístrese en HUB",
-      "connect": "CONECTAR",
-      "manual_credentials": "YA TENGO LAS CREDENCIALES",
-      "bridge_id": "ID de puente",
-      "username": "Nombre de usuario",
-      "client_key": "Clave del cliente",
-      "wait_message": "Espera, estoy hablando con tu puente Hue...",
-      "caution": "PRECAUCIÓN: otros nodos Hue de terceros instalados al mismo tiempo pueden causar problemas y deben eliminarse.",
-      "link_button_wait": "Pulsa el botón de enlace del puente Hue. Esperando confirmación…",
-      "registration_failed": "Error al registrar el puente Hue.",
-      "registration_unreachable": "No se puede contactar con el puente Hue."
-    }
-  }
-}

package/nodes/locales/es/knxUltimateAI.html

@@ -1,13 +0,0 @@
-<script type="text/html" data-help-name="knxUltimateAI">
-### Actualizar a KNX Ultimate 8
-
-La versión 7 muestra un pequeño botón **Actualizar a v8** en la parte superior de este editor. Descarga una copia de los flujos, instala los paquetes HUE/Matter necesarios, convierte los nodos compatibles, realiza un Deploy completo, verifica los flujos guardados e instala la versión 8. Reinicia después el servicio Node-RED cuando se indique; recargar solo el navegador no es suficiente. Los nodos antiguos KNX AI detienen la operación automática.
-
-[Guía completa de actualización](https://supergiovane.github.io/node-red-contrib-knx-ultimate/wiki/es-Upgrade-to-v8)
-
-<br/>
-
-  <p><b>Este es un nodo heredado oculto, conservado únicamente para los flows existentes.</b></p>
-  <p>Para instalaciones nuevas, utiliza el nodo independiente <b>Cerebrum Ultimate</b> del paquete <code>node-red-contrib-cerebrum-ultimate</code>. Sustituye a este nodo y utiliza KNX Ultimate como integración compatible opcional.</p>
-  <p><a href="https://github.com/Supergiovane/node-red-contrib-cerebrum-ultimate#readme" target="_blank">Abrir la documentación de Cerebrum Ultimate</a>.</p>
-</script>