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

package/nodes/locales/en/knxUltimateMatterBridge.html

@@ -1,65 +0,0 @@
-<script type="text/markdown" data-help-name="knxUltimateMatterBridge">
-### 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/>
-
-## 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.
-
-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|
-|--|--|
-| Matter bridge | The Matter Bridge configuration node this device belongs to |
-| KNX GW | KNX gateway used for telegrams. **Optional**: without it the device runs in flow-only mode via the node PINs. Auto-selected when your project has only one gateway |
-| Name | What Alexa & Co. show and use for voice commands |
-| Device type | The Matter device type (see below); it drives which group address fields appear |
-| Read status at startup | Sends a `GroupValue_Read` to the status GAs at startup, so the Matter attributes are populated |
-
-## Device types and group addresses
-
-|Type|Group addresses|
-|--|--|
-| On/Off light, Plug | On/Off command GA, On/Off status GA (DPT 1.001) |
-| Dimmable light | + Dimming % command/status GA (DPT 5.001) |
-| RGB color light | + RGB color command/status GA (DPT 232.600). The Matter color (hue/saturation or XY, from the app color wheel) is converted to/from the KNX RGB triplet |
-| Tunable white light | + Color temperature command/status GA in Kelvin (DPT 7.600) |
-| Cover / Shutter | Up/Down (DPT 1.008), Stop (DPT 1.017), Position % command/status (DPT 5.001), optional position inversion |
-| Thermostat (heating and/or cooling) | Current temperature GA, Setpoint command/status GA (DPT 9.001). Optionally add a Cooling setpoint command/status GA to also expose a Cool mode (dual-setpoint) |
-| Room air conditioner | One Matter device combining On/Off (DPT 1.001), current temperature and heating/cooling setpoints (DPT 9.001), and fan speed % (DPT 5.001) command/status GAs |
-| Fan / Ventilation | Fan speed % command/status GA (DPT 5.001) |
-| Door lock | Lock/Unlock command GA and Locked/Unlocked status GA (DPT 1.001; `true` = locked) |
-| Sensors (temperature, humidity, light, occupancy, contact) | One status GA each |
-| Smoke/CO alarm | Smoke alarm status GA + optional CO alarm status GA (DPT 1.005): critical notifications on the phone |
-| Water leak detector | Leak status GA (DPT 1.005) |
-| Air quality sensor (CO2) | CO2 status GA in ppm (DPT 9.008); the air quality class (good/fair/moderate/poor...) is derived automatically |
-| Robot vacuum | **Flow-only**: no group addresses. Enable the node PINs: assistant commands ("start cleaning", pause/resume/go home) arrive on the output as `rvcmode`/`rvccommand`; report the state back with `msg.payload = { function: "rvcstate", value: "running"|"docked"|"charging"|"paused"|"error" }` and the mode with `function: "rvcmode", value: "cleaning"|"idle"` |
-
-- **Command GA**: written to the KNX bus when the assistant sends a command.
-- **Status GA**: read from the bus to keep the Matter attributes (and the apps) updated.
-
-## Advanced compatibility
-
-These options are hidden unless they apply to the selected type. Dimmable devices can ignore the brightness command that some controllers send immediately after `On`. For covers, **Swap Open / Close** reverses both the binary KNX command and percentage direction. **Cover slider debounce** coalesces rapid intermediate targets before writing to KNX: `0` uses adaptive windows (400 ms for the first command, 150 ms for subsequent commands); `1`–`5000` forces one fixed window. Covers can also optimistically update the Matter position after a command, then correct it when the KNX status GA reports the real position.
-
-## Node PINs
-
-The PIN selector is outside the editor tabs. Enabling it reveals a contextual **Flow input/output** section directly below, with copyable examples filtered to the selected device type:
-
-- **Input**: update the Matter state from the flow, without the KNX bus: `msg.payload = { function: "onoff", value: true }` (`function` is one of `onoff`, `level`, `rgb`, `colortemp`, `position`, `temperature`, `humidity`, `illuminance`, `occupancy`, `contact`, `currenttemp`, `setpoint`, `coolingsetpoint`, `fanspeed`, `lock`, `smoke`, `co`, `leak`, `co2`, `rvcstate`, `rvcmode`). Useful to expose flow-computed values (e.g. a virtual sensor) to Alexa & Co.
-- **Output**: every command received from a Matter controller is forwarded to the flow: `msg.topic` = device name, `msg.payload` = value, `msg.matter` = the raw command. A device without command GAs becomes a **flow-only device**.
-
-## Notes
-
-- The Matter identity of the device is tied to this node: deleting the node and creating a new one makes the apps see a brand-new device.
-- Added/renamed/removed device nodes are picked up by the paired controllers within seconds, without re-pairing the bridge.
-</script>

