node-red-contrib-knx-ultimate 6.3.12 → 6.3.13

package/CHANGELOG.md

@@ -6,6 +6,11 @@
 
 # CHANGELOG
 
+**Version 6.3.13** - August 2026<br/>
+
+- **Matter**: promoted Matter Controller, Matter Bridge and Expose KNX to Matter from BETA to production-ready status; removed BETA labels and experimental warnings from the palette, editor help, examples and multilingual documentation while retaining pairing, backup and endpoint-structure safety guidance.<br/>
+- **Matter visual identity**: changed the Matter node background to the official Matter Day color (`#F3FFFF`) and the controller/bridge icon artwork to Matter Night (`#131926`) for readable, standards-aligned palette and canvas presentation.<br/>
+
 **Version 6.3.12** - August 2026<br/>
 
 - **HUE Controller**: completed the EN, IT, DE, FR, ES and zh-CN editor translations, including Light Level, Locate, Light mapping labels, mapping placeholders, error messages and tutorial links; the embedded profiles and dynamic device labels now follow Node-RED's active locale instead of a potentially stale page-language attribute. Corrected French/Spanish Hue and KNX terminology and realigned the localized help and wiki documentation.<br/>

package/examples/Matter Controller - Semantic Flow Input.json

@@ -4,7 +4,7 @@
     "type": "tab",
     "label": "Matter Controller - Flow input",
     "disabled": false,
