node-red-contrib-3dm-space 1.0.2 → 1.0.3

package/README.md

@@ -77,7 +77,7 @@ The Config Store saves the latest settings locally.
 
 If Node-RED restarts, the last saved settings are loaded again automatically.
 
-The node has **24 outputs** that can be used for local control.
+The node has **24 outputs** that can be used for local control. You can turn outputs not used to minimize the node size saving flow editor space.
 
 ## Basic Setup
 
@@ -159,7 +159,7 @@ The Config Store saves the settings locally and keeps using them even after a re
 
 The **3DM Config Store** node has 24 outputs.
 
-These outputs can be used to control local logic in Node-RED.
+These outputs can be used to control local logic in Node-RED. You can turn outputs not used off,  the outputs will align with the 3DM scada canvas node and other schedule and control nodes that have reference to 24 outputs.
 
 Typical uses include:
 
@@ -222,8 +222,8 @@ Receiving saved settings:
 
 ## Notes
 
-- Use **3DM Out** to send live data to 3DM.space.
-- Use **3DM In** to receive commands and settings from 3DM.space.
+- Use **3DM Out** to send live data to 3DM.space. This can be read on 3DM devices via "Latest telemetry" under the device properties
+- Use **3DM In** to receive commands and settings from 3DM.space. Data can be sent from 3DM.space to the PassPort via "Attributes" under the device properties 
 - Use **3DM Config Store** to save settings and run local control logic.
 - Device credentials should be copied directly from 3DM.space.
 - Node Name fields are optional and are only used inside Node-RED.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "node-red-contrib-3dm-space",
-  "version": "1.0.2",
+  "version": "1.0.3",
   "description": "Node-RED nodes for 3DM.space SCADA Cloud telemetry, attributes, and local config storage",
   "main": "3dm-cloud-config.js",
   "license": "GPL-3.0-or-later",
@@ -30,4 +30,4 @@
   "optionalDependencies": {
     "node-persistent-queue": "^0.3.1"
   }
-}
+}