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

package/nodes/locales/en/knxUltimateHueScene.json

@@ -1,41 +0,0 @@
-{
-  "knxUltimateHueScene": {
-    "title": "Hue Scene node",
-    "paletteLabel": "Hue Scene",
-    "hue_scene": "Hue Scene",
-    "recall_as": "Recall as",
-    "recall_active": "Recall as Active",
-    "recall_dynamic": "Recall as Dynamic",
-    "recall_static": "Recall as Static",
-    "recall": "Recall",
-    "status": "Status",
-    "scene_selector": "Scene selector",
-    "knx_scene_n": "KNX Scene n.",
-    "node_pins": "Node input/output pins",
-    "node_pins_hide": "Hide pins",
-    "node_pins_show": "Show node input/output pins",
-    "tabs": {
-      "single": "Single scene",
-      "multi": "Multi scene",
-      "behaviour": "Behaviour"
-    },
-    "single_info": "Select the Hue scene and choose how it should be recalled when the KNX address is triggered.",
-    "mapping_info": "Map the KNX addresses that recall the scene or report its current state.",
-    "multi_info": "Associate KNX scene numbers with Hue scenes. Each rule recalls a different Hue scene.",
-    "behaviour_info": "Decide whether the Node-RED output pin should remain visible when KNX delivery is disabled.",
-    "status_ga": "Status GA",
-    "output_info": "Without a KNX gateway the flow output stays enabled so Hue events continue to reach Node-RED.",
-    "no_scenes": "No Hue scenes found. Use the refresh icon after adding new scenes.",
-    "multi_scene_placeholder": "Hue scene name"
-  },
-  "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/knxUltimateHueTapDial.html

@@ -1,40 +0,0 @@
-<script type="text/markdown" data-help-name="knxUltimateHueTapDial">
-### 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>
-The **Hue Tap Dial** node maps the rotary service of the Hue Tap Dial to KNX and forwards the raw Hue events to your flow. Use the refresh icon beside the device field after pairing a new dial on the bridge.
-
-### Tabs
-
-- **Mapping** - select the KNX GA and DPT used for the rotation events. Supported datapoints: DPT 3.007 (relative dim), DPT 5.001 (absolute level 0-100 %) and DPT 232.600 (vendor colour control).
-- **Behaviour** - show or hide the Node-RED output pin. When no KNX gateway is configured the output is kept enabled so Hue events still reach the flow.
-
-### General settings
-
-|Property|Description|
-|--|--|
-| KNX GW | KNX gateway used for GA autocomplete. |
-| Hue Bridge | Hue Bridge hosting the Tap Dial. |
-| Hue Tap Dial | Rotary device to control (autocomplete; refresh button reloads the list). |
-
-### Mapping tab
-
-|Property|Description|
-|--|--|
-| Rotate GA | KNX GA receiving rotation events (supports DPT 3.007, 5.001, 232.600). |
-| Name | Friendly label for the GA. |
-
-### Outputs
-
-|#|Port|Payload|
-|--|--|--|
-|1|Standard output|`msg.payload` (object) Raw Hue event emitted by the Tap Dial.|
-
-> ℹ️ KNX-specific widgets appear only after selecting a KNX gateway; the Mapping tab stays hidden until both the bridge and the gateway are configured.
-</script>

package/nodes/locales/en/knxUltimateHueTapDial.json

@@ -1,28 +0,0 @@
-{
-  "knxUltimateHueTapDial": {
-    "title": "Hue Tap Dial node (rotary)",
-    "paletteLabel": "Hue Tap Dial",
-    "hue_device": "Hue Tap Dial",
-    "tabs": {
-      "mapping": "Mapping",
-      "behaviour": "Behaviour"
-    },
-    "mapping_info": "Link the Hue Tap Dial rotation events to a KNX group address.",
-    "behaviour_info": "Decide whether the Node-RED output pin should remain visible when KNX delivery is disabled.",
-    "node_pins": "Node input/output pins",
-    "node_pins_hide": "Hide pins",
-    "node_pins_show": "Show node input/output pins",
-    "output_info": "Without a KNX gateway the flow output stays enabled so Hue events continue to reach Node-RED.",
-    "no_devices": "No Hue Tap Dial devices found. Use the refresh icon after pairing a new dial."
-  },
-  "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/knxUltimateHueTemperatureSensor.html

@@ -1,38 +0,0 @@
-<script type="text/markdown" data-help-name="knxUltimateHueTemperatureSensor">
-### 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 reads temperature (°C) from a Hue temperature sensor and maps it 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 temperature sensor | Hue temperature sensor (autocomplete while typing) |
-| Read status at startup | On startup/reconnect, read current value and send it to KNX (default: no) |
-
-**Mapping**
-
-|Property|Description|
-|--|--|
-| Temp | KNX GA for temperature in Celsius. Recommended DPT: <b>9.001</b> |
-
-### Outputs
-
-1. Standard output
-   : `msg.payload` (number): current temperature in °C
-
-### Details
-
-`msg.payload` carries the numeric temperature value.
-</script>

package/nodes/locales/en/knxUltimateHueTemperatureSensor.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"
-  },
-  "knxUltimateHueTemperatureSensor": {
-    "paletteLabel": "Hue Temperature Sensor",
-    "hue_sensor": "Hue temperature sensor",
-    "no_devices": "No temperature sensors available",
-    "tabs": {
-      "mapping": "Mapping",
-      "behaviour": "Behaviour"
-    },
-    "mapping_info": "Link the KNX group address that should emit the temperature value.",
-    "behaviour_info": "Configure how the sensor reads 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 temperature values are still emitted to your flow."
-  }
-}

