node-red-contrib-modbus-modpackqt 3.3.7 → 3.3.8

package/CHANGELOG.md

@@ -4,6 +4,18 @@ All notable changes to **node-red-contrib-modbus-modpackqt** are documented
 here. This project follows [Semantic Versioning](https://semver.org/) — pin a
 major version (`^2.0.0`) in production.
 
+## [3.3.8] — 2026-05-10
+
+### Changed
+
+- **Plain-language labels in master nodes.** The dropdown that selects a
+  config is now labelled **Target Device** (was "Runtime") in master-read,
+  master-write, and master-probe, with clearer helper text.
+- **Config dialog: "Device" section renamed to "Target Device".**
+- **Config dialog: Host field renamed to "IP Address"** with an example
+  placeholder (`e.g. 192.168.1.10`) and an inline hint explaining what to
+  enter. Port and Unit ID placeholders also clarified.
+
 ## [3.3.7] — 2026-05-10
 
 ### Added

package/nodes/lib/probe-runtime.js

@@ -18,7 +18,7 @@
 const http = require('http');
 const { URL } = require('url');
 
-const PALETTE_VERSION = '3.3.7';
+const PALETTE_VERSION = '3.3.8';
 const DEFAULT_PORT = parseInt(process.env.MODPACKQT_PROBE_PORT, 10) || 8502;
 const BIND_HOST    = process.env.MODPACKQT_PROBE_HOST || '127.0.0.1';
 const PORT_RETRY   = 5;

package/nodes/modpackqt-config.html

@@ -127,18 +127,21 @@
     Picks a saved connection from modpackqt.com — auto-fills Host, Port, and Unit ID below.
   </div>
 
-  <h4 style="margin-top:18px">Device</h4>
+  <h4 style="margin-top:18px">Target Device</h4>
   <div class="form-row modpackqt-tcp-only">
-    <label for="node-config-input-targetHost"><i class="fa fa-plug"></i> Host</label>
-    <input type="text" id="node-config-input-targetHost" placeholder="Modbus device IP/hostname">
+    <label for="node-config-input-targetHost"><i class="fa fa-plug"></i> IP Address</label>
+    <input type="text" id="node-config-input-targetHost" placeholder="e.g. 192.168.1.10 — IP/hostname of the Modbus device">
+  </div>
+  <div class="form-tips modpackqt-tcp-only" style="font-size:11px;color:#6b7280;margin:-8px 0 12px 105px">
+    The IP address (or hostname) of the target Modbus device on your network.
   </div>
   <div class="form-row modpackqt-tcp-only">
     <label for="node-config-input-targetPort"><i class="fa fa-hashtag"></i> Port</label>
-    <input type="number" id="node-config-input-targetPort" min="1" max="65535" placeholder="502">
+    <input type="number" id="node-config-input-targetPort" min="1" max="65535" placeholder="502 (Modbus TCP default)">
   </div>
   <div class="form-row">
     <label for="node-config-input-unitId"><i class="fa fa-id-card"></i> Unit ID</label>
-    <input type="number" id="node-config-input-unitId" min="1" max="247" placeholder="1">
+    <input type="number" id="node-config-input-unitId" min="1" max="247" placeholder="1 (slave address on the bus)">
   </div>
 
   <h4 style="margin-top:18px">Transport</h4>

package/nodes/modpackqt-master-probe.html

@@ -56,11 +56,11 @@
     <input type="text" id="node-input-name" placeholder="(optional, e.g. Inverter A)">
   </div>
   <div class="form-row">
-    <label for="node-input-server"><i class="fa fa-cog"></i> Runtime</label>
+    <label for="node-input-server"><i class="fa fa-plug"></i> Target Device</label>
     <input type="text" id="node-input-server">
   </div>
   <div class="form-tips" style="font-size:11px;color:#6b7280;margin:-8px 0 12px 105px">
-    The runtime config carries the device target — the probe deep-links the web tester to it.
+    Pick the Modbus device this probe should attach to — the web tester deep-links to it.
   </div>
 
   <div class="form-row">

package/nodes/modpackqt-master-read.html

@@ -31,11 +31,11 @@
     <input type="text" id="node-input-name" placeholder="Name">
   </div>
   <div class="form-row">
-    <label for="node-input-server"><i class="fa fa-cog"></i> Runtime</label>
+    <label for="node-input-server"><i class="fa fa-plug"></i> Target Device</label>
     <input type="text" id="node-input-server">
   </div>
   <div class="form-tips" style="font-size:11px;color:#6b7280;margin:-8px 0 12px 105px">
-    The runtime config carries Host / Port / Unit. To talk to a different device, create another runtime config (pencil → +).
+    Pick the Modbus device this node should read from. Each target device carries its own Host / Port / Unit ID — to talk to a different device, click the pencil → + to add one.
   </div>
 
   <div class="form-row">

package/nodes/modpackqt-master-write.html

@@ -27,11 +27,11 @@
     <input type="text" id="node-input-name" placeholder="Name">
   </div>
   <div class="form-row">
-    <label for="node-input-server"><i class="fa fa-cog"></i> Runtime</label>
+    <label for="node-input-server"><i class="fa fa-plug"></i> Target Device</label>
     <input type="text" id="node-input-server">
   </div>
   <div class="form-tips" style="font-size:11px;color:#6b7280;margin:-8px 0 12px 105px">
-    The runtime config carries Host / Port / Unit. To talk to a different device, create another runtime config (pencil → +).
+    Pick the Modbus device this node should write to. Each target device carries its own Host / Port / Unit ID — to talk to a different device, click the pencil → + to add one.
   </div>
 
   <div class="form-row">

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "node-red-contrib-modbus-modpackqt",
-  "version": "3.3.7",
+  "version": "3.3.8",
   "description": "Modbus commissioning, testing & analysis tools for Node-RED. Embedded Modbus TCP/RTU master + slave server, FC1/FC2/FC3/FC4 reads, FC5/FC6/FC15/FC16 writes, built-in slave register store, and a passive traffic monitor for debugging. 100% free, MIT, no usage limits. By ModPackQT — open the matching web console at modpackqt.com for register decoding, simulation and AI assistance.",
   "keywords": [
     "node-red",