@camstack/addon-provider-homeassistant 1.2.141 → 1.2.143

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-DdU8yrnj.js");
+const require_dist = require("../dist-BQE3XuD4.js");
 let node_crypto = require("node:crypto");
 //#region src/ha-export/topics.ts
 /**
@@ -2756,6 +2756,10 @@ 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."
@@ -2868,6 +2872,10 @@ var CAPS_NOT_EXPORTED = [
 		cap: "videoclips",
 		reason: "Media retrieval by handle, not a state. Clips reach the operator through notifications and the viewer."
 	},
+	{
+		cap: "recording",
+		reason: "Since D625 this is the per-camera COVERAGE and PLAYBACK collection: which sources a camera has recordings in, what each covers over a window, and how to play an instant of it. Every method takes a window and a chosen source, so nothing here is a state a descriptor could publish — an entity would have to invent both. What an operator actually wants in Home Assistant is \"is this camera recording\", and that is `RecordingConfig.enabled` on `recording-archive`, which the camera-function switches already export as the ONE authority (D62). A second entity over this cap would be the second knob that decision forbids."
+	},
 	{
 		cap: "webrtc-session",
 		reason: "A session opener — the definition of transport."
@@ -4034,8 +4042,8 @@ async function applyCameraFunctionWrite(api, deviceId, write, sourceNodeId) {
 			});
 			return;
 		case "recording-enabled": {
-			const config = await api.recording.getDeviceConfig.query({ deviceId });
-			await api.recording.setDeviceConfig.mutate({
+			const config = await api.recordingArchive.getDeviceConfig.query({ deviceId });
+			await api.recordingArchive.setDeviceConfig.mutate({
 				deviceId,
 				config: {
 					...config,
@@ -6854,7 +6862,7 @@ var HaExportAddon = class extends require_dist.BaseAddon {
 	* that is not read stays `unknown` — unread, never failed.
 	*/
 	async buildSyntheticNodes(topology) {
-		const usage = await this.ctx.api.recording.getStorageUsage.query({}).catch((err) => {
+		const usage = await this.ctx.api.recordingArchive.getStorageUsage.query({}).catch((err) => {
 			this.ctx.logger.warn("ha-export: could not read storage usage, the footage entities go unknown", { meta: { error: errMsg(err) } });
 			return null;
 		});
@@ -7198,7 +7206,7 @@ var HaExportAddon = class extends require_dist.BaseAddon {
 			});
 			return null;
 		});
-		const recordingEnabled = await this.ctx.api.recording.getDeviceConfig.query({ deviceId }).then((config) => config.enabled).catch((err) => {
+		const recordingEnabled = await this.ctx.api.recordingArchive.getDeviceConfig.query({ deviceId }).then((config) => config.enabled).catch((err) => {
 			this.ctx.logger.warn("ha-export: could not read recording config, the recording function degrades", {
 				tags: { deviceId },
 				meta: { error: errMsg(err) }

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-R2qhuV_9.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-CcnfBSQ5.mjs";
 import { createHmac, timingSafeEqual } from "node:crypto";
 //#region src/ha-export/topics.ts
 /**
@@ -2751,6 +2751,10 @@ 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."
@@ -2863,6 +2867,10 @@ var CAPS_NOT_EXPORTED = [
 		cap: "videoclips",
 		reason: "Media retrieval by handle, not a state. Clips reach the operator through notifications and the viewer."
 	},
+	{
+		cap: "recording",
+		reason: "Since D625 this is the per-camera COVERAGE and PLAYBACK collection: which sources a camera has recordings in, what each covers over a window, and how to play an instant of it. Every method takes a window and a chosen source, so nothing here is a state a descriptor could publish — an entity would have to invent both. What an operator actually wants in Home Assistant is \"is this camera recording\", and that is `RecordingConfig.enabled` on `recording-archive`, which the camera-function switches already export as the ONE authority (D62). A second entity over this cap would be the second knob that decision forbids."
+	},
 	{
 		cap: "webrtc-session",
 		reason: "A session opener — the definition of transport."
@@ -4029,8 +4037,8 @@ async function applyCameraFunctionWrite(api, deviceId, write, sourceNodeId) {
 			});
 			return;
 		case "recording-enabled": {
-			const config = await api.recording.getDeviceConfig.query({ deviceId });
-			await api.recording.setDeviceConfig.mutate({
+			const config = await api.recordingArchive.getDeviceConfig.query({ deviceId });
+			await api.recordingArchive.setDeviceConfig.mutate({
 				deviceId,
 				config: {
 					...config,
@@ -6849,7 +6857,7 @@ var HaExportAddon = class extends BaseAddon {
 	* that is not read stays `unknown` — unread, never failed.
 	*/
 	async buildSyntheticNodes(topology) {
-		const usage = await this.ctx.api.recording.getStorageUsage.query({}).catch((err) => {
+		const usage = await this.ctx.api.recordingArchive.getStorageUsage.query({}).catch((err) => {
 			this.ctx.logger.warn("ha-export: could not read storage usage, the footage entities go unknown", { meta: { error: errMsg(err) } });
 			return null;
 		});
@@ -7193,7 +7201,7 @@ var HaExportAddon = class extends BaseAddon {
 			});
 			return null;
 		});
-		const recordingEnabled = await this.ctx.api.recording.getDeviceConfig.query({ deviceId }).then((config) => config.enabled).catch((err) => {
+		const recordingEnabled = await this.ctx.api.recordingArchive.getDeviceConfig.query({ deviceId }).then((config) => config.enabled).catch((err) => {
 			this.ctx.logger.warn("ha-export: could not read recording config, the recording function degrades", {
 				tags: { deviceId },
 				meta: { error: errMsg(err) }

package/package.json

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