@camstack/addon-provider-homeassistant 1.2.140 → 1.2.142

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

@@ -3,7 +3,7 @@ Object.defineProperties(exports, {
 	[Symbol.toStringTag]: { value: "Module" }
 });
 //#endregion
-const require_dist = require("../dist-D1vVHAPR.js");
+const require_dist = require("../dist-1gj-XZ-R.js");
 let node_crypto = require("node:crypto");
 //#region src/ha-export/topics.ts
 /**
@@ -2756,6 +2756,14 @@ function capEntitySpecs(capName) {
 	return specs;
 }
 var CAPS_NOT_EXPORTED = [
+	{
+		cap: "recording-onboard",
+		reason: "An EDITOR of the CAMERA’s own recorder: a weekly schedule of windows per trigger, plus the facts about the card it writes to. The schedule is a document an operator authors, not a reading — an entity would publish 168 slots as a state and nothing in Home Assistant could act on it. The storage side is a reading, but it belongs to the camera’s own health rather than to this cap’s editor surface, and publishing capacity here would put the same number in two places the day a health cap carries it. ONE thing here is arguably a real binary sensor: `recordingToNowhere` — scheduled to record with no usable card. It is deliberately NOT exported yet, because exporting half a cap needs the split decided first, and the two cameras it fires on today are already a danger banner and a WARN."
+	},
+	{
+		cap: "camera-grid-layout",
+		reason: "An EDITOR, not a reading: it carries which camera sits in which cell of a composite grid, authored through a host widget in the device tab. Nothing about it is a measurement and nothing in Home Assistant can act on it — the grid itself already reaches HA as an ordinary camera entity, which is the thing an operator actually watches. An entity here would publish a layout document as a state and never carry a value anyone could use."
+	},
 	{
 		cap: "stream-signals",
 		reason: "A DECLARATION, not a state: it lists the signals a camera can emit to wake its own stream, so the broker can offer them as wake sources. Nothing about it changes over time and nothing about it is a reading — an entity here would show a constant list forever. The signals themselves already reach Home Assistant where they mean something: motion as the motion sensor, a camera-native detection as its own binary sensor."

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

@@ -1,4 +1,4 @@
-import { At as EventCategory, C as buildAddonRouteProvider, Et as string, N as deviceExportCapability, X as oauthIntegrationCapability, a as COCO_TO_MACRO, c as FanDirectionSchema, i as CAMERA_SWITCH_ORDER, l as HvacModeSchema, o as CameraSwitchIdSchema, p as addonRoutesCapability, pt as BaseAddon, t as AlarmArmModeSchema, u as MediaPlayerRepeatSchema, vt as nodePin } from "../dist-DEPiNusb.mjs";
+import { C as buildAddonRouteProvider, F as deviceExportCapability, Nt as EventCategory, Q as oauthIntegrationCapability, a as COCO_TO_MACRO, c as FanDirectionSchema, gt as BaseAddon, i as CAMERA_SWITCH_ORDER, kt as string, l as HvacModeSchema, o as CameraSwitchIdSchema, p as addonRoutesCapability, t as AlarmArmModeSchema, u as MediaPlayerRepeatSchema, xt as nodePin } from "../dist-DbcraPOl.mjs";
 import { createHmac, timingSafeEqual } from "node:crypto";
 //#region src/ha-export/topics.ts
 /**
@@ -2751,6 +2751,14 @@ function capEntitySpecs(capName) {
 	return specs;
 }
 var CAPS_NOT_EXPORTED = [
+	{
+		cap: "recording-onboard",
+		reason: "An EDITOR of the CAMERA’s own recorder: a weekly schedule of windows per trigger, plus the facts about the card it writes to. The schedule is a document an operator authors, not a reading — an entity would publish 168 slots as a state and nothing in Home Assistant could act on it. The storage side is a reading, but it belongs to the camera’s own health rather than to this cap’s editor surface, and publishing capacity here would put the same number in two places the day a health cap carries it. ONE thing here is arguably a real binary sensor: `recordingToNowhere` — scheduled to record with no usable card. It is deliberately NOT exported yet, because exporting half a cap needs the split decided first, and the two cameras it fires on today are already a danger banner and a WARN."
+	},
+	{
+		cap: "camera-grid-layout",
+		reason: "An EDITOR, not a reading: it carries which camera sits in which cell of a composite grid, authored through a host widget in the device tab. Nothing about it is a measurement and nothing in Home Assistant can act on it — the grid itself already reaches HA as an ordinary camera entity, which is the thing an operator actually watches. An entity here would publish a layout document as a state and never carry a value anyone could use."
+	},
 	{
 		cap: "stream-signals",
 		reason: "A DECLARATION, not a state: it lists the signals a camera can emit to wake its own stream, so the broker can offer them as wake sources. Nothing about it changes over time and nothing about it is a reading — an entity here would show a constant list forever. The signals themselves already reach Home Assistant where they mean something: motion as the motion sensor, a camera-native detection as its own binary sensor."

package/package.json

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