node-red-contrib-ccu 4.6.2 → 4.7.1

package/CHANGELOG.md

@@ -5,6 +5,79 @@ Notable changes to node-red-contrib-ccu. Format follows
 user-visible symptom and the cause, not the commit list (the release notes
 append commits automatically).
 
+## 4.7.1 (2026-10-28)
+
+### Fixed
+
+- **On openccu-lite every write of a decimal value failed** - a dimmer's or a
+  blind's `LEVEL`, a thermostat's set point, an `ON_TIME`, through _value_,
+  _set value_, _rpc_ and the other nodes alike. A `FLOAT` datapoint is sent as
+  a typed double, which over XML-RPC is homematic-xmlrpc's
+  `{explicitDouble: n}`; the lite-rpc connection of 4.7.0 passed that object
+  on as it was, so the interface process got a struct where a number belongs
+  and refused it (`Failure` from rfd and hs485d,
+  `-5 Invalid parameter or value` from hmipserver). The lite-rpc connection
+  now sends lite-rpc's own typed double, `{double: n}` (or the plain number
+  on a system that does not announce it) - in `setValue`, in a paramset of
+  `putParamset` and in a multicall. The direct connection to a CCU is unchanged. Until this version
+  the workaround was _CCU_ in the connection node's _openccu-lite interfaces_.
+- **Errors of the lite-rpc connection said less than they should:** a fault
+  of the interface process was logged as `fault -1 undefined` and reached the
+  flow as `OccuLiteError: Failure`, and a token without the needed rights did
+  not say which right it lacks. The fault now carries its code and text, and a
+  refused call names the missing scope.
+
+## 4.7.0 (2026-10-27)
+
+### Added
+
+- **On openccu-lite the interfaces are reached through the system's lite-rpc**
+  (with [occulite-client](https://www.npmjs.com/package/occulite-client))
+  instead of XML-RPC/BIN-RPC clients and callback servers of this node's own -
+  the requests over the system's web port, the events from a stream the
+  connection opens, replayed after a break and re-read after a restart of the
+  system; one subscriber at the interface processes serves every program on
+  the system, and nothing registers with `init`. The credential is the
+  openccu-lite token of the connection node, or on the system itself
+  RedMatic's own token, which the system mints for it. A new setting
+  _openccu-lite interfaces_ in the connection node chooses: _auto_ (the
+  default; the CCU way on a CCU), _openccu-lite_ (lite-rpc only) or _CCU_ (the
+  direct connection with callbacks, on openccu-lite too). An existing
+  connection is moved to lite-rpc once, at its first start on openccu-lite,
+  and the log says so; a choice made in the node is never changed by a later
+  version. The value cache is filled from the system's state store at deploy,
+  so nodes with _cache_ get a value on openccu-lite as well. CUxD and CCU-Jack
+  keep their own connections. On a CCU, RaspberryMatic and OpenCCU nothing
+  changes.
+
+### Changed
+
+- **An interface process that is not up yet is tried every 3 s for the first
+  90 s, then every 15 s.** The 1, 2, 4, 8 s steps and the 15 s after them
+  missed hmipserver's ready moment on a booting system by up to 15 s (measured
+  on an openccu-lite Pi 4: hmipserver answers 50-55 s after the boot, the next
+  attempt came at 61 s). The same holds after a process went away. When one
+  interface appears, the others still waiting are tried at once, and the log
+  line that reports the connection says how long after the start (or after the
+  outage) it came. The metadata API's re-detection on openccu-lite follows the
+  same schedule.
+- **The port of each interface can be set in the connection node**, beside its
+  checkbox: blank is the CCU's port for the transport as before (2001/42001 and
+  so on, the 3xxxx ports on the CCU itself), a number replaces it - for a CCU
+  behind port forwarding, or a simulator on another port.
+- The test suite runs hm-simulator 1.4 on free ports, so it runs beside a CCU
+  or another suite, and drives the simulator's scenario API: devices paired
+  and removed while Node-RED runs, a ramp-time write, a service message, an
+  interface process that restarts and forgets its clients, TLS with basic
+  auth.
+- **On openccu-lite the metadata stream reports as `Metadata`, not as
+  "Interface ReGaHSS".** The system has no ReGaHSS; the connection borrowed
+  that slot for the stream's state, so the log said "Interface ReGaHSS
+  connected" at every start and reconnect, right next to "this box has no
+  ReGaHSS". The log now says "Metadata stream connected", the nodes' status
+  counts the stream under that name, and the editors' interface lists do not
+  offer it.
+
 ## 4.6.2 (2026-10-23)
 
 ### Fixed

