@camstack/addon-provider-tuya 0.2.75 → 0.2.77

package/dist/addon.js

@@ -8669,17 +8669,29 @@ var HHMM = /^([01]\d|2[0-3]):[0-5]\d$/;
 /**
 * DERIVED per-camera storage summary — the single field cheap consumers read
 * (the viewer's status dot, the camera list) instead of walking `bands`:
-*  - `off`        — no band covers the camera (or it is disabled).
-*  - `events`     — every band records around triggers only.
-*  - `continuous` — at least one band records continuously.
-*
-* NEVER authored: the recorder stamps it from the authoritative `bands` on
-* every save (`activeModeForConfig`). Writing it has no effect.
+*  - `off`               — no band covers the camera (or it is disabled).
+*  - `events`            — every band records around triggers only.
+*  - `continuous`        — at least one band records continuously.
+*  - `on-device-decision`— the DEVICE decides: recording runs for as long as the
+*    camera raises its own `recording-signal` level (a robot that cleans). There
+*    is no schedule to author, because there is no hour to program — see
+*    {@link RecordingConfigSchema}`.deviceDecision`.
+*
+* NEVER authored: the recorder stamps it from the authoritative intent
+* (`bands` + `deviceDecision`) on every save (`activeModeForConfig`). Writing it
+* has no effect.
+*
+* `on-device-decision` is named for WHO decides, not for how the recording is
+* requested. `on-demand` was rejected: in this repo's vocabulary a "demand" is
+* something the operator makes (the live gate is the recorder's own "demand
+* window"), and a knob whose name suggests the operator starts it while the
+* device actually does is the D62 shape — a control nobody can predict.
 */
 var RecordingStorageModeSchema = _enum([
 	"off",
 	"events",
-	"continuous"
+	"continuous",
+	"on-device-decision"
 ]);
 /**
 * Le macro classi che possono aprire una finestra di registrazione — le stesse
@@ -8729,22 +8741,7 @@ var RecordingTriggersSchema = object({
 	* il livello: un contatto trovato già aperto al riavvio del runner non fa
 	* registrare.
 	*/
-	sensorDeviceIds: array(number().int().positive()).min(1).max(16).refine(noDuplicates, { message: "sensorDeviceIds must not repeat a device" }).optional(),
-	/**
-	* La camera registra per tutta la durata del SEGNALE che lei stessa
-	* pubblica — la cap `recording-signal` (`active: true` mentre il device è in
-	* funzione: un robot che pulisce). È un LIVELLO, non un fronte: la finestra
-	* resta aperta finché il segnale è alto e si chiude `postBufferSec` dopo la
-	* caduta, così una pulizia di quaranta minuti è UNA clip.
-	*
-	* Non nomina un device: il segnale è della camera stessa, tenuto fresco dal
-	* suo provider (D224); il recorder lo ascolta su `DeviceStateChanged` e lo
-	* riconcilia leggendo la slice via RPC, con un tetto oltre il quale un
-	* segnale mai abbassato (un evento perso) non può tenere aperta una
-	* registrazione (D11). Vedi `recorder/addon/band-decision.ts`
-	* (`holdTrigger` / `releaseTrigger`).
-	*/
-	deviceSignal: boolean().optional()
+	sensorDeviceIds: array(number().int().positive()).min(1).max(16).refine(noDuplicates, { message: "sensorDeviceIds must not repeat a device" }).optional()
 });
 /**
 * Mode of a single recording band — the recorder per-band vocabulary.
@@ -8774,13 +8771,28 @@ var RecordingBandSchema = object({
 	end: string().regex(HHMM),
 	mode: RecordingBandModeSchema,
 	triggers: RecordingBandTriggersSchema.optional(),
+	/**
+	* RETIRED (D381). A band no longer carries a pre-buffer of its own.
+	*
+	* It was the retroactive KEEP bound — which already-written segments survive
+	* a trigger — and it had to be at least as wide as the widest pre-roll the
+	* broker could serve, or the gate would delete the seconds the ring had just
+	* handed the writer. That "at least as wide as" is the tell: it was a second
+	* expression of the broker's retention, in different units, in a different
+	* addon, with an invariant the operator had to maintain by hand. The keep
+	* bound is now derived from the one prebuffer ceiling and there is nothing
+	* left to configure here.
+	*
+	* The key survives in the SHAPE so a config written before that record still
+	* parses and can be migrated deliberately — `RecordingBandSchema` is not
+	* strict, so simply deleting it would strip an operator's value in silence on
+	* the next save (the failure D380 came one commit from shipping). Nothing
+	* reads it: {@link stripRetiredBandPreBufferSec} removes it on load.
+	*/
 	preBufferSec: number().min(0).optional(),
 	postBufferSec: number().min(0).optional()
 });
