node-red-contrib-ccu 4.2.0 → 4.4.0

package/nodes/lib/valuestatus.js

@@ -0,0 +1,145 @@
+/* Node status line showing the last known value and how old it is
+   (B-5, issues #54 and #52).
+
+   The data was always there - the connection keeps value, ts and lc for
+   every datapoint and system variable - the nodes just never showed it,
+   and the sysvar node only showed anything at all when "emit value on
+   start" was enabled. The age is re-rendered on a timer so the line does
+   not silently become stale between events. */
+
+/** Node-RED status lines are narrow - keep them readable. */
+const MAX_TEXT = 45;
+
+const MINUTE = 60;
+const HOUR = 60 * MINUTE;
+const DAY = 24 * HOUR;
+
+/** How often the age is re-rendered, matched to the resolution shown. */
+function refreshInterval(seconds) {
+    if (seconds < MINUTE) {
+        return 5000;
+    }
+
+    if (seconds < HOUR) {
+        return 30000;
+    }
+
+    return 300000;
+}
+
+/**
+ * Compact age of a timestamp, in the style Node-RED status lines use.
+ * @param {number} ts epoch milliseconds
+ * @param {number} now epoch milliseconds
+ * @returns {string} e.g. '5s', '12m', '3h', '2d'
+ */
+function relativeTime(ts, now) {
+    const seconds = Math.max(0, Math.round((now - ts) / 1000));
+    if (seconds < MINUTE) {
+        return seconds + 's';
+    }
+
+    if (seconds < HOUR) {
+        return Math.floor(seconds / MINUTE) + 'm';
+    }
+
+    if (seconds < DAY) {
+        return Math.floor(seconds / HOUR) + 'h';
+    }
+
+    return Math.floor(seconds / DAY) + 'd';
+}
+
+/**
+ * The status text for a value with a timestamp.
+ * @param {*} value
+ * @param {number} [ts] epoch milliseconds; omitted renders the value alone
+ * @param {number} now epoch milliseconds
+ * @returns {string}
+ */
+function formatValueStatus(value, ts, now) {
+    let text = String(value);
+    if (text.length > MAX_TEXT) {
+        text = text.slice(0, MAX_TEXT - 1) + '…';
+    }
+
+    if (!ts) {
+        return text;
+    }
+
+    return text + ' (' + relativeTime(ts, now) + ')';
+}
+
+/**
+ * Keeps a node's status line showing the last value and its age.
+ *
+ * @param {object} node the Node-RED node (needs .status())
+ * @param {object} [options]
+ * @param {Function} [options.now] clock, for tests
+ * @returns {{set: Function, clear: Function, stop: Function}}
+ */
+function valueStatus(node, options) {
+    const now = (options && options.now) || Date.now;
+    let timer = null;
+    let current = null;
+
+    function render() {
+        if (!current) {
+            return;
+        }
+
+        node.status({
+            fill: 'green',
+            shape: 'ring',
+            text: formatValueStatus(current.value, current.ts, now()),
+        });
+    }
+
+    function schedule() {
+        if (timer) {
+            clearInterval(timer);
+            timer = null;
+        }
+
+        if (!current || !current.ts) {
+            return;
+        }
+
+        const interval = refreshInterval(Math.round((now() - current.ts) / 1000));
+        timer = setInterval(() => {
+            render();
+            // the resolution coarsens as the value ages - re-arm accordingly
+            schedule();
+        }, interval);
+        if (typeof timer.unref === 'function') {
+            timer.unref();
+        }
+    }
+
+    return {
+        /**
+         * @param {*} value
+         * @param {number} [ts] epoch milliseconds
+         */
+        set(value, ts) {
+            current = {value, ts};
+            render();
+            schedule();
+        },
+        clear() {
+            current = null;
+            if (timer) {
+                clearInterval(timer);
+                timer = null;
+            }
+        },
+        stop() {
+            if (timer) {
+                clearInterval(timer);
+                timer = null;
+            }
+        },
+    };
+}
+
+module.exports = {valueStatus, formatValueStatus, relativeTime};

