node-red-contrib-knx-ultimate 5.2.3 → 5.2.5

package/CHANGELOG.md

@@ -6,9 +6,18 @@
 
 # CHANGELOG
 
+**Version 5.2.5** - July 2026<br/>
+
+- Maintenance release.<br/>
+
+**Version 5.2.4** - July 2026<br/>
+
+- **Matter Bridge — bridge name**: the _Matter bridge name_ field (the name Alexa/Google/Apple show for the bridge itself) now falls back to the configuration node's own **Name** when left empty, instead of the generic `KNX-Ultimate Bridge`. The field is empty by default with a placeholder hint, so a freshly named bridge is never anonymous during pairing.<br/>
+  - **Naming clarification**: Alexa and Google Home honor the names set on the bridge and on the device nodes, so they appear automatically in the apps. **Apple Home deliberately ignores the provided names and asks you to name each accessory manually during setup** — this is an Apple/HomeKit limitation, not a bridge issue. Node help and the online docs now document this difference in all six languages (EN/IT/DE/FR/ES/zh-CN).<br/>
+
 **Version 5.2.3** - July 2026<br/>
 
-- **MQTT / Home Assistant bridge — Entity name format**: new selector to reshape the names exposed to Home Assistant. The ETS import builds each name with the group-address path first (e.g. `(Lights->Ground floor) Living room`); now you can choose *As imported from ETS* (default), *Name first* (`Living room (Lights->Ground floor)`), *Name only* (`Living room`) or *Name + group address* (`Living room (0/1/2)`). Changing it only updates the friendly name (the `unique_id`/`object_id` stay stable, so existing entities are not duplicated).<br/>
+- **MQTT / Home Assistant bridge — Entity name format**: new selector to reshape the names exposed to Home Assistant. The ETS import builds each name with the group-address path first (e.g. `(Lights->Ground floor) Living room`); now you can choose _As imported from ETS_ (default), _Name first_ (`Living room (Lights->Ground floor)`), _Name only_ (`Living room`) or _Name + group address_ (`Living room (0/1/2)`). Changing it only updates the friendly name (the `unique_id`/`object_id` stay stable, so existing entities are not duplicated).<br/>
   - The group-address list in the editor now previews the chosen format **live**: pick a format and every row is re-labelled instantly, exactly as it will appear in Home Assistant, without reloading the list or losing the expose / read-only ticks.<br/>
   - Entity names are sanitized before publishing: ASCII control characters are stripped and runs of whitespace collapsed (ETS exports sometimes lose an accented character and leave a double space, e.g. `Velocità vento` → `Velocit  vento`), and a name that would be empty falls back to the group address.<br/>
 - **Documentation**: node help and the online IoT-Bridge page updated for the new option in all six languages (EN/IT/DE/FR/ES/zh-CN).<br/>
@@ -18,7 +27,7 @@
 - New **Matter Bridge (BETA)**: exposes **KNX group addresses as Matter devices**. Alexa, Google Home, Apple Home (or any Matter controller) commission the bridge once — via QR code or 11-digit manual code shown in the editor — and see all your KNX devices with the names you typed, ready for app and voice control. It is the opposite direction of the Matter Device node introduced in 5.1.0.<br/>
   - Two-node architecture (like the HUE and Matter Controller integrations): a **Matter Bridge** configuration node is the bridge itself (holds the pairing, the QR code and the port), and a **Matter Bridge device** node is added per exposed device and points to it. Spread the device nodes across your flows, each with its own status — no giant list.<br/>
   - **17 device types**: on/off light, dimmable light, **RGB color light** (DPT 232.600, converted to/from the Matter color wheel), **tunable white light** (color temperature in Kelvin, DPT 7.600), plug, cover/shutter (up/down, stop, position % with optional inversion), thermostat (current temperature + heating setpoint, both ways), **fan/ventilation** (speed %), sensors (temperature, humidity, illuminance, occupancy, contact), **smoke/CO alarm**, **water leak detector**, **air quality sensor** (CO2 ppm with automatic air-quality classification) and **robot vacuum** (flow-only: integrate your robot with any Node-RED node and expose it to the voice assistants).<br/>
