@camstack/addon-notifiers 1.2.84 → 1.2.85

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
@@ -20319,8 +20319,25 @@ var occupancyRecheckFramesField = {
20319
20319
  * (analyzer attaches detected `regions[]`; onboard does not — the
20320
20320
  * camera typically only reports a binary signal plus an optional
20321
20321
  * channel/AI class which lives in dedicated event channels).
20322
- */
20323
- var MotionSourceEnum = _enum(["onboard", "analyzer"]);
20322
+ *
20323
+ * - `onboard` — the camera's firmware said something moved.
20324
+ * - `analyzer` — this runner's frame-diff said so, and attaches `regions[]`.
20325
+ * - `device-activity` — the DEVICE said it is doing its job: the
20326
+ * `recording-signal` LEVEL the same device raises for the recorder
20327
+ * ([D380](../../../../docs/decisions/adr-0380-a-device-decided-recording-is-a-mode-with-no-schedule-seeded-once.md)),
20328
+ * republished as a motion source. It attaches **nothing** — no regions, no
20329
+ * class: the only fact it carries is that the device is active, and a robot
20330
+ * vacuum that is itself the moving object has no region worth sending. It is
20331
+ * a LEVEL, so unlike `onboard` it has a real falling edge, and unlike
20332
+ * `analyzer` it must not open the frame-diff side-channel — the runner's
20333
+ * `handleOnboardMotionAnalyzer` gate is `source === 'onboard'` and stays that
20334
+ * way ([D392](../../../../docs/decisions/adr-0392-a-device-that-says-it-is-working-is-a-motion-source-of-its-own.md)).
20335
+ */
20336
+ var MotionSourceEnum = _enum([
20337
+ "onboard",
20338
+ "analyzer",
20339
+ "device-activity"
20340
+ ]);
20324
20341
  /**
20325
20342
  * List of motion sources active on a camera. Empty array is valid:
20326
20343
  * "no source" — happens for battery cams without firmware motion when
package/dist/addon.mjs CHANGED
@@ -20292,8 +20292,25 @@ var occupancyRecheckFramesField = {
20292
20292
  * (analyzer attaches detected `regions[]`; onboard does not — the
20293
20293
  * camera typically only reports a binary signal plus an optional
20294
20294
  * channel/AI class which lives in dedicated event channels).
20295
- */
20296
- var MotionSourceEnum = _enum(["onboard", "analyzer"]);
20295
+ *
20296
+ * - `onboard` — the camera's firmware said something moved.
20297
+ * - `analyzer` — this runner's frame-diff said so, and attaches `regions[]`.
20298
+ * - `device-activity` — the DEVICE said it is doing its job: the
20299
+ * `recording-signal` LEVEL the same device raises for the recorder
20300
+ * ([D380](../../../../docs/decisions/adr-0380-a-device-decided-recording-is-a-mode-with-no-schedule-seeded-once.md)),
20301
+ * republished as a motion source. It attaches **nothing** — no regions, no
20302
+ * class: the only fact it carries is that the device is active, and a robot
20303
+ * vacuum that is itself the moving object has no region worth sending. It is
20304
+ * a LEVEL, so unlike `onboard` it has a real falling edge, and unlike
20305
+ * `analyzer` it must not open the frame-diff side-channel — the runner's
20306
+ * `handleOnboardMotionAnalyzer` gate is `source === 'onboard'` and stays that
20307
+ * way ([D392](../../../../docs/decisions/adr-0392-a-device-that-says-it-is-working-is-a-motion-source-of-its-own.md)).
20308
+ */
20309
+ var MotionSourceEnum = _enum([
20310
+ "onboard",
20311
+ "analyzer",
20312
+ "device-activity"
20313
+ ]);
20297
20314
  /**
20298
20315
  * List of motion sources active on a camera. Empty array is valid:
20299
20316
  * "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-notifiers",
3
- "version": "1.2.84",
3
+ "version": "1.2.85",
4
4
  "description": "System notifiers addon for CamStack — a `notification-output` collection provider hosting per-kind notifier adapters (ntfy, pushover, gotify, telegram, discord, webhook, zentik).",
5
5
  "keywords": [
6
6
  "camstack",