package/nodes/locales/de/ccu-display.html

@@ -4,4 +4,21 @@
     als Nachricht übergeben werden diese
     anstelle der Konfiguration genutzt.</p>
     <p>Mit <code>msg.disbleX</code> kann explizit gesetzt werden, dass keine Daten für die Zeile übertragen werden.</p>
+
+    <h3>Dynamische Konfiguration</h3>
+    <p><code>msg.config</code> ist ein Objekt, dessen Eigenschaften die Konfiguration dieses Nodes für genau diese Nachricht überschreiben. Die gespeicherte Konfiguration bleibt unverändert.</p>
+    <ul>
+        <li><code>iface</code></li>
+        <li><code>channel</code></li>
+        <li><code>channelType</code></li>
+        <li><code>sound</code></li>
+        <li><code>repeat</code></li>
+        <li><code>pause</code></li>
+        <li><code>signal</code></li>
+        <li><code>line1 ... line6</code></li>
+        <li><code>color1 ... color6</code></li>
+        <li><code>icon1 ... icon6</code></li>
+        <li><code>disable1 ... disable6</code></li>
+    </ul>
+    <p><code>msg.line1</code> usw. funktionieren unverändert weiter.</p>
 </script>

package/nodes/locales/de/ccu-rpc-event.json

@@ -4,5 +4,6 @@
     "change": "Nur geänderte Werte ausgeben",
     "cache": "Beim Start letzten bekannten Wert ausgeben",
     "working": "Während WORKING keine Werte ausgeben",
+    "certainOnly": "Unsichere Werte verwerfen"
   }
 }

package/nodes/locales/de/ccu-sysvar.json

@@ -2,6 +2,7 @@
   "ccu-sysvar": {
     "tip": "Wird keine Variable ausgewählt kann der Variablen-Name über msg.topic übergeben werden.",
     "change": "Nur geänderte Werte ausgeben",
-    "cache": "Beim Start aktuellen Wert ausgeben"
+    "cache": "Beim Start aktuellen Wert ausgeben",
+    "property": "Wert aus"
   }
-}
+}

package/nodes/locales/de/ccu-value.json

@@ -8,6 +8,7 @@
     "change": "Nur geänderte Werte ausgeben",
     "cache": "Beim Start letzten bekannten Wert ausgeben",
     "working": "Während WORKING keine Werte ausgeben",
-    "queue": "Queue"
+    "queue": "Queue",
+    "certainOnly": "Unsichere Werte verwerfen"
   }
 }

package/nodes/locales/en-US/ccu-display.html

@@ -3,4 +3,21 @@
     <p>If <code>msg.lineX</code>, <code>msg.iconX</code> or <code>msg.colorX</code>
     are set in the message these are used instead of the configuration.</p>
     <p> With <code>msg.disbleX</code> you can explicitly set that no data is transferred for the line.</p>
+
+    <h3>Dynamic configuration</h3>
+    <p><code>msg.config</code> is an object whose properties override this node's configuration for that one message. The stored configuration is never modified.</p>
+    <ul>
+        <li><code>iface</code></li>
+        <li><code>channel</code></li>
+        <li><code>channelType</code></li>
+        <li><code>sound</code></li>
+        <li><code>repeat</code></li>
+        <li><code>pause</code></li>
+        <li><code>signal</code></li>
+        <li><code>line1 ... line6</code></li>
+        <li><code>color1 ... color6</code></li>
+        <li><code>icon1 ... icon6</code></li>
+        <li><code>disable1 ... disable6</code></li>
+    </ul>
+    <p><code>msg.line1</code> and friends keep working unchanged.</p>
 </script>

package/nodes/locales/en-US/ccu-rpc-event.json

