homematic-manager 3.0.0 → 3.0.1

package/data/manifest.json

@@ -1,5 +1,5 @@
 {
-  "generatedAt": "2026-09-30T14:40:52.310Z",
+  "generatedAt": "2026-09-30T20:15:59.038Z",
   "sources": [
     {
       "name": "openccu-data/easymode_extract",
@@ -34,7 +34,7 @@
     {
       "name": "homematic-manager/legacy-easymode-localization",
       "version": "2.7.1",
-      "url": "https://github.com/hobbyquaker/homematic-manager/tree/master/www/easymodes/localization",
+      "url": "https://github.com/hobbyquaker/homematic-manager/tree/2.7.1/www/easymodes/localization",
       "sha256": "00e0e2d79c7fbc1f97b8e7cb10d4da4473a3f693d0d07493ad909c14ddfb906c"
     }
   ],

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

@@ -1,6 +1,6 @@
 {
   "name": "@homematic-manager/backend",
-  "version": "3.0.0",
+  "version": "3.0.1",
   "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/devices/hmipKey.d.ts

@@ -5,7 +5,7 @@
  * sticker shows them twice:
  *
  * - as a QR code, `EQ01SG<SGTIN, 24 hex>DLK<key, 32 hex>` - the form 2.x's scanner parsed
- *   (`legacy/www/js/homematic-manager.js`), with a four-character prefix before `SG`;
+ *   (`www/js/homematic-manager.js` at the tag 2.7.1), with a four-character prefix before `SG`;
  * - printed, the SGTIN in groups of four and the key as 26 characters of eQ-3's base-32 alphabet in
  *   groups of 5-5-5-5-6 (`XXXXX-XXXXX-XXXXX-XXXXX-XXXXXX`).
  *

package/node_modules/@homematic-manager/core/dist/devices/hmipKey.js

@@ -5,7 +5,7 @@
  * sticker shows them twice:
  *
  * - as a QR code, `EQ01SG<SGTIN, 24 hex>DLK<key, 32 hex>` - the form 2.x's scanner parsed
- *   (`legacy/www/js/homematic-manager.js`), with a four-character prefix before `SG`;
+ *   (`www/js/homematic-manager.js` at the tag 2.7.1), with a four-character prefix before `SG`;
  * - printed, the SGTIN in groups of four and the key as 26 characters of eQ-3's base-32 alphabet in
  *   groups of 5-5-5-5-6 (`XXXXX-XXXXX-XXXXX-XXXXX-XXXXXX`).
  *

package/node_modules/@homematic-manager/core/dist/links/roles.d.ts

@@ -45,6 +45,20 @@ export interface DecodedLinkFlags {
     readonly unknownBits: number;
 }
 export declare function decodeLinkFlags(flags: number | undefined): DecodedLinkFlags;
+/**
+ * Is this a link between two channels of one device - the button of a switch or dimmer actuator
+ * driving its own relay (`KEQ…:1` → `KEQ…:1`), or a dimmer's real channel and its virtual ones
+ * (`JEQ…:1` → `JEQ…:2`)? An address that does not parse is never part of one.
+ */
+export declare function isInternalLink(link: Pick<Link, 'SENDER' | 'RECEIVER'>): boolean;
+/**
+ * The `FLAGS` of a link as the grid shows them (B-86): rfd reports every device-internal link with
+ * `SENDER_BROKEN` set (a lab HM-LC-Sw1's own `:1` → `:1` answers `FLAGS: 1`, and the maintainer's
+ * dimmers and switch plugs flag each of their internal links), although the links work. For such a
+ * link the two broken bits carry no information and are dropped; a link to or from a peer that is
+ * not a device of this interface (`@1A2B3C:14`) keeps them, as does every other link.
+ */
+export declare function linkFlags(link: Pick<Link, 'SENDER' | 'RECEIVER' | 'FLAGS'>): DecodedLinkFlags;
 /** `getLinks` request flags, as the RPC console offers them. */
 export declare const GET_LINKS_FLAGS: {
     readonly GROUP: 1;

package/node_modules/@homematic-manager/core/dist/links/roles.js

@@ -11,7 +11,7 @@
  * roles), the maintenance channel `:0` never does, and a channel without the matching role list is
  * not offered at all.
  */
-import { isMaintenanceAddress } from '../address/address.js';
+import { isMaintenanceAddress, tryParseAddress } from '../address/address.js';
 import { isChannelDescription, parseRoles } from '../devices/index.js';
 /**
  * `FLAGS` of a link record: the interface process marks the side whose configuration it could not
@@ -36,6 +36,30 @@ export function decodeLinkFlags(flags) {
         unknownBits: bits & ~(LINK_FLAGS.SENDER_BROKEN | LINK_FLAGS.RECEIVER_BROKEN),
     };
 }
+/**
+ * Is this a link between two channels of one device - the button of a switch or dimmer actuator
+ * driving its own relay (`KEQ…:1` → `KEQ…:1`), or a dimmer's real channel and its virtual ones
+ * (`JEQ…:1` → `JEQ…:2`)? An address that does not parse is never part of one.
+ */
+export function isInternalLink(link) {
+    const sender = tryParseAddress(link.SENDER);
+    const receiver = tryParseAddress(link.RECEIVER);
+    return sender !== undefined && receiver !== undefined && sender.device === receiver.device;
+}
+/**
+ * The `FLAGS` of a link as the grid shows them (B-86): rfd reports every device-internal link with
+ * `SENDER_BROKEN` set (a lab HM-LC-Sw1's own `:1` → `:1` answers `FLAGS: 1`, and the maintainer's
+ * dimmers and switch plugs flag each of their internal links), although the links work. For such a
+ * link the two broken bits carry no information and are dropped; a link to or from a peer that is
+ * not a device of this interface (`@1A2B3C:14`) keeps them, as does every other link.
+ */
+export function linkFlags(link) {
+    const decoded = decodeLinkFlags(link.FLAGS);
+    if (!decoded.broken || !isInternalLink(link)) {
+        return decoded;
+    }
+    return { senderBroken: false, receiverBroken: false, broken: false, unknownBits: decoded.unknownBits };
+}
 /** `getLinks` request flags, as the RPC console offers them. */
 export const GET_LINKS_FLAGS = {
     GROUP: 1,

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

@@ -1,6 +1,6 @@
 {
   "name": "@homematic-manager/core",
-  "version": "3.0.0",
+  "version": "3.0.1",
   "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.0.0",
+  "version": "3.0.1",
   "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.3.0"
   },
   "dependencies": {
-    "@homematic-manager/backend": "3.0.0",
-    "@homematic-manager/core": "3.0.0",
+    "@homematic-manager/backend": "3.0.1",
+    "@homematic-manager/core": "3.0.1",
     "binrpc": "^4.2.0",
     "homematic-rega": "^2.0.0",
     "homematic-xmlrpc": "^2.0.0",