package/nodes/locales/en/knxUltimateHueZigbeeConnectivity.html

@@ -1,39 +0,0 @@
-<script type="text/markdown" data-help-name="knxUltimateHueZigbeeConnectivity">
-### 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 retrieves the Zigbee connectivity status from a Hue device and exposes it to KNX.</p>
-
-Start typing the KNX device name or Group Address in the GA field; suggestions appear while you type.
-
-**General**
-
-|Property|Description|
-|--|--|
-| KNX GW | KNX gateway used to publish the status. |
-| Hue Bridge | Hue Bridge to query. |
-| Hue zigbee connectivity | Hue sensor/device providing the Zigbee connectivity info. Autocomplete while typing. |
-
-**Mapping**
-
-|Property|Description|
-|--|--|
-| Status | KNX Group Address that reflects Zigbee connectivity. Becomes _true_ when connected, otherwise _false_. |
-| Read status at startup | Reads current status at editor start/reconnection and emits to KNX. Default: "yes”. |
-
-### Outputs
-
-1. Standard output
-   : payload (boolean): connectivity state.
-
-### Details
-
-`msg.payload` carries the boolean state (true/false).\
-`msg.status` contains a textual status: one of **connected, disconnected, connectivity\_issue, unidirectional\_incoming** .
-</script>

package/nodes/locales/en/knxUltimateHueZigbeeConnectivity.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"
-  },
-  "knxUltimateHueZigbeeConnectivity": {
-    "paletteLabel": "Hue Zigbee Connectivity",
-    "hue_sensor": "Hue zigbee connectivity",
-    "no_devices": "No zigbee connectivity devices available",
-    "tabs": {
-      "mapping": "Mapping",
-      "behaviour": "Behaviour"
-    },
-    "mapping_info": "Link the KNX group address that should reflect the Zigbee connectivity state.",
-    "behaviour_info": "Choose whether to read the connectivity state at startup and 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 connectivity events are still emitted to your flow."
-  }
-}

package/nodes/locales/en/knxUltimateHuedevice_software_update.html