@@ -3,6 +3,7 @@
     "tip": "Tip: ",
     "change": "Emit only changed values",
     "cache": "Emit cached value on start",
-    "working": "Don't emit values while actuator is in WORKING state"
+    "working": "Don't emit values while actuator is in WORKING state",
+    "certainOnly": "Discard uncertain values"
   }
-}
+}

package/nodes/locales/en-US/ccu-switch.html

@@ -0,0 +1,12 @@
+<script type="text/html" data-help-name="ccu-switch">
+    <h3>Dynamic configuration</h3>
+    <p><code>msg.config</code> is an object whose properties override this node's configuration for that one message. The stored configuration is never modified.</p>
+    <ul>
+        <li><code>iface</code></li>
+        <li><code>channel</code></li>
+        <li><code>datapoint</code></li>
+        <li><code>datapointProperty</code></li>
+        <li><code>sysvar</code></li>
+        <li><code>sysvarProperty</code></li>
+    </ul>
+</script>

package/nodes/locales/en-US/ccu-sysvar.json

@@ -2,6 +2,7 @@
   "ccu-sysvar": {
     "tip": "Omit the variable name to supply it via msg.payload",
     "change": "Emit changed values only",
-    "cache": "Emit value on start"
+    "cache": "Emit value on start",
+    "property": "Value from"
   }
-}
+}

package/nodes/locales/en-US/ccu-value.json

@@ -8,6 +8,7 @@
     "change": "Emit changed values only",
     "cache": "Emit cached value on start",
     "working": "Don't emit values while actuator is in WORKING state",
