@camstack/addon-provider-wyze 0.2.96 → 0.2.98

package/dist/addon.js

@@ -16519,6 +16519,7 @@ var NcSystemEventKindSchema = _enum([
 	"addon-crash-loop",
 	"addon-update-available",
 	"server-update-available",
+	"wrapper-update-available",
 	"alarm-triggered",
 	"alarm-armed",
 	"alarm-disarmed",
@@ -19964,7 +19965,17 @@ var EventDensityBucketSchema = object({
 	bucketStart: number(),
 	motion: number().int(),
 	object: number().int(),
-	audio: number().int()
+	audio: number().int(),
+	/**
+	* Energy-weighted mean dBFS of the audio events in this bucket — the LEVEL,
+	* as opposed to `audio`, which is their COUNT (D431).
+	*
+	* ABSENT when the bucket holds no audio event. Absence means "nothing was
+	* measured", which is not the same claim as silence, and a lane that cannot
+	* tell them apart paints a quiet hour at full scale — which is exactly what
+	* the count-on-a-level-meter did.
+	*/
+	audioDbfs: number().optional()
 });
 /**
 * One camera's row in a `getEventDensityBatch` answer.
@@ -22065,6 +22076,53 @@ var ImageContractSchema = object({
 	/** One operator-grade sentence: this node runs image X; the contract says Y. */
 	message: string()
 });
