node-red-contrib-uos-nats 1.3.3 → 1.3.5

package/README.md

@@ -94,8 +94,8 @@ Publishes your own data to the Data Hub.
 - **Provider not visible?** Ensure **Provider ID** matches your **Client ID**. Easiest way: Leave Provider ID empty in the node.
 - **Connection Failed?** Check Host/IP and ensure Client ID/Secret are correct.
 - **Variable ID "undefined" or "ERR"?** 
-  - Ensure the provider is publishing correct definitions.
-  - The nodes attempt to autofix missing IDs by using the variable index (0, 1, 2...) if the provider supports it.
+  - The ID column is hidden by default to avoid confusion. The node handles ID resolution automatically.
+  - If a variable fails, check if the Key (name) is correct on the Data Hub.
 - **Write not working?** Ensure your OAuth client has `hub.variables.readwrite` scope.
 - **Debug:** Check the Node-RED "Debug" sidebar for error messages.
 

package/nodes/datahub-input.html

@@ -247,7 +247,6 @@
         
         <div style="display:grid; grid-template-columns: 30px 1fr; background:#eee; font-size:11px; font-weight:bold; padding:4px 0; border-bottom:1px solid #ccc;">
             <div style="text-align:center;"><i class="fa fa-check-square-o"></i></div>
-            <!-- ID Column Removed -->
             <div style="padding-left:10px;">Name</div>
         </div>
 
@@ -317,18 +316,11 @@
         Use the <b>Load Variables</b> button to browse and select variables from the provider.
         Selected variables are automatically added to the list.
     </p>
-    <p>
-        The table maps Variable Keys (names) to their IDs.
-    </p>
-    
+
     <h5>Manual Entry (Fallback)</h5>
     <p>
-        If the "Load Variables" feature is unavailable, you can manually add variables knowing their IDs:
+        If the "Load Variables" feature is unavailable, you can manually add variables by editing the <code>manualVariables</code> property (Advanced).
     </p>
-    <ul>
-        <li><b>Variable Key:</b> The name (e.g. <code>machine.temp</code>)</li>
-        <li><b>Variable ID:</b> The numeric ID (e.g. <code>5</code>)</li>
-    </ul>
 
     <h4>4. Trigger Mode</h4>
     <dl>

package/nodes/datahub-write.html

@@ -175,7 +175,21 @@
             });
 
             // Initial state
-            $listContainer.html('<div style="padding:20px; text-align:center; color:#999;">Click <b>Load Variables</b> to browse.</div>');
+            const initId = $inputId.val();
+            const initKey = $inputKey.val();
+
+            if (initId || initKey) {
+                // Show dummy entry for currently selected variable
+                const dummy = [{
+                    id: initId || '?',
+                    // If ID is missing, key is enough. If Key is missing, show ID.
+                    key: initKey || `ID: ${initId}`
+                }];
+                renderList(dummy);
+                $statusMsg.text('Selected variable shown. Load again to refresh.').css('color', '#888');
+            } else {
+                $listContainer.html('<div style="padding:20px; text-align:center; color:#999;">Click <b>Load Variables</b> to browse.</div>');
+            }
 
             // Set initial display (Removed updateSelectionDisplay call)
             // But we might want to manually populate inputs if they are empty? No, defaults handle that.
@@ -304,8 +318,8 @@
     <pre><code>{
   "success": true,
   "providerId": "u_os_adm",
-  "variableId": 5,
-  "value": false
+  "count": 1,
+  "firstValue": false
 }</code></pre>
 
     <h3>Example Flow</h3>

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "node-red-contrib-uos-nats",
-  "version": "1.3.3",
+  "version": "1.3.5",
   "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",