node-red-contrib-uos-nats 1.3.61 → 1.3.68

package/README.md

@@ -77,7 +77,7 @@ Reads values from existing providers (like `u_os_adm`).
 ### DataHub - Write
 Changes values in other providers.
 -   **Single Mode:** Select a variable from the list. Send `msg.payload` = value.
--   **Batch Mode:** Select NO variable (clear selection). Send `msg.payload` as a JSON object: `{"var_key": value, "var2": value}` (uses Configured Provider).
+-   **Batch Mode:** Select NO variable (clear selection). Send `msg.payload` as a FLAT JSON object: `{"var_key": value, "machine.status": value}` (uses Configured Provider). **Nested objects are NOT supported** (keys must use dot-notation).
 -   **Dynamic Mode:** Send a full target object to write anywhere:
     ```json
     {
@@ -87,8 +87,8 @@ Changes values in other providers.
     }
     ```json
     {
-      "provider": "target_provider_id",
-      "key": "variable_key",
+      "provider": "u_os_sbm",
+      "key": "ur20_8do_p_1.process_data.channel_7.do",
       "value": 123
     }
     ```

package/nodes/datahub-write.html

@@ -250,12 +250,12 @@
     </ol>
     <p>If no variable is selected, the node works in <b>Batch Mode</b> or <b>Dynamic Mode</b>.</p>
     <ul>
-        <li><b>Batch:</b> Send a JSON object to update multiple keys for the configured Provider: <code>{"key": value, "key2": value}</code></li>
+        <li><b>Batch:</b> Send a FLAT JSON object to update multiple keys for the configured Provider: <code>{"key": value, "machine.status": value}</code>. <br><b>Note:</b> Nested objects are NOT flattened automatically. Use dot-notation for keys!</li>
         <li><b>Dynamic:</b> Send a specific object to target ANY Provider/Key:
             <code>
             {
                 "provider": "u_os_sbm",
-                "key": "machine.outputs.DO01",
+                "key": "ur20_8do_p_1.process_data.channel_7.do",
                 "value": true
             }
             </code>

package/nodes/uos-config.js

@@ -187,6 +187,9 @@ module.exports = function (RED) {
           // Ensure we have a valid token initially
           await this.getToken();
 
+          // Sanitize clientName for Inbox usage (Strict NATS subjects)
+          const safeClientName = this.clientName.replace(/[^a-zA-Z0-9_-]/g, '_');
+
           this.nc = await connect({
             servers: `nats://${this.host}:${this.port}`,
             // Authenticator must be SYNCHRONOUS. We rely on background refresh to keep this.tokenInfo current.
@@ -197,7 +200,10 @@ module.exports = function (RED) {
             // REVERT: Use Configured Client Name for Connection.
             // Using UUID caused "Authorization Violation" for some users.
             name: this.clientName,
-            inboxPrefix: `_INBOX.${this.clientName}`, // RESTORED: Spec requires strictly this format.
+
+            // inboxPrefix: `_INBOX.${safeClientName}`, // RESTORED: Spec requires strictly this format (ACLs enforce it). 
+            // Using safeClientName avoids invalid subject errors.
+            inboxPrefix: `_INBOX.${safeClientName}`,
             maxReconnectAttempts: -1, // Infinite reconnects
             reconnectTimeWait: 2000,
           });
@@ -457,10 +463,18 @@ module.exports = function (RED) {
         if (!def || !def.variables) return null;
 
         const v = def.variables.find(v => v.key === variableKey);
-        if (v) return v.id;
+        if (v) {
+          return {
+            id: v.id,
+            fingerprint: def.fingerprint || BigInt(0),
+            dataType: v.dataType
+          };
+        }
 
         // Try explicit numeric string fallback
-        if (!isNaN(variableKey)) return parseInt(variableKey);
+        if (!isNaN(variableKey)) {
+          return { id: parseInt(variableKey), fingerprint: BigInt(0) }; // Fallback, no fingerprint known
+        }
 
         return null;
       } catch (e) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "node-red-contrib-uos-nats",
-  "version": "1.3.61",
+  "version": "1.3.68",
   "description": "Node-RED nodes for Weidmüller u-OS Data Hub. Read, write, and provide variables via NATS protocol with OAuth2 authentication. Features: Variable Key resolution, custom icons, example flows, and provider definition caching.",
   "author": {
     "name": "IoTUeli",