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

package/nodes/locales/en/knxUltimateGarage.html

@@ -1,79 +0,0 @@
-<script type="text/markdown" data-help-name="knxUltimateGarage">
-### 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 GARAGE DOOR
-
-<p>Control a KNX garage door with direct Boolean commands or toggle impulses, optional hold-open / disable GAs, safety photocell feedback and automatic re-close. The node can emit movement and obstruction indicators as well as structured events for the flow.</p>
-
-**Command group addresses**
-
-|Property|Description|
-|--|--|
-| Command GA (true=open, false=close) | Boolean GA (`gaCommand`) where `true` opens and `false` closes. Default DPT 1.001. |
-| Impulse GA | Rising edge toggles the door (`gaImpulse`, default DPT 1.017). Used automatically when no direct command GA is provided. |
-| Hold-open GA | Keeps the door open and cancels auto re-close while true (`gaHoldOpen`). |
-| Disable GA | Blocks any command emitted by the node (`gaDisable`). Useful during maintenance/manual mode. |
-
-**Input / sensor group addresses**
-
-|Property|Description|
-|--|--|
-| Photocell GA | Goes true when the beam is interrupted; the node reopens and flags obstruction (`gaPhotocell`). |
-| Moving GA | Optional pulse when the node commands movement so other devices can follow the motion (`gaMoving`). |
-| Obstruction GA | Mirrors the obstruction status for dashboards, alarms or logic blocks (`gaObstruction`). |
-
-**Automatic re-close**
-
-- Enable *Auto re-close* to start a countdown whenever the door becomes open.
-- Hold-open or disable cancel the timer until they return to false.
-- When the timer expires the node sends the close command (or impulse) and raises an `auto-close` event.
-
-**Safety**
-
-- A photocell true during closing immediately reopens the door and sets the obstruction flag.
-- External writes to the obstruction GA keep the internal status aligned with dashboards.
-- Movement pulses can drive ventilation, lighting or alarm routines.
-
-## Inputs
-
-|Property|Description|
-|--|--|
-| `msg.payload` | Accepts `true`, `false`, `'open'`, `'close'` or `'toggle'` to control the door from the flow. |
-| KNX telegrams | Reacts to the configured GAs (command, impulse, hold-open, disable, photocell, moving, obstruction). |
-
-## Flow example
-
-```javascript
-
-// Open the door
-msg.payload = 'open'; // also accepts true
-return msg;
-```
-
-```javascript
-// Close the door
-msg.payload = 'close'; // also accepts false
-return msg;
-```
-
-```javascript
-// Toggle the door state
-msg.payload = 'toggle';
-return msg;
-```
-
-## Outputs
-
-|Property|Description|
-|--|--|
-| Events (optional) | With *Emit events* enabled the node outputs objects containing `event`, `state`, `disabled`, `holdOpen` and `obstruction` so you can log or supervise the door. |
-
-</script>

package/nodes/locales/en/knxUltimateGarage.json

