@camstack/addon-provider-homeassistant 1.2.622 → 1.2.624

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_dist = require("../dist-33tQA0eu.js");
+const require_dist = require("../dist-_Yi49Ixo.js");
 let node_crypto = require("node:crypto");
 require("node:zlib");
 let node_fs = require("node:fs");
@@ -427,7 +427,7 @@ function toSlug(value) {
 * `unique_id` — Home Assistant keys its registry on
 * `(platform, integration, unique_id)` — and one of the two would lose the
 * race and be dropped with a "does not generate unique IDs" error. So the
-* operator's existing `camera.videocamera_ingresso` is left exactly where
+* operator's existing `camera.camera_front_door` is left exactly where
 * it is and gains SIBLINGS: one per profile, one per substream, which are
 * the streams membership cannot express.
 *
@@ -5088,7 +5088,7 @@ function sameBrokers(a, b) {
 * export runner came up while the cap resolver was still answering
 * "no provider registered" for hub-resident caps; at 21:55:13 a refresh
 * found `knownBrokers` stale (`[]` vs `[ha_001]`) and wrote BOTH keys. The
-* two exported cameras (590 salone, 615 ingresso) were erased from the
+* two exported cameras (104 hall, 101 front door) were erased from the
 * store, `devices` fell from 4 to 2 (the two synthetic devices), and Home
 * Assistant kept every camera entity as a restored/unavailable orphan for
 * three days: no stream ("the hub does not export this camera"), no

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

@@ -1,4 +1,4 @@
-import { At as BaseAddon, D as buildAddonRouteProvider, F as consumableFormOf, Gt as string, H as deviceExportCapability, I as consumableKindOf, It as nodePin, Rt as array, Ut as object, Yt as EventCategory, _ as addonRoutesCapability, a as COCO_TO_MACRO, at as oauthIntegrationCapability, c as ConsumableItemSchema, d as FanDirectionSchema, f as HvacModeSchema, i as CAMERA_SWITCH_ORDER, l as ConsumableStatusSchema, o as CameraSwitchIdSchema, p as MediaPlayerRepeatSchema, qt as unknown, s as ConsumableFormSchema, t as AlarmArmModeSchema } from "../dist-C6zA8__P.mjs";
+import { At as BaseAddon, D as buildAddonRouteProvider, F as consumableFormOf, Gt as string, H as deviceExportCapability, I as consumableKindOf, It as nodePin, Rt as array, Ut as object, Yt as EventCategory, _ as addonRoutesCapability, a as COCO_TO_MACRO, at as oauthIntegrationCapability, c as ConsumableItemSchema, d as FanDirectionSchema, f as HvacModeSchema, i as CAMERA_SWITCH_ORDER, l as ConsumableStatusSchema, o as CameraSwitchIdSchema, p as MediaPlayerRepeatSchema, qt as unknown, s as ConsumableFormSchema, t as AlarmArmModeSchema } from "../dist-BJRmTD1G.mjs";
 import { createHmac, timingSafeEqual } from "node:crypto";
 import "node:zlib";
 import "node:fs";
@@ -399,7 +399,7 @@ function toSlug(value) {
 * `unique_id` — Home Assistant keys its registry on
 * `(platform, integration, unique_id)` — and one of the two would lose the
 * race and be dropped with a "does not generate unique IDs" error. So the
-* operator's existing `camera.videocamera_ingresso` is left exactly where
+* operator's existing `camera.camera_front_door` is left exactly where
 * it is and gains SIBLINGS: one per profile, one per substream, which are
 * the streams membership cannot express.
 *
@@ -5053,7 +5053,7 @@ function sameBrokers(a, b) {
 * export runner came up while the cap resolver was still answering
 * "no provider registered" for hub-resident caps; at 21:55:13 a refresh
 * found `knownBrokers` stale (`[]` vs `[ha_001]`) and wrote BOTH keys. The
-* two exported cameras (590 salone, 615 ingresso) were erased from the
+* two exported cameras (104 hall, 101 front door) were erased from the
 * store, `devices` fell from 4 to 2 (the two synthetic devices), and Home
 * Assistant kept every camera entity as a restored/unavailable orphan for
 * three days: no stream ("the hub does not export this camera"), no

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@camstack/addon-provider-homeassistant",
-  "version": "1.2.622",
+  "version": "1.2.624",
   "description": "Home Assistant device provider addon for CamStack",
   "keywords": [
     "camstack",