package/nodes/locales/en/knxUltimateMatterBridge.json

@@ -1,123 +0,0 @@
-{
-  "knxUltimateMatterBridge": {
-    "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.",
-    "read_status_startup": "Read the status group addresses at startup",
-    "opt_yes": "Yes",
-    "opt_no": "No",
-    "node_pins": "Node Input/Output PINs",
-    "node_pins_hide": "Hide",
-    "node_pins_show": "Show node input/output PINs",
-    "type_change_warning": "Changing the device type after the bridge has been paired changes the Matter endpoint structure. Alexa/Google/Apple may keep the old endpoint as unreachable; you may need to reset/re-pair the Matter Bridge or create a new exposed device instead.",
-    "fields": {
-      "type": "Device type",
-      "name": "Name (shown by Alexa & Co.)",
-      "name_placeholder": "e.g. Kitchen light",
-      "invert": "Invert position %"
-    },
-    "advanced": {
-      "title": "Advanced compatibility",
-      "help": " Use these options only when a Matter controller or a KNX actuator needs special handling.",
-      "alexa_dedup_ms": "Alexa duplicate-command window (ms, 0 = off)",
-      "turn_on_behavior": "Turn-on behavior",
-      "turn_on_ignore_level": "Ignore brightness sent immediately after On",
-      "turn_on_forward_all": "Forward every brightness command",
-      "ignore_level_ms": "Ignore brightness after On (ms)",
-      "cover_swap_open_close": "Swap cover Open / Close",
-      "cover_slider_debounce": "Cover slider debounce (ms, 0 = adaptive)",
-      "cover_update_mode": "Cover state update",
-      "cover_optimistic": "Optimistically update Matter position",
-      "cover_wait_status": "Wait for KNX status only",
-      "cover_status_timeout": "Cover status timeout (ms)"
-    },
-    "tabs": {
-      "mappings": "KNX mappings",
-      "advanced": "Advanced options"
-    },
-    "flow_help": {
-      "title": "Flow input/output",
-      "intro": "These examples match the selected device type and are available while the node input/output PINs are enabled.",
-      "input_title": "Flow → Matter (node input)",
-      "input_hint": "Send one of these messages to update the exposed Matter state without writing to KNX.",
-      "output_title": "Matter → Flow (node output)",
-      "output_hint": "Commands received from a Matter controller are emitted with the value in msg.payload and raw routing details in msg.matter.",
-      "function": "Function",
-      "message": "Example message",
-      "copy": "Copy",
-      "copied": "Message copied",
-      "no_input": "This device type has no flow state-update examples.",
-      "no_output": "This device type does not emit controller commands; its output remains silent."
-    },
-    "functions": {
-      "fn_onoff_cmd": "On/Off command GA",
-      "fn_onoff_status": "On/Off status GA",
-      "fn_level_cmd": "Dimming % command GA",
-      "fn_level_status": "Dimming % status GA",
-      "fn_sensor_ga": "Sensor status GA",
-      "fn_updown": "Up/Down command GA",
-      "fn_stop": "Stop command GA",
-      "fn_position_cmd": "Position % command GA",
-      "fn_position_status": "Position % status GA",
-      "fn_currenttemp": "Current temperature GA",
-      "fn_setpoint_cmd": "Setpoint command GA",
-      "fn_setpoint_status": "Setpoint status GA",
-      "fn_coolingsetpoint_cmd": "Cooling setpoint command GA",
-      "fn_coolingsetpoint_status": "Cooling setpoint status GA",
-      "fn_rgb_cmd": "RGB color command GA (DPT 232.600)",
-      "fn_rgb_status": "RGB color status GA (DPT 232.600)",
-      "fn_ct_cmd": "Color temperature command GA (Kelvin)",
-      "fn_ct_status": "Color temperature status GA (Kelvin)",
-      "fn_smoke_ga": "Smoke alarm status GA",
-      "fn_co_ga": "CO alarm status GA (optional)",
-      "fn_leak_ga": "Leak status GA",
-      "fn_co2_ga": "CO2 status GA (ppm, DPT 9.008)",
-      "fn_fanspeed_cmd": "Fan speed % command GA",
-      "fn_fanspeed_status": "Fan speed % status GA",
-      "fn_lock_cmd": "Lock/Unlock command GA",
-      "fn_lock_status": "Locked/Unlocked status GA"
-    },
-    "types": {
-      "onofflight": "On/Off light",
-      "dimmablelight": "Dimmable light",
-      "rgblight": "RGB color light",
-      "colortemperaturelight": "Tunable white light (color temperature)",
-      "onoffplug": "Plug / Socket (on/off)",
-      "temperaturesensor": "Temperature sensor",
-      "humiditysensor": "Humidity sensor",
-      "lightsensor": "Light sensor (Lux)",
-      "occupancysensor": "Occupancy sensor",
-      "contactsensor": "Contact sensor",
-      "windowcovering": "Cover / Shutter",
-      "thermostat": "Thermostat (heating)",
-      "roomairconditioner": "Room air conditioner",
-      "fan": "Fan / Ventilation",
-      "doorlock": "Door lock",
-      "smokecoalarm": "Smoke/CO alarm",
-      "waterleakdetector": "Water leak detector",
-      "airqualitysensor": "Air quality sensor (CO2)",
-      "robotvacuum": "Robot vacuum (flow-only, via node PINs)"
-    },
-    "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:",
-      "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 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."
-    },
-    "bridge": "Matter bridge",
-    "device_name": "Name (shown by Alexa & Co.)",
-    "device_help": "Pick the device type and give it the name the voice assistant will use, then fill the group addresses. The KNX gateway is optional: without it, enable the node PINs and drive the device from the flow."
-  },
-  "common": {
-    "ga": "GA",
-    "dpt": "DPT",
-    "name": "Name",
-    "knx_gw": "KNX GW"
-  }
-}

