@camstack/addon-provider-homeassistant 1.2.643 → 1.2.644

package/dist/ha-export/ha-export.addon.js

@@ -24,7 +24,7 @@ var __toESM = (mod, isNodeMode, target) => (target = mod != null ? __create(__ge
 	enumerable: true
 }) : target, mod));
 //#endregion
-const require_ha_broker_source = require("../ha-broker-source-zbaephU5.js");
+const require_ha_broker_source = require("../ha-broker-source-tDtT7Zi-.js");
 let node_crypto = require("node:crypto");
 require("node:zlib");
 let node_fs = require("node:fs");
@@ -261,7 +261,7 @@ var DEVICE_KEY_PREFIX = "camstack-";
 * The rationale that used to sit here — "numeric ids are reallocated by a
 * re-sync, so a captured number would address whichever camera inherited
 * it" — was FALSE and is deleted rather than softened.
-* `allocateNextDeviceId` (`@camstack/system`,
+* `allocateNextDeviceId` (`@camstack/server/system`,
 * `device-meta-store.ts`) is a monotonic counter: it reads
 * `nextDeviceId ?? 1` and writes `current + 1`. A freed id is never
 * re-issued. The worst case after a re-adoption is an ORPHANED entity —

package/dist/ha-export/ha-export.addon.mjs

@@ -1,4 +1,4 @@
-import { $t as array, B as consumableKindOf, Et as sendToExportedTarget, Gt as baseUnitOf, K as deviceExportCapability, Ut as BaseAddon, Xt as isReadingQuantity, Zt as nodePin, _ as PLUG_APPLIANCE_TYPES, bt as runExportedAction, c as COCO_TO_MACRO, cn as unknown, d as ConsumableItemSchema, f as ConsumableStatusSchema, g as MediaPlayerRepeatSchema, gt as pruneDeletedEntities, h as HvacModeSchema, i as AlarmArmModeSchema, in as object, j as buildAddonRouteProvider, l as CameraSwitchIdSchema, m as FanDirectionSchema, on as string, r as listHomeAssistantBrokers, s as CAMERA_SWITCH_ORDER, u as ConsumableFormSchema, un as EventCategory, ut as oauthIntegrationCapability, x as addonRoutesCapability, z as consumableFormOf } from "../ha-broker-source-DxSvfCed.mjs";
+import { B as consumableKindOf, Et as sendToExportedTarget, K as deviceExportCapability, Kt as isReadingQuantity, Vt as baseUnitOf, Yt as array, _ as PLUG_APPLIANCE_TYPES, bt as runExportedAction, c as COCO_TO_MACRO, d as ConsumableItemSchema, en as object, f as ConsumableStatusSchema, g as MediaPlayerRepeatSchema, gt as pruneDeletedEntities, h as HvacModeSchema, i as AlarmArmModeSchema, in as unknown, j as buildAddonRouteProvider, l as CameraSwitchIdSchema, m as FanDirectionSchema, nn as string, qt as nodePin, r as listHomeAssistantBrokers, s as CAMERA_SWITCH_ORDER, u as ConsumableFormSchema, un as EventCategory, ut as oauthIntegrationCapability, x as addonRoutesCapability, z as consumableFormOf, zt as BaseAddon } from "../ha-broker-source-DmHRCdW2.mjs";
 import { createHmac, timingSafeEqual } from "node:crypto";
 import "node:zlib";
 import "node:fs";
@@ -233,7 +233,7 @@ var DEVICE_KEY_PREFIX = "camstack-";
 * The rationale that used to sit here — "numeric ids are reallocated by a
 * re-sync, so a captured number would address whichever camera inherited
 * it" — was FALSE and is deleted rather than softened.
-* `allocateNextDeviceId` (`@camstack/system`,
+* `allocateNextDeviceId` (`@camstack/server/system`,
 * `device-meta-store.ts`) is a monotonic counter: it reads
 * `nextDeviceId ?? 1` and writes `current + 1`. A freed id is never
 * re-issued. The worst case after a re-adoption is an ORPHANED entity —

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@camstack/addon-provider-homeassistant",
-  "version": "1.2.643",
+  "version": "1.2.644",
   "description": "Home Assistant device provider addon for CamStack",
   "keywords": [
     "camstack",
@@ -125,6 +125,9 @@
     "bundle": {
       "displayName": "Home Assistant",
       "description": "Device provider (import) + native entity export (push). Two addons, one bundle, separate processes."
+    },
+    "requires": {
+      "server": ">=1.2.719"
     }
   },
   "files": [