-    "queue": "Queue Commands"
+    "queue": "Queue Commands",
+    "certainOnly": "Discard uncertain values"
   }
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "node-red-contrib-ccu",
-  "version": "4.2.0",
+  "version": "4.4.0",
   "license": "MIT",
   "main": "none",
   "keywords": [

package/patch-certainonly.py

@@ -0,0 +1,51 @@
+import io
+import json
+
+# --- editors: certainOnly checkbox (#96) -----------------------------------
+for name, default_anchor in (
+    ("ccu-value", "            cache: {value: false},\n"),
+    ("ccu-rpc-event", "            cache: {value: false},\n"),
+):
+    p = "nodes/%s.html" % name
+    s = io.open(p, encoding="utf-8").read()
+
+    assert default_anchor in s, "defaults anchor in " + p
+    s = s.replace(default_anchor, default_anchor + "            certainOnly: {value: false},\n", 1)
+
+    old = """            <label class="ccu-checkbox">
+                <input type="checkbox" id="node-input-cache">
+                <span data-i18n="%s.cache"></span>
+            </label>
+        </div>
+    </div>""" % name
+    new = """            <label class="ccu-checkbox">
+                <input type="checkbox" id="node-input-cache">
+                <span data-i18n="%s.cache"></span>
+            </label>
+
+            <label class="ccu-checkbox">
+                <input type="checkbox" id="node-input-certainOnly">
+                <span data-i18n="%s.certainOnly"></span>
+            </label>
+        </div>
+    </div>""" % (name, name)
+    assert old in s, "checkbox block in " + p
+    s = s.replace(old, new, 1)
+
+    io.open(p, "w", encoding="utf-8", newline="\n").write(s)
+    print("patched", p)
+
+# --- locales ---------------------------------------------------------------
+LABELS = {
+    "de": "Unsichere Werte verwerfen",
+    "en-US": "Discard uncertain values",
+}
+for loc, label in LABELS.items():
+    for name in ("ccu-value", "ccu-rpc-event"):
+        p = "nodes/locales/%s/%s.json" % (loc, name)
+        d = json.load(io.open(p, encoding="utf-8"))
+        d[name]["certainOnly"] = label
+        io.open(p, "w", encoding="utf-8", newline="\n").write(
+            json.dumps(d, indent=2, ensure_ascii=False) + "\n"
+        )
+        print("locale", p)

package/roadmap-archive/B-17.md

@@ -0,0 +1,106 @@
+# B-17 — openccu-lite (a CCU without ReGaHSS)
+
+**✅ done 2026-09-06** (`4.4.0`).
+
+[openccu-lite](https://github.com/hobbyquaker/openccu-lite) is a Homematic
+CCU firmware that drops ReGaHSS. The interface processes are the ones we
+already talk to (`rfd` BidCos-RF/BIN-RPC, `hs485d`, `hmipserver`
+XML-RPC) — but nothing listens on 8181/8183, `rega.exe`/`tclrega.exe` do
+not exist, HM-Script is never interpreted, and there are no ReGa ids.
+Everything this package took from the ReGa apart from names, rooms and
+functions has no replacement there.
+
+What it offers instead is `occulited`'s **metadata API**, a small JSON
+store served under `/api/meta/v1/` behind the box's lighttpd, with a
+Server-Sent-Events change stream. Its porting kit (`docs/porting-from-rega.md`,
+`docs/PORTING-PROMPT.md`, `docs/meta-api.md` and the `fixtures/`
+conformance corpus in the openccu-lite repository) is what this item
+was implemented against.
+
+## The rule the port follows
+
+Keep the ReGa code path, add a provider, detect at runtime. On a CCU3,
+RaspberryMatic or OpenCCU nothing changes: the same configuration, the
+same messages, the same cache files.
+
+## What was built
+
+- **`nodes/lib/metaprovider.js`** — the counterpart of the `getRega*()`
+  methods. `detect()` is the feature test (`GET /api/meta/v1/version`,
+  no credential, 404 on a CCU). `MetaProvider` loads `GET /snapshot`,
+  then follows `GET /events/sse?since=<revision>`: `object.updated` and
+  `object.deleted` are applied to the in-memory document, everything
+  that can rewrite member paths (`node.*`, `enum.*`, `import`, an
+  explicit `resync`, a gap in the revisions) re-reads the snapshot.
+  `buildNames()` is pure and derives exactly what the rest of the code
+  already reads — `channelNames`, `channelRooms`, `channelFunctions`
+  keyed by the bare address (the API's ref is `<interface>.<address>`),
+  plus the `rooms` / `functions` name lists the editor asks for.
+- **Rooms and functions are a tree** there (`room/eg/wohnzimmer`), not a
+  flat list. They are flattened to the arrays the nodes have always
+  published, ancestors included and most specific first, so a channel in
+  _Wohnzimmer_ below _Erdgeschoss_ matches a room filter on either name
+  and `msg.room` is still the room the user means.
+- **Detection in the startup path** of `ccu-connection.js`: when the
+  ReGaHSS interface is ticked, the node probes once before deciding
+  between `startMeta()` and `getRegaData()`. The provider probes again
+  on every reconnect; three failed probes in a row hand control back to
+  the detection (a restored backup or a firmware swap under a running
+  Node-RED), and on the ReGa side a failing `getRegaData()` /
+  `refreshRegaData()` re-probes at most every five minutes. So a box
+  that changes kind is picked up in both directions without a redeploy.
+- **Credential**: on the box the read-only local token
+  (`/usr/local/etc/occulite/local-token`) is read automatically, off the
+  box an _openccu-lite token_ field takes one created on the box's Users
+  page. `401`/`403` degrades to addresses-only, is logged once, and is
+  retried — never fatal. An _openccu-lite port_ field covers boxes whose
+  web server is not on 80/443 (it is also what the integration test
+  uses).
+- **The ReGa-only nodes stay**: `ccu-sysvar`, `ccu-program`,
+  `ccu-script` and `ccu-poll` remain in the palette and in flows, the
+  connection logs one line about them when it starts, and every message
+  they get is rejected with `… are not available on this box
+(openccu-lite has no ReGaHSS)` instead of breaking the connection.
+- **No new dependency.** `node:http`/`node:https` rather than `fetch`,
+  because the connection node already offers "ignore invalid TLS
+  certificates", which `fetch` cannot express per request without
+  pulling in undici — and a Node stream is the natural shape for SSE.
+
+## Tests
+
+16 unit tests in `test/unit/metaprovider.test.js` (`npm run test:pure`):
+`buildNames()` over the openccu-lite conformance corpus, copied verbatim
+into `test/fixtures/openccu-lite/` (`valid-house`, `valid-empty`,
+`valid-depth-8`), plus a fake `/api/meta/v1` server built from
+`node:http` for detection (openccu-lite / a CCU's 404 / a 200 that is
+not the metadata API / nothing listening), the 401 path, an event →
+"names changed" round trip, the re-snapshot triggers, reconnects and the
+"not an openccu-lite any more" hand-back. The existing ReGa specs are
+untouched.
+
+Verified against a real `occulited` (built from the openccu-lite
+repository, `--listen 127.0.0.1:2132`, the `valid-house` fixture
+imported) with `node-red-node-test-helper` driving a real
+`ccu-connection` node: names, rooms and functions match the box; a
+`PATCH /objects/{ref}` rename, a room rename and a `node.moved` all
+reach `ccu.channelNames` / `ccu.channelRooms` in under 150 ms; the four
+ReGa-only nodes error per message; `createMessage()` produces the same
+`channelName` / `rooms` / `room` / `functions` / `function` fields as on
+a CCU.
+
+## Findings handed back to openccu-lite
+
+1. `occulited`'s SSE endpoint does not flush the response header until
+   it has an event or a heartbeat to write, so an HTTP client cannot
+   tell "connected" from "still connecting" for up to 30 s. A client
+   that applies its ordinary request timeout to the open stream tears it
+   down on every cycle; this implementation arms a separate idle timeout
+   after the socket connects and reports "connected" once the snapshot
+   is in, not when the stream opens.
+2. The porting prompt's example is `fetch`, which cannot do per-request
+   TLS verification settings in Node — worth a sentence in the kit,
+   since every integration that offers "ignore invalid certificates"
+   hits it.
+
+Original item: openccu-lite port — names, rooms and functions from the
+metadata API instead of ReGaHSS, ReGa path unchanged, runtime detection.

package/roadmap-archive/B-2.md

@@ -0,0 +1,69 @@
+# B-2 — Dynamic node configuration via msg
+
+**✅ done 2026-09-04** (`4.3.0`) — issues #172, #71, #103, #80, #56,
+#148, #185, #133.
+
+The request arrived from every direction and was deliberately designed
+once rather than patched per node (which is why PR #173's auto-subscribe
+was closed rather than merged).
+
+## The mechanism
+
+`msg.config` is an object whose properties override the receiving node's
+own configuration **for that message only**. `nodes/lib/dynconfig.js`
+builds the effective configuration; the stored one is never touched.
+
+Why a namespace rather than flat properties everywhere: an event message
+already carries `channel`, `datapoint`, `deviceType`, `rooms` and friends,
+so honouring those on the signal or display node would let any message
+coming from an event node silently retarget it. `msg.ccu` was the obvious
+namespace but is taken — it holds the CCU host name — hence `msg.config`.
+
+Each node passes the list of keys it accepts; anything else in
+`msg.config` is ignored, so a stray property cannot reach node internals.
+The flat mechanism the value/get-value/set-value nodes always had (fill in
+fields left empty in the dialog from `msg.channel`, `msg.rooms`, …) is
+unchanged and keeps working; `msg.config` wins over it.
+
+## Per node
+
+- **set-value** — the whole filter plus `force`. This is also the fix for
+  #133: `setValues()` wrote message properties into `this.config`, so the
+  `if (!config[key])` guard skipped every later message and the node
+  stayed pinned to the first message's targets. The whitelist/blacklist
+  are keyed by the effective filter now, so an unchanged filter keeps the
+  caching benefit and a changed one is re-evaluated. The 200-line inline
+  matching chain moved to `nodes/lib/channelfilter.js` (pure, 14 tests),
+  which also fixed the device-name filter requiring the _channel_ to have
+  a ReGa name while comparing the _device_ name.
+- **value** — `iface`, `channel`, `datapoint`. A message without a
+  payload writes nothing (the 4.0.0 guard) and now retargets the output
+  subscription, which is what #172 asked for. For a node with its own
+  channel/datapoint configured this is a no-op unless `msg.config`
+  overrides them, so no existing flow changes behaviour.
+- **switch** — the source selection (`iface`/`channel`/`datapoint`/
+  `datapointProperty`/`sysvar`/`sysvarProperty`), so one node serves a
+  whole subflow (#103).
+- **sysvar** — `name`, plus a typed input for _where the value comes
+  from_ (msg/flow/global/env) instead of always `msg.payload` (#56).
+- **signal** — every command field including `soundList`/`dimmerList`,
+  which also accept a plain array of values instead of the editor's
+  list-of-objects shape (#148). The existing `<field>Type` typed inputs
+  keep working; `msg.config` wins over them.
+- **display** — channel and the EP-WM55 settings, joining the lines,
+  colours and icons that were already overridable.
+
+## Subflows (#158)
+
+Node-RED substitutes `${PARAMETER}` in a node's string properties before
+the node is constructed, so subflow parameters already worked at runtime —
+but the editor's channel autocomplete cleared any value that was not a
+known channel address, wiping the placeholder every time the dialog was
+opened. Fixed in the value, get-value, switch, signal and alexa editors.
+
+Not done: an explicit `env` type on the filter fields of the event nodes.
+The `${PARAMETER}` route covers the use case and the filters are read once
+at construction, so a typed input would need runtime evaluation for little
+gain. Revisit if someone asks.
+
+Original item: | B-2 | Dynamic node configuration via msg — recurring theme #172, #71, #103, #80, #56, plus #148 (SOUNDFILE_LIST via msg), #158 (subflow env config) and #133 — the latter confirmed still broken in 4.0.0: `setValues()` writes msg values into `config` permanently, so the first message's filters stick. Design properly rather than merging PR #173's auto-subscribe | tracker |

package/roadmap-archive/B-3.md

@@ -0,0 +1,57 @@
+# B-3 — ccu-mqtt node fixes and additions
+
+**✅ done 2026-09-04** (`4.3.0`) — issues #115, #22, #167, plus the three
+findings from ROADMAP §8.2 that the hm2mqtt 3.0 rewrite had confirmed.
+
+## Fixed
+
+- **The writeable check never fired.** Both `putParam` and `putParamset`
+  tested `!(description.OPERATIONS) && 2`, which is `(!OPERATIONS) && 2` —
+  always falsy, since `OPERATIONS` is a non-zero number for every real
+  parameter. Read-only parameters were written regardless. Now
+  `!(OPERATIONS & 2)`, and the write is skipped.
+- **`putParamset` cast against the wrong description.** It passed
+  `paramsetDescription[filter.param]` for every parameter; `filter.param`
+  only exists on the `putParam` topic, so it was `undefined` there and
+  the whole paramset went out uncast (strings where the CCU wanted
+  numbers or booleans). Each value is cast against its own description.
+- **Enum names never worked.** The CCU returns them in `VALUE_LIST`, but
+  `lib/cast.js` and `lib/message.js` read `ENUM`, which no interface
+  process sends: all 9494 ENUM-typed datapoints in the shipped
+  `paramsets.json` carry `VALUE_LIST` and none carries `ENUM`. So
+  `msg.datapointEnum` and `msg.valueEnum` had always been `undefined`,
+  and writing e.g. `AUTO-MODE` to an enum datapoint fell through to the
+  numeric cast and produced `0`. `enumList()` reads `VALUE_LIST` with
+  `ENUM` as a fallback for hand-written data.
+- **The divergent cast copy is gone.** `ccu-mqtt.paramCast` differed from
+  `lib/cast.js` only in clamping to MIN/MAX (and in producing `NaN` for
+  unparseable input, which XML-RPC cannot encode). `castValue` gained a
+  `clamp` option; the mqtt node passes it, the value nodes do not (#74).
+- The empty-name topic bug (`hm/status//STATE` for channels without a
+  ReGa name) was already fixed in 4.2.0.
+
+## Added
+
+- **`get`** (#115): `hm/get/<channel>/<datapoint>` republishes the last
+  known value on its status topic. An empty datapoint republishes every
+  datapoint of the channel. Fresh user interest in April 2026.
+- **`rpc`** (#22): the topic was already in the dispatcher's table, but
+  the class had no `rpc()` method, so `typeof this[command] === 'function'`
+  was false and the message was silently dropped; `topicOutputRpc` was
+  never read at all. That is why both fields sat commented out in the
+  editor since 2018 — exposing them would have created two settings that
+  do nothing. Both are visible now; the result or the error is published
+  on the response topic, and the never-working default topic loses its
+  meaningless `${command}` segment (migrated on dialog open). An empty
+  topic disables a command.
+- **#167**: `getRegaData()` (channel names, rooms, functions, groups) ran
+  once, in the connection constructor; the recurring poll only refreshed
+  variables and programs. A function added in the CCU WebUI was therefore
+  invisible until the flow was redeployed. New connection option
+  _names/rooms refresh_ (minutes, default 15, 0 = off) re-reads channel
+  names, rooms and functions from the ReGa poll's tail.
+
+`resolveChannel()` now holds the channel-name/address resolution the four
+command handlers each had inline.
+
+Original item: | B-3 | Fix the ccu-mqtt node bugs verified in hm2mqtt ROADMAP §1.3 (see §8.2); also #115 get/update method (fresh user interest Apr 2026), #22 missing RPC-topic GUI, #167 stale rooms/functions | hm2mqtt |

package/roadmap-archive/B-4.md

@@ -0,0 +1,44 @@
+# B-4 — Local-CCU detection
+
+**✅ done 2026-09-04** (`4.3.0`).
+
+When Node-RED runs on the CCU itself (RedMatic), the interface processes
+can be reached directly on their 3xxxx ports — BINRPC for BidCos and
+ReGa, and without the hop through the CCU's lighttpd proxy. The
+connection node picked that up from:
+
+```js
+const rfdConf = fs.readFileSync('/etc/lighttpd/conf.d/proxy.conf').toString();
+if (rfdConf.match(/"port"\s+=>\s+32001/)) {
+  this.isLocal = true;
+}
+```
+
+On current firmware that file is a single line:
+
+```
+include "/var/etc/lighttpd_proxy.conf"
+```
+
+which itself only contains `include "/etc/lighttpd/conf.d/proxy_normal.conf"` —
+the `"port" => 32001` markers are two levels down the include chain.
+So the regex has not matched in years and every local install silently
+went through the proxy on 1999/2000/2001/2010/9292.
+
+Measured on a lab CCU3 with firmware 3.89.8: `proxy.conf` is the bare
+include above, while 31999, 32001, 32010 and 39292 are all listening.
+
+## Fix
+
+`nodes/lib/localccu.js` asks the kernel instead of parsing lighttpd's
+configuration: a listener on rfd's direct port (32001, or the ReGa's 31999) is exactly the condition that makes using the direct ports
+correct, and it cannot drift when eQ-3 reorganises the config files
+again. `/proc/net/tcp` and `/proc/net/tcp6` are plain files, so the check
+stays synchronous — the interface table is built in the constructor —
+and on a host without `/proc` (Windows, macOS) it simply reports "not
+local", which is the safe answer.
+
+8 unit tests, including the real `/proc/net/tcp` line format from the
+3.89.8 lab box.
+
+Original item: | B-4 | Fix/remove the dead `isLocal` detection (`/etc/lighttpd/conf.d/proxy.conf` grep, `ccu-connection.js:346` — file is a stub on firmware ≥ 3.87, so local installs silently go through the proxy) | hm2mqtt §15.4 |

package/roadmap-archive/B-5.md

@@ -0,0 +1,57 @@
+# B-5 — Ping checks, sysvar node properties and status
+
+**✅ done 2026-09-04** (`4.3.0`) — issues #44, #54, #52, #124, #166, #96,
+#56, #183.
+
+A collection of small connection- and node-level items that had all been
+open since 2019/2020.
+
+- **#44 — configurable ping checks.** The connection node had a _ping
+  timeout_ field but no way to switch the check off: entering 0 fell
+  through `Number.parseInt(config.rpcPingTimeout, 10) || 60` back to 60
+  seconds. New _RPC ping_ checkbox (default on). Off means no periodic
+  ping and no timeout-triggered re-init for that connection — the honest
+  reading of "deactivate ping checks", with the consequence documented in
+  the dialog.
+- **#54 / #52 — last value and its age under the node.** The connection
+  keeps `value`, `ts` and `lc` for every datapoint and system variable;
+  the nodes simply never showed them, and the sysvar node showed nothing
+  at all unless "emit value on start" was enabled.
+  `nodes/lib/valuestatus.js` renders `<value> (3m)` and re-renders on a timer whose
+  interval follows the resolution shown, so the line does not go stale
+  between events. Used by the sysvar node (which also seeds it from the
+  connection's cache when "emit value on start" is off) and the rpc-event
+  node (which shows the topic that last fired).
+- **#96 — filter uncertain values.** The `uncertain` flag was already in
+  every message; there was no way to filter on it. `uncertain` is a
+  subscription filter property now, exposed as a _discard uncertain
+  values_ checkbox on the value and rpc-event nodes. It is only put into
+  the filter when the option is on, so existing subscriptions are
+  unaffected, and it is evaluated before `callCallback()`'s attribute
+  loop, which may break early for a whitelisted datapoint.
+- **#166 — immediate sysvar echo lost under concurrency.** `setVariable()`
+  triggers a ReGa poll so the new value comes back without waiting for
+  the 30 s interval, but only `if (!this.regaPollPending)`, and
+  `regaPoll()` itself no-ops while one is in flight. Writing several
+  variables at once therefore left all but the first invisible for up to
+  a poll interval — exactly the reported symptom ("works for one
+  variable, not for several"). The request is remembered and exactly one
+  more poll runs when the current one finishes.
+- **#183 — RSSI conversion guarded.** `dp.value -= 256` ran for every
+  RSSI_DEVICE/RSSI_PEER value from the ReGa poll, so a value that was
+  already signed, or the 0 that means "never received", became -318 or
+  -256. Now only for values above 127, matching hm2mqtt's guard. (The
+  XML-RPC event path needs no conversion.)
+- **#124 — re-read variable descriptions on poll** was already fixed in
+  2020 (commit 453f2b2, v3.2.1) and the issue merely never closed; the
+  remaining gap (`info` not selectable as a property) is noted below.
+- **#56** — the sysvar node's configurable source property landed with
+  B-2, which owns the dialog change.
+
+## Not done
+
+- `info` (a variable's description) is still not selectable as a single
+  property in the get-value/sysvar nodes; it is reachable through the
+  whole message. Left for whoever touches those property lists next.
+
+Original item: | B-5 | Configurable ping checks (#44), sysvar node property/status improvements (#54, #56, #52 last-event status, #124 re-read descriptions on poll, #166 immediate sysvar echo, #96 uncertain-filter option) | tracker |