package/nodes/locales/en/knxUltimateMatterControllerDevice.html

@@ -1,57 +0,0 @@
-<script type="text/markdown" data-help-name="knxUltimateMatterControllerDevice">
-### 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/>
-
-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.
-
-It replaces the unpublished per-device Matter controller nodes and keeps the full light UI when the selected endpoint is a light.
-
-## Configuration
-
-|Field|Description|
-|--|--|
-| KNX GW | KNX gateway used to write and answer the configured group addresses. It can be left empty when only Node-RED output is needed. The saved gateway remains selected while the editor initializes and changes only after an explicit user selection. |
-| Matter controller | Matter controller configuration node where the device has been commissioned. |
-| Matter device | Matter endpoint selected from commissioned devices. The UI is rebuilt from its real capabilities. |
-| Switch / Plug / Light On-Off | On/Off command and status group addresses, usually DPT `1.001`. |
-| Door Lock | A DPT `1.xxx` command GA invokes `lockDoor` for `true` and `unlockDoor` for `false`; a separate status GA receives only unambiguous Locked/Unlocked states. If the endpoint requires it, store the remote-operation PIN in the credential field. Commands not advertised by the endpoint are rejected. |
-| Other endpoints | Plugs, On/Off actuators, covers, thermostats, fans, environmental/contact/occupancy sensors, battery, power and energy endpoints use the multi-purpose mapped profile. The dedicated **Mappings** tab contains only mappings backed by clusters, attributes and commands advertised by that endpoint; leave a GA empty to disable it. |
-| Light controls | For light endpoints, the same light UI is used: relative DIM (DPT `3.007`), brightness %, RGB/HSV, tunable white, switch-on brightness/temperature, day/night lighting, min/max dim level and dim speed. Unsupported sections are hidden. |
-| Sensors | Sensor endpoints expose their measurement/status GA only when supported: temperature, humidity, illuminance, occupancy, contact and battery. |
-| Read at startup | Publishes the cached Matter value at deploy/startup or when the device reconnects. |
-| Update local state from KNX write | Updates the local Matter/KNX cache when a telegram is written on a configured KNX GA. |
-| Node Input/Output PINs | Shows Node-RED input/output pins and reveals the **Flow input** section directly below this field. Lights show their supported top-level light-state messages; non-light endpoints show the simple `{function,value}` contract and advanced Matter fields. The selection is preserved when the editor is reopened. |
-
-## Flow input
-
-Enable **Node Input/Output PINs** to reveal the **Flow input** section directly below the selector. For lights it shows copyable examples for the supported top-level properties, such as `msg.on`, `msg.dimming`, `msg.color_temperature` and `msg.color`. For non-light endpoints it is built from the advertised structure and provides the selected Endpoint ID, every readable/writable attribute and every accepted command. It remains available when the node is used only by a flow without a KNX gateway.
-
-Simple writes use `msg.payload = {function:"position",value:35}`. Omit `value` to read a supported state, for example `{function:"temperature"}`; the output uses human units and includes raw routing details in `msg.matter`. Supported functions include `onoff`, `level`, `position`, `tiltposition`, `open`, `close`, `stop`, `setpoint`, `coolingsetpoint`, `currenttemp`, `fanspeed`, sensor readings and `identify`, but only when advertised by that endpoint. Door Lock accepts `{function:"lock",value:true|false}`.
-
-Existing advanced inputs remain valid: use top-level `msg.clusterId` plus `msg.command`/`msg.args`, or `msg.attribute` with optional `msg.value`. Node ID and Endpoint ID are already selected by the node; `msg.endpointId` is only an optional override.
-
-## Universal Mode
-
-Select **Universal Mode** in the **Mode** selector to receive every attribute report, cluster event and device initialization from this Matter controller. It always has one input and one output and does not use endpoint mappings. A KNX gateway is optional and is used only by the Battery Monitor alarm/text GAs.
-
-The **Universal Battery Monitor** scans all endpoints for Power Source, emits an initial snapshot, and caches complete normalized battery state. The optional KNX GAs publish an aggregate alarm as DPT 1.005 and cycle low-battery device names every 2 seconds as DPT 16.001. Send `{payload:{action:"getAllBatteries"}}` to retrieve the cached inventory.
-
-Outputs carry the raw value in `msg.payload` and routing details in `msg.matter` (`source`, `nodeId`, `endpointId`, `clusterId`, attribute/event name). Inputs use `msg.nodeId`, `msg.endpointId`, `msg.clusterId` and either `msg.command` with `msg.args`, or `msg.attribute`; add `msg.value` to write, omit it to read. The selectors may also be nested under `msg.matter`.
-
-Examples: `{nodeId:"100",endpointId:1,clusterId:6,command:"on",args:{}}` turns On; `{nodeId:"100",endpointId:1,clusterId:47,attribute:"batPercentRemaining"}` reads battery. Battery reports remain in raw Matter half-percent units; divide by two in a Function node when a percentage is needed.
-
-## Behaviour
-
-The node keeps a local cache from Matter updates and KNX writes, answers KNX read requests from that cache, and can emit/read values at startup. Only the configured group addresses are listened to, so unrelated KNX traffic is ignored.
-
-Commands are scheduled in a separate ordered lane for each commissioned device. An offline, timing-out or removed device therefore cannot delay other Matter devices that use the same KNX group address. A node that still references a removed device rejects the command immediately and shows **Device no longer commissioned** in red; select a valid Matter device or remove the stale Controller node.
-
-An unavailable-device error is latched: further KNX and flow commands are ignored and cannot overwrite the red status. The node resumes automatically as soon as that Matter device reports `connected`; opening the node editor also clears the latch to allow a manual retry.
-</script>