-  - Bidirectional with loop protection: assistant commands write to the KNX *command* group addresses; telegrams on the *status* group addresses update the Matter attributes (and the apps). At startup each device node can send a `GroupValue_Read` to its status GAs so the Matter attributes are populated before the first app query.<br/>
+  - Bidirectional with loop protection: assistant commands write to the KNX _command_ group addresses; telegrams on the _status_ group addresses update the Matter attributes (and the apps). At startup each device node can send a `GroupValue_Read` to its status GAs so the Matter attributes are populated before the first app query.<br/>
   - **Live device reconciliation**: the Matter server stays alive across re-deploys — added/renamed/removed device nodes appear on the paired controllers within seconds, without restarting Node-RED and without re-pairing.<br/>
   - Optional **node Input/Output PINs**: the output forwards every controller command to the flow; the input updates the Matter state from flow messages (`msg.payload = { function, value }`). Devices without a command GA become flow-only devices.<br/>
   - The **KNX gateway is optional** on the device node: without it the device runs in flow-only mode, useful to expose flow-computed or non-KNX devices to Alexa & Co.<br/>
@@ -33,7 +42,7 @@
 
 - New **Matter integration (BETA)**: control any commissioned **Matter device** from the KNX bus and track its states on KNX group addresses.<br/>
   - New **Matter Controller** configuration node: a full Matter controller with its own fabric (based on [matter.js](https://github.com/project-chip/matter.js)). Pair devices directly from the editor using the 11-digit manual pairing code or the QR code content (`MT:...`); commissioning works over the IP network (WiFi/Ethernet or Thread via border router). The commissioned devices list shows name, product, node ID and connection state, with one-click unpair. Fabric credentials are stored under `knxultimatestorage/matter` in the Node-RED user directory.<br/>
-  - New **Matter Device (BETA)** node: pick a paired Matter device and map KNX group addresses to its functions with a dynamic mapping list. The function list is **human friendly**: it shows only the functions the device really exposes, with plain-language localized names (e.g. *"On/Off switch"*, *"Instantaneous power (W)"*, *"Room temperature (°C)"*) and the current value in brackets, instead of raw Matter cluster/attribute names. Friendly endpoint names for 34 common device types (smart plug, dimmable light, cover, thermostat, sensors...).<br/>
+  - New **Matter Device (BETA)** node: pick a paired Matter device and map KNX group addresses to its functions with a dynamic mapping list. The function list is **human friendly**: it shows only the functions the device really exposes, with plain-language localized names (e.g. _"On/Off switch"_, _"Instantaneous power (W)"_, _"Room temperature (°C)"_) and the current value in brackets, instead of raw Matter cluster/attribute names. Friendly endpoint names for 34 common device types (smart plug, dimmable light, cover, thermostat, sensors...).<br/>
   - Mappings are bidirectional: **KNX → Matter** (commands/attribute writes, e.g. GA 1/1/1 DPT 1.001 → OnOff) and **Matter → KNX** (attribute changes written to the GA; `GroupValue_Read` requests answered from the cache). Automatic value conversion for the common clusters: OnOff, LevelControl (0-254 ↔ %), WindowCovering (percent100ths ↔ %, up/down), ColorControl (mireds ↔ Kelvin), Thermostat and temperature/humidity sensors (centi-units ↔ units), illuminance (log scale ↔ Lux), battery (half-percent ↔ %), power/energy metering (mW ↔ W, mWh ↔ kWh), door lock, occupancy and contact sensors.<br/>
   - Selecting a function pre-fills the **suggested KNX DPT** and the GA name; the group address field has the usual **ETS autocomplete**. Optional node input/output pins for raw Matter access from the flow. Editor and help localized in EN/IT/DE/FR/ES/zh-CN.<br/>
 
@@ -48,14 +57,14 @@
 **Version 5.0.2** - July 2026<br/>
 
 - **IoT Bridge** node, **MQTT / Home Assistant (native)** mode:<br/>
-  - New **Read only** flag per group address in the *Group addresses to expose* list: a read-only GA is still published to Home Assistant (its state stays visible) but never accepts commands back to the KNX bus (switches are exposed as `binary_sensor`, numbers/text as `sensor`). Added *Set read only* / *Clear read only* buttons that apply it to all currently shown (filtered) addresses.<br/>
-  - New **KNX bus connection** selector: *Stand-alone* (default, talks to the KNX gateway directly) or *Flow messages*, which enables the node's input/output pins — wire a **KNXUltimate** node in Universal mode to the input (KNX bus → MQTT) and another to the output (MQTT → KNX bus). Pins are shown only when needed (none in stand-alone, one input + one output in flow mode).<br/>
+  - New **Read only** flag per group address in the _Group addresses to expose_ list: a read-only GA is still published to Home Assistant (its state stays visible) but never accepts commands back to the KNX bus (switches are exposed as `binary_sensor`, numbers/text as `sensor`). Added _Set read only_ / _Clear read only_ buttons that apply it to all currently shown (filtered) addresses.<br/>
+  - New **KNX bus connection** selector: _Stand-alone_ (default, talks to the KNX gateway directly) or _Flow messages_, which enables the node's input/output pins — wire a **KNXUltimate** node in Universal mode to the input (KNX bus → MQTT) and another to the output (MQTT → KNX bus). Pins are shown only when needed (none in stand-alone, one input + one output in flow mode).<br/>
   - Editor help and online docs updated in EN/IT/DE/FR/ES/zh-CN.<br/>
 
 **Version 5.0.1** - June 2026<br/>
 
-- **IoT Bridge** node (renamed **MQTT - IoT** in the UI): new **MQTT / Home Assistant (native)** mode selectable via a *Mode* dropdown. In this mode the node connects directly to an MQTT broker and bridges KNX ↔ MQTT both ways, publishing **Home Assistant MQTT Discovery** so KNX appears automatically in Home Assistant (no `mqtt in`/`mqtt out` wiring needed). The classic IoT bridge mode is unchanged.<br/>
-  - Every group address imported in the KNX gateway (ETS list) can be **exposed automatically** as a Home Assistant entity (switch, sensor, binary_sensor, number, text), typed from its DPT. A checkbox list with filter and *Select all / none* lets you choose exactly which GAs to publish.<br/>
+- **IoT Bridge** node (renamed **MQTT - IoT** in the UI): new **MQTT / Home Assistant (native)** mode selectable via a _Mode_ dropdown. In this mode the node connects directly to an MQTT broker and bridges KNX ↔ MQTT both ways, publishing **Home Assistant MQTT Discovery** so KNX appears automatically in Home Assistant (no `mqtt in`/`mqtt out` wiring needed). The classic IoT bridge mode is unchanged.<br/>
+  - Every group address imported in the KNX gateway (ETS list) can be **exposed automatically** as a Home Assistant entity (switch, sensor, binary_sensor, number, text), typed from its DPT. A checkbox list with filter and _Select all / none_ lets you choose exactly which GAs to publish.<br/>
   - New **Covers & Thermostats** editor: composite entities that aggregate several GAs (cover with up/down, stop and position including KNX↔HA position inversion; thermostat with current temperature, setpoint and optional on/off). The cover/thermostat GA fields have **ETS group-address autocomplete**, like the KNX device node.<br/>
   - Robust lifecycle: the MQTT broker is closed gracefully on deploy / Node-RED exit (retained `offline`, forced disconnect, hard-capped so a slow or unreachable broker never blocks a deploy); all MQTT event handlers are fully guarded.<br/>
   - Editor help and online docs updated, plus Home Assistant / MQTT logos on the docs pages. Localized in EN/IT/DE/FR/ES/zh-CN.<br/>

package/README.md

@@ -1,7 +1,16 @@
+<p align="center">
+  <img src="img/logo-supervibe.png" alt="KNX Ultimate - Max Supervibe" width="200">
+</p>
+
 ![Logo](img/logo-big.png)
 
-<br/>
+## 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.
 
+<br/>
+<br/>
+<br/>
 
 [![NPM version][npm-version-image]][npm-url]
 [![Node.js version][node-version-image]][npm-url]
@@ -15,7 +24,6 @@
 [![JavaScript Style Guide][standard-image]][standard-url]
 [![Youtube][youtube-image]][youtube-url]
 
-
 <p align="center">
   <img src="img/readmemain.png" alt="Sample Node" width="70%">
 </p>
@@ -61,5 +69,4 @@
 [flows-url]: https://flows.nodered.org/node/node-red-contrib-knx-ultimate
 [paypal-image]: https://img.shields.io/badge/Support-PayPal-blue
 [paypal-url]: https://www.paypal.com/donate/?hosted_button_id=S8SKPUBSPK758
-
 [docs-button-image]: https://img.shields.io/badge/Docs-Open%20Documentation-0d4c70?style=for-the-badge&logo=book&logoColor=f4fbff

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

@@ -12,7 +12,7 @@ Dieser Konfigurations-Node ist die **Matter-Bridge selbst**: Er betreibt den Mat
 |Feld|Beschreibung|
 |--|--|
 | Name | Der Name dieses Konfigurations-Nodes in Node-RED |
-| Name der Matter-Bridge | Wie die Bridge selbst in den Matter-Apps heißt |
+| Name der Matter-Bridge | Wie die Bridge selbst in den Matter-Apps heißt. **Leer lassen, um den Namen dieses Nodes zu verwenden.** |
 | Port | UDP-Port des Matter-Servers (Standard 5540). Jede Bridge braucht ihren eigenen Port, daher sind **mehrere unabhängige Bridges** möglich |
 
 ## Kopplung
@@ -31,4 +31,5 @@ Die Bridge-Identität ist an diesen Konfigurations-Node gebunden und wird in `kn
 
 - Der Node-RED-Host muss **IPv6 link-local** aktiviert haben (Standard-Matter-Anforderung) und von den Controllern im lokalen Netzwerk erreichbar sein.
 - Hinzugefügte/umbenannte/entfernte Device-Nodes werden von den gekoppelten Controllern innerhalb von Sekunden übernommen, ohne neue Kopplung.
+- **Namen:** Alexa und Google Home übernehmen die hier gesetzten Namen (Bridge-Name und Device-Node-Namen). **Apple Home ignoriert sie und verlangt, jedes Zubehör bei der Einrichtung manuell zu benennen** — eine Einschränkung von Apple, nicht der Bridge.
 </script>

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

@@ -5,6 +5,7 @@
       "intro": "Dieser Konfigurations-Node ist die Matter-Bridge selbst: Alexa, Google Home, Apple Home (oder jeder Matter-Controller) koppeln sie einmal und sehen alle KNX-Geräte, die du ihr zuweist. Füge \"Matter Bridge device\"-Nodes in deinen Flows hinzu und verweise sie hierher. Zuerst deployen, dann erneut öffnen für den Kopplungscode.",
       "node-config-input-name": "Name",
       "bridge_name": "Name der Matter-Bridge",
+      "bridge_name_ph": "Leer lassen, um den Node-Namen zu verwenden",
       "port": "Port",
       "pairing_title": "Kopplung (Alexa, Google Home, Apple Home...)",
       "not_running": "Die Matter-Bridge läuft noch nicht. Deployen, ein paar Sekunden warten und dann auf Aktualisieren klicken.",

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

@@ -12,7 +12,7 @@ This configuration node is the **Matter bridge itself**: it runs the Matter serv
 |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 |
+| 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
@@ -31,4 +31,5 @@ The bridge identity is tied to this configuration node and stored in `knxultimat
 
 - 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

@@ -5,6 +5,7 @@
       "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.",

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

@@ -12,7 +12,7 @@ Este nodo de configuración es el **bridge Matter en sí**: ejecuta el servidor
 |Campo|Descripción|
 |--|--|
 | Nombre | El nombre de este nodo de configuración en Node-RED |
-| Nombre del bridge Matter | Cómo se llama el bridge en las apps Matter |
+| Nombre del bridge Matter | Cómo se llama el bridge en las apps Matter. **Déjalo vacío para reutilizar el Nombre de este nodo.** |
 | Puerto | Puerto UDP del servidor Matter (por defecto 5540). Cada bridge necesita su propio puerto, por lo que puedes ejecutar **varios bridges independientes** |
 
 ## Emparejamiento
@@ -31,4 +31,5 @@ La identidad del bridge está ligada a este nodo de configuración y se guarda e
 
 - 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.
 - Los nodos de dispositivo añadidos/renombrados/eliminados se detectan en pocos segundos, sin volver a emparejar.
+- **Nombres:** Alexa y Google Home respetan los nombres que pongas aquí (nombre del bridge y nombres de los nodos de dispositivo). **Apple Home los ignora y te pide nombrar cada accesorio manualmente durante la configuración** — es una limitación de Apple, no del bridge.
 </script>

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

@@ -5,6 +5,7 @@
       "intro": "Este nodo de configuración es el bridge Matter en sí: Alexa, Google Home, Apple Home (o cualquier controlador Matter) lo emparejan una vez y ven todos los dispositivos KNX que le conectes. Añade nodos \"Matter Bridge device\" en tus flows y apúntalos aquí. Haz deploy primero y vuelve a abrir para obtener el código.",
       "node-config-input-name": "Nombre",
       "bridge_name": "Nombre del bridge Matter",
+      "bridge_name_ph": "Déjalo vacío para usar el nombre del nodo",
       "port": "Puerto",
       "pairing_title": "Emparejamiento (Alexa, Google Home, Apple Home...)",
       "not_running": "El bridge Matter aún no está en ejecución. Haz deploy, espera unos segundos y pulsa actualizar.",

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

@@ -12,7 +12,7 @@ Ce nœud de configuration est le **bridge Matter lui-même** : il exécute le se
 |Champ|Description|
 |--|--|
 | Nom | Le nom de ce nœud de configuration dans Node-RED |
-| Nom du bridge Matter | Le nom du bridge lui-même dans les apps Matter |
+| Nom du bridge Matter | Le nom du bridge lui-même dans les apps Matter. **Laissez vide pour réutiliser le Nom de ce nœud.** |
 | Port | Port UDP du serveur Matter (5540 par défaut). Chaque bridge a besoin de son propre port, vous pouvez donc exécuter **plusieurs bridges indépendants** |
 
 ## Appairage
@@ -31,4 +31,5 @@ L'identité du bridge est liée à ce nœud de configuration et enregistrée dan
 
 - 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.
 - Les nœuds d'appareil ajoutés/renommés/supprimés sont pris en compte en quelques secondes, sans nouvel appairage.
+- **Noms :** Alexa et Google Home respectent les noms définis ici (nom du bridge et noms des nœuds d'appareil). **Apple Home les ignore et vous demande de nommer chaque accessoire manuellement lors de la configuration** — c'est une limite d'Apple, pas du bridge.
 </script>

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

@@ -5,6 +5,7 @@
       "intro": "Ce nœud de configuration est le bridge Matter lui-même : Alexa, Google Home, Apple Home (ou tout contrôleur Matter) l'appairent une fois et voient tous les appareils KNX que vous y rattachez. Ajoutez des nœuds \"Matter Bridge device\" dans vos flux et pointez-les ici. Déployez d'abord, puis rouvrez pour obtenir le code d'appairage.",
       "node-config-input-name": "Nom",
       "bridge_name": "Nom du bridge Matter",
+      "bridge_name_ph": "Laisser vide pour utiliser le nom du nœud",
       "port": "Port",
       "pairing_title": "Appairage (Alexa, Google Home, Apple Home...)",
       "not_running": "Le bridge Matter n'est pas encore démarré. Déployez, attendez quelques secondes puis cliquez sur actualiser.",

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

@@ -12,7 +12,7 @@ Questo nodo di configurazione è il **bridge Matter vero e proprio**: esegue il
 |Campo|Descrizione|
 |--|--|
 | Nome | Il nome di questo nodo di configurazione in Node-RED |
-| Nome del bridge Matter | Come viene chiamato il bridge stesso nelle app Matter |
+| Nome del bridge Matter | Come viene chiamato il bridge stesso nelle app Matter. **Lascia vuoto per riusare il Nome di questo nodo.** |
 | Porta | Porta UDP del server Matter (default 5540). Ogni bridge richiede la propria porta, quindi puoi eseguire **più bridge indipendenti** |
 
 ## Abbinamento
@@ -31,4 +31,5 @@ L'identità del bridge è legata a questo nodo di configurazione ed è salvata i
 
 - L'host Node-RED deve avere **IPv6 link-local** attivo (requisito standard Matter) ed essere raggiungibile dai controller sulla rete locale.
 - I nodi device aggiunti/rinominati/rimossi vengono recepiti dai controller abbinati in pochi secondi, senza riabbinare.
+- **Nomi:** Alexa e Google Home rispettano i nomi che imposti qui (nome del bridge e nomi dei nodi device). **Apple Home li ignora e ti chiede di nominare manualmente ogni accessorio durante l'abbinamento** — è un limite di Apple, non del bridge.
 </script>

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

@@ -5,6 +5,7 @@
       "intro": "Questo nodo di configurazione è il bridge Matter vero e proprio: Alexa, Google Home, Apple Home (o qualunque controller Matter) lo associano una volta sola e vedono tutti i dispositivi KNX che gli colleghi. Aggiungi i nodi \"Matter Bridge device\" nei tuoi flow e puntali qui. Fai prima il deploy, poi riapri per ottenere il codice di abbinamento.",
       "node-config-input-name": "Nome",
       "bridge_name": "Nome del bridge Matter",
+      "bridge_name_ph": "Lascia vuoto per usare il nome del nodo",
       "port": "Porta",
       "pairing_title": "Abbinamento (Alexa, Google Home, Apple Home...)",
       "not_running": "Il bridge Matter non è ancora in esecuzione. Fai il deploy, attendi qualche secondo e clicca aggiorna.",

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

@@ -12,7 +12,7 @@
 |字段|说明|
 |--|--|
 | 名称 | 此配置节点在 Node-RED 中的名称 |
-| Matter 桥接器名称 | 桥接器本身在 Matter App 中显示的名称 |
+| Matter 桥接器名称 | 桥接器本身在 Matter App 中显示的名称。**留空则使用此节点的名称。** |
 | 端口 | Matter 服务器的 UDP 端口（默认 5540）。每个桥接器需要独立的端口，因此可以运行**多个独立的桥接器** |
 
 ## 配对
@@ -31,4 +31,5 @@
 
 - Node-RED 主机必须启用 **IPv6 link-local**（Matter 标准要求），并且控制器可在本地网络访问到它。
 - 添加/重命名/移除的设备节点会在几秒内被已配对的控制器识别，无需重新配对。
+- **名称：** Alexa 和 Google Home 会采用你在此设置的名称（桥接器名称和设备节点名称）。**Apple Home 会忽略它们，并要求你在配置过程中手动为每个配件命名**——这是 Apple 的限制，而非桥接器的问题。
 </script>

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

@@ -5,6 +5,7 @@
       "intro": "此配置节点就是 Matter 桥接器本身：Alexa、Google Home、Apple Home（或任何 Matter 控制器）配对一次即可看到你挂接的所有 KNX 设备。在流程中添加 \"Matter Bridge device\" 节点并指向这里。先部署，然后重新打开获取配对码。",
       "node-config-input-name": "名称",
       "bridge_name": "Matter 桥接器名称",
+      "bridge_name_ph": "留空则使用节点名称",
       "port": "端口",
       "pairing_title": "配对（Alexa、Google Home、Apple Home...）",
       "not_running": "Matter 桥接器尚未运行。请先部署，等待几秒后点击刷新。",

package/nodes/matterbridge-config.html

@@ -5,7 +5,7 @@
         category: 'config',
         defaults: {
             name: { value: '' },
-            bridgeDeviceName: { value: 'KNX-Ultimate Bridge' },
+            bridgeDeviceName: { value: '' },
             bridgePort: { value: 5540, required: true, validate: RED.validators.number() }
         },
         oneditprepare: function () {
@@ -101,7 +101,7 @@
     <label for="node-config-input-bridgeDeviceName" style="width:180px;">
       <i class="fa fa-share-alt"></i> <span data-i18n="matterbridge-config.properties.bridge_name"></span>
     </label>
-    <input type="text" id="node-config-input-bridgeDeviceName" style="width:220px;">
+    <input type="text" id="node-config-input-bridgeDeviceName" style="width:220px;" data-i18n="[placeholder]matterbridge-config.properties.bridge_name_ph">
     <label for="node-config-input-bridgePort" style="width:60px; text-align:right;"><span data-i18n="matterbridge-config.properties.port"></span></label>
     <input type="number" id="node-config-input-bridgePort" style="width:90px;">
   </div>

package/nodes/matterbridge-config.js

@@ -28,7 +28,9 @@ module.exports = (RED) => {
 
     node.name = config.name === undefined || config.name === '' ? 'Matter Bridge' : config.name
     node.bridgePort = Number(config.bridgePort) || 5540
-    node.bridgeDeviceName = config.bridgeDeviceName === undefined || config.bridgeDeviceName === '' ? 'KNX-Ultimate Bridge' : config.bridgeDeviceName
+    // Name advertised to the Matter controllers (Alexa/Google honor it; Apple Home forces manual naming).
+    // If left empty, fall back to this config node's own name so the bridge is never anonymous.
+    node.bridgeDeviceName = config.bridgeDeviceName === undefined || config.bridgeDeviceName === '' ? node.name : config.bridgeDeviceName
     node.matterInstanceId = `knxultimate-bridge-${node.id.replace(/[^a-zA-Z0-9]/g, '')}`
     node.matterStoragePath = path.join(RED.settings.userDir || '.', 'knxultimatestorage', 'matter')
 

package/package.json

@@ -3,7 +3,7 @@
   "engines": {
     "node": ">=20.18.1"
   },
-  "version": "5.2.3",
+  "version": "5.2.5",
   "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/",
@@ -82,12 +82,22 @@
   },
   "keywords": [
     "node-red",
+    "node-red-contrib",
     "KNX",
+    "knx-secure",
     "ETS",
     "eib",
     "konnex",
     "IOT",
-    "philips hue"
+    "philips hue",
+    "hue",
+    "matter",
+    "mqtt",
+    "home-assistant",
+    "building-automation",
+    "home-automation",
+    "smarthome",
+    "routing"
   ],
   "author": "Massimo Saccani (Supergiovane)",
   "license": "MIT",
@@ -123,4 +133,4 @@
     "vite": "^7.1.3",
     "vue": "^3.5.21"
   }
-}
+}