@@ -1,51 +0,0 @@
-{
-  "knxUltimateGarage": {
-    "title": "Garage door",
-    "paletteLabel": "Garage (deprecated)",
-    "node-input-server": "KNX Gateway",
-    "node-input-name": "Name",
-    "node-input-outputtopic": "Topic for emitted events",
-    "command": "Command GA (true=open, false=close)",
-    "impulse": "Impulse GA",
-    "holdOpen": "Hold-open GA",
-    "disable": "Disable GA",
-    "photocell": "Photocell GA",
-    "moving": "Moving GA",
-    "obstruction": "Obstruction GA",
-    "autoCloseEnable": "Enable auto re-close",
-    "autoCloseSeconds": "Auto re-close delay (seconds)",
-    "node-input-emitEvents": "Emit events on node output",
-    "placeholders": {
-      "outputtopic": "Optional topic for node events",
-      "ga": "e.g. 1/2/3",
-      "commandName": "Door actuator",
-      "impulseName": "Impulse input",
-      "holdOpenName": "Hold-open switch",
-      "disableName": "Disable command",
-      "photocellName": "Photocell sensor",
-      "movingName": "Movement indicator",
-      "obstructionName": "Obstruction indicator"
-    },
-    "help": {
-      "intro": "Controls a KNX garage door with direct open/close commands, impulse inputs, safety sensors and automatic re-close.",
-      "commands": "Commands",
-      "command_ga": "Use the command GA for boolean control: true opens, false closes. The node also emits this when the auto close triggers.",
-      "impulse_ga": "An impulse GA toggles the door. Rising edges toggle the internal state; it is also used if no direct command GA is configured.",
-      "holdopen_ga": "Hold-open GA keeps the door open and cancels the auto re-close until it returns to false.",
-      "disable_ga": "Disable GA stops the node from issuing new commands. Useful for maintenance or manual mode.",
-      "safety": "Safety and status",
-      "photocell_ga": "The photocell GA should go true when the beam is interrupted. The node re-opens the door and flags obstruction.",
-      "moving_ga": "Movement GA (optional) is pulsed whenever the node commands the door to move, allowing other devices to follow the motion.",
-      "obstruction_ga": "Obstruction GA mirrors the obstruction state so other KNX components can react.",
-      "auto": "Automatic re-close",
-      "auto_close": "Enable the auto re-close timer to close the door automatically after the configured delay once it is open, unless hold-open or disable are active.",
-      "events": "Node output",
-      "events_desc": "With event emission enabled the node outputs structured messages (open, close, toggle, obstruction, disabled, hold-open, auto-close) for flow logic."
-    },
-    "section_commands": "Command group addresses",
-    "section_inputs": "Input / sensor 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/knxUltimateGlobalContext.html

@@ -1,124 +0,0 @@
-<script type="text/markdown" data-help-name="knxUltimateGlobalContext">
-### 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 GLOBAL VARIABLE
-
-This node exposes the group address received from the bus, to a **global variable** <br/>
-You can write to the KNX BUS by simply update the global variable!<br/>
-
-## Overview
-
-Put a Global Context Node into the flow, then give it a name.<br/>
-The name you give to the node, will become the global context variable's name.<br/>
-That's all. For security reasons, please **change the default node name** <br/>
-You can access the global variable by adding the suffix \_READ to the node's name.<br/>
-You can enable/disable the global context variable, or enable READONLY or READ/WRITE in the configuration window.<br/>
-You can issue a KNX BUS write command, by simply modify the global variable name with suffix \_WRITE. _ **After the commands have been executed, the global variable with suffix \_WRITE is automatically emptied, not to infinitely repeat the commands. ** _ <br/>**Settings**
-
-|Property|Description|
-|--|--|
-| Gateway | The KNX Gateway. |
-| Variable Name (no spaces, only chars [a-z]) | Name of the global context. 2 variables with this name will be created, one with \_READ suffix (for reading group addresses) and the other with \_WRITE suffix (for writing group addresses). For example, if the variable name is "KNXGlobalContext", the 2 variables KNXGlobalContext\_READ and KNXGlobalContext\_WRITE are created. Since the global variable is visible from all nodes (even non-KNX-Ultimate ones), for security reasons, set a name other than the default one. Click the sample link at the bottom of the page. |
-| Expose as Global variable | Choose if and how you want to expose the global variable. If you do not intend to write on the KNX BUS, for safety, leave "read only". |
-| BUS write interval | The node checks the variable with \_WRITE suffix at regular intervals to write on the KNX bus. Choose the interval you prefer. |
-
-## MSG PROPERTIES
-
-```javascript
-
-// Properties of the variable, both in reading and in writing
-{
-    address : "0/0/1",
-    dpt: "1.001", 
-    payload: true,
-    devicename:"Dinning Room->Table Light"
-}
-
-```
-
-# USAGE
-
-## Global Context Node Sample
-
-This node exposes the group address received from the bus, to a **global variable** <br/>
-You can write to the KNX BUS by simply update the global variable!<br/>
-
-## Overview
-
-Put a Global Context Node into the flow, then give it a name.<br/>
-The name you give to the node, will become the global context variable's name.<br/>
-That's all. For security reasons, please **change the default node name** <br/>
-You can access the global variable by adding the suffix \_READ to the node's name.<br/>
-You can enable/disable the global context variable, or enable READONLY or READ/WRITE in the configuration window.<br/>
-You can issue a KNX BUS write command, by simply modify the global variable name with suffix \_WRITE. _ **After the commands have been executed, the global variable with suffix \_WRITE is automatically emptied, not to infinitely repeat the commands.** _<br/>
-
-<br/>
-
-<img src="https://raw.githubusercontent.com/Supergiovane/node-red-contrib-knx-ultimate/master/img/wiki/globalcontextnode.png" width="90%"><br/>
-
-<br/>
-
-### View code
-
-> Adjust the nodes according to your setup
-
-```javascript
-
-[{"id":"ababb834.9073","type":"knxUltimateGlobalContext","z":"5ed79f4a958a1f20","server":"b60c0d73.1c02b","name":"KNXContextBanana","exposeAsVariable":"exposeAsVariableREADWRITE","writeExecutionInterval":"1000","x":230,"y":200,"wires":[]},{"id":"2954e7ea.f53988","type":"function","z":"5ed79f4a958a1f20","name":"Write to the KNXContextBanana variable","func":"// This function writes some values to the KNX bus\nlet GroupAddresses = [];\nGroupAddresses.push ({address: \"0/0/10\", dpt:\"1.001\", payload:true});\nGroupAddresses.push({ address: \"0/0/11\", dpt: \"1.001\", payload: true });\nGroupAddresses.push({ address: \"0/0/12\", dpt: \"1.001\", payload: false });\n\n// You can also avoid setting datapoint.\n// This works gread if you have imported the ETS file, otherwise it'll guess the datapoint type by analyzing the payload\nGroupAddresses.push ({address: \"0/0/14\", payload:false});\nGroupAddresses.push({ address: \"0/0/15\", payload: 50 });\n\n// Remember: add the string \"_WRITE\" after the node name to write to the bus\nglobal.set(\"KNXContextBanana_WRITE\",GroupAddresses);\n","outputs":0,"noerr":0,"initialize":"","finalize":"","libs":[],"x":480,"y":300,"wires":[]},{"id":"bd4380e3.8c1ea","type":"inject","z":"5ed79f4a958a1f20","name":"Call the function","props":[{"p":"payload"},{"p":"topic","vt":"str"}],"repeat":"","crontab":"","once":false,"onceDelay":0.1,"topic":"","payload":"true","payloadType":"bool","x":220,"y":300,"wires":[["2954e7ea.f53988"]]},{"id":"269bf86a.34e9f8","type":"comment","z":"5ed79f4a958a1f20","name":"Exposing the Group Addresses to the global context variable","info":"","x":360,"y":160,"wires":[]},{"id":"f9a6ff93.086a","type":"function","z":"5ed79f4a958a1f20","name":"Read the KNXContextBanana variable","func":"// This function reads the variable\n// Remember: add the string \"_READ\" after the node name to read the variable\nlet GroupAddresses = global.get(\"KNXContextBanana_READ\") || [];\n\n// Outputs the array, as example\nnode.send({payload:GroupAddresses});\n\n// Get the Group Address object, having address 0/0/10\nlet Ga = GroupAddresses.find(a => a.address === \"0/0/10\");\n\n// Outputs the object, as example\nnode.send({ Found: Ga });\n\n// Do some testing and output some stuffs.\nif (Ga.payload === true) return {payload : \"FOUND AND TRUE\"};\nif (Ga.payload === false) return {payload : \"FOUND AND FALSE\"};\n\n","outputs":1,"noerr":0,"initialize":"","finalize":"","libs":[],"x":410,"y":420,"wires":[["f4109aa5.270e08"]]},{"id":"64c9e0f0.b13178","type":"inject","z":"5ed79f4a958a1f20","name":"Read","props":[{"p":"payload"},{"p":"topic","vt":"str"}],"repeat":"","crontab":"","once":false,"onceDelay":0.1,"topic":"","payload":"true","payloadType":"bool","x":190,"y":420,"wires":[["f9a6ff93.086a"]]},{"id":"f4109aa5.270e08","type":"debug","z":"5ed79f4a958a1f20","name":"","active":true,"tosidebar":true,"console":false,"tostatus":false,"complete":"true","targetType":"full","statusVal":"","statusType":"auto","x":630,"y":420,"wires":[]},{"id":"bf16d5a9.073b6","type":"comment","z":"5ed79f4a958a1f20","name":"Check global variable and do some stuffs","info":"","x":300,"y":380,"wires":[]},{"id":"85c342f08c9c4705","type":"comment","z":"5ed79f4a958a1f20","name":"This function writes some values to the bus","info":"","x":310,"y":260,"wires":[]},{"id":"b60c0d73.1c02b","type":"knxUltimate-config","host":"224.0.23.12","port":"3671","physAddr":"15.15.22","suppressACKRequest":false,"csv":"","KNXEthInterface":"Auto","KNXEthInterfaceManuallyInput":"","statusDisplayLastUpdate":false,"statusDisplayDeviceNameWhenALL":true,"statusDisplayDataPoint":true,"stopETSImportIfNoDatapoint":"fake","loglevel":"error","name":"Multicast","localEchoInTunneling":true,"delaybetweentelegrams":"","delaybetweentelegramsfurtherdelayREAD":"","ignoreTelegramsWithRepeatedFlag":false,"keyringFileXML":""}]
-
-```
-
-<br/>
-
-## Get the variable's value
-
-```javascript
-
-// This function reads the variable
-// Remember: add the string "_READ" after the node name to read the variable
-let GroupAddresses = global.get("KNXContextBanana_READ") || [];
-
-// Outputs the array, as example
-node.send({payload:GroupAddresses});
-
-// Get the Group Address object, having address 0/0/10
-let Ga = GroupAddresses.find(a => a.address === "0/0/10");
-
-// Outputs the object, as example
-node.send({ Found: Ga });
-
-// Do some testing and output some stuffs.
-if (Ga.payload === true) return {payload : "FOUND AND TRUE"};
-if (Ga.payload === false) return {payload : "FOUND AND FALSE"};
-
-```
-
-## Send KNX telegram via global variable
-
-```javascript
-
-// This function writes the value to the KNX bus
-let GroupAddressesSend = [];
-GroupAddressesSend.push({address: "0/0/10", dpt:"1.001", payload:msg.payload});
-
-// You can also avoid setting datapoint.
-// This works gread if you have imported the ETS file, otherwise it'll guess the datapoint type by analyzing the payload
-GroupAddressesSend.push({address: "0/0/11", payload:msg.payload});
-
-// Remember: add the string "_WRITE" after the node name to write to the bus
-global.set("KNXContextBanana_WRITE",GroupAddressesSend);
-
-```
-
-# SAMPLE
-
-<a href="https://supergiovane.github.io/node-red-contrib-knx-ultimate/wiki/SampleGlobalContextNode" target="_blank"><i class="fa fa-info-circle"></i>See this Sample</a>
-</script>

package/nodes/locales/en/knxUltimateGlobalContext.json

@@ -1,24 +0,0 @@
-{
-  "knxUltimateGlobalContext": {
-    "paletteLabel": "KNX Global Context (deprecated)",
-    "title": "KNX Global Context",
-    "node-input-name": "Variable Name (no spaces, only chars [a-z])",
-    "advanced": {
-      "exposeAsVariable": "Expose as Global variable",
-      "exposeAsVariableNO": "No",
-      "exposeAsVariableREADONLY": "Read Only",
-      "exposeAsVariableREADWRITE": "Read/Write",
-      "node-input-server": "Gateway",
-      "writeExecutionInterval": "BUS write interval",
-      "warning": "Warning: a single node is shared between ALL FLOWS. You don't need more than one node; regardless of where it is, you can see the variable GLOBALLY."
-    },
-    "interval_250ms": "250ms",
-    "interval_500ms": "500ms",
-    "interval_1000ms_default": "1000ms (Default)",
-    "interval_1500ms": "1500ms",
-    "interval_2000ms": "2000ms",
-    "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/knxUltimateHATranslator.html

@@ -1,25 +0,0 @@
-<script type="text/markdown" data-help-name="knxUltimateHATranslator">
-### 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>This node translates the input msg to valid true/false values.<p>
-
-It can translate an input payload, to a true/false boolean values.<br />
-Each row in the text box, represents a translation command. <br/>
-You can add your own translation row.<br/>
-
-|Property|Description|
-|--|--|
-| Name | The node name. |
-| Input | The input msg property to be evaluated and translated. |
-| Translate | Add, delete or edit your own translation command. The row's translation command must be **input string from HA:KNX value** (_KNX value_ as true or false). For example: <code>open:true</code> <code>closed:false</code>. |
-
-<br/>
-</script>

package/nodes/locales/en/knxUltimateHATranslator.json

@@ -1,8 +0,0 @@
-{
-  "knxUltimateHATranslator": {
-    "paletteLabel": "Home Assistant translator (deprecated)",
-    "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/knxUltimateHueAreaMotion.html

@@ -1,44 +0,0 @@
-<script type="text/markdown" data-help-name="knxUltimateHueAreaMotion">
-### 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/>
-
-<p><strong>Deprecated:</strong> This dedicated HUE node remains available for existing flows. Use <strong>HUE Controller</strong> for new work. The legacy node is marked <code>(deprecated)</code> in the palette and on the canvas, uses a lighter color than HUE Controller, and its editor opens with a migration notice. The high-contrast orange migration button with white text converts all legacy HUE nodes locally; afterwards it opens only an editable email draft. The email is never sent automatically. When the process finishes, a fixed Node-RED message remains visible until you click OK and offers an optional support button; the donation page opens only when that button is clicked. <a href="https://youtu.be/f0Evf2QFI7c" target="_blank" rel="noopener noreferrer">Watch the explanatory video on YouTube</a> before starting.</p>
-<p>The Hue Motion Area node listens to MotionAware area motion events (Hue Bridge Pro) and mirrors the aggregated detected/not-detected state to KNX or your Node-RED flow.</p>
-
-Start typing in the GA field (name or Group Address) to link the KNX GA; devices appear while you type.
-
-**General**
-
-|Property|Description|
-|--|--|
-| KNX GW | Select the KNX gateway to be used. |
-| HUE Bridge | Select the Hue Bridge Pro to be used. |
-| HUE Area | MotionAware area (convenience or security) to monitor (autocomplete while typing). |
-| Read status at startup | On startup/reconnect, read the current value and send it to KNX (default: yes). |
-
-**Mapping**
-
-|Property|Description|
-|--|--|
-| Motion | KNX GA for the area motion state (boolean). Recommended DPT: <b>1.001</b>. |
-
-**Behaviour**
-
-|Property|Description|
-|--|--|
-| Node output pin | Show or hide the Node-RED output. When no KNX gateway is selected the output pin stays enabled so MotionAware events still reach your flow. |
-
-### Outputs
-
-1. Standard output  
-   : `msg.payload` (boolean): `true` when motion is detected in the area, otherwise `false`.
-
-### Details
-
-`msg.payload` carries the latest MotionAware area motion status (aggregated from the underlying sensors).
-</script>

package/nodes/locales/en/knxUltimateHueAreaMotion.json

@@ -1,31 +0,0 @@
-{
-  "common": {
-    "ga": "GA",
-    "dpt": "DPT",
-    "name": "Name",
-    "youtube_sample": "Youtube sample",
-    "knx_gw": "KNX GW",
-    "hue_bridge": "Hue Bridge",
-    "philips_hue": "Philips HUE",
-    "read": "Read"
-  },
-  "knxUltimateHueAreaMotion": {
-    "paletteLabel": "Hue Motion Area",
-    "heading": "Hue Motion Area node",
-    "hue_area": "Hue Motion Area",
-    "no_devices": "No MotionAware areas available",
-    "tabs": {
-      "motion": "Motion",
-      "behaviour": "Behaviour"
-    },
-    "node_pins": "Node output pin",
-    "node_pins_hide": "Hide",
-    "node_pins_show": "Show Node-RED output pin",
-    "output_info": "No KNX gateway selected. When the Node-RED output pin is enabled, MotionAware area motion events are still emitted to your flow.",
-    "read_status_startup": "Read status at startup",
-    "opt_no": "No",
-    "opt_yes_emit": "Yes, and emit KNX telegrams.",
-    "motion_info": "Link your KNX group address to receive the aggregated motion state for this MotionAware area."
-  }
-}
-

package/nodes/locales/en/knxUltimateHueBattery.html

@@ -1,37 +0,0 @@
-<script type="text/markdown" data-help-name="knxUltimateHueBattery">
-### 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/>
-
-<p><strong>Deprecated:</strong> This dedicated HUE node remains available for existing flows. Use <strong>HUE Controller</strong> for new work. The legacy node is marked <code>(deprecated)</code> in the palette and on the canvas, uses a lighter color than HUE Controller, and its editor opens with a migration notice. The high-contrast orange migration button with white text converts all legacy HUE nodes locally; afterwards it opens only an editable email draft. The email is never sent automatically. When the process finishes, a fixed Node-RED message remains visible until you click OK and offers an optional support button; the donation page opens only when that button is clicked. <a href="https://youtu.be/f0Evf2QFI7c" target="_blank" rel="noopener noreferrer">Watch the explanatory video on YouTube</a> before starting.</p>
-<p>This node exposes the battery level of a Hue device to KNX and raises an event whenever the value changes.</p>
-
-Start typing the KNX device name or Group Address in the GA field; matching entries appear while you type. Use the refresh icon next to <q>Hue sensor</q> to reload the list from the Hue bridge after adding new devices.
-
-**General**
-
-|Property|Description|
-|--|--|
-| KNX GW | KNX gateway used to publish the battery level (required before KNX mapping fields appear). |
-| Hue Bridge | Hue Bridge that hosts the device. |
-| Hue battery sensor | Hue device/sensor providing the battery level (supports autocomplete and refresh). |
-
-**Mapping**
-
-|Property|Description|
-|--|--|
-| Level | KNX GA for the battery percentage (0-100%). Recommended DPT: <b>5.001</b>. |
-
-**Behaviour**
-
-|Property|Description|
-|--|--|
-| Read status at startup | On deploy/reconnect read the current battery value and publish it to KNX. Default: "yes”. |
-| Node output pin | Show or hide the Node-RED output. When no KNX gateway is selected the output stays enabled so Hue events continue to reach the flow. |
-
-> ℹ️ KNX mapping widgets remain hidden until a KNX gateway is selected. This keeps the editor tidy when the node is used only to forward Hue events into Node-RED.
-</script>

package/nodes/locales/en/knxUltimateHueBattery.json

@@ -1,30 +0,0 @@
-{
-  "common": {
-    "ga": "GA",
-    "dpt": "DPT",
-    "name": "Name",
-    "youtube_sample": "Youtube sample",
-    "knx_gw": "KNX GW",
-    "hue_bridge": "Hue Bridge",
-    "philips_hue": "Philips HUE",
-    "read": "Read"
-  },
-  "knxUltimateHueBattery": {
-    "paletteLabel": "Hue Battery Sensor",
-    "hue_sensor": "Hue battery sensor",
-    "no_devices": "No battery devices available",
-    "tabs": {
-      "mapping": "Mapping",
-      "behaviour": "Behaviour"
-    },
-    "mapping_info": "Link the KNX group address that should emit the battery percentage.",
-    "behaviour_info": "Configure how the sensor behaves at startup and whether to expose the Node-RED output pin.",
-    "read_status_startup": "Read status at startup",
-    "opt_no": "No",
-    "opt_yes_emit": "Yes, and emit KNX telegrams.",
-    "node_pins": "Node output pin",
-    "node_pins_show": "Show Node-RED output pin",
-    "node_pins_hide": "Hide",
-    "output_info": "No KNX gateway selected. When the Node-RED output pin is enabled, Hue battery events are still emitted to your flow."
-  }
-}

package/nodes/locales/en/knxUltimateHueButton.html

@@ -1,52 +0,0 @@
-<script type="text/markdown" data-help-name="knxUltimateHueButton">
-### 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/>
-
-<p><strong>Deprecated:</strong> This dedicated HUE node remains available for existing flows. Use <strong>HUE Controller</strong> for new work. The legacy node is marked <code>(deprecated)</code> in the palette and on the canvas, uses a lighter color than HUE Controller, and its editor opens with a migration notice. The high-contrast orange migration button with white text converts all legacy HUE nodes locally; afterwards it opens only an editable email draft. The email is never sent automatically. When the process finishes, a fixed Node-RED message remains visible until you click OK and offers an optional support button; the donation page opens only when that button is clicked. <a href="https://youtu.be/f0Evf2QFI7c" target="_blank" rel="noopener noreferrer">Watch the explanatory video on YouTube</a> before starting.</p>
-<p>The Hue Button node maps Hue button events to KNX group addresses and exposes the same events on its flow output via <code>button.button_report.event</code>.</p>
-
-Start typing in the GA field (name or Group Address) to link the KNX GA; devices appear while you type.
-
-**General**
-
-|Property|Description|
-|--|--|
-| KNX GW | Select the KNX gateway to be used |
-| Hue Bridge | Select the Hue Bridge to be used |
-| Hue Button | Hue button to be used (autocomplete while typing) |
-
-**Switch**
-
-|Property|Description|
-|--|--|
-| Switch | GA triggered by <code>short\_release</code> (quick press/release). |
-| Status GA | Optional feedback GA when <em>Toggle values</em> is enabled to keep the internal toggle state aligned with other actuators. |
-
-**Dim**
-
-|Property|Description|
-|--|--|
-| Dim | GA used during <code>long\_press</code>/<code>repeat</code> events for dimming (typically DPT 3.007). |
-
-**Behaviour**
-
-|Property|Description|
-|--|--|
-| Toggle values on each event | If enabled, the node alternates between <code>true/false</code> and up/down dimming payloads. |
-| Switch payload | Payload sent to KNX/flow when Toggle values is disabled. |
-| Dim payload | Direction sent to KNX/flow when Toggle values is disabled. |
-
-### Outputs
-
-1. Standard output
-   : `msg.payload` carries the boolean (or dim object) sent to KNX; `msg.event` is the Hue event string (e.g. `short_release`, `repeat`).
-
-### Details
-
-`msg.event` mirrors `button.button_report.event`. The original Hue event is exposed in `msg.rawEvent`. Use the optional Status GA to keep the toggle state in sync with wall switches or other controllers.
-</script>

package/nodes/locales/en/knxUltimateHueButton.json

@@ -1,34 +0,0 @@
-{
-  "knxUltimateHueButton": {
-    "paletteLabel": "Hue Button",
-    "hue_sensor": "Hue Button",
-    "no_devices": "No Hue buttons available",
-    "tabs": {
-      "switch": "Switch",
-      "dim": "Dim",
-      "behaviour": "Behaviour"
-    },
-    "switch_info": "Link the KNX group address triggered by short presses.",
-    "switch_status": "Status GA",
-    "dim_info": "Configure the KNX dimming GA that handles repeat events during long presses.",
-    "behaviour_info": "Select whether events toggle values automatically or send fixed payloads.",
-    "toggle_values": "Toggle values on each event",
-    "toggle_values_hint": "Enable to alternate true/false and dim up/down; disable to send fixed payloads defined below.",
-    "switch_send": "Switch payload",
-    "dim_send": "Dim payload",
-    "dim_up": "Up",
-    "dim_down": "Down",
-    "dim_stop": "Stop",
-    "output_info": "No KNX gateway selected. Events are still emitted on the Node-RED output pin."
-  },
-  "common": {
-    "ga": "GA",
-    "dpt": "DPT",
-    "name": "Name",
-    "youtube_sample": "Youtube sample",
-    "knx_gw": "KNX GW",
-    "hue_bridge": "Hue Bridge",
-    "philips_hue": "Philips HUE",
-    "read": "Read"
-  }
-}

package/nodes/locales/en/knxUltimateHueCameraMotion.html

@@ -1,38 +0,0 @@
-<script type="text/markdown" data-help-name="knxUltimateHueCameraMotion">
-### 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/>
-
-<p><strong>Deprecated:</strong> This dedicated HUE node remains available for existing flows. Use <strong>HUE Controller</strong> for new work. The legacy node is marked <code>(deprecated)</code> in the palette and on the canvas, uses a lighter color than HUE Controller, and its editor opens with a migration notice. The high-contrast orange migration button with white text converts all legacy HUE nodes locally; afterwards it opens only an editable email draft. The email is never sent automatically. When the process finishes, a fixed Node-RED message remains visible until you click OK and offers an optional support button; the donation page opens only when that button is clicked. <a href="https://youtu.be/f0Evf2QFI7c" target="_blank" rel="noopener noreferrer">Watch the explanatory video on YouTube</a> before starting.</p>
-<p>The Hue Camera Motion node listens to Philips Hue camera motion services and mirrors the detected/not detected state to KNX.</p>
-
-Start typing in the GA field (name or Group Address) to link the KNX GA; devices appear while you type.
-
-**General**
-
-|Property|Description|
-|--|--|
-| KNX GW | Select the KNX gateway to be used |
-| Hue Bridge | Select the Hue Bridge to be used |
-| Hue Camera Motion | Hue camera motion sensor (autocomplete while typing) |
-| Read status at startup | On startup/reconnect, read the current value and send it to KNX (default: no) |
-
-**Mapping**
-
-|Property|Description|
-|--|--|
-| Motion | KNX GA for camera motion (boolean). Recommended DPT: <b>1.001</b> |
-
-### Outputs
-
-1. Standard output
-   : `msg.payload` (boolean): `true` when motion is detected; otherwise `false`
-
-### Details
-
-`msg.payload` carries the latest motion status reported by the Hue camera service.
-</script>

package/nodes/locales/en/knxUltimateHueCameraMotion.json

@@ -1,30 +0,0 @@
-{
-  "common": {
-    "ga": "GA",
-    "dpt": "DPT",
-    "name": "Name",
-    "youtube_sample": "Youtube sample",
-    "knx_gw": "KNX GW",
-    "hue_bridge": "Hue Bridge",
-    "philips_hue": "Philips HUE",
-    "read": "Read"
-  },
-  "knxUltimateHueCameraMotion": {
-    "paletteLabel": "Hue Camera Motion",
-    "heading": "Hue Camera Motion node",
-    "hue_sensor": "Hue Camera Motion",
-    "no_devices": "No camera motion devices available",
-    "tabs": {
-      "motion": "Motion",
-      "behaviour": "Behaviour"
-    },
-    "node_pins": "Node output pin",
-    "node_pins_hide": "Hide",
-    "node_pins_show": "Show Node-RED output pin",
-    "output_info": "No KNX gateway selected. When the Node-RED output pin is enabled, Hue camera motion events are still emitted to your flow.",
-    "read_status_startup": "Read status at startup",
-    "opt_no": "No",
-    "opt_yes_emit": "Yes, and emit KNX telegrams.",
-    "motion_info": "Link your KNX motion group address to receive the detected/not detected state."
-  }
-}