@camstack/types 1.2.163 → 1.2.164

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

@@ -32,6 +32,7 @@ export declare const MotionOnMotionChangedDataSchema: z.ZodObject<{
     source: z.ZodEnum<{
         onboard: "onboard";
         analyzer: "analyzer";
+        "device-activity": "device-activity";
     }>;
     regions: z.ZodOptional<z.ZodReadonly<z.ZodArray<z.ZodObject<{
         bbox: z.ZodObject<{
@@ -96,6 +97,7 @@ export declare const motionCapability: {
                 source: z.ZodEnum<{
                     onboard: "onboard";
                     analyzer: "analyzer";
+                    "device-activity": "device-activity";
                 }>;
                 regions: z.ZodOptional<z.ZodReadonly<z.ZodArray<z.ZodObject<{
                     bbox: z.ZodObject<{

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

@@ -93,10 +93,24 @@ export type StatelessStepRefusal = z.infer<typeof StatelessStepRefusalSchema>;
  * (analyzer attaches detected `regions[]`; onboard does not — the
  * camera typically only reports a binary signal plus an optional
  * channel/AI class which lives in dedicated event channels).
+ *
+ * - `onboard` — the camera's firmware said something moved.
+ * - `analyzer` — this runner's frame-diff said so, and attaches `regions[]`.
+ * - `device-activity` — the DEVICE said it is doing its job: the
+ *   `recording-signal` LEVEL the same device raises for the recorder
+ *   ([D380](../../../../docs/decisions/adr-0380-a-device-decided-recording-is-a-mode-with-no-schedule-seeded-once.md)),
+ *   republished as a motion source. It attaches **nothing** — no regions, no
+ *   class: the only fact it carries is that the device is active, and a robot
+ *   vacuum that is itself the moving object has no region worth sending. It is
+ *   a LEVEL, so unlike `onboard` it has a real falling edge, and unlike
+ *   `analyzer` it must not open the frame-diff side-channel — the runner's
+ *   `handleOnboardMotionAnalyzer` gate is `source === 'onboard'` and stays that
+ *   way ([D392](../../../../docs/decisions/adr-0392-a-device-that-says-it-is-working-is-a-motion-source-of-its-own.md)).
  */
 export declare const MotionSourceEnum: z.ZodEnum<{
     onboard: "onboard";
     analyzer: "analyzer";
+    "device-activity": "device-activity";
 }>;
 export type MotionSource = z.infer<typeof MotionSourceEnum>;
 /**
@@ -116,6 +130,7 @@ export type MotionSource = z.infer<typeof MotionSourceEnum>;
 export declare const MotionSourcesSchema: z.ZodArray<z.ZodEnum<{
     onboard: "onboard";
     analyzer: "analyzer";
+    "device-activity": "device-activity";
 }>>;
 export type MotionSources = z.infer<typeof MotionSourcesSchema>;
 /**
@@ -130,6 +145,7 @@ export declare const ReportMotionInputSchema: z.ZodObject<{
     source: z.ZodDefault<z.ZodEnum<{
         onboard: "onboard";
         analyzer: "analyzer";
+        "device-activity": "device-activity";
     }>>;
     regions: z.ZodOptional<z.ZodReadonly<z.ZodArray<z.ZodObject<{
         bbox: z.ZodObject<{
@@ -218,6 +234,7 @@ declare const RunnerCameraConfigSchema: z.ZodObject<{
     motionSources: z.ZodDefault<z.ZodArray<z.ZodEnum<{
         onboard: "onboard";
         analyzer: "analyzer";
+        "device-activity": "device-activity";
     }>>>;
     pipelineEnabled: z.ZodDefault<z.ZodBoolean>;
     steps: z.ZodOptional<z.ZodReadonly<z.ZodArray<z.ZodType<import("./pipeline-executor.cap.js").PipelineStepInputOutput, unknown, z.core.$ZodTypeInternals<import("./pipeline-executor.cap.js").PipelineStepInputOutput, unknown>>>>>;
@@ -477,6 +494,7 @@ export declare const pipelineRunnerCapability: {
             motionSources: z.ZodDefault<z.ZodArray<z.ZodEnum<{
                 onboard: "onboard";
                 analyzer: "analyzer";
+                "device-activity": "device-activity";
             }>>>;
             pipelineEnabled: z.ZodDefault<z.ZodBoolean>;
             steps: z.ZodOptional<z.ZodReadonly<z.ZodArray<z.ZodType<import("./pipeline-executor.cap.js").PipelineStepInputOutput, unknown, z.core.$ZodTypeInternals<import("./pipeline-executor.cap.js").PipelineStepInputOutput, unknown>>>>>;
@@ -545,6 +563,7 @@ export declare const pipelineRunnerCapability: {
             source: z.ZodDefault<z.ZodEnum<{
                 onboard: "onboard";
                 analyzer: "analyzer";
+                "device-activity": "device-activity";
             }>>;
             regions: z.ZodOptional<z.ZodReadonly<z.ZodArray<z.ZodObject<{
                 bbox: z.ZodObject<{

package/dist/device/device-profile.d.ts

@@ -105,7 +105,7 @@ export interface DeviceProfileDefaults {
      *  explicitly to enable SW motion). PIR-sourced motion currently
      *  flows through `'onboard'` because Reolink's accessory PIRs feed
      *  the parent camera's firmware motion event channel. */
-    readonly motionSources?: readonly ('onboard' | 'analyzer')[];
+    readonly motionSources?: import('../capabilities/pipeline-runner.cap.js').MotionSources;
     readonly audioMode?: PipelinePhaseMode;
     readonly detectionMode?: PipelinePhaseMode;
 }

package/dist/index.js

@@ -20939,8 +20939,25 @@ var occupancyRecheckFramesField = {
 * (analyzer attaches detected `regions[]`; onboard does not — the
 * camera typically only reports a binary signal plus an optional
 * channel/AI class which lives in dedicated event channels).
-*/
-var MotionSourceEnum = zod.z.enum(["onboard", "analyzer"]);
+*
+* - `onboard` — the camera's firmware said something moved.
+* - `analyzer` — this runner's frame-diff said so, and attaches `regions[]`.
+* - `device-activity` — the DEVICE said it is doing its job: the
+*   `recording-signal` LEVEL the same device raises for the recorder
+*   ([D380](../../../../docs/decisions/adr-0380-a-device-decided-recording-is-a-mode-with-no-schedule-seeded-once.md)),
+*   republished as a motion source. It attaches **nothing** — no regions, no
+*   class: the only fact it carries is that the device is active, and a robot
+*   vacuum that is itself the moving object has no region worth sending. It is
+*   a LEVEL, so unlike `onboard` it has a real falling edge, and unlike
+*   `analyzer` it must not open the frame-diff side-channel — the runner's
+*   `handleOnboardMotionAnalyzer` gate is `source === 'onboard'` and stays that
+*   way ([D392](../../../../docs/decisions/adr-0392-a-device-that-says-it-is-working-is-a-motion-source-of-its-own.md)).
+*/
+var MotionSourceEnum = zod.z.enum([
+	"onboard",
+	"analyzer",
+	"device-activity"
+]);
 /**
 * List of motion sources active on a camera. Empty array is valid:
 * "no source" — happens for battery cams without firmware motion when
@@ -21204,13 +21221,20 @@ var RunnerCameraDeviceUIFields = [
 		type: "multiselect",
 		label: "Motion Sources",
 		default: ["analyzer"],
-		options: [{
-			value: "analyzer",
-			label: "Frame-diff Analyzer (motion addon)"
-		}, {
-			value: "onboard",
-			label: "Camera Onboard Sensor"
-		}]
+		options: [
+			{
+				value: "analyzer",
+				label: "Frame-diff Analyzer (motion addon)"
+			},
+			{
+				value: "onboard",
+				label: "Camera Onboard Sensor"
+			},
+			{
+				value: "device-activity",
+				label: "Device activity (the device says it is working)"
+			}
+		]
 	},
 	{
 		key: "motionFps",

package/dist/index.mjs

@@ -20938,8 +20938,25 @@ var occupancyRecheckFramesField = {
 * (analyzer attaches detected `regions[]`; onboard does not — the
 * camera typically only reports a binary signal plus an optional
 * channel/AI class which lives in dedicated event channels).
-*/
-var MotionSourceEnum = z.enum(["onboard", "analyzer"]);
+*
+* - `onboard` — the camera's firmware said something moved.
+* - `analyzer` — this runner's frame-diff said so, and attaches `regions[]`.
+* - `device-activity` — the DEVICE said it is doing its job: the
+*   `recording-signal` LEVEL the same device raises for the recorder
+*   ([D380](../../../../docs/decisions/adr-0380-a-device-decided-recording-is-a-mode-with-no-schedule-seeded-once.md)),
+*   republished as a motion source. It attaches **nothing** — no regions, no
+*   class: the only fact it carries is that the device is active, and a robot
+*   vacuum that is itself the moving object has no region worth sending. It is
+*   a LEVEL, so unlike `onboard` it has a real falling edge, and unlike
+*   `analyzer` it must not open the frame-diff side-channel — the runner's
+*   `handleOnboardMotionAnalyzer` gate is `source === 'onboard'` and stays that
+*   way ([D392](../../../../docs/decisions/adr-0392-a-device-that-says-it-is-working-is-a-motion-source-of-its-own.md)).
+*/
+var MotionSourceEnum = z.enum([
+	"onboard",
+	"analyzer",
+	"device-activity"
+]);
 /**
 * List of motion sources active on a camera. Empty array is valid:
 * "no source" — happens for battery cams without firmware motion when
@@ -21203,13 +21220,20 @@ var RunnerCameraDeviceUIFields = [
 		type: "multiselect",
 		label: "Motion Sources",
 		default: ["analyzer"],
-		options: [{
-			value: "analyzer",
-			label: "Frame-diff Analyzer (motion addon)"
-		}, {
-			value: "onboard",
-			label: "Camera Onboard Sensor"
-		}]
+		options: [
+			{
+				value: "analyzer",
+				label: "Frame-diff Analyzer (motion addon)"
+			},
+			{
+				value: "onboard",
+				label: "Camera Onboard Sensor"
+			},
+			{
+				value: "device-activity",
+				label: "Device activity (the device says it is working)"
+			}
+		]
 	},
 	{
 		key: "motionFps",

package/dist/interfaces/event-bus.d.ts

@@ -409,8 +409,10 @@ export interface PhaseTransitionPayload {
     from: 'watching' | 'active';
     to: 'watching' | 'active';
     reason: 'motion_detected' | 'cooldown_expired';
-    /** Motion source that armed the cooldown — present on both ON and OFF. */
-    source?: 'onboard' | 'analyzer';
+    /** Motion source that armed the cooldown — present on both ON and OFF.
+     *  The enum itself, never a hand-copied union: this was a second list of
+     *  the sources and it silently excluded every variant added after it. */
+    source?: import('../capabilities/pipeline-runner.cap.js').MotionSource;
     /** Cooldown window in ms that was/is active for this transition. */
     cooldownMs?: number;
     /** Ms epoch of the transition. */

package/dist/interfaces/stream-broker.d.ts

@@ -395,6 +395,21 @@ export interface CameraDetectionConfig {
     readonly detectionStreamId: string;
     readonly motionFps: number;
     readonly detectionFps: number;
+    /**
+     * The detection rate a session opened by the `device-activity` source is
+     * capped to (D392). A device-activity session is LONG — a cleaning run is
+     * tens of minutes of continuous activity — so it is analysed at a rate that
+     * can be sustained for that long, while a session any other trigger opens
+     * keeps `detectionFps`. Resolved by the orchestrator and applied at dispatch
+     * (`detectionFpsForTrigger`), so what reaches a runner is still a plain
+     * `detectionFps` and no runner needs to know this field exists.
+     *
+     * OPTIONAL because this config is built at several sites, not all of which
+     * resolve the device store. Absent means "not resolved here" and the cap
+     * still applies at `ACTIVITY_DETECTION_FPS_DEFAULT` — the safe direction: a
+     * long session runs slow rather than at full rate for an hour.
+     */
+    readonly activityDetectionFps?: number;
     readonly motionCooldownMs: number;
     /**
      * Orchestrator on-motion session-hold cap (ms). While the session is active

package/package.json

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