@camstack/types 1.2.175 → 1.2.176

package/dist/capabilities/pipeline-analytics.cap.d.ts

@@ -1433,6 +1433,7 @@ export declare const EventDensityBucketSchema: z.ZodObject<{
     motion: z.ZodNumber;
     object: z.ZodNumber;
     audio: z.ZodNumber;
+    audioDbfs: z.ZodOptional<z.ZodNumber>;
 }, z.core.$strip>;
 export type EventDensityBucket = z.infer<typeof EventDensityBucketSchema>;
 /**
@@ -1477,6 +1478,7 @@ export declare const EventDensityForDeviceSchema: z.ZodObject<{
         motion: z.ZodNumber;
         object: z.ZodNumber;
         audio: z.ZodNumber;
+        audioDbfs: z.ZodOptional<z.ZodNumber>;
     }, z.core.$strip>>>;
 }, z.core.$strip>;
 export type EventDensityForDevice = z.infer<typeof EventDensityForDeviceSchema>;
@@ -2614,6 +2616,7 @@ export declare const pipelineAnalyticsCapability: {
             motion: z.ZodNumber;
             object: z.ZodNumber;
             audio: z.ZodNumber;
+            audioDbfs: z.ZodOptional<z.ZodNumber>;
         }, z.core.$strip>>>, import("./capability-definition.js").CapabilityMethodKind>;
         /**
          * The same histogram, for a SET of cameras, in one round trip.
@@ -2649,6 +2652,7 @@ export declare const pipelineAnalyticsCapability: {
                 motion: z.ZodNumber;
                 object: z.ZodNumber;
                 audio: z.ZodNumber;
+                audioDbfs: z.ZodOptional<z.ZodNumber>;
             }, z.core.$strip>>>;
         }, z.core.$strip>>>, import("./capability-definition.js").CapabilityMethodKind>;
         /**

package/dist/capabilities/recording.cap.d.ts

@@ -35,6 +35,7 @@ export declare const RecordingAvailabilitySchema: z.ZodObject<{
         startMs: z.ZodNumber;
         endMs: z.ZodNumber;
     }, z.core.$strip>>;
+    profilesWithFootage: z.ZodArray<z.ZodString>;
 }, z.core.$strip>;
 export type RecordingAvailability = z.infer<typeof RecordingAvailabilitySchema>;
 export declare const RecordingDaysSchema: z.ZodObject<{
@@ -84,6 +85,7 @@ export declare const RecordingAvailabilityForDeviceSchema: z.ZodObject<{
         startMs: z.ZodNumber;
         endMs: z.ZodNumber;
     }, z.core.$strip>>>;
+    profilesWithFootage: z.ZodReadonly<z.ZodArray<z.ZodString>>;
 }, z.core.$strip>;
 export type RecordingAvailabilityForDevice = z.infer<typeof RecordingAvailabilityForDeviceSchema>;
 /**
@@ -377,6 +379,7 @@ export declare const recordingCapability: {
             deviceId: z.ZodNumber;
             fromMs: z.ZodNumber;
             toMs: z.ZodNumber;
+            profile: z.ZodOptional<z.ZodString>;
         }, z.core.$strip>, z.ZodObject<{
             deviceId: z.ZodNumber;
             ranges: z.ZodArray<z.ZodObject<{
@@ -384,6 +387,7 @@ export declare const recordingCapability: {
                 startMs: z.ZodNumber;
                 endMs: z.ZodNumber;
             }, z.core.$strip>>;
+            profilesWithFootage: z.ZodArray<z.ZodString>;
         }, z.core.$strip>, "query">;
         /**
          * `getAvailability` for a SET of cameras, in one round trip.
@@ -418,6 +422,7 @@ export declare const recordingCapability: {
                 startMs: z.ZodNumber;
                 endMs: z.ZodNumber;
             }, z.core.$strip>>>;
+            profilesWithFootage: z.ZodReadonly<z.ZodArray<z.ZodString>>;
         }, z.core.$strip>>>, "query">;
         /** Which calendar days in [fromMs,toMs) have ≥1 recorded segment, bucketed by
          *  the client's local day (`tzOffsetMinutes` = minutes to add to UTC). Drives

package/dist/index.js

@@ -19912,7 +19912,17 @@ var EventDensityBucketSchema = zod.z.object({
 	bucketStart: zod.z.number(),
 	motion: zod.z.number().int(),
 	object: zod.z.number().int(),
-	audio: zod.z.number().int()
+	audio: zod.z.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: zod.z.number().optional()
 });
 /**
 * Most cameras one `getEventDensityBatch` may name.
@@ -33309,7 +33319,23 @@ var RecordingRangeSchema = zod.z.object({
 });
 var RecordingAvailabilitySchema = zod.z.object({
 	deviceId: zod.z.number(),
-	ranges: zod.z.array(RecordingRangeSchema)
+	ranges: zod.z.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: zod.z.array(zod.z.string())
 });
 var RecordingDaysSchema = zod.z.object({
 	deviceId: zod.z.number(),
@@ -33350,7 +33376,11 @@ var RECORDING_TIMELINE_BATCH_MAX = 200;
 var RecordingAvailabilityForDeviceSchema = zod.z.object({
 	deviceId: zod.z.number(),
 	read: zod.z.enum(["read", "unreadable"]),
-	ranges: zod.z.array(RecordingRangeSchema).readonly()
+	ranges: zod.z.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: zod.z.array(zod.z.string()).readonly()
 });
 /**
 * One camera's row in a `getDaysWithRecordingsBatch` answer. Same rule as
@@ -33650,7 +33680,14 @@ var recordingCapability = {
 		getAvailability: require_sleep.method(zod.z.object({
 			deviceId: zod.z.number(),
 			fromMs: zod.z.number(),
-			toMs: zod.z.number()
+			toMs: zod.z.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: zod.z.string().optional()
 		}), RecordingAvailabilitySchema, {
 			kind: "query",
 			auth: "protected"

package/dist/index.mjs

@@ -19911,7 +19911,17 @@ var EventDensityBucketSchema = z.object({
 	bucketStart: z.number(),
 	motion: z.number().int(),
 	object: z.number().int(),
-	audio: z.number().int()
+	audio: z.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: z.number().optional()
 });
 /**
 * Most cameras one `getEventDensityBatch` may name.
@@ -33308,7 +33318,23 @@ var RecordingRangeSchema = z.object({
 });
 var RecordingAvailabilitySchema = z.object({
 	deviceId: z.number(),
-	ranges: z.array(RecordingRangeSchema)
+	ranges: z.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: z.array(z.string())
 });
 var RecordingDaysSchema = z.object({
 	deviceId: z.number(),
@@ -33349,7 +33375,11 @@ var RECORDING_TIMELINE_BATCH_MAX = 200;
 var RecordingAvailabilityForDeviceSchema = z.object({
 	deviceId: z.number(),
 	read: z.enum(["read", "unreadable"]),
-	ranges: z.array(RecordingRangeSchema).readonly()
+	ranges: z.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: z.array(z.string()).readonly()
 });
 /**
 * One camera's row in a `getDaysWithRecordingsBatch` answer. Same rule as
@@ -33649,7 +33679,14 @@ var recordingCapability = {
 		getAvailability: method(z.object({
 			deviceId: z.number(),
 			fromMs: z.number(),
-			toMs: z.number()
+			toMs: z.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: z.string().optional()
 		}), RecordingAvailabilitySchema, {
 			kind: "query",
 			auth: "protected"

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@camstack/types",
-  "version": "1.2.175",
+  "version": "1.2.176",
   "description": "Shared types, interfaces, and model catalogs for the CamStack detection ecosystem",
   "keywords": [
     "camstack",