-({
-	preBufferSec: 15,
-	postBufferSec: 30
-}).postBufferSec * 1e3;
+({ postBufferSec: 30 }).postBufferSec * 1e3;
 /**
 * Per-device retention overrides. Every field is optional; an unset or `0`
 * value inherits the node-wide recorder default. Only footage-lifetime limits
@@ -8828,8 +8840,29 @@ var RecordingConfigSchema = object({
 	* "off" is the absence of a covering band, never a band value.
 	*/
 	bands: array(RecordingBandSchema).default([]),
+	/**
+	* THE device-decided intent: record for as long as the camera itself raises
+	* `recording-signal` (`active: true` while the device is in function — a
+	* robot that cleans). AUTHORED, unlike `mode`, and the only authored
+	* recording intent that is not a band.
+	*
+	* It carries NO schedule on purpose. A band is an HOUR, and this feature has
+	* no hour to program: the device decides. What it costs the operator is one
+	* flag — "this camera can record on its own" — and what it buys is the same
+	* hold/release the recorder already implements (D371, `holdTrigger` /
+	* `releaseTrigger`): the window opens on the rise, stays open for the whole
+	* job however long it is, and closes one pad after the fall.
+	*
+	* EXCLUSIVE with `bands` (below): two authorities deciding when the same
+	* camera records is the D62 failure. `off` remains `enabled: false`, so an
+	* operator switching this camera off is REPORTED off, never as broken.
+	*/
+	deviceDecision: boolean().optional(),
 	retention: RecordingRetentionSchema.optional()
-}).strict();
+}).strict().refine((config) => config.deviceDecision !== true || config.bands.length === 0, {
+	message: "deviceDecision is a whole-config mode and carries no schedule: it cannot be combined with bands",
+	path: ["bands"]
+});
 /**
 * Entity-relocation job state (storage entity-routing spec, Phase 4).
 *
@@ -21862,11 +21895,7 @@ var CameraAudioStatusSchema = object({
 });
 /** Recording block — null when no recording cap is active for this device. */
 var CameraRecordingStatusSchema = object({
-	mode: _enum([
-		"off",
-		"continuous",
-		"events"
-	]),
+	mode: RecordingStorageModeSchema,
 	active: boolean(),
 	storageBytes: number()
 });
