node-red-contrib-uos-nats 0.1.25 → 0.1.26

package/README.md

@@ -4,9 +4,9 @@
 
 Node-RED nodes to read and write u-OS Data Hub variables via NATS. This package exposes three building blocks:
 
-1. **u-OS Config** – stores host, OAuth client credentials and manages the shared NATS connection.
-2. **DataHub Input** – subscribes to an existing provider and emits JSON messages. Enter the provider ID and optional comma-separated variable names.
-3. **DataHub Output** – automatically registers a provider (default `nodered`), flattens incoming JSON structures and publishes them to the Data Hub.
+1. **u-OS Config** – stores host, OAuth client credentials and manages the shared NATS connection. Includes a **Test Connection** button for immediate feedback.
+2. **DataHub Input** – subscribes to an existing provider and emits JSON messages. Supports both **Event-based** and **Polling** updates.
+3. **DataHub Output** – automatically registers a provider (defaults to your Client Name/ID), flattens incoming JSON structures and publishes them to the Data Hub.
 
 The nodes reuse the FlatBuffer helpers from the standalone Node sample, so they speak the native NATS API.
 
@@ -38,13 +38,18 @@ The config node automatically fetches tokens via Client Credentials flow.
 
 ## DataHub Input Node
 
-- Select the u-OS config node, then choose one of the discovered providers from the dropdown. 
-- **Troubleshooting**: If the dropdown remains empty, check the Node-RED debug tab. The node logs the API response count. Ensure your OAuth client has `hub.variables.readonly` permission.
-- Pick the variables you need from the multi-select list. Leave it empty to receive all variables.
+- Select the u-OS config node.
+- **Providers**: Click the **Refresh** button to list available providers. This list can be cached from the "Test Connection" button in the Config Node.
+- **Variables**: Select a provider, then click *Refresh* to load its variables. **Note:** To load variables, the Config Node **must be deployed** first!
+- **Polling (ms)**:
+  - `0`: **Events only**. Efficient and fast.
+  - `> 0`: **Hybrid Mode**. Receives events **AND** polls values every X ms.
+- **Troubleshooting**: If lists remain empty, check the Node-RED debug tab. Ensure your OAuth client has `hub.variables.readonly` permission.
 
 ## DataHub Output Node
 
-- Reuses the u-OS config node. The provider ID defaults to `nodered` and is created automatically upon the first message.
+- Reuses the u-OS config node.
+- **Provider ID**: Leave this field **EMPTY** (recommended) to automatically use the **Client Name** defined in your u-OS Config. This ensures your permissions always match.
 - Send a JSON object to the input pin. **Nested objects are supported** and create subcategories automatically:
   ```json
   {

package/nodes/datahub-input.html

@@ -332,10 +332,23 @@
     <dt>u-OS Config</dt>
     <dd>Pick the connection node that holds host, port and OAuth credentials.</dd>
     <dt>Provider ID</dt>
-    <dd>Provider to read. The drop-down lists every provider returned by the Control Center REST API.</dd>
-    <dt>Variables</dt>
-    <dd>Select one or more variable keys (single/multi-select). Leave unselected to stream all variables from the provider.</dd>
+    <dd>Provider to read. The drop-down lists every provider returned by the  <p><strong>Attributes:</strong></p>
+  <dl>
+    <dt>Polling (ms)</dt>
+    <dd>
+      <ul>
+        <li><code>0</code> (default): <strong>Event-based only</strong>. You receive updates whenever they happen.</li>
+        <li><code>> 0</code>: <strong>Hybrid Mode</strong>. You receive live Events <strong>AND</strong> the node explicitly reads all values every X milliseconds. Useful if you suspect missed events.</li>
+      </ul>
+    </dd>
+    <dt>Provider & Variables</dt>
+    <dd>Click the <strong>Refresh</strong> button to load the lists. Providers can be cached, but <strong>Variables require a deployed Config Node</strong> to be loaded securely.</dd>
   </dl>
+  <p><strong>Troubleshooting:</strong></p>
+  <ul>
+      <li><strong>Empty Variable List:</strong> Ensure the Config Node is <strong>DEPLOYED</strong>. The "Test Connection" button only checks basic connectivity, but reading variable schemas requires a running flow.</li>
+      <li><strong>Permission Information:</strong> If you don't see a specific provider, your OAuth Client might lack read permissions for it.</li>
+  </ul>
   <p>Each message has <code>msg.payload</code> shaped like:</p>
 <pre>{
   "type": "snapshot" | "change",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "node-red-contrib-uos-nats",
-  "version": "0.1.25",
+  "version": "0.1.26",
   "description": "Node-RED nodes for u-OS Data Hub via NATS",
   "repository": {
     "type": "git",