node-red-contrib-knx-ultimate 4.3.15 → 4.3.16

package/CHANGELOG.md

@@ -6,6 +6,11 @@
 
 # CHANGELOG
 
+**Version 4.3.16** - May 2026<br/>
+
+- Docs/help/wiki: updated **KNX DateTime** help HTML and DateTime wiki pages (**EN/IT**) to document current `DPT 19.001` behavior based on JavaScript `Date`, additional input object fields (`msg.payload.dateTime` / `timestamp` / `epoch`), queued send while gateway is disconnected (latest pending only), and output metadata `msg.knxUltimateDateTime.date`.<br/>
+- Bump knxultimate Engine to 5.5.7<br/>
+
 **Version 4.3.15** - May 2026<br/>
 
 - FIX: DPT dropdown in editor now remains open when clicking on an already populated datapoint field (no immediate close on mouse button release).<br/>

package/nodes/locales/en/knxUltimateDateTime.html

@@ -10,6 +10,9 @@ It can send:
 
 You can configure one or more group addresses and the node will write to all configured outputs.
 
+Note about **DPT 19.001**:
+- the node starts from a JavaScript `Date` and converts it to KNX DateTime via the KNX engine.
+
 ## When it sends
 
 - **On deploy/startup** (optional, with delay).
@@ -26,6 +29,10 @@ Supported payloads:
 - a timestamp number (milliseconds since epoch)
 - a string accepted by `new Date("...")`
 - `"now"`
+- an object with one of these fields:
+  - `msg.payload.dateTime`
+  - `msg.payload.timestamp`
+  - `msg.payload.epoch`
 
 Example:
 
@@ -34,12 +41,17 @@ msg.payload = new Date();
 return msg;
 ```
 
+## Gateway disconnected
+
+If the KNX gateway is disconnected, the send is queued and sent automatically when the connection comes back.
+The node keeps **only one pending request** (the latest one).
+
 ## Output
 
 The node emits one message per send:
 - `msg.payload`: the `Date` that has been written
 - `msg.sent`: array of `{ ga, dpt, name }`
 - `msg.reason`: `input`, `startup`, `periodic` or `button`
+- `msg.knxUltimateDateTime.date`: date/time in ISO format (`toISOString()`)
 
 </script>
-

package/nodes/locales/it/knxUltimateDateTime.html

@@ -10,6 +10,9 @@ Può inviare:
 
 Puoi configurare uno o più indirizzi di gruppo: il nodo scrive su tutti quelli configurati.
 
+Nota su **DPT 19.001**:
+- il nodo parte da una `Date` JavaScript e la converte in telegramma KNX DateTime tramite l'engine KNX.
+
 ## Quando invia
 
 - **Al deploy/avvio** (opzionale, con ritardo).
@@ -26,6 +29,10 @@ Payload supportati:
 - numero timestamp (millisecondi dall'epoch)
 - stringa accettata da `new Date("...")`
 - `"now"`
+- oggetto con uno di questi campi:
+  - `msg.payload.dateTime`
+  - `msg.payload.timestamp`
+  - `msg.payload.epoch`
 
 Esempio:
 
@@ -34,12 +41,17 @@ msg.payload = new Date();
 return msg;
 ```
 
+## Gateway non connesso
+
+Se il gateway KNX non è connesso, l'invio viene messo in coda e parte appena torna la connessione.
+Il nodo mantiene **una sola richiesta pendente** (l'ultima ricevuta).
+
 ## Output
 
 Il nodo emette un messaggio ad ogni invio:
 - `msg.payload`: la `Date` inviata
 - `msg.sent`: array di `{ ga, dpt, name }`
 - `msg.reason`: `input`, `startup`, `periodic` o `button`
+- `msg.knxUltimateDateTime.date`: data/ora in formato ISO (`toISOString()`)
 
 </script>
-

package/package.json

@@ -3,7 +3,7 @@
   "engines": {
     "node": ">=20.18.1"
   },
-  "version": "4.3.15",
+  "version": "4.3.16",
   "description": "Control your KNX and KNX Secure intallation via Node-Red! A bunch of KNX nodes, with integrated Philips HUE control, ETS group address importer, KNX AI for diagnosticsand KNX routing between interfaces. Easy to use and highly configurable.",
   "files": [
     "nodes/",
@@ -19,7 +19,7 @@
     "dns-sync": "0.2.1",
     "google-translate-tts": "^0.3.0",
     "js-yaml": "4.1.1",
-    "knxultimate": "5.5.6",
+    "knxultimate": "5.5.7",
     "lodash": "4.18.1",
     "node-color-log": "12.0.1",
     "ping": "0.4.4",
@@ -117,4 +117,4 @@
     "vite": "^7.1.3",
     "vue": "^3.5.21"
   }
-}
+}