package/nodes/locales/en/knxUltimateMatterControllerDevice.json

@@ -1,146 +0,0 @@
-{
-  "knxUltimateMatterControllerDevice": {
-    "title": "Control Matter from KNX",
-    "node-input-name": "Name",
-    "node-input-nameLightSwitch": "Switch (bit)",
-    "node-input-GALightSwitch": "GA",
-    "node-input-dptLightSwitch": "dpt",
-    "node-input-nameLightState": "State (bit)",
-    "node-input-GALightState": "GA",
-    "node-input-dptLightState": "dpt",
-    "node-input-hueLight": "Matter device",
-    "paletteLabel": "Control Matter from KNX",
-    "no_devices": "No Matter devices found. Check the Matter controller and click refresh.",
-    "input_help_label": "Flow input",
-    "input_help_pin_hint": "Enable the node input/output PINs before sending these messages.",
-    "input_help_endpoint": "Selected endpoint",
-    "input_help_endpoint_hint": "The node already knows the Node ID and Endpoint ID, so the simple messages do not need them.",
-    "input_help_simple_title": "Simple messages",
-    "input_help_simple_hint": "These functions use human units and are translated to the Matter cluster, command or attribute shown by the selected endpoint.",
-    "input_help_light_hint": "Light endpoints accept light-state properties directly on msg (not inside msg.payload). Only controls supported by the selected light are shown.",
-    "input_help_advanced_title": "Advanced Matter details",
-    "input_help_advanced_hint": "Only advertised attributes and commands are listed. Attribute write examples use 0 as a placeholder; command arguments may need to be adapted to the Matter data type.",
-    "input_help_operation": "Operation",
-    "input_help_function": "Function",
-    "input_help_target": "Matter target",
-    "input_help_message": "Message",
-    "input_help_read": "Read",
-    "input_help_write": "Write",
-    "input_help_command": "Command",
-    "input_help_copy": "Copy",
-    "input_help_copied": "Message copied",
-    "input_help_no_simple": "This endpoint has no known simple input functions.",
-    "input_help_no_structure": "The Matter structure is unavailable. Refresh the device list while the endpoint is online.",
-    "input_functions": {
-      "onoff": "On / Off", "on": "On", "off": "Off", "level": "Level", "brightness": "Brightness", "color_temperature": "Colour temperature", "xy_color": "XY colour", "position": "Cover position", "tiltposition": "Cover tilt", "open": "Open", "close": "Close", "stop": "Stop", "setpoint": "Heating setpoint", "coolingsetpoint": "Cooling setpoint", "currenttemp": "Current temperature", "fanspeed": "Fan speed", "temperature": "Temperature", "humidity": "Humidity", "illuminance": "Illuminance", "occupancy": "Occupancy", "contact": "Contact", "battery": "Battery", "activepower": "Active power", "importedenergy": "Imported energy", "identify": "Identify", "lock": "Lock", "unlock": "Unlock"
-    },
-    "tabs": {
-      "switch": "Switch",
-      "dim": "Dim",
-      "tunable_white": "Tunable white",
-      "rgb_hsv": "RGB/HSV",
-      "effects": "Effects",
-      "mappings": "Mappings",
-      "behaviour": "Behaviour"
-    },
-    "control": "Control",
-    "status": "Status",
-    "door_lock_command": "Lock / unlock",
-    "door_lock_status": "Lock state",
-    "door_lock_pin": "Remote-operation PIN",
-    "door_lock_pin_required": "This lock reports that a PIN is required for remote operation.",
-    "door_lock_commands_missing": "This endpoint does not advertise both lock and unlock commands. Missing commands will be rejected.",
-    "mapped": {
-      "onoff_command": "On / Off command", "onoff_state": "On / Off state", "cover_updown": "Cover up / down", "cover_stop": "Cover stop", "cover_position_command": "Cover position command", "cover_position_state": "Cover position state", "heating_command": "Heating setpoint command", "heating_state": "Heating setpoint state", "cooling_command": "Cooling setpoint command", "cooling_state": "Cooling setpoint state", "local_temperature": "Local temperature", "fan_command": "Fan speed command", "fan_state": "Fan speed state", "temperature": "Temperature", "humidity": "Humidity", "illuminance": "Illuminance", "occupancy": "Occupancy", "contact": "Boolean / contact state", "battery": "Battery", "active_power": "Active power", "imported_energy": "Imported energy"
-    },
-    "night_lighting": "Night Lighting",
-    "no_night_lighting": "No night lighting",
-    "get_current": "Get current",
-    "get_again": "Get again",
-    "wait": "Wait...",
-    "locate_no_bridge": "Select a Matter controller first",
-    "locate_no_device": "Select a Matter device first",
-    "locate_success": "Locate command sent",
-    "locate_started": "Locate mode started. Press again to stop (auto-stops after 10 minutes).",
-    "locate_stopped": "Locate mode stopped.",
-    "locate_start_title": "Locate selected Matter device",
-    "locate_stop_title": "Stop locate mode",
-    "locate_error": "Unable to locate Matter device",
-    "day_night": "Day/Night",
-    "invert_day_night": "Invert day/night value",
-    "override_night_mode": "Force day mode",
-    "override_no": "No",
-    "override_set_day_fast_this": "Switch to DAY mode by rapid switching the light off then on (this light only)",
-    "override_set_day_fast_all": "Switch to DAY mode by rapid switching the light off then on (apply to ALL light nodes)",
-    "node_pins": "Node Input/Output PINs",
-    "node_pins_hide": "Hide",
-    "node_pins_show": "Show node input/output PINs",
-    "read_status_startup": "Read status at startup",
-    "opt_no": "No",
-    "opt_yes_emit": "Yes, and emit KNX telegrams.",
-    "knx_brightness_status": "KNX Brightness Status",
-    "knx_brightness_onhueoff": "When the Matter light is Off send 0%. When it is On, restore the previous value (default KNX behaviour)",
-    "knx_brightness_no": "Leave as is (default Matter behaviour)",
-    "update_local_state_from_knx_write": "Update local cached Matter state from KNX bus writes",
-    "update_local_state_from_knx_write_hint": "Enabled: faster local reactions and consistent immediate KNX read responses. Disabled: keep the cache aligned only with real Matter reports.",
-    "use_min_brightness": "Use minimum brightness specified for the Matter light",
-    "k_suffix": "K",
-    "temp_desc_2200": "(start of Philips White Ambiance lights range)",
-    "temp_desc_2700": "(warm white, intimate, cozy, personal, for living rooms)",
-    "temp_desc_3000": "(soft white, warm, calming, for bathrooms and kitchens)",
-    "temp_desc_3500_day": "(neutral white, balanced, friendly, inviting, for office spaces and retail)",
-    "temp_desc_3500_night": "(not recommended for night time - neutral white, for office spaces and retail)",
-    "temp_desc_4100_day": "(cool white, precise, clean, focused, for garages and grocery stores)",
-    "temp_desc_4100_night": "(not recommended for night time - cool white, precise, clean, focused, for garages and grocery stores)",
-    "temp_desc_5000_day": "(bright white, vibrant, crisp, for warehouses, sports stadiums and healthcare)",
-    "temp_desc_5000_night": "(not recommended for night time - bright white, vibrant, crisp, for warehouses, sports stadiums and healthcare)",
-    "temp_desc_6500_day": "(daylight, alert, energetic, for indoor agriculture)",
-    "temp_desc_6500_night": "(not recommended for night time - daylight, alert, energetic, for indoor agriculture)",
-    "switch_on_behaviour": "Switch on behaviour",
-    "none": "None",
-    "switch_off": "(Switch Off)",
-    "select_color": "Select color",
-    "select_temperature_brightness": "Select temperature and brightness",
-    "select_brightness": "Select brightness",
-    "effect_command": "Effect command",
-    "effect_status": "Effect status",
-    "effect_mapping": "Mappings",
-    "effect_autofill": "Fill with available effects",
-    "effect_tip": "Provide KNX value / Matter effect pairs. When the incoming KNX payload matches the value, the selected effect is applied to the light.",
-    "effect_tip_status": "If a status group address is configured, the current Matter effect is emitted using the mapped KNX value or the effect name.",
-    "effect_not_supported": "This light does not expose Matter effects.",
-    "effect_knx_value_placeholder": "Value to match",
-    "effect_base_label": "Basic Matter effects",
-    "effect_native_label": "Native Matter effects",
-    "matter_controller": "Matter controller",
-    "matter_device": "Matter device",
-    "device_type": "Device type",
-    "matter_section": "Matter device",
-    "controller_mode": "Mode",
-    "single_mode": "Single device",
-    "universal_mode": "Universal Mode (all Matter devices)",
-    "universal_mode_description": "Listen to and control all Matter devices connected to this controller. Universal Mode works without KNX mappings.",
-    "universal_service": "Service",
-    "universal_service_battery_monitor": "Universal Battery Monitor",
-    "universal_service_all_events": "All Matter events",
-    "universal_battery_threshold": "Low battery threshold",
-    "universal_low_battery_ga": "Low battery alarm GA",
-    "universal_low_battery_text_ga": "Low battery device GA",
-    "universal_battery_only_low": "Emit only low batteries",
-    "universal_emit_initial": "Emit initial battery snapshot",
-    "universal_include_raw": "Include raw Matter event",
-    "universal_mode_status": "Universal Matter mode",
-    "universal_mode_locate_disabled": "Locate is unavailable in Universal Mode.",
-    "universal_controller_name": "Matter Universal Controller"
-  },
-  "common": {
-    "ga": "GA",
-    "dpt": "DPT",
-    "name": "Name",
-    "youtube_sample": "Youtube sample",
-    "knx_gw": "KNX GW",
-    "hue_bridge": "Matter controller",
-    "philips_hue": "Matter",
-    "read": "Read"
-  }
-}