+/**
+* The shell verdict (see {@link WrapperKindSchema}) with the proofs that
+* produced it.
+*
+* There is deliberately NO `canSelfUpdate` and no apply action: a wrapper
+* update is an ANNOUNCEMENT. The notification body carries the exact command
+* for a `docker` shell and says the app restarts into the new build for
+* `electron`, and that sentence is chosen from `kind` alone — a boolean
+* nothing reads is the defect this repo keeps paying for.
+*/
+var WrapperIdentitySchema = object({
+	kind: _enum([
+		"docker",
+		"electron",
+		"native",
+		"contradictory",
+		"unknown"
+	]),
+	/** Every probe that ran, in a stable order. Never empty. */
+	evidence: array(object({
+		/** Which probe this row reports. */
+		fact: _enum([
+			"dockerenv-file",
+			"proc-1-cgroup",
+			"platform",
+			"electron-app-version-env"
+		]),
+		/**
+		* `observed` — this process read it itself. `declared` — the shell told the
+		* process and nothing here can check it. Only the Electron app version is
+		* ever `declared`, and only because a child cannot see its parent.
+		*/
+		mode: _enum(["observed", "declared"]),
+		/** Did the probe support the fact it names? A `false` row is still evidence. */
+		holds: boolean(),
+		/** What was actually read, verbatim enough for an operator to argue with. */
+		detail: string()
+	})),
+	/**
+	* The version of the SHELL, when the shell has one it can state: the
+	* Electron app version it declared, or the baked seed closure that
+	* fingerprints a container / app bundle. `null` for `contradictory` and
+	* `unknown` — which version belongs to the shell is precisely what is not
+	* known there.
+	*/
+	currentVersion: string().nullable()
+});
 var ServerRollbackInfoSchema = object({
 	/** The version that failed (or was manually rolled back). */
 	fromVersion: string(),
@@ -22106,7 +22164,13 @@ var ServerPackageStatusSchema = object({
 	* Seed-vs-contract verdict (see {@link ImageContractSchema}). Optional for
 	* version skew: an older provider's payload simply omits it.
 	*/
-	imageContract: ImageContractSchema.optional()
+	imageContract: ImageContractSchema.optional(),
+	/**
+	* What this node runs INSIDE (see {@link WrapperIdentitySchema}). Optional
+	* for version skew: an older provider's payload simply omits it, and an
+	* absent wrapper is unknown — never `native`.
+	*/
+	wrapper: WrapperIdentitySchema.optional()
 });
 var ServerUpdateCheckResultSchema = object({
 	packageName: string(),
@@ -30091,7 +30155,23 @@ var RecordingRangeSchema = object({
 });
 var RecordingAvailabilitySchema = object({
 	deviceId: number(),
-	ranges: array(RecordingRangeSchema)
+	ranges: array(RecordingRangeSchema),
+	/**
+	* Every profile this camera has footage in — not only the one `ranges`
+	* describes (D433).
+	*
+	* `ranges` answers for ONE profile by design: the timeline is a single bar,
+	* and enumerating all of them triples the directory reads for a bar that
+	* would look identical. But the answer used to say nothing about that, so a
+	* caller asking "what can I export?" read the single preferred profile as
+	* the only one that exists — on this deployment every camera records `high`
+	* AND `low`, the low tree holding 14 GB for camera 615 alone, and the export
+	* UI could not see it.
+	*
+	* Cheap: it is the same shallow directory read the profile CHOICE already
+	* makes. Ask for a specific profile's ranges with the `profile` input.
+	*/
+	profilesWithFootage: array(string())
 });
 var RecordingDaysSchema = object({
 	deviceId: number(),
@@ -30117,7 +30197,11 @@ var RecordingDaysSchema = object({
 var RecordingAvailabilityForDeviceSchema = object({
 	deviceId: number(),
 	read: _enum(["read", "unreadable"]),
-	ranges: array(RecordingRangeSchema).readonly()
+	ranges: array(RecordingRangeSchema).readonly(),
+	/** Same field, same meaning, as the singular answer (D433). A row that
+	*  dropped it would tell a grid caller the archive holds one profile.
+	*  Empty on an `'unreadable'` row: nobody looked. */
+	profilesWithFootage: array(string()).readonly()
 });
 /**
 * One camera's row in a `getDaysWithRecordingsBatch` answer. Same rule as
@@ -30407,7 +30491,14 @@ var ReadWindowBytesResultSchema = discriminatedUnion("kind", [object({
 method(object({
 	deviceId: number(),
 	fromMs: number(),
-	toMs: number()
+	toMs: number(),
+	/**
+	* Answer for THIS profile instead of the preferred one (D433). Absent
+	* keeps the timeline's behaviour — one bar, one profile, one set of
+	* reads. `profilesWithFootage` on the answer says what may be asked
+	* for.
+	*/
+	profile: string().optional()
 }), RecordingAvailabilitySchema, {
 	kind: "query",
 	auth: "protected"

package/dist/addon.mjs

@@ -16498,6 +16498,7 @@ var NcSystemEventKindSchema = _enum([
 	"addon-crash-loop",
 	"addon-update-available",
 	"server-update-available",
+	"wrapper-update-available",
 	"alarm-triggered",
 	"alarm-armed",
 	"alarm-disarmed",
@@ -19943,7 +19944,17 @@ var EventDensityBucketSchema = object({
 	bucketStart: number(),
 	motion: number().int(),
 	object: number().int(),
-	audio: number().int()
+	audio: number().int(),
+	/**
+	* Energy-weighted mean dBFS of the audio events in this bucket — the LEVEL,
+	* as opposed to `audio`, which is their COUNT (D431).
+	*
+	* ABSENT when the bucket holds no audio event. Absence means "nothing was
+	* measured", which is not the same claim as silence, and a lane that cannot
+	* tell them apart paints a quiet hour at full scale — which is exactly what
+	* the count-on-a-level-meter did.
+	*/
+	audioDbfs: number().optional()
 });
 /**
 * One camera's row in a `getEventDensityBatch` answer.
@@ -22044,6 +22055,53 @@ var ImageContractSchema = object({
 	/** One operator-grade sentence: this node runs image X; the contract says Y. */
 	message: string()
 });
+/**
+* The shell verdict (see {@link WrapperKindSchema}) with the proofs that
+* produced it.
+*
+* There is deliberately NO `canSelfUpdate` and no apply action: a wrapper
+* update is an ANNOUNCEMENT. The notification body carries the exact command
+* for a `docker` shell and says the app restarts into the new build for
+* `electron`, and that sentence is chosen from `kind` alone — a boolean
+* nothing reads is the defect this repo keeps paying for.
+*/
+var WrapperIdentitySchema = object({
+	kind: _enum([
+		"docker",
+		"electron",
+		"native",
+		"contradictory",
+		"unknown"
+	]),
+	/** Every probe that ran, in a stable order. Never empty. */
+	evidence: array(object({
+		/** Which probe this row reports. */
+		fact: _enum([
+			"dockerenv-file",
+			"proc-1-cgroup",
+			"platform",
+			"electron-app-version-env"
+		]),
+		/**
+		* `observed` — this process read it itself. `declared` — the shell told the
+		* process and nothing here can check it. Only the Electron app version is
+		* ever `declared`, and only because a child cannot see its parent.
+		*/
+		mode: _enum(["observed", "declared"]),
+		/** Did the probe support the fact it names? A `false` row is still evidence. */
+		holds: boolean(),
+		/** What was actually read, verbatim enough for an operator to argue with. */
+		detail: string()
+	})),
+	/**
+	* The version of the SHELL, when the shell has one it can state: the
+	* Electron app version it declared, or the baked seed closure that
+	* fingerprints a container / app bundle. `null` for `contradictory` and
+	* `unknown` — which version belongs to the shell is precisely what is not
+	* known there.
+	*/
+	currentVersion: string().nullable()
+});
 var ServerRollbackInfoSchema = object({
 	/** The version that failed (or was manually rolled back). */
 	fromVersion: string(),
@@ -22085,7 +22143,13 @@ var ServerPackageStatusSchema = object({
 	* Seed-vs-contract verdict (see {@link ImageContractSchema}). Optional for
 	* version skew: an older provider's payload simply omits it.
 	*/
-	imageContract: ImageContractSchema.optional()
+	imageContract: ImageContractSchema.optional(),
+	/**
+	* What this node runs INSIDE (see {@link WrapperIdentitySchema}). Optional
+	* for version skew: an older provider's payload simply omits it, and an
+	* absent wrapper is unknown — never `native`.
+	*/
+	wrapper: WrapperIdentitySchema.optional()
 });
 var ServerUpdateCheckResultSchema = object({
 	packageName: string(),
@@ -30070,7 +30134,23 @@ var RecordingRangeSchema = object({
 });
 var RecordingAvailabilitySchema = object({
 	deviceId: number(),
-	ranges: array(RecordingRangeSchema)
+	ranges: array(RecordingRangeSchema),
+	/**
+	* Every profile this camera has footage in — not only the one `ranges`
+	* describes (D433).
+	*
+	* `ranges` answers for ONE profile by design: the timeline is a single bar,
+	* and enumerating all of them triples the directory reads for a bar that
+	* would look identical. But the answer used to say nothing about that, so a
+	* caller asking "what can I export?" read the single preferred profile as
+	* the only one that exists — on this deployment every camera records `high`
+	* AND `low`, the low tree holding 14 GB for camera 615 alone, and the export
+	* UI could not see it.
+	*
+	* Cheap: it is the same shallow directory read the profile CHOICE already
+	* makes. Ask for a specific profile's ranges with the `profile` input.
+	*/
+	profilesWithFootage: array(string())
 });
 var RecordingDaysSchema = object({
 	deviceId: number(),
@@ -30096,7 +30176,11 @@ var RecordingDaysSchema = object({
 var RecordingAvailabilityForDeviceSchema = object({
 	deviceId: number(),
 	read: _enum(["read", "unreadable"]),
-	ranges: array(RecordingRangeSchema).readonly()
+	ranges: array(RecordingRangeSchema).readonly(),
+	/** Same field, same meaning, as the singular answer (D433). A row that
+	*  dropped it would tell a grid caller the archive holds one profile.
+	*  Empty on an `'unreadable'` row: nobody looked. */
+	profilesWithFootage: array(string()).readonly()
 });
 /**
 * One camera's row in a `getDaysWithRecordingsBatch` answer. Same rule as
@@ -30386,7 +30470,14 @@ var ReadWindowBytesResultSchema = discriminatedUnion("kind", [object({
 method(object({
 	deviceId: number(),
 	fromMs: number(),
-	toMs: number()
+	toMs: number(),
+	/**
+	* Answer for THIS profile instead of the preferred one (D433). Absent
+	* keeps the timeline's behaviour — one bar, one profile, one set of
+	* reads. `profilesWithFootage` on the answer says what may be asked
+	* for.
+	*/
+	profile: string().optional()
 }), RecordingAvailabilitySchema, {
 	kind: "query",
 	auth: "protected"

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@camstack/addon-provider-wyze",
-  "version": "0.2.96",
+  "version": "0.2.98",
   "description": "Wyze camera device-provider addon for CamStack — wraps the @apocaliss92/wyze-bridge-js P2P/DTLS client, feeding the stream-broker via the pull-rfc4571 lazy-publish path (a structural twin of addon-provider-reolink)",
   "keywords": [
     "camstack",