-    "info": "Example of the semantic msg.payload = { function, value } contract for Control Matter from KNX (BETA).\n\nAfter importing:\n1. Open the example Matter Controller node.\n2. Select your existing Matter Controller configuration and a commissioned non-light endpoint.\n3. Enable Node Input/Output PINs.\n4. In the Flow input section shown below the PIN selector, use only the Inject nodes matching functions advertised by the device.\n\nThis example creates no matter-config and sends no command automatically."
+    "info": "Example of the semantic msg.payload = { function, value } contract for Control Matter from KNX.\n\nAfter importing:\n1. Open the example Matter Controller node.\n2. Select your existing Matter Controller configuration and a commissioned non-light endpoint.\n3. Enable Node Input/Output PINs.\n4. In the Flow input section shown below the PIN selector, use only the Inject nodes matching functions advertised by the device.\n\nThis example creates no matter-config and sends no command automatically."
   },
   {
     "id": "matter_semantic_instructions",

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

@@ -1,6 +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>
+  <text x="20" y="21" fill="#131926" 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"/>
+    fill="none" stroke="#131926" stroke-width="2.6" stroke-linecap="round" stroke-linejoin="round"/>
 </svg>

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

@@ -1,6 +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>
+  <text x="20" y="21" fill="#131926" 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"/>
+    fill="none" stroke="#131926" stroke-width="2.6" stroke-linecap="round" stroke-linejoin="round"/>
 </svg>

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

@@ -1,6 +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">
-    <g fill="#ffffff" stroke="none">
+    <g fill="#131926" stroke="none">
         <circle cx="20" cy="30" r="4.5"/>
         <g id="matterArrow">
             <rect x="18.4" y="9" width="3.2" height="11"/>

package/nodes/knxUltimateMatterBridge.html

@@ -118,15 +118,15 @@
 
     RED.nodes.registerType('knxUltimateMatterBridge', {
       category: 'KNX Ultimate Matter',
-      color: '#8FE3D4',
+      color: '#F3FFFF',
       defaults: gaDefaults,
       inputs: 0,
       outputs: 0,
       icon: 'node-matter-bridge-icon.svg',
       label() {
-        return this.name || 'Expose KNX to Matter (BETA)';
+        return this.name || 'Expose KNX to Matter';
       },
-      paletteLabel: 'Expose KNX to Matter (BETA)',
+      paletteLabel: 'Expose KNX to Matter',
       oneditprepare() {
         try { RED.sidebar.show('help'); } catch (error) { /* empty */ }
         const node = this;
@@ -632,7 +632,7 @@
 </script>
 
 <script type="text/markdown" data-help-name="knxUltimateMatterBridge">
-Exposes **one KNX device as a Matter device**. This node is in **BETA**.
+Exposes **one KNX device as a Matter device**.
 
 Point it to a **Matter Bridge** configuration node (the actual bridge, paired once by Alexa/Google Home/Apple Home), pick the device type, give it the name the assistant will use, and fill the group addresses.
 

package/nodes/knxUltimateMatterControllerDevice.html

@@ -10,7 +10,7 @@
 
     RED.nodes.registerType("knxUltimateMatterControllerDevice", {
       category: "KNX Ultimate Matter",
-      color: "#8FE3D4",
+      color: "#F3FFFF",
       defaults: {
         //buttonState: {value: true},
         server: { type: "knxUltimate-config", required: false },
@@ -142,9 +142,9 @@
       outputs: 0,
       icon: "node-matter-controller-icon.svg",
       label: function () {
-        return this.name || this.matterDeviceName || "Control Matter from KNX (BETA)";
+        return this.name || this.matterDeviceName || "Control Matter from KNX";
       },
-      paletteLabel: "Control Matter from KNX (BETA)",
+      paletteLabel: "Control Matter from KNX",
       oneditprepare: function () {
         // Go to the help panel
         try {

package/nodes/locales/de/knxUltimateMatterBridge.html

@@ -1,6 +1,4 @@
 <script type="text/markdown" data-help-name="knxUltimateMatterBridge">
-> Dieser Node ist in **BETA**: Er funktioniert, aber Details können sich zwischen Releases noch ändern.
-
 ## Übersicht
 
 Jeder Expose KNX to Matter Node stellt **ein KNX-Gerät als Matter-Gerät** bereit: Die gekoppelten Controller (Alexa, Google Home, Apple Home...) sehen es mit dem von dir vergebenen Namen — bereit für App- und Sprachsteuerung. Verweise ihn auf einen **Matter Bridge**-Konfigurations-Node (die eigentliche Bridge, einmal gekoppelt - der Kopplungs-QR-Code lebt dort) und füge beliebig viele Device-Nodes hinzu, überall in deinen Flows.

package/nodes/locales/de/knxUltimateMatterBridge.json

@@ -1,6 +1,6 @@
 {
   "knxUltimateMatterBridge": {
-    "title": "Expose KNX to Matter (BETA)",
+    "title": "Expose KNX to Matter",
     "bridge_name": "Name der Matter-Bridge",
     "port": "Port",
     "devices_help": "Füge die KNX-Geräte hinzu, die über Matter bereitgestellt werden sollen. Der \"Name\" ist der, den Alexa/Google/Apple anzeigen und für Sprachbefehle verwenden. Befehls-GA = wird geschrieben, wenn der Assistent einen Befehl sendet; Status-GA = wird vom Bus gelesen, um die App aktuell zu halten.",

package/nodes/locales/de/knxUltimateMatterControllerDevice.html

@@ -1,6 +1,4 @@
 <script type="text/markdown" data-help-name="knxUltimateMatterControllerDevice">
-> Dieser Knoten ist **BETA**: das Verhalten kann sich ändern, während die Matter-Implementierung weiter verfeinert wird.
-
 Dieser Knoten steuert einen bereits gekoppelten Matter-Endpunkt über KNX. Wähle das Matter-Gerät aus; der Editor erkennt die Fähigkeiten des Endpunkts und zeigt nur die passenden KNX-Zuordnungen.
 
 Ein Klick oder Fokus auf das Matter-Gerätefeld öffnet immer die vollständige Liste der gekoppelten Endpunkte, auch wenn bereits ein Gerät ausgewählt ist. Beim Tippen wird die Liste weiterhin gefiltert.

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

@@ -1,7 +1,5 @@
 <script type="text/markdown" data-help-name="matterbridge-config">
-# Matter Bridge (BETA)
-
-> Dieser Node ist in **BETA**: Er funktioniert, aber Details können sich zwischen Releases noch ändern.
+# Matter Bridge
 
 ## Übersicht
 

package/nodes/locales/en/knxUltimateMatterBridge.html

@@ -1,6 +1,4 @@
 <script type="text/markdown" data-help-name="knxUltimateMatterBridge">
-> This node is in **BETA**: it works, but details may still change between releases.
-
 ## Overview
 
 Each Expose KNX to Matter node exposes **one KNX device as a Matter device**: the paired controllers (Alexa, Google Home, Apple Home...) see it, with the name you typed, ready for app and voice control. Point it to a **Matter Bridge** configuration node (the actual bridge, paired once - the pairing QR code lives there) and add as many device nodes as you want, anywhere in your flows.

package/nodes/locales/en/knxUltimateMatterBridge.json

@@ -1,6 +1,6 @@
 {
   "knxUltimateMatterBridge": {
-    "title": "Expose KNX to Matter (BETA)",
+    "title": "Expose KNX to Matter",
     "bridge_name": "Matter bridge name",
     "port": "Port",
     "devices_help": "Add the KNX devices to expose on Matter. The \"Name\" is what Alexa/Google/Apple will show and use for voice commands. Command GA = written when the assistant sends a command; Status GA = read from the bus to keep the app updated.",

package/nodes/locales/en/knxUltimateMatterControllerDevice.html

@@ -1,6 +1,4 @@
 <script type="text/markdown" data-help-name="knxUltimateMatterControllerDevice">
-> This node is in **BETA**: behaviour can change while the Matter implementation is refined.
-
 This node controls a commissioned Matter endpoint from KNX. Select the Matter device and the editor detects its capabilities, then shows only the KNX mappings that make sense for that endpoint.
 
 Clicking or focusing the Matter device field always opens the complete commissioned endpoint list, even when a device is already selected. Typing continues to filter it.

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

@@ -1,7 +1,5 @@
 <script type="text/markdown" data-help-name="matterbridge-config">
-# Matter Bridge (BETA)
-
-> This node is in **BETA**: it works, but details may still change between releases.
+# Matter Bridge
 
 ## Overview
 

package/nodes/locales/es/knxUltimateMatterBridge.html

@@ -1,6 +1,4 @@
 <script type="text/markdown" data-help-name="knxUltimateMatterBridge">
-> Este nodo está en **BETA**: funciona, pero algunos detalles pueden cambiar entre versiones.
-
 ## Descripción general
 
 Cada nodo Expose KNX to Matter expone **un dispositivo KNX como dispositivo Matter**: los controladores emparejados (Alexa, Google Home, Apple Home...) lo ven, con el nombre que hayas elegido, listo para el control por app y por voz. Apúntalo a un nodo de configuración **Bridge Matter** (el bridge en sí, emparejado una sola vez - el QR de emparejamiento vive allí) y añade tantos nodos de dispositivo como quieras, en cualquier flow.

package/nodes/locales/es/knxUltimateMatterBridge.json

@@ -1,6 +1,6 @@
 {
   "knxUltimateMatterBridge": {
-    "title": "Expose KNX to Matter (BETA)",
+    "title": "Expose KNX to Matter",
     "bridge_name": "Nombre del bridge Matter",
     "port": "Puerto",
     "devices_help": "Añade los dispositivos KNX a exponer en Matter. El \"Nombre\" es el que Alexa/Google/Apple muestran y usan para los comandos de voz. GA de comando = se escribe cuando el asistente envía un comando; GA de estado = se lee del bus para mantener la app actualizada.",

package/nodes/locales/es/knxUltimateMatterControllerDevice.html

@@ -1,6 +1,4 @@
 <script type="text/markdown" data-help-name="knxUltimateMatterControllerDevice">
-> Este nodo está en **BETA**: el comportamiento puede cambiar mientras se mejora la implementación Matter.
-
 Este nodo controla desde KNX un endpoint Matter ya emparejado. Selecciona el dispositivo Matter y el editor detecta sus capacidades, mostrando solo las asignaciones KNX coherentes con ese endpoint.
 
 Al hacer clic o enfocar el campo del dispositivo Matter siempre se abre la lista completa de endpoints emparejados, aunque ya haya un dispositivo seleccionado. Al escribir, la lista sigue filtrándose.

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

@@ -1,7 +1,5 @@
 <script type="text/markdown" data-help-name="matterbridge-config">
-# Bridge Matter (BETA)
-
-> Este nodo está en **BETA**: funciona, pero algunos detalles pueden cambiar entre versiones.
+# Bridge Matter
 
 ## Descripción general
 

package/nodes/locales/fr/knxUltimateMatterBridge.html

@@ -1,6 +1,4 @@
 <script type="text/markdown" data-help-name="knxUltimateMatterBridge">
-> Ce nœud est en **BETA** : il fonctionne, mais des détails peuvent encore changer entre les versions.
-
 ## Vue d'ensemble
 
 Chaque nœud Expose KNX to Matter expose **un appareil KNX comme appareil Matter** : les contrôleurs appairés (Alexa, Google Home, Apple Home...) le voient, avec le nom que vous avez choisi, prêt pour le contrôle par app et à la voix. Pointez-le vers un nœud de configuration **Bridge Matter** (le bridge lui-même, appairé une seule fois - le QR d'appairage vit là-bas) et ajoutez autant de nœuds d'appareil que vous voulez, n'importe où dans vos flux.

package/nodes/locales/fr/knxUltimateMatterBridge.json

@@ -1,6 +1,6 @@
 {
   "knxUltimateMatterBridge": {
-    "title": "Expose KNX to Matter (BETA)",
+    "title": "Expose KNX to Matter",
     "bridge_name": "Nom du bridge Matter",
     "port": "Port",
     "devices_help": "Ajoutez les appareils KNX à exposer sur Matter. Le \"Nom\" est celui qu'Alexa/Google/Apple affichent et utilisent pour les commandes vocales. GA de commande = écrite quand l'assistant envoie une commande ; GA d'état = lue depuis le bus pour tenir l'app à jour.",

package/nodes/locales/fr/knxUltimateMatterControllerDevice.html

@@ -1,6 +1,4 @@
 <script type="text/markdown" data-help-name="knxUltimateMatterControllerDevice">
-> Ce nœud est en **BETA** : le comportement peut changer pendant l amélioration de l'implémentation Matter.
-
 Ce nœud contrôle depuis KNX un endpoint Matter déjà appairé. Sélectionnez l'appareil Matter et l'éditeur détecte ses capacités, puis affiche uniquement les mappings KNX adaptés à cet endpoint.
 
 Un clic ou le focus sur le champ de l'appareil Matter ouvre toujours la liste complète des endpoints appairés, même si un appareil est déjà sélectionné. La saisie continue de filtrer la liste.

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

@@ -1,7 +1,5 @@
 <script type="text/markdown" data-help-name="matterbridge-config">
-# Bridge Matter (BETA)
-
-> Ce nœud est en **BETA** : il fonctionne, mais des détails peuvent encore changer entre les versions.
+# Bridge Matter
 
 ## Vue d'ensemble
 

package/nodes/locales/it/knxUltimateMatterBridge.html

@@ -1,6 +1,4 @@
 <script type="text/markdown" data-help-name="knxUltimateMatterBridge">
-> Questo nodo è in **BETA**: funziona, ma alcuni dettagli potrebbero cambiare tra una release e l'altra.
-
 ## Panoramica
 
 Ogni nodo Expose KNX to Matter espone **un dispositivo KNX come dispositivo Matter**: i controller abbinati (Alexa, Google Home, Apple Home...) lo vedono, con il nome che hai scelto, pronto per il controllo da app e vocale. Puntalo a un nodo di configurazione **Bridge Matter** (il bridge vero e proprio, abbinato una sola volta - il QR di abbinamento vive lì) e aggiungi quanti nodi device vuoi, ovunque nei tuoi flow.

package/nodes/locales/it/knxUltimateMatterBridge.json

@@ -1,6 +1,6 @@
 {
   "knxUltimateMatterBridge": {
-    "title": "Expose KNX to Matter (BETA)",
+    "title": "Expose KNX to Matter",
     "bridge_name": "Nome del bridge Matter",
     "port": "Porta",
     "devices_help": "Aggiungi i dispositivi KNX da esporre su Matter. Il \"Nome\" è quello che Alexa/Google/Apple mostrano e usano per i comandi vocali. GA comando = scritto quando l'assistente invia un comando; GA stato = letto dal bus per tenere aggiornata l'app.",

package/nodes/locales/it/knxUltimateMatterControllerDevice.html

@@ -1,6 +1,4 @@
 <script type="text/markdown" data-help-name="knxUltimateMatterControllerDevice">
-> Questo nodo è in **BETA**: il comportamento può cambiare mentre l'implementazione Matter viene rifinita.
-
 Questo nodo controlla da KNX un endpoint Matter già abbinato. Seleziona il dispositivo Matter e l'editor rileva le sue capability, mostrando solo le mappature KNX coerenti con quell'endpoint.
 
 Un click o il focus sul campo del dispositivo Matter apre sempre l'elenco completo degli endpoint abbinati, anche quando un dispositivo è già selezionato. Digitando, l'elenco continua a essere filtrato.

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

@@ -1,7 +1,5 @@
 <script type="text/markdown" data-help-name="matterbridge-config">
-# Bridge Matter (BETA)
-
-> Questo nodo è in **BETA**: funziona, ma alcuni dettagli potrebbero cambiare tra una release e l'altra.
+# Bridge Matter
 
 ## Panoramica
 

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

@@ -1,6 +1,4 @@
 <script type="text/markdown" data-help-name="knxUltimateMatterBridge">
-> 此节点处于 **BETA** 阶段：可以正常工作，但细节可能在版本之间发生变化。
-
 ## 概述
 
 每个 Expose KNX to Matter 节点将**一个 KNX 设备公开为 Matter 设备**：已配对的控制器（Alexa、Google Home、Apple Home...）会以您输入的名称看到它，随时可通过 App 和语音控制。将它指向一个 **Matter 桥接器**配置节点（真正的桥接器，只需配对一次 - 配对二维码在那里），然后在流程中随意添加任意数量的设备节点。

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

@@ -1,6 +1,6 @@
 {
   "knxUltimateMatterBridge": {
-    "title": "Expose KNX to Matter (BETA)",
+    "title": "Expose KNX to Matter",
     "bridge_name": "Matter 桥接器名称",
     "port": "端口",
     "devices_help": "添加要在 Matter 上公开的 KNX 设备。\"名称\"是 Alexa/Google/Apple 显示并用于语音命令的名称。命令 GA = 助手发送命令时写入；状态 GA = 从总线读取以保持 App 更新。",

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

@@ -1,6 +1,4 @@
 <script type="text/markdown" data-help-name="knxUltimateMatterControllerDevice">
-> 此节点为 **BETA**：Matter 实现继续完善时，行为可能会变化。
-
 此节点用于从 KNX 控制已经配对的 Matter endpoint。选择 Matter 设备后，编辑器会检测它的能力，并只显示与该 endpoint 匹配的 KNX 映射。
 
 单击 Matter 设备字段或使其获得焦点时，即使已经选择了设备，也会始终打开完整的已配对 endpoint 列表；输入文字仍可筛选列表。

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

@@ -1,7 +1,5 @@
 <script type="text/markdown" data-help-name="matterbridge-config">
-# Matter 桥接器 (BETA)
-
-> 此节点处于 **BETA** 阶段：可以正常工作，但细节可能在版本之间发生变化。
+# Matter 桥接器
 
 ## 概述
 

package/package.json

@@ -3,7 +3,7 @@
   "engines": {
     "node": ">=20.18.1"
   },
-  "version": "6.3.12",
+  "version": "6.3.13",
   "description": "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 with AI, virtual devices, and powerful automation nodes. Build professional, reliable, and scalable smart home and building automation projects with minimal effort.",
   "files": [
     "nodes/",