package/nodes/locales/en/knxUltimateSceneController.html

@@ -1,117 +0,0 @@
-<script type="text/markdown" data-help-name="knxUltimateSceneController">
-### 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>The scene controllre node, behaves exactly as a scene controller KNX device. It's capable of saving and recalling a scene.</p>
-
-# SCENE CONTROLLER NODE SETTINGS
-
-| Property | Description |
-| ------------ | ---------------------------------------------------------------------------------------------------- |
-| Gateway | Selected KNX gateway. |
-| Scene Recall | **Datapoint ** and**Trigger Value ** . Group Address for scene recall. Example 0/0/1. The scene controller will react to telegrams coming from this group address, to recall the scene. The datapoint is the datapoint type (DPT) of the _scene recall_ group address. The Trigger Value is the value that must be reveived, to trigger the scene recall.**Remember ** : to trigger a scene or save a scene via a DIM command, put in the scene recall or scene save**trigger value** , the correct object for dimming ({decr\_incr:1,data:5} for dim increase, {decr\_incr:0,data:5} for dim decrease) |
-| Scene Save | **Datapoint ** and**Trigger Value ** . Group Address for saving a scene. Example 0/0/2. The scene controller will react to telegrams coming from this group address, by saving all the current values of all devices in the scene, that can be recalled later. Every time you press, or long press a real knx pushbutton in your building, the scene controller will read the values of all devices in the scene and save it in a non volatile storage. The datapoint is the datapoint type (DPT) of the _scene save_ group address. The Trigger Value is the value that must be reveived, to trigger the scene saving.**Remember ** : to trigger a scene or save a scene via a DIM command, put in the scene recall or scene save**trigger value** , the correct object for dimming ({decr\_incr:1,data:5} for dim increase, {decr\_incr:0,data:5} for dim decrease) |
-| Node name | Node name, in the format "Recall: device name used to recall the scene / Save: device name for saving the scene". But you can set whatever name you want. |
-| Topic | Node's topic. |
-
-## SCENE CONFIGURATION
-
-You need to add devices to the scene, like a standard real scene controller knx device. This is a list, each row represents a device.
-
-_ **The scene node automatically saves the updated values of all actuators belonging to the scene, whenever it receives a new value from the BUS.** _
-
-| Property | Description |
-| ------------- | ---------------------------------------------------------------------------------------------------- |
-| ADD button | Add a row to the list. |
-| Row's field | First field is the group address, second is the datapoint, third is the default value for this device in the scene (this can be overridden by the _scene save_ function). Below, is the device name.<br/> To insert a _pause_, type **wait ** in the first field and a number in the last field, that represents the time (in milliseconds) of the pause, for example**2000 ** <br/><br>The**wait ** command accept also values indicating seconds, minutes or hours.<br>To set a value in seconds, add**s ** after the numeric value, for example (**12s ** )<br>To set a value in minutes, add**m ** after the numeric value, for example (**5m ** )<br>To set a value in hours, add**h ** after the numeric value, for example (**1h** ) |
-| Remove button | Remove a device from the list. |
-
-# MESSAGE OUTPUT FROM THE SCENE CONTROLLER NODE
-
-```javascript
-
-msg = {
-    topic: "Scene Controller" <i>(Contains the node's topic, for example "MyTopic").</i>
-    recallscene: <i>(<b>true</b> if a scene has been recalled, otherwise <b>false</b>).</i> 
-    savescene: <i>(<b>true</b> if a scene has been saved, otherwise <b>false</b>).</i> 
-    savevalue: <i>(<b>true</b> if a group address value belonging to an actuator in the scene, has been manually saved by a msg input, otherwise <b>false</b>).</i> 
-    disabled: <i>(<b>true</b> if the scene controller has been disabled via input message msg.disabled = true, otherwise <b>false</b>).</i> 
-}
-
-```
-
----
-
-# INPUT FLOW MESSAGE
-
-The Scene Controller node reacts primarly to KNX telegrams and rely to that to recall and save scenes.
-
-You can, however, recall and save scenes by sending a msg to the node. The scene controller can be disabled to inhibite the commands coming from the KNX Bus.
-
-**RECALL A SCENE**
-
-```javascript
-
-// Example of a function that recall the scene
-msg.recallscene = true; 
-return msg;
-
-```
-
-**SAVE A SCENE**
-
-```javascript
-
-// Example of a function that saves the scene
-msg.savescene = true; 
-return msg;
-
-```
-
-**SAVE CURRENT VALUE OF A GROUP ADDRESS ** _**The scene node already saves the updated values of all actuators belonging to the scene.** _
-
-Sometimes it is useful to be able to save the current value of a group address that is different from the one entered in the scene, as the real value of the scene actuator.
-
-For example, a shutter actuator usually has a command group address and a status one.
-
-The node saves the scene by taking command group address values, which may not be aligned with the true state value.
-
-However, you can work around this by manually updating the command group address value, taking it from the status group address.
-
-Think this: if you have a blind actuator, having a group address for move, a group address for step, a group address for absolute height etc... the only group address knowing the exact position of the blind, is the **absolute height value status** group address. <br/>
-
-With this status group address, you can update the command group addresses of the blind actuators belonging to the scene. Please see the sample in the wiki.
-
-```javascript
-
-// Example of a function that saves the status of a blind actuator, belongind to the scene.
-msg.savevalue = true; 
-msg.topic = "0/1/1";
-msg.payload = 70;
-return msg;
-
-```
-
-**DISABLE SCENE CONTROLLER**
-
-You can disable the scene controller (it disables the reception of telegram from KNX BUS but the node still accept the input msg from the flow instead). Sometime is advisable to disable the recall and save of a scene, for example, when it's night and you call, from a KNX Pushbutton, a "TV Scene" that raises or lowers a blind, the scene won't be recalled or saved. Instead, you can enable another scene, just for night, for example to dim a series of lights.
-
-```javascript
-
-// Example of disabling the scene controller. The commands coming from KNX BUS will be disabled. The node still accept the input msg from the flow instead!
-msg.disabled = true; // Otherwise "msg.disabled = false" to re-enable the node.
-return msg;
-
-```
-
-## SEE ALSO
-
-[Sample Scene Controller](https://supergiovane.github.io/node-red-contrib-knx-ultimate/wiki/Sample-Scene-Node)
-</script>

package/nodes/locales/en/knxUltimateSceneController.json

@@ -1,32 +0,0 @@
-{
-    "knxUltimateSceneController": {
-        "paletteLabel": "KNX Scene Controller (deprecated)",
-        "title": "Scene controller",
-        "properties": {
-            "node-input-server": "Gateway",
-            "node-input-topic": "Scene Recall",
-            "node-input-dpt": "Datapoint",
-            "node-input-topicTrigger": "Trigger",
-            "node-input-topicSave": "Scene Save",
-            "node-input-name": "Node Name",
-            "node-input-outputtopic": "Topic"
-        },
-        "placeholder": {
-            "leaveempty": "Leave empty to use Group Address",
-            "valueexample": "Ex: false, true, otherwise any value"
-        },
-        "other": {
-            "sceneConfig": "Scene default values configuration",
-            "add": "Press ADD, to add a device in the scene"
-        },
-        "advanced": {
-            "notify-DPT3007": "You selected a relative DIM. Please <a target='_blank' href='https://supergiovane.github.io/node-red-contrib-knx-ultimate/wiki/-Sample---Dimming'>click here to view this sample</a> and learn how to handle such payload.",
-            "notify-DPT18001": "You selected a scene Datapoint. Please <a target='_blank' href='https://supergiovane.github.io/node-red-contrib-knx-ultimate/wiki/-Sample---Control-a-scene-actuator'>click here to view this sample</a> and learn how to handle such payload.",
-            "notify-DPT232600": "You selected an RGB Datapoint. Please <a target='_blank' href='https://supergiovane.github.io/node-red-contrib-knx-ultimate/wiki/-Sample---RGB-Color'>click here to view this sample</a> and learn how to handle such payload.",
-            "notify-DPT251600": "You selected an RGBW Datapoint. Please <a target='_blank' href='https://supergiovane.github.io/node-red-contrib-knx-ultimate/wiki/-Sample---RGBW-Color-plus-White'>click here to view this sample</a> and learn how to handle such payload."
-        },
-        "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/knxUltimateStaircase.html

@@ -1,77 +0,0 @@
-<script type="text/markdown" data-help-name="knxUltimateStaircase">
-### 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.
-
-# KNX STAIRCASE LIGHT
-
-<p>Use this node to implement a KNX staircase timer. It listens for trigger pulses, drives the output actuator, mirrors the state on a status GA and honours manual override or block commands.</p>
-
-**Group addresses**
-
-|Property|Description|
-|--|--|
-| Trigger GA | Binary input that starts the timer when it receives `1`. If “0 command cancels the cycle” is enabled, a `0` stops the light immediately. |
-| Output GA | Actuator driven while the cycle is active. Select the DPT that matches the load (binary, dimming, analog, …). |
-| Status GA | Mirrors the active/pre-warning state. With pre-warning in *Toggle status GA* mode it will briefly change state before timeout. |
-| Override GA | Forces the light ON and pauses the timer for the duration of the override signal. |
-| Block GA | When true, new triggers are ignored. Depending on *When blocked* the light is either forced OFF or left untouched. |
-
-**Timer behaviour**
-
-|Option|Description|
-|--|--|
-| Timer duration | Base countdown length for the staircase cycle. |
-| On new trigger | Choose whether further pulses restart the timer, extend it by the configured duration, or are ignored. |
-| 0 command cancels the cycle | Ends the cycle with reason `manual-off` when the trigger returns to `0`. |
-| When blocked | Decide if a block command should only inhibit new triggers or also force the output off. |
-
-**Pre-warning**
-
-|Option|Description|
-|--|--|
-| Send pre-warning | Enables the alert before timeout. |
-| Pre-warning offset | Seconds before the end when the alert is triggered. |
-| Pre-warning mode | *Toggle status GA* briefly toggles the status address. *Flash output* switches the output off and back on after the configured flash duration. |
-| Flash duration | Time in milliseconds the output remains off when flashing. |
-
-**Node output**
-
-- When *Emit events* is enabled the node outputs structured objects describing `trigger`, `extend`, `prewarn`, `timeout`, `override`, `block` and `manual-off` events. Each payload includes `event`, `remaining`, `active`, `override`, `blocked` and optional details.
-- Without events enabled you can rely on the KNX status GA for automation feedback.
-
-## Inputs
-
-|Property|Description|
-|--|--|
-| Flow input | Send `true`, `false`, `"open"` or `"close"` from the flow to start or cancel the timer. |
-| KNX telegrams | The node reacts to telegrams for the configured group addresses. |
-
-## Flow example
-
-```javascript
-
-// Start the staircase timer
-msg.payload = true;
-return msg;
-```
-
-```javascript
-// Cancel the timer (requires '0 command cancels the cycle')
-msg.payload = false;
-return msg;
-```
-
-## Outputs
-
-|Property|Description|
-|--|--|
-| Events (optional) | Sends the event objects when *Emit events* is checked. |
-
-</script>