@camstack/addon-matter-broker 0.2.79 → 0.2.80

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.
package/dist/addon.js CHANGED
@@ -20579,8 +20579,25 @@ var occupancyRecheckFramesField = {
20579
20579
  * (analyzer attaches detected `regions[]`; onboard does not — the
20580
20580
  * camera typically only reports a binary signal plus an optional
20581
20581
  * channel/AI class which lives in dedicated event channels).
20582
- */
20583
- var MotionSourceEnum = _enum(["onboard", "analyzer"]);
20582
+ *
20583
+ * - `onboard` — the camera's firmware said something moved.
20584
+ * - `analyzer` — this runner's frame-diff said so, and attaches `regions[]`.
20585
+ * - `device-activity` — the DEVICE said it is doing its job: the
20586
+ * `recording-signal` LEVEL the same device raises for the recorder
20587
+ * ([D380](../../../../docs/decisions/adr-0380-a-device-decided-recording-is-a-mode-with-no-schedule-seeded-once.md)),
20588
+ * republished as a motion source. It attaches **nothing** — no regions, no
20589
+ * class: the only fact it carries is that the device is active, and a robot
20590
+ * vacuum that is itself the moving object has no region worth sending. It is
20591
+ * a LEVEL, so unlike `onboard` it has a real falling edge, and unlike
20592
+ * `analyzer` it must not open the frame-diff side-channel — the runner's
20593
+ * `handleOnboardMotionAnalyzer` gate is `source === 'onboard'` and stays that
20594
+ * way ([D392](../../../../docs/decisions/adr-0392-a-device-that-says-it-is-working-is-a-motion-source-of-its-own.md)).
20595
+ */
20596
+ var MotionSourceEnum = _enum([
20597
+ "onboard",
20598
+ "analyzer",
20599
+ "device-activity"
20600
+ ]);
20584
20601
  /**
20585
20602
  * List of motion sources active on a camera. Empty array is valid:
20586
20603
  * "no source" — happens for battery cams without firmware motion when
package/dist/addon.mjs CHANGED
@@ -20577,8 +20577,25 @@ var occupancyRecheckFramesField = {
20577
20577
  * (analyzer attaches detected `regions[]`; onboard does not — the
20578
20578
  * camera typically only reports a binary signal plus an optional
20579
20579
  * channel/AI class which lives in dedicated event channels).
20580
- */
20581
- var MotionSourceEnum = _enum(["onboard", "analyzer"]);
20580
+ *
20581
+ * - `onboard` — the camera's firmware said something moved.
20582
+ * - `analyzer` — this runner's frame-diff said so, and attaches `regions[]`.
20583
+ * - `device-activity` — the DEVICE said it is doing its job: the
20584
+ * `recording-signal` LEVEL the same device raises for the recorder
20585
+ * ([D380](../../../../docs/decisions/adr-0380-a-device-decided-recording-is-a-mode-with-no-schedule-seeded-once.md)),
20586
+ * republished as a motion source. It attaches **nothing** — no regions, no
20587
+ * class: the only fact it carries is that the device is active, and a robot
20588
+ * vacuum that is itself the moving object has no region worth sending. It is
20589
+ * a LEVEL, so unlike `onboard` it has a real falling edge, and unlike
20590
+ * `analyzer` it must not open the frame-diff side-channel — the runner's
20591
+ * `handleOnboardMotionAnalyzer` gate is `source === 'onboard'` and stays that
20592
+ * way ([D392](../../../../docs/decisions/adr-0392-a-device-that-says-it-is-working-is-a-motion-source-of-its-own.md)).
20593
+ */
20594
+ var MotionSourceEnum = _enum([
20595
+ "onboard",
20596
+ "analyzer",
20597
+ "device-activity"
20598
+ ]);
20582
20599
  /**
20583
20600
  * List of motion sources active on a camera. Empty array is valid:
20584
20601
  * "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-matter-broker",
3
- "version": "0.2.79",
3
+ "version": "0.2.80",
4
4
  "description": "Matter broker addon for CamStack — owns a Matter fabric (commissioning + the long-lived controller) via the matter.js controller and brokers commissioned Matter nodes into CamStack",
5
5
  "keywords": [
6
6
  "camstack",