@camstack/addon-provider-tuya 0.2.76 → 0.2.78

package/dist/addon.js

@@ -8771,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
@@ -11354,12 +11369,30 @@ var BackupDestinationInfoSchema = object({
 	lastSuccessAt: number().optional(),
 	/** Newest-archive size from `manifests.json`, or undefined. */
 	lastSuccessSizeBytes: number().optional(),
-	/** Per-destination cron expression. Empty = manual-only (no schedule). */
+	/**
+	* Cron cadence(s) of the ENABLED schedules that fan out to this
+	* destination, comma-joined. Absent when no enabled schedule targets it
+	* — a destination nothing is scheduled to write to must not advertise a
+	* cadence (D384). This is never the `backup_destination_policies.cron`
+	* column: that per-location cron has scheduled nothing since 2026-07-28
+	* and reading it made a destination with a DISABLED schedule claim a
+	* nightly run.
+	*/
 	cron: string().optional(),
-	/** ms-epoch of next computed firing for this destination's cron, if any. */
+	/** ms-epoch of the next firing across those schedules (earliest), if any. */
 	nextRunAt: number().optional(),
-	/** ms-epoch of last successful scheduled run (mirrors policy.lastRunAt). */
-	lastRunAt: number().optional()
+	/**
+	* ms-epoch of the last time a run ATTEMPTED to write here — success or
+	* failure. Never a success stamp: pair it with `lastSuccessAt` (the
+	* newest archive that actually landed) and `lastError`.
+	*/
+	lastAttemptAt: number().optional(),
+	/**
+	* Why the last attempt failed, verbatim. Absent when the last attempt
+	* landed the archive. A destination that has never been written to has
+	* neither this nor `lastAttemptAt`.
+	*/
+	lastError: string().optional()
 });
 /**
 * Per-archive entry returned by `backup.listArchives({ destinationId })`.
@@ -11522,8 +11555,16 @@ var BackupScheduleSchema = object({
 	retentionCount: number().int().min(1).max(1e3),
 	/** Optional subset of source locations to include; omitted = all. */
 	dataSources: array(string()).readonly().optional(),
-	/** ms-epoch of last successful run. */
-	lastRunAt: number().optional(),
+	/**
+	* ms-epoch of the last tick that FIRED this schedule. Stamped before the
+	* archive runs (it is the dedupe anchor), so it says "attempted", never
+	* "succeeded" — a run refused by every destination stamps it too.
+	*/
+	lastAttemptAt: number().optional(),
+	/** ms-epoch of the last run of this schedule that landed at ≥1 destination. */
+	lastSuccessAt: number().optional(),
+	/** Why the last fired run failed, verbatim. Absent when it succeeded. */
+	lastError: string().optional(),
 	/** ms-epoch of next computed firing (read-only, filled on list). */
 	nextRunAt: number().optional()
 });
@@ -11572,14 +11613,7 @@ method(_void(), array(BackupDestinationInfoSchema).readonly(), { auth: "admin" }
 	locationId: string(),
 	enabled: boolean(),
 	retentionCount: number().int().min(1).max(1e3),
-	label: string().optional(),
-	/**
-	* Per-destination cron expression. Empty string clears the
-	* schedule (manual-only). Validated server-side via croner;
-	* malformed expressions reject the upsert with an actionable
-	* message.
-	*/
-	cron: string().optional()
+	label: string().optional()
 }), _void(), {
 	kind: "mutation",
 	auth: "admin"

package/dist/addon.mjs

@@ -8770,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
@@ -11353,12 +11368,30 @@ var BackupDestinationInfoSchema = object({
 	lastSuccessAt: number().optional(),
 	/** Newest-archive size from `manifests.json`, or undefined. */
 	lastSuccessSizeBytes: number().optional(),
-	/** Per-destination cron expression. Empty = manual-only (no schedule). */
+	/**
+	* Cron cadence(s) of the ENABLED schedules that fan out to this
+	* destination, comma-joined. Absent when no enabled schedule targets it
+	* — a destination nothing is scheduled to write to must not advertise a
+	* cadence (D384). This is never the `backup_destination_policies.cron`
+	* column: that per-location cron has scheduled nothing since 2026-07-28
+	* and reading it made a destination with a DISABLED schedule claim a
+	* nightly run.
+	*/
 	cron: string().optional(),
-	/** ms-epoch of next computed firing for this destination's cron, if any. */
+	/** ms-epoch of the next firing across those schedules (earliest), if any. */
 	nextRunAt: number().optional(),
-	/** ms-epoch of last successful scheduled run (mirrors policy.lastRunAt). */
-	lastRunAt: number().optional()
+	/**
+	* ms-epoch of the last time a run ATTEMPTED to write here — success or
+	* failure. Never a success stamp: pair it with `lastSuccessAt` (the
+	* newest archive that actually landed) and `lastError`.
+	*/
+	lastAttemptAt: number().optional(),
+	/**
+	* Why the last attempt failed, verbatim. Absent when the last attempt
+	* landed the archive. A destination that has never been written to has
+	* neither this nor `lastAttemptAt`.
+	*/
+	lastError: string().optional()
 });
 /**
 * Per-archive entry returned by `backup.listArchives({ destinationId })`.
@@ -11521,8 +11554,16 @@ var BackupScheduleSchema = object({
 	retentionCount: number().int().min(1).max(1e3),
 	/** Optional subset of source locations to include; omitted = all. */
 	dataSources: array(string()).readonly().optional(),
-	/** ms-epoch of last successful run. */
-	lastRunAt: number().optional(),
+	/**
+	* ms-epoch of the last tick that FIRED this schedule. Stamped before the
+	* archive runs (it is the dedupe anchor), so it says "attempted", never
+	* "succeeded" — a run refused by every destination stamps it too.
+	*/
+	lastAttemptAt: number().optional(),
+	/** ms-epoch of the last run of this schedule that landed at ≥1 destination. */
+	lastSuccessAt: number().optional(),
+	/** Why the last fired run failed, verbatim. Absent when it succeeded. */
+	lastError: string().optional(),
 	/** ms-epoch of next computed firing (read-only, filled on list). */
 	nextRunAt: number().optional()
 });
@@ -11571,14 +11612,7 @@ method(_void(), array(BackupDestinationInfoSchema).readonly(), { auth: "admin" }
 	locationId: string(),
 	enabled: boolean(),
 	retentionCount: number().int().min(1).max(1e3),
-	label: string().optional(),
-	/**
-	* Per-destination cron expression. Empty string clears the
-	* schedule (manual-only). Validated server-side via croner;
-	* malformed expressions reject the upsert with an actionable
-	* message.
-	*/
-	cron: string().optional()
+	label: string().optional()
 }), _void(), {
 	kind: "mutation",
 	auth: "admin"

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@camstack/addon-provider-tuya",
-  "version": "0.2.76",
+  "version": "0.2.78",
   "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",