@@ -1,36 +0,0 @@
-<script type="text/markdown" data-help-name="knxUltimateHuedevice_software_update">
-### 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 monitors whether a selected Hue device has a software update available and publishes the status to KNX.</p>
-
-Start typing the name or group address of your KNX device in the GA field, the avaiable devices start showing up while
-you're typing.
-
-**General**
-
-|Property|Description|
-|--|--|
-| KNX GW | Select the KNX gateway to be used |
-| Hue Bridge | Select the Hue Bridge to be used |
-| Hue device | Hue device to monitor for software updates (autocomplete while typing).|
-
-**Mapping**
-
-| Property | Description |
-|--|--|
-| Status | KNX GA reflecting update status. _true_ if an update is available/ready/being installed, otherwise _false_. |
-| Read status at startup | Read current status at startup/reconnection and emit to KNX (default "yes”). |
-
-### Outputs
-
-1. Standard output
-   : payload (boolean): update flag.
-   : status (string): one of **no\_update, update\_pending, ready\_to\_install, installing** .
-</script>

package/nodes/locales/en/knxUltimateHuedevice_software_update.json

@@ -1,30 +0,0 @@
-{
-  "knxUltimateHuedevice_software_update": {
-    "paletteLabel": "Hue Software Update",
-    "hue_device": "Hue device",
-    "tabs": {
-      "mapping": "Mapping",
-      "behaviour": "Behaviour"
-    },
-    "mapping_info": "Map the KNX address that reports the software-update status.",
-    "behaviour_info": "Control startup reads and the Node-RED output pin visibility.",
-    "node_pins": "Node input/output pins",
-    "node_pins_hide": "Hide pins",
-    "node_pins_show": "Show node input/output pins",
-    "output_info": "Without a KNX gateway the flow output stays enabled so Hue events continue to reach Node-RED.",
-    "no_devices": "No Hue devices found. Use the refresh icon after adding a new device.",
-    "read_status_startup": "Read status at startup",
-    "opt_no": "No",
-    "opt_yes_emit": "Yes, and emit KNX telegrams."
-  },
-  "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/knxUltimateLoadControl.html

@@ -1,76 +0,0 @@
-<script type="text/markdown" data-help-name="knxUltimateLoadControl">
-### 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 LOAD CONTROL NODE
-
-<p>With the Load Control node you can automatically manage the disconnection of loads (washing machine, oven, etc.) when the current consumption exceeds a certain threshold.  
-
-The devices are turned off intelligently, checking the possible consumption of the device to determine whether to turn it off together with others. <br/>
-The node can automatically reactivate the loads. <br/>
-The node turns off one device (or multiple devices) at a time, based on the order you have selected.<br/>
-
-**General**
-
-|Property|Description|
-|--|--|
-| Gateway | KNX gateway. It is also possible not to select any gateway; in this case, only incoming messages to the node will be considered. |
-| Mode | Select _Automatic (internal)_ to use Monitor W/threshold/timers. Select _Manual (msg.shedding)_ to disable the internal logic and use only `msg.shedding` commands (`shed`/`unshed`). |
-| Monitor W | Group address representing the total consumption of your building. |
-| Limit W | Maximum threshold that your electricity meter can withstand. When this threshold is exceeded, the node starts to turn off the devices. |
-| Delay switch off (s) | Expressed in seconds, indicates how often the node will evaluate consumption and switch off each device. |
-| Delay switch on (s) | Expressed in seconds, indicates how often the node will evaluate consumption and turn on each device that was turned off. |
-
-<br/>
-
-**LOAD CONTROL**
-
-Here you can add devices to turn off in case of overload. <br/>
-Choose the device to turn off. Enter the device name or its group address. <br/>
-Enter any group address that indicates the consumption of the device chosen in the first line. **This is an optional parameter** . If the device is consuming more than a certain number of Watts, it means that it is in use. If it consumes less, the device will be considered "not in use" and both this and the next will be turned off at once.<br/>
-If _Automatic recovery_ is enabled, the device is automatically reactivated when the "reset delay" expires.
-
-## Inputs
-
-|Property|Description|
-|--|--|
-| `msg.readstatus = true` | Force the reading of the values from the KNX BUS of each device in the list. _ **The node already does everything by itself** _, but if necessary, it is possible to use this command to force a re-reading of the current values in watt.|
-| `msg.enable = true` | Enable the load control.|
-| `msg.disable = true` | Disable the load control.|
-| `msg.reset = true` | Reset node states and turn all devices back on.|
-| `msg.shedding` | String. In _Manual_ mode: `shed` switches off the next load, `unshed` restores the previous one. In _Automatic_ mode: `shed`/`unshed` forces the internal logic; `auto` restores normal monitoring. |
-
-## Outputs
-
-1. Standard output
-   : payload (string|object) : the standard output of the command.
-
-## Details
-
-```javascript
-
-msg = {
-  "topic": "Home Total Consumption", // Node Name
-  "operation": "Increase Shedding" or "Decrease Shedding" or operation reflecting the input message (disable, enable, reset), // Operation
-  "device": "Washing machine", // Device shedded
-  "ga": "", // Group address of the shedded device
-  "totalPowerConsumption": 3100, // Current power consumption
-  "wattLimit": 3000, // Limit you set in the config window
-  "payload": 1, // Current shedding stage
-}
-
-```
-
-# Sample
-
-<a href="https://supergiovane.github.io/node-red-contrib-knx-ultimate/wiki/SampleLoadControl">CLICK HERE FOR THE EXAMPLE</a>
-
-<br/>
-</script>

package/nodes/locales/en/knxUltimateLoadControl.json

@@ -1,28 +0,0 @@
-{
-    "knxUltimateLoadControl": {
-        "paletteLabel": "KNX Load Control (deprecated)",
-        "title": "Load control",
-        "primoaldistacco": "(this is the first to be switched off)",
-        "properties": {
-            "node-input-server": "Gateway",
-            "node-input-name": "NoNameme",
-            "node-input-controlMode": "Mode",
-            "node-input-dpt": "Datapoint",
-            "node-input-topic": "Monitor W",
-            "node-input-controlGA": "Load",
-            "node-input-monitorGA": "In use",
-            "node-input-wattLimit": "Limit W",
-            "node-input-sheddingCheckInterval": "Delay switch off (s)",
-            "node-input-sheddingRestoreDelay": "Delay switch on (s)",
-            "node-input-autoRestore": "Automatic recovery"
-        },
-        "selectlists": {
-            "controlModeAuto": "Automatic (internal)",
-            "controlModeMsg": "Manual (msg.shedding)"
-        },
-        "other": {},
-        "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/knxUltimateLogger.html

@@ -1,161 +0,0 @@
-<script type="text/markdown" data-help-name="knxUltimateLogger">
-### 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.
-
-# Logger
-
-<p>The Logger node records all telegrams and outputs it in an ETS bus monitor XML compatible file.</p> 
-<br/>
-You can save the file on disk or send it to an FTP server, for example. The file can be then read by your ETS, for example for diagnostic or for a replay of the telegrams.
-<br/>
-The node can also count telegrams per second (or any interval you want).
-<br/> <a href="https://supergiovane.github.io/node-red-contrib-knx-ultimate/wiki/Logger-Sample" target="_blank">Examples are here.</a>
-
-<br/>
-
-## SETTINGS
-
-|Property|Description|
-|--|--|
-| Gateway | The KNX gateway. |
-| Topic | The topic of the node. |
-| Node Name | Node name. |
-
-## ETS compatible BUS Diagnostic File
-
-|Property|Description|
-|--|--|
-| Auto start timer | Starts the timer automatically on deploy or on node-red start. |
-| New payload every (in minutes) | Interval for emitting the payload and/or saving to file. When saving to file, once the configured row limit is reached, the file is **rotated**, removing the oldest rows first. |
-| Max number of rows (0 = no limit) | This represents the maximum number of lines the XML file can contain (older lines are dropped first). Put 0 not to limit the number of rows in the file. When file saving is enabled, this value also represents the maximum number of rows in the file; when the limit is reached, the file is **rotated**, removing older rows over time. |
-| Action | `Emit payload only` or `Emit payload and save to file`. |
-| File path (absolute or relative) | Where to save the XML when action is set to save. |
-<br/>
-
-## KNX Telegram Counter
-
-|Property|Description|
-|--|--|
-| Auto start timer | Starts the timer automatically on deploy or on node-red start. |
-| Count interval (in seconds) | How often emit a msg to the flow, containing the KNX telegrams count. In Seconds. |
-
-<br/>
-
----
-
-# MESSAGE OUTPUT FROM THE LOGGER
-
-**PIN 1: XML ETS bus monitor compatible file File**
-
-You can use a file node to save the payload to the filesystem, or you can send it, for example, to an FTP server.
-
-```javascript
-
-msg = {
-        topic:"MyLogger" 
-        payload: "CommunicationLog xmlns=http://knx.org/xml/telegrams/01 Telegram Timestamp=2020-03-27T07:32:39.470Z Service=L_Data.ind...." (A String containing the XML file)
-    } 
-
-```
-
-<br/><br/>
-
-**PIN 2: KNX Telegram Counter**
-
-Each count, the node will emit a telegram like this:
-
-```javascript
-
-msg = {
-        topic:"",
-        payload:10,
-        countIntervalInSeconds:5,
-        currentTime:"25/10/2021, 11:11:44"
-    } 
-
-```
-
-<br/>
-
----
-
-# INPUT FLOW MESSAGE
-
-You can control the Logger in some ways.
-
-## ETS XML compatible BUS monitor file
-
-**START TIMER** <br/>
-
-```javascript
-
-// Start the timer
-msg.etsstarttimer = true;
-return msg;
-
-```
-
-**STOP TIMER** <br/>
-
-```javascript
-
-// Start the timer
-msg.etsstarttimer = false;
-return msg;
-
-```
-
-**IMMEDIATELY OUTPUT A PAYLOAD WITH THE ETS FILE** <br/>
-
-```javascript
-
-// Output payload. Restart timer as well (in case the timer was active)
-msg.etsoutputnow = true;
-return msg;
-
-```
-
-## KNX TELEGRAM COUNTER
-
-**START TIMER** <br/>
-
-```javascript
-
-// Start the timer
-msg.telegramcounterstarttimer = true;
-return msg;
-
-```
-
-**STOP TIMER** <br/>
-
-```javascript
-
-// Start the timer
-msg.telegramcounterstarttimer = false;
-return msg;
-
-```
-
-**IMMEDIATELY OUTPUT TELEGRAM COUNT MESSAGE** <br/>
-
-```javascript
-
-// Output payload. 
-msg.telegramcounteroutputnow = true;
-return msg;
-
-```
-
-## SEE ALSO
-
-- _SAMPLES_
-  - [Sample Logger](https://supergiovane.github.io/node-red-contrib-knx-ultimate/wiki/Logger-Sample)
-</script>

package/nodes/locales/en/knxUltimateLogger.json

@@ -1,31 +0,0 @@
-{
-    "knxUltimateLogger": {
-        "paletteLabel": "KNX Logger (deprecated)",
-        "title": "KNX logger for ETS",
-        "properties": {
-            "node-input-server": "Gateway",
-            "node-input-topic": "Topic",
-            "node-input-name": "Node Name",
-            "node-input-autoStartTimerCreateETSXML": "Auto start timer",
-            "mlxETSFileAccordion": "ETS compatible BUS Diagnostic File",
-            "node-input-intervalCreateETSXML": "New payload every (in minutes)",
-            "node-input-maxRowsInETSXML": "Max number of rows (0 = no limit)",
-            "node-input-saveMode": "Action",
-            "node-input-filePath": "File path (absolute or relative)",
-            "telegramCounter": "KNX Telegram Counter",
-            "node-input-intervalTelegramCount": "Count interval (in seconds)"
-        },
-        "placeholder": {
-            "node-input-filePath": "/var/tmp/knx-logger.xml"
-        },
-        "selectlists": {
-            "saveMode": {
-                "emit": "Emit payload only",
-                "emit_save": "Emit payload and save to file"
-            }
-        },
-        "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"
-    }
-}