@camstack/addon-provider-amcrest 0.2.94 → 0.2.95

package/dist/addon.js

@@ -19910,7 +19910,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.
@@ -30137,7 +30147,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(),
@@ -30163,7 +30189,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
@@ -30453,7 +30483,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

@@ -19911,7 +19911,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.
@@ -30138,7 +30148,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(),
@@ -30164,7 +30190,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
@@ -30454,7 +30484,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-amcrest",
-  "version": "0.2.94",
+  "version": "0.2.95",
   "description": "Amcrest/Dahua camera device provider addon for CamStack — Dahua CGI over HTTP(S) with digest auth (snapshot, RTSP catalog, PTZ, image/day-night config)",
   "keywords": [
     "camstack",