@camstack/addon-export-hap 1.2.91 → 1.2.92

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.
@@ -20932,8 +20932,25 @@ var occupancyRecheckFramesField = {
20932
20932
  * (analyzer attaches detected `regions[]`; onboard does not — the
20933
20933
  * camera typically only reports a binary signal plus an optional
20934
20934
  * channel/AI class which lives in dedicated event channels).
20935
- */
20936
- var MotionSourceEnum = _enum(["onboard", "analyzer"]);
20935
+ *
20936
+ * - `onboard` — the camera's firmware said something moved.
20937
+ * - `analyzer` — this runner's frame-diff said so, and attaches `regions[]`.
20938
+ * - `device-activity` — the DEVICE said it is doing its job: the
20939
+ * `recording-signal` LEVEL the same device raises for the recorder
20940
+ * ([D380](../../../../docs/decisions/adr-0380-a-device-decided-recording-is-a-mode-with-no-schedule-seeded-once.md)),
20941
+ * republished as a motion source. It attaches **nothing** — no regions, no
20942
+ * class: the only fact it carries is that the device is active, and a robot
20943
+ * vacuum that is itself the moving object has no region worth sending. It is
20944
+ * a LEVEL, so unlike `onboard` it has a real falling edge, and unlike
20945
+ * `analyzer` it must not open the frame-diff side-channel — the runner's
20946
+ * `handleOnboardMotionAnalyzer` gate is `source === 'onboard'` and stays that
20947
+ * way ([D392](../../../../docs/decisions/adr-0392-a-device-that-says-it-is-working-is-a-motion-source-of-its-own.md)).
20948
+ */
20949
+ var MotionSourceEnum = _enum([
20950
+ "onboard",
20951
+ "analyzer",
20952
+ "device-activity"
20953
+ ]);
20937
20954
  /**
20938
20955
  * List of motion sources active on a camera. Empty array is valid:
20939
20956
  * "no source" — happens for battery cams without firmware motion when
@@ -20920,8 +20920,25 @@ var occupancyRecheckFramesField = {
20920
20920
  * (analyzer attaches detected `regions[]`; onboard does not — the
20921
20921
  * camera typically only reports a binary signal plus an optional
20922
20922
  * channel/AI class which lives in dedicated event channels).
20923
- */
20924
- var MotionSourceEnum = _enum(["onboard", "analyzer"]);
20923
+ *
20924
+ * - `onboard` — the camera's firmware said something moved.
20925
+ * - `analyzer` — this runner's frame-diff said so, and attaches `regions[]`.
20926
+ * - `device-activity` — the DEVICE said it is doing its job: the
20927
+ * `recording-signal` LEVEL the same device raises for the recorder
20928
+ * ([D380](../../../../docs/decisions/adr-0380-a-device-decided-recording-is-a-mode-with-no-schedule-seeded-once.md)),
20929
+ * republished as a motion source. It attaches **nothing** — no regions, no
20930
+ * class: the only fact it carries is that the device is active, and a robot
20931
+ * vacuum that is itself the moving object has no region worth sending. It is
20932
+ * a LEVEL, so unlike `onboard` it has a real falling edge, and unlike
20933
+ * `analyzer` it must not open the frame-diff side-channel — the runner's
20934
+ * `handleOnboardMotionAnalyzer` gate is `source === 'onboard'` and stays that
20935
+ * way ([D392](../../../../docs/decisions/adr-0392-a-device-that-says-it-is-working-is-a-motion-source-of-its-own.md)).
20936
+ */
20937
+ var MotionSourceEnum = _enum([
20938
+ "onboard",
20939
+ "analyzer",
20940
+ "device-activity"
20941
+ ]);
20925
20942
  /**
20926
20943
  * List of motion sources active on a camera. Empty array is valid:
20927
20944
  * "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-hap",
3
- "version": "1.2.91",
3
+ "version": "1.2.92",
4
4
  "description": "HomeKit (HAP) exporter for CamStack devices. Publishes each exposed device as its own HomeKit accessory: cameras and doorbells with SRTP streaming, HomeKit Secure Video, motion, two-way audio, PTZ and battery; switches, lights, locks and sensors through a capability→service table.",
5
5
  "keywords": [
6
6
  "camstack",