package/README.md

@@ -36,8 +36,22 @@ BINRPC/XMLRPC works unchanged. Device, channel, room and function names come fro
 ReGaHSS; the connection node detects this at start (`GET /api/meta/v1/version`), nothing has to be configured, and
 `msg.channelName`, `msg.rooms`, `msg.functions` and the room/function filters keep their shape.
 
-- Node-RED **on the system** (RedMatic from its addon catalogue): the system's own read-only token is used, nothing to do.
-- Node-RED **elsewhere**: an API token of the system goes into the connection node's **openccu-lite token** field.
+Since 4.7.0 the interface processes are reached through the system's **lite-rpc** as well, with
+[occulite-client](https://www.npmjs.com/package/occulite-client): the requests over the system's web port, the events
+from a stream the connection opens (replayed after a break, re-read after a restart of the system), one subscriber at
+the processes for every program on the system, no callback server and no `init` of this node's own; the value cache is
+filled from the system's state store at deploy. The connection node's **openccu-lite interfaces** setting chooses
+_auto_ (the default: lite-rpc on openccu-lite, the CCU way on a CCU), _openccu-lite_ (lite-rpc only) or _CCU_ (the
+direct connection with callbacks, on openccu-lite too); an existing connection is moved to lite-rpc once at its first
+start on openccu-lite, the log says so, and a choice made in the node is never changed by a later version. CUxD and
+CCU-Jack keep their own connections.
+
+- Node-RED **on the system** (RedMatic from its addon catalogue): lite-rpc with RedMatic's own token, which the system
+  mints for it from RedMatic's manifest (RedMatic 9.13 or later); the names come with the system's read-only token.
+  Nothing to configure. An older RedMatic has no such token and connects the CCU way, the log says so.
+- Node-RED **elsewhere**: an API token of the system goes into the connection node's **openccu-lite token** field -
+  for lite-rpc it needs the `rpc:*` scope of what the flow does (`rpc:read` for events and reads, `rpc:operate` for
+  `setValue`, `rpc:configure` for paramsets and links, `rpc:admin` for the rest; the rpc node may call anything).
 - **System variables, programs and HM-Script do not exist there.** The `ccu-sysvar`, `ccu-program`, `ccu-script` and
   `ccu-poll` nodes stay in the flows and answer every message with an error.
 

package/nodes/ccu-connection.html

@@ -13,6 +13,12 @@
             cuxdEnabled: {value: false},
             jackEnabled: {value: false},
             jackPort: {value: 2121},
+            regaPort: {value: ''},
+            bcrfPort: {value: ''},
+            bcwiPort: {value: ''},
+            iprfPort: {value: ''},
+            virtPort: {value: ''},
+            cuxdPort: {value: ''},
 
             regaPoll: {value: true},
             regaInterval: {value: 30},
@@ -31,6 +37,7 @@
             username: {value: ''},
 
             metaPort: {value: ''},
+            connectionType: {value: 'auto'},
 
             queueTimeout: {value: 5000, required: true},
             queuePause: {value: 250, required: true},
@@ -223,12 +230,18 @@
     <div class="form-row">
         <label for="node-input-rfdEnabled"><i class="icon-tag"></i> Interfaces</label>
         <div style="width: 70%; display: inline-block; vertical-align: text-top;">
-            <label class="ccu-checkbox"><input type="checkbox" id="node-config-input-regaEnabled"> ReGaHSS</label><br>
-            <label class="ccu-checkbox"><input type="checkbox" id="node-config-input-bcrfEnabled"> BidCos-RF</label><br>
-            <label class="ccu-checkbox"><input type="checkbox" id="node-config-input-bcwiEnabled"> BidCos-Wired</label><br>
-            <label class="ccu-checkbox"><input type="checkbox" id="node-config-input-iprfEnabled"> HmIP-RF</label><br>
-            <label class="ccu-checkbox"><input type="checkbox" id="node-config-input-virtEnabled"> VirtualDevices</label><br>
-            <label class="ccu-checkbox"><input type="checkbox" id="node-config-input-cuxdEnabled"> CUxD</label><br>
+            <label class="ccu-checkbox"><input type="checkbox" id="node-config-input-regaEnabled"> ReGaHSS</label>
+            <input type="text" id="node-config-input-regaPort" class="ccu-port" style="width: 70px;" placeholder="8181"><br>
+            <label class="ccu-checkbox"><input type="checkbox" id="node-config-input-bcrfEnabled"> BidCos-RF</label>
+            <input type="text" id="node-config-input-bcrfPort" class="ccu-port" style="width: 70px;" placeholder="2001"><br>
+            <label class="ccu-checkbox"><input type="checkbox" id="node-config-input-bcwiEnabled"> BidCos-Wired</label>
+            <input type="text" id="node-config-input-bcwiPort" class="ccu-port" style="width: 70px;" placeholder="2000"><br>
+            <label class="ccu-checkbox"><input type="checkbox" id="node-config-input-iprfEnabled"> HmIP-RF</label>
+            <input type="text" id="node-config-input-iprfPort" class="ccu-port" style="width: 70px;" placeholder="2010"><br>
+            <label class="ccu-checkbox"><input type="checkbox" id="node-config-input-virtEnabled"> VirtualDevices</label>
+            <input type="text" id="node-config-input-virtPort" class="ccu-port" style="width: 70px;" placeholder="9292"><br>
+            <label class="ccu-checkbox"><input type="checkbox" id="node-config-input-cuxdEnabled"> CUxD</label>
+            <input type="text" id="node-config-input-cuxdPort" class="ccu-port" style="width: 70px;" placeholder="8701"><br>
             <label class="ccu-checkbox"><input type="checkbox" id="node-config-input-jackEnabled"> CCU-Jack</label>
             <input type="text" id="node-config-input-jackPort" style="width: 70px;" placeholder="2121">
         </div>
@@ -300,10 +313,18 @@
         <label for="node-config-input-password"><i class="icon-tag"></i> Password</label>
         <input type="password" id="node-config-input-password">
     </div>
+    <div class="form-row">
+        <label for="node-config-input-connectionType"><i class="icon-tag"></i> openccu-lite interfaces</label>
+        <select id="node-config-input-connectionType" style="width: 70%;">
+            <option value="auto">auto: through the system's lite-rpc on openccu-lite (the default), the CCU way elsewhere</option>
+            <option value="openccu-lite">openccu-lite: lite-rpc only</option>
+            <option value="ccu">CCU: directly, with callbacks (XML-RPC/BIN-RPC) - on openccu-lite too</option>
+        </select>
+    </div>
     <div class="form-row">
         <label for="node-config-input-metaToken"><i class="icon-tag"></i> openccu-lite token</label>
         <input type="password" id="node-config-input-metaToken" placeholder="olt_...">
-        <small>Only for openccu-lite (a CCU ignores this). Leave empty when Node-RED runs on the box.</small>
+        <small>Only for openccu-lite (a CCU ignores this). Leave empty when Node-RED runs on the system itself (RedMatic).</small>
     </div>
     <div class="form-row">
         <label for="node-config-input-metaPort"><i class="icon-tag"></i> openccu-lite port</label>