@@ -30128,11 +30157,10 @@ DeviceType.Camera, DeviceType.Sensor, DeviceType.Switch, method(object({ deviceI
 var RecordingStatusSchema = object({
 	deviceId: number(),
 	enabled: boolean(),
-	activeMode: _enum([
-		"off",
-		"continuous",
-		"events"
-	]),
+	/** THE derived storage mode, from the one definition
+	*  (`deriveRecordingMode`) — never a second enum. A duplicated list is how
+	*  `on-device-decision` could have reached the recorder and not the status. */
+	activeMode: RecordingStorageModeSchema,
 	nodeId: string(),
 	storageBytes: number()
 });

package/dist/addon.mjs

@@ -8668,17 +8668,29 @@ var HHMM = /^([01]\d|2[0-3]):[0-5]\d$/;
 /**
 * DERIVED per-camera storage summary — the single field cheap consumers read
 * (the viewer's status dot, the camera list) instead of walking `bands`:
-*  - `off`        — no band covers the camera (or it is disabled).
-*  - `events`     — every band records around triggers only.
-*  - `continuous` — at least one band records continuously.
-*
-* NEVER authored: the recorder stamps it from the authoritative `bands` on
-* every save (`activeModeForConfig`). Writing it has no effect.
+*  - `off`               — no band covers the camera (or it is disabled).
+*  - `events`            — every band records around triggers only.
+*  - `continuous`        — at least one band records continuously.
+*  - `on-device-decision`— the DEVICE decides: recording runs for as long as the
+*    camera raises its own `recording-signal` level (a robot that cleans). There
+*    is no schedule to author, because there is no hour to program — see
+*    {@link RecordingConfigSchema}`.deviceDecision`.
+*
+* NEVER authored: the recorder stamps it from the authoritative intent
+* (`bands` + `deviceDecision`) on every save (`activeModeForConfig`). Writing it
+* has no effect.
+*
+* `on-device-decision` is named for WHO decides, not for how the recording is
+* requested. `on-demand` was rejected: in this repo's vocabulary a "demand" is
+* something the operator makes (the live gate is the recorder's own "demand
+* window"), and a knob whose name suggests the operator starts it while the
+* device actually does is the D62 shape — a control nobody can predict.
 */
 var RecordingStorageModeSchema = _enum([
 	"off",
 	"events",
-	"continuous"
+	"continuous",
+	"on-device-decision"
 ]);
 /**
 * Le macro classi che possono aprire una finestra di registrazione — le stesse
@@ -8728,22 +8740,7 @@ var RecordingTriggersSchema = object({
 	* il livello: un contatto trovato già aperto al riavvio del runner non fa
 	* registrare.
 	*/
-	sensorDeviceIds: array(number().int().positive()).min(1).max(16).refine(noDuplicates, { message: "sensorDeviceIds must not repeat a device" }).optional(),
-	/**
-	* La camera registra per tutta la durata del SEGNALE che lei stessa
-	* pubblica — la cap `recording-signal` (`active: true` mentre il device è in
-	* funzione: un robot che pulisce). È un LIVELLO, non un fronte: la finestra
-	* resta aperta finché il segnale è alto e si chiude `postBufferSec` dopo la
-	* caduta, così una pulizia di quaranta minuti è UNA clip.
-	*
-	* Non nomina un device: il segnale è della camera stessa, tenuto fresco dal
-	* suo provider (D224); il recorder lo ascolta su `DeviceStateChanged` e lo
-	* riconcilia leggendo la slice via RPC, con un tetto oltre il quale un
-	* segnale mai abbassato (un evento perso) non può tenere aperta una
-	* registrazione (D11). Vedi `recorder/addon/band-decision.ts`
-	* (`holdTrigger` / `releaseTrigger`).
-	*/
-	deviceSignal: boolean().optional()
+	sensorDeviceIds: array(number().int().positive()).min(1).max(16).refine(noDuplicates, { message: "sensorDeviceIds must not repeat a device" }).optional()
 });
 /**
 * Mode of a single recording band — the recorder per-band vocabulary.
@@ -8773,13 +8770,28 @@ var RecordingBandSchema = object({
 	end: string().regex(HHMM),
 	mode: RecordingBandModeSchema,
 	triggers: RecordingBandTriggersSchema.optional(),
+	/**
+	* RETIRED (D381). A band no longer carries a pre-buffer of its own.
+	*
+	* It was the retroactive KEEP bound — which already-written segments survive
+	* a trigger — and it had to be at least as wide as the widest pre-roll the
+	* broker could serve, or the gate would delete the seconds the ring had just
+	* handed the writer. That "at least as wide as" is the tell: it was a second
+	* expression of the broker's retention, in different units, in a different
+	* addon, with an invariant the operator had to maintain by hand. The keep
+	* bound is now derived from the one prebuffer ceiling and there is nothing
+	* left to configure here.
+	*
+	* The key survives in the SHAPE so a config written before that record still
+	* parses and can be migrated deliberately — `RecordingBandSchema` is not
+	* strict, so simply deleting it would strip an operator's value in silence on
+	* the next save (the failure D380 came one commit from shipping). Nothing
+	* reads it: {@link stripRetiredBandPreBufferSec} removes it on load.
+	*/
 	preBufferSec: number().min(0).optional(),
 	postBufferSec: number().min(0).optional()
 });
