@camstack/addon-export-google 0.1.44 → 0.1.45

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -20413,8 +20413,25 @@ var occupancyRecheckFramesField = {
20413
20413
  * (analyzer attaches detected `regions[]`; onboard does not — the
20414
20414
  * camera typically only reports a binary signal plus an optional
20415
20415
  * channel/AI class which lives in dedicated event channels).
20416
- */
20417
- var MotionSourceEnum = _enum(["onboard", "analyzer"]);
20416
+ *
20417
+ * - `onboard` — the camera's firmware said something moved.
20418
+ * - `analyzer` — this runner's frame-diff said so, and attaches `regions[]`.
20419
+ * - `device-activity` — the DEVICE said it is doing its job: the
20420
+ * `recording-signal` LEVEL the same device raises for the recorder
20421
+ * ([D380](../../../../docs/decisions/adr-0380-a-device-decided-recording-is-a-mode-with-no-schedule-seeded-once.md)),
20422
+ * republished as a motion source. It attaches **nothing** — no regions, no
20423
+ * class: the only fact it carries is that the device is active, and a robot
20424
+ * vacuum that is itself the moving object has no region worth sending. It is
20425
+ * a LEVEL, so unlike `onboard` it has a real falling edge, and unlike
20426
+ * `analyzer` it must not open the frame-diff side-channel — the runner's
20427
+ * `handleOnboardMotionAnalyzer` gate is `source === 'onboard'` and stays that
20428
+ * way ([D392](../../../../docs/decisions/adr-0392-a-device-that-says-it-is-working-is-a-motion-source-of-its-own.md)).
20429
+ */
20430
+ var MotionSourceEnum = _enum([
20431
+ "onboard",
20432
+ "analyzer",
20433
+ "device-activity"
20434
+ ]);
20418
20435
  /**
20419
20436
  * List of motion sources active on a camera. Empty array is valid:
20420
20437
  * "no source" — happens for battery cams without firmware motion when
@@ -20409,8 +20409,25 @@ var occupancyRecheckFramesField = {
20409
20409
  * (analyzer attaches detected `regions[]`; onboard does not — the
20410
20410
  * camera typically only reports a binary signal plus an optional
20411
20411
  * channel/AI class which lives in dedicated event channels).
20412
- */
20413
- var MotionSourceEnum = _enum(["onboard", "analyzer"]);
20412
+ *
20413
+ * - `onboard` — the camera's firmware said something moved.
20414
+ * - `analyzer` — this runner's frame-diff said so, and attaches `regions[]`.
20415
+ * - `device-activity` — the DEVICE said it is doing its job: the
20416
+ * `recording-signal` LEVEL the same device raises for the recorder
20417
+ * ([D380](../../../../docs/decisions/adr-0380-a-device-decided-recording-is-a-mode-with-no-schedule-seeded-once.md)),
20418
+ * republished as a motion source. It attaches **nothing** — no regions, no
20419
+ * class: the only fact it carries is that the device is active, and a robot
20420
+ * vacuum that is itself the moving object has no region worth sending. It is
20421
+ * a LEVEL, so unlike `onboard` it has a real falling edge, and unlike
20422
+ * `analyzer` it must not open the frame-diff side-channel — the runner's
20423
+ * `handleOnboardMotionAnalyzer` gate is `source === 'onboard'` and stays that
20424
+ * way ([D392](../../../../docs/decisions/adr-0392-a-device-that-says-it-is-working-is-a-motion-source-of-its-own.md)).
20425
+ */
20426
+ var MotionSourceEnum = _enum([
20427
+ "onboard",
20428
+ "analyzer",
20429
+ "device-activity"
20430
+ ]);
20414
20431
  /**
20415
20432
  * List of motion sources active on a camera. Empty array is valid:
20416
20433
  * "no source" — happens for battery cams without firmware motion when
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@camstack/addon-export-google",
3
- "version": "0.1.44",
3
+ "version": "0.1.45",
4
4
  "description": "Google Home export — hub-side smart-home fulfillment (SYNC / QUERY / EXECUTE / DISCONNECT) for the non-camera fleet, served over the hub's own OAuth account link. No Google credential is stored, sent or required.",
5
5
  "keywords": [
6
6
  "camstack",