homematic-manager 3.1.4 → 3.2.0

package/node_modules/@homematic-manager/backend/dist/api/backend.js

@@ -47,6 +47,8 @@ export const SERVICE_MESSAGE_POLL_MS = 300_000;
  * `names.changed` whenever ReGa answers.
  */
 export const REGA_CONNECT_WAIT_MS = 3000;
+/** The paramset keys that are names; any other key of a description request is a link's peer. */
+const OWN_PARAMSETS = new Set(['MASTER', 'VALUES', 'SERVICE', 'ROUTING_TABLE']);
 /** How long the HmIP `getParamset(:0, VALUES)` sweep waits for the device list to settle. */
 export const HMIP_SWEEP_DELAY_MS = 1000;
 /**
@@ -1515,7 +1517,9 @@ export class Backend {
     async #describe(interfaceName, address, paramset) {
         const index = this.#caches.devices.index(interfaceName);
         const description = index.get(address);
-        const isLink = paramset !== 'MASTER' && paramset !== 'VALUES' && paramset !== 'SERVICE';
+        // task 97: an HmIP router's ROUTING_TABLE is a paramset of its own (eQ-3's addendum), not a
+        // peer address - asked as LINK it is refused, and the routing table dialog could not open
+        const isLink = !OWN_PARAMSETS.has(paramset);
         const identity = description
             ? this.#caches.descriptions.identity(interfaceName, description, isLink ? 'LINK' : paramset, index.parentOf(address))
             : undefined;

package/node_modules/@homematic-manager/backend/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@homematic-manager/backend",
-  "version": "3.1.4",
+  "version": "3.2.0",
   "type": "module",
   "description": "Homematic Manager backend: XML-RPC/BIN-RPC clients and callback servers, caches, optional ReGa",
   "license": "AGPL-3.0-or-later",

package/node_modules/@homematic-manager/core/dist/rssi/index.d.ts

@@ -67,6 +67,12 @@ export declare const RSSI_BANDS: readonly RssiBand[];
  *   offset of 256 or with the sign dropped. `130…255` is `value - 256`, `-255…-130` is
  *   `-value - 256` (which is what turns the maintainer's `-208` into a perfectly ordinary
  *   -48 dBm), and a bare positive `2…126` is the same level without its minus.
+ * - The same two shapes come **from rfd itself**, without ReGa
+ *   (https://github.com/OpenCCU/OpenCCU-Base/issues/185): it reads the RSSI byte of the module's
+ *   send status (the ACK) into a `char` and negates it like an event's magnitude, so `RSSI_PEER`
+ *   and `rssiInfo` carry a positive `2…126` on x86_64 (`char` is signed; `55` is -55 dBm) and
+ *   `-130…-255` on ARM (`char` is unsigned; `-236` is -20 dBm). The same two branches catch
+ *   them, and they stay after an upstream fix, for older firmware.
  *
  * The mapping is the one Home Assistant's `aiohomematic` applies (`model/generic/sensor.py`,
  * `_fix_rssi`); OpenCCU's WebUI does the `- 256` half in

package/node_modules/@homematic-manager/core/dist/rssi/index.js

@@ -50,6 +50,12 @@ export const RSSI_BANDS = [
  *   offset of 256 or with the sign dropped. `130…255` is `value - 256`, `-255…-130` is
  *   `-value - 256` (which is what turns the maintainer's `-208` into a perfectly ordinary
  *   -48 dBm), and a bare positive `2…126` is the same level without its minus.
+ * - The same two shapes come **from rfd itself**, without ReGa
+ *   (https://github.com/OpenCCU/OpenCCU-Base/issues/185): it reads the RSSI byte of the module's
+ *   send status (the ACK) into a `char` and negates it like an event's magnitude, so `RSSI_PEER`
+ *   and `rssiInfo` carry a positive `2…126` on x86_64 (`char` is signed; `55` is -55 dBm) and
+ *   `-130…-255` on ARM (`char` is unsigned; `-236` is -20 dBm). The same two branches catch
+ *   them, and they stay after an upstream fix, for older firmware.
  *
  * The mapping is the one Home Assistant's `aiohomematic` applies (`model/generic/sensor.py`,
  * `_fix_rssi`); OpenCCU's WebUI does the `- 256` half in

package/node_modules/@homematic-manager/core/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@homematic-manager/core",
-  "version": "3.1.4",
+  "version": "3.2.0",
   "type": "module",
   "description": "Pure domain logic of the Homematic Manager: no I/O, no DOM",
   "license": "AGPL-3.0-or-later",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "homematic-manager",
-  "version": "3.1.4",
+  "version": "3.2.0",
   "type": "module",
   "description": "Configure and administer Homematic and HomematicIP devices - devices and channels, direct links, paramsets, RSSI, service messages, events and an RPC console - from a local HTTP/WebSocket server that also serves the web UI",
   "keywords": [
@@ -67,8 +67,8 @@
     "hm-simulator": "^1.4.0"
   },
   "dependencies": {
-    "@homematic-manager/backend": "3.1.4",
-    "@homematic-manager/core": "3.1.4",
+    "@homematic-manager/backend": "3.2.0",
+    "@homematic-manager/core": "3.2.0",
     "binrpc": "^4.2.0",
     "homematic-rega": "^2.0.0",
     "homematic-xmlrpc": "^2.0.0",