-({
-	preBufferSec: 15,
-	postBufferSec: 30
-}).postBufferSec * 1e3;
+({ postBufferSec: 30 }).postBufferSec * 1e3;
 /**
 * Per-device retention overrides. Every field is optional; an unset or `0`
 * value inherits the node-wide recorder default. Only footage-lifetime limits
@@ -8827,8 +8839,29 @@ var RecordingConfigSchema = object({
 	* "off" is the absence of a covering band, never a band value.
 	*/
 	bands: array(RecordingBandSchema).default([]),
+	/**
+	* THE device-decided intent: record for as long as the camera itself raises
+	* `recording-signal` (`active: true` while the device is in function — a
+	* robot that cleans). AUTHORED, unlike `mode`, and the only authored
+	* recording intent that is not a band.
+	*
+	* It carries NO schedule on purpose. A band is an HOUR, and this feature has
+	* no hour to program: the device decides. What it costs the operator is one
+	* flag — "this camera can record on its own" — and what it buys is the same
+	* hold/release the recorder already implements (D371, `holdTrigger` /
+	* `releaseTrigger`): the window opens on the rise, stays open for the whole
+	* job however long it is, and closes one pad after the fall.
+	*
+	* EXCLUSIVE with `bands` (below): two authorities deciding when the same
+	* camera records is the D62 failure. `off` remains `enabled: false`, so an
+	* operator switching this camera off is REPORTED off, never as broken.
+	*/
+	deviceDecision: boolean().optional(),
 	retention: RecordingRetentionSchema.optional()
-}).strict();
+}).strict().refine((config) => config.deviceDecision !== true || config.bands.length === 0, {
+	message: "deviceDecision is a whole-config mode and carries no schedule: it cannot be combined with bands",
+	path: ["bands"]
+});
 /**
 * Entity-relocation job state (storage entity-routing spec, Phase 4).
 *
@@ -21861,11 +21894,7 @@ var CameraAudioStatusSchema = object({
 });
 /** Recording block — null when no recording cap is active for this device. */
 var CameraRecordingStatusSchema = object({
-	mode: _enum([
-		"off",
-		"continuous",
-		"events"
-	]),
+	mode: RecordingStorageModeSchema,
 	active: boolean(),
 	storageBytes: number()
 });
@@ -30127,11 +30156,10 @@ DeviceType.Camera, DeviceType.Sensor, DeviceType.Switch, method(object({ deviceI
 var RecordingStatusSchema = object({
 	deviceId: number(),
 	enabled: boolean(),
-	activeMode: _enum([
-		"off",
-		"continuous",
-		"events"
-	]),
+	/** THE derived storage mode, from the one definition
+	*  (`deriveRecordingMode`) — never a second enum. A duplicated list is how
+	*  `on-device-decision` could have reached the recorder and not the status. */
+	activeMode: RecordingStorageModeSchema,
 	nodeId: string(),
 	storageBytes: number()
 });

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@camstack/addon-provider-tuya",
-  "version": "0.2.75",
+  "version": "0.2.77",
   "description": "Tuya / Smart Life device-provider addon for CamStack — account-onboarded (Tuya IoT cloud fetch of device localKeys) + LOCAL DP control via the @apocaliss92/nodetuya encrypted-LAN client, exposing switch / water-heater-family kettle entities",
   "keywords": [
     "camstack",