@camstack/addon-provider-reolink 1.2.22 → 1.2.24

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.
Files changed (3) hide show
  1. package/dist/addon.js +820 -68
  2. package/dist/addon.mjs +820 -68
  3. package/package.json +1 -1
package/dist/addon.mjs CHANGED
@@ -7239,8 +7239,31 @@ var AdoptionJobSchema = object({
7239
7239
  error: string().nullable()
7240
7240
  });
7241
7241
  /**
7242
- * Per-camera FUNCTION SWITCHES — the one coherent on/off surface over the
7243
- * pipeline functions an operator thinks in terms of.
7242
+ * Per-camera FUNCTION SWITCHES.
7243
+ *
7244
+ * ## The aggregate group is being withdrawn — the BADGE is not (D113)
7245
+ *
7246
+ * This file shipped as "the one coherent on/off surface over the pipeline
7247
+ * functions an operator thinks in terms of". The operator's verdict on
7248
+ * 2026-08-12 was that the coherent surface bought complexity and no clarity:
7249
+ * every function already had a settings page of its own, and a second place to
7250
+ * turn it off is a second place to look. Each switch is going back to its own
7251
+ * component's original options — detection to the detection-pipeline wrapper
7252
+ * binding, audio analysis to its own, recording to `RecordingConfig.enabled`
7253
+ * (which was always first-class; the switch was a veneer over
7254
+ * `recording.setDeviceConfig`), notifications to a notification-center
7255
+ * per-device setting, the two camera planes to their own components.
7256
+ *
7257
+ * What survives is {@link composeSwitchedOff}: `CameraStatus.switchedOff`, the
7258
+ * thing that lets a status surface say DISABLED instead of BROKEN, recomposed
7259
+ * straight from the authorities with no group in the middle. That rule was
7260
+ * never about a control panel.
7261
+ *
7262
+ * Everything else here — {@link CAMERA_SWITCH_CATALOG}, {@link CameraSwitch},
7263
+ * {@link deriveCameraSwitches}, the `pipelineOrchestrator.getCameraSwitches` /
7264
+ * `setCameraSwitch` pair — is a COMPATIBILITY surface for as long as deployed
7265
+ * viewers (v1.0.305) and the admin UI still call it. It is deleted when they
7266
+ * stop; nothing new may be built on it.
7244
7267
  *
7245
7268
  * ## This file adds no state
7246
7269
  *
@@ -7591,7 +7614,15 @@ var RecordingConfigSchema = object({
7591
7614
  * Each completed/failed run also lands one durable ops-log row on its owning
7592
7615
  * addon surface.
7593
7616
  */
7617
+ /**
7618
+ * `queued` exists because the recorder mover is SINGLE-FLIGHT and an operator
7619
+ * rebalance enqueues one job per (camera, profile). Refusing the second job —
7620
+ * what the engine did before — turned a fifteen-camera rebalance into fifteen
7621
+ * manual retries. Queued jobs run FIFO; a queued job that is cancelled never
7622
+ * runs at all.
7623
+ */
7594
7624
  var RelocateJobStateSchema = _enum([
7625
+ "queued",
7595
7626
  "running",
7596
7627
  "done",
7597
7628
  "failed",
@@ -7626,6 +7657,15 @@ var RelocateFootageInputSchema = object({
7626
7657
  /** Limits relocation to the logical profile class. Omit only for the
7627
7658
  * pre-orchestration compatibility path. */
7628
7659
  footageClass: RelocateFootageClassSchema.optional(),
7660
+ /** Scope the move to ONE camera. Absent = every camera on the source, which
7661
+ * is what a whole-disk drain means. The rebalance path always sets it: its
7662
+ * unit is a (camera, profile) pile, not a disk. */
7663
+ deviceId: number().int().optional(),
7664
+ /** Scope the move to specific segment profiles (`high` / `mid` / `low`).
7665
+ * Finer than `footageClass`, which cannot separate high from mid — and the
7666
+ * placement plan assigns those two independently, so a rebalance that could
7667
+ * only say "recordings" would move footage the plan never asked to move. */
7668
+ profiles: array(string()).optional(),
7629
7669
  /** Copy throttle in MB/s (default 40) — the drain is a background chore,
7630
7670
  * never allowed to starve live writers. */
7631
7671
  throttleMbps: number().min(1).max(1e3).optional()
@@ -7761,6 +7801,21 @@ var StorageLocationSchema = object({
7761
7801
  nodeId: string().optional(),
7762
7802
  isDefault: boolean().default(false),
7763
7803
  isSystem: boolean().default(false),
7804
+ /**
7805
+ * Operator opt-in: whether consumers that BALANCE across several locations
7806
+ * of a type may write here. Recordings reads it today; event media and
7807
+ * backups are the next consumers, which is why the flag lives on the
7808
+ * location rather than in any one addon's store — nothing has to be
7809
+ * extended to add the next consumer.
7810
+ *
7811
+ * OPTIONAL, and ABSENT MEANS ACTIVE. Every location persisted before the
7812
+ * flag existed reads back with no flag and keeps working exactly as before;
7813
+ * that is the whole compat story, and it is why no migration ships with it.
7814
+ * A newly CREATED sibling is stamped `false` by the orchestrator (creating a
7815
+ * disk must not silently start writing to it); the default of a type is
7816
+ * always stamped `true`.
7817
+ */
7818
+ enabled: boolean().optional(),
7764
7819
  /** COMPUTED at read time by the orchestrator (statfs of the backing volume
7765
7820
  * for node-local locations it can reach) — never persisted, absent when the
7766
7821
  * volume is remote/unreachable. The single capacity truth every UI reads. */
@@ -12500,7 +12555,8 @@ method(object({
12500
12555
  }), EmbeddingResultSchema), method(object({ text: string() }), EmbeddingResultSchema), method(_void(), EmbeddingInfoSchema);
12501
12556
  /**
12502
12557
  * filesystem-browse — per-node capability for browsing the node's local
12503
- * filesystem, sandboxed to operator-configured allowed roots. Used by the
12558
+ * filesystem. Reads are unconfined (whole filesystem, from `/` down); WRITES
12559
+ * are sandboxed to operator-configured allowed roots (D115). Used by the
12504
12560
  * admin "Add filesystem location" flow to pick a node + path. `mode:'per-node'`
12505
12561
  * (one provider per node); the hub calls it with `{nodeId}` so the codegen
12506
12562
  * routes to that exact node (default `nodeIdMode:'routing'`).
@@ -14341,6 +14397,13 @@ var MaskGridDimsSchema = object({
14341
14397
  * `package-event` are pure trigger kinds (no urgency dimension). Extending
14342
14398
  * this one field keeps the schema additive — a rule still declares exactly
14343
14399
  * one trigger.
14400
+ *
14401
+ * AUDIO rules add no member here, for the reason occupancy added none: the
14402
+ * enum is mirrored by hand in the viewer (`scripts/check-viewer-condition-
14403
+ * mirror.ts` fails the build on a member the app cannot render) and every
14404
+ * member costs a release train. A sustained-sound rule is therefore an
14405
+ * `immediate` rule carrying {@link NcConditions.audio} — the condition is the
14406
+ * trigger discriminator, exactly as `occupancy` is on `device-event`.
14344
14407
  */
14345
14408
  var NcDeliverySchema = _enum([
14346
14409
  "immediate",
@@ -14355,15 +14418,32 @@ var NcDeliverySchema = _enum([
14355
14418
  * depend on a provider's raw event name or payload shape.
14356
14419
  */
14357
14420
  var NcSystemEventKindSchema = _enum([
14358
- "camera-online",
14359
- "camera-offline",
14421
+ "device-online",
14422
+ "device-offline",
14423
+ "device-disabled",
14424
+ "device-enabled",
14360
14425
  "stream-online",
14361
14426
  "stream-offline",
14362
14427
  "node-online",
14363
14428
  "node-offline",
14364
14429
  "addon-update-available",
14365
- "server-update-available"
14430
+ "server-update-available",
14431
+ "alarm-triggered",
14432
+ "alarm-armed",
14433
+ "alarm-disarmed",
14434
+ "camera-online",
14435
+ "camera-offline",
14436
+ "camera-disabled",
14437
+ "camera-enabled"
14438
+ ]);
14439
+ /** The legacy tail of {@link NcSystemEventKindSchema} — see its docblock. */
14440
+ var NC_LEGACY_SYSTEM_EVENT_KINDS = new Set([
14441
+ "camera-online",
14442
+ "camera-offline",
14443
+ "camera-disabled",
14444
+ "camera-enabled"
14366
14445
  ]);
14446
+ NcSystemEventKindSchema.options.filter((kind) => !NC_LEGACY_SYSTEM_EVENT_KINDS.has(kind));
14367
14447
  /**
14368
14448
  * One coherent system-event condition. `kinds` is the required opt-in safety
14369
14449
  * gate; the remaining lists are optional narrowing filters relevant to the
@@ -14372,6 +14452,18 @@ var NcSystemEventKindSchema = _enum([
14372
14452
  var NcSystemEventConditionSchema = object({
14373
14453
  kinds: array(NcSystemEventKindSchema).min(1),
14374
14454
  deviceIds: array(number().int()).min(1).optional(),
14455
+ /**
14456
+ * Narrow a `device-*` kind to these device TYPES (`DeviceType` values —
14457
+ * `camera`, `switch`, `sensor`, `container`, …). Absent = every type, which
14458
+ * is what a liveness rule means when nobody said otherwise.
14459
+ *
14460
+ * This is where "only my cameras" is expressed, and it lives on the rule for
14461
+ * one reason: the intake cannot know which devices this household cares
14462
+ * about, and a producer-side filter is one no operator can change. Fails
14463
+ * CLOSED — a subject whose device type is unknown (an id the device mirror
14464
+ * does not carry) matches no `deviceTypes` list.
14465
+ */
14466
+ deviceTypes: array(string().min(1)).min(1).optional(),
14375
14467
  nodeIds: array(string().min(1)).min(1).optional(),
14376
14468
  packageNames: array(string().min(1)).min(1).optional()
14377
14469
  });
@@ -14422,6 +14514,47 @@ var NcOccupancyConditionSchema = object({
14422
14514
  sustainSeconds: number().int().min(0).max(3600).default(15)
14423
14515
  });
14424
14516
  /**
14517
+ * Audio condition (IMMEDIATE trigger) — a rule on SOUND, not on a picture.
14518
+ *
14519
+ * Operator-approved vocabulary (2026-08-12, option A — the same one the
14520
+ * reference notifier uses, so an operator moving between them re-uses what
14521
+ * they already know): a rule matches when, over a sampling window of
14522
+ * `samplingSeconds`, at least `hitPercent`% of the audio samples in that
14523
+ * window are HITS. A sample is a hit when it satisfies BOTH present filters:
14524
+ *
14525
+ * - `dbThreshold` — its level is at or above this many dBFS (see
14526
+ * {@link NC_AUDIO_DBFS_FLOOR}: negative-going, `0` = full scale);
14527
+ * - `labels` — the classifier put at least one of these labels on it.
14528
+ *
14529
+ * Both are OPTIONAL and independent, which is the point of the shape: a
14530
+ * loudness rule ("something loud at 3am") needs no model to be right, and a
14531
+ * label rule ("a dog barked") needs no threshold. **Fail-closed when NEITHER
14532
+ * is given** — a window in which every sample is trivially a hit would fire on
14533
+ * silence, so the engine refuses such a condition rather than notifying on
14534
+ * nothing (the schema cannot express "at least one of" without becoming a
14535
+ * ZodEffects the cap path would have to special-case).
14536
+ *
14537
+ * `hitPercent` is over the samples the window actually HOLDS, and the window
14538
+ * must be FULL before it can match — a window that has been open for two
14539
+ * seconds of its ten is 100% of nothing, and firing on it would make
14540
+ * `samplingSeconds` decorative.
14541
+ *
14542
+ * Labels are the audio macro classes (`AUDIO_MACRO_LABELS` / the NC taxonomy's
14543
+ * `audio-*` ids). Both spellings are accepted — the matcher normalizes the
14544
+ * `audio-` prefix away on both sides, so a picker that offers taxonomy ids and
14545
+ * an operator who typed `dog` mean the same thing.
14546
+ */
14547
+ var NcAudioConditionSchema = object({
14548
+ /** Audio macro labels; absent = any sound (level-only rule). */
14549
+ labels: array(string().min(1)).min(1).optional(),
14550
+ /** Level floor in dBFS (negative-going, `0` = full scale); absent = any level. */
14551
+ dbThreshold: number().min(-96).max(0).optional(),
14552
+ /** Percentage of the window's samples that must be hits (1–100). */
14553
+ hitPercent: number().int().min(1).max(100).default(60),
14554
+ /** Length of the sampling window in seconds. */
14555
+ samplingSeconds: number().int().min(1).max(300).default(10)
14556
+ });
14557
+ /**
14425
14558
  * Which zone-crossing DIRECTION a rule accepts (`ObjectEvent.zoneCrossing`).
14426
14559
  *
14427
14560
  * The values are not symmetric, and deliberately so — the absent value has to
@@ -14694,7 +14827,33 @@ var NcConditionsSchema = object({
14694
14827
  * threshold and holds for `sustainSeconds`. Fail-closed on missing
14695
14828
  * substrate (no snapshot / missing zone). See {@link NcOccupancyCondition}.
14696
14829
  */
14697
- occupancy: NcOccupancyConditionSchema.optional()
14830
+ occupancy: NcOccupancyConditionSchema.optional(),
14831
+ /**
14832
+ * IMMEDIATE only. Sustained-sound matcher — `hitPercent` of the samples in a
14833
+ * `samplingSeconds` window clear the optional `dbThreshold` and carry one of
14834
+ * the optional `labels`. Fail-closed on missing substrate (no audio samples,
14835
+ * a window that is not full yet, neither filter given). See
14836
+ * {@link NcAudioCondition}.
14837
+ *
14838
+ * Presence of this key is what makes a rule an AUDIO rule: the engine fires
14839
+ * it ONLY on a confirmed audio window, and a rule carrying it never fires on
14840
+ * a detection, a track or a device event (the same fail-closed pairing
14841
+ * `occupancy` has with the `device-event` trigger). That is how audio labels
14842
+ * leave `classes`: an audio rule names its sounds HERE, and the legacy path
14843
+ * (an `immediate` rule naming an `audio-*` class, one notification per
14844
+ * classified sample) stays exactly as it was for rules that already use it.
14845
+ *
14846
+ * NOT in {@link NC_CONDITION_CATALOG} yet, and that is the sequencing rule
14847
+ * rather than an oversight: the viewer mirrors the descriptor enums BY HAND
14848
+ * (`camstack/src/data/notification-center.ts`, guarded by
14849
+ * `scripts/check-viewer-condition-mirror.ts`) and its rule editor STRIPS the
14850
+ * condition fields it does not know when a rule is saved from the phone.
14851
+ * Publishing an editor for a condition the app cannot round-trip is how an
14852
+ * operator loses a rule's conditions by opening it — so the descriptor, the
14853
+ * admin widget and the viewer mirror land together (P2 + P3), and only then
14854
+ * does an audio rule become authorable.
14855
+ */
14856
+ audio: NcAudioConditionSchema.optional()
14698
14857
  });
14699
14858
  /** One delivery target: a `notification-output` Target ref + passthrough params. */
14700
14859
  var NcRuleTargetSchema = object({
@@ -14808,6 +14967,73 @@ var NcThrottleSchema = object({
14808
14967
  */
14809
14968
  granularity: NcThrottleGranularitySchema.optional()
14810
14969
  });
14970
+ /**
14971
+ * How long the confirm gate may hold ONE notification, and how big the picture
14972
+ * it judges may be.
14973
+ *
14974
+ * The clamp is the product decision, not a coincidence of the model: p50 was
14975
+ * 4.9 s warm and 15.3 s cold against qwen3-vl-8b, and a notification that
14976
+ * arrives after the visitor has gone is not a notification. 448 px was enough
14977
+ * to score 16/16 on the operator's parking scenario — bigger costs latency and
14978
+ * tokens for pixels the model pools away.
14979
+ */
14980
+ var NC_CONFIRM_MIN_TIMEOUT_MS = 1e3;
14981
+ var NC_CONFIRM_MAX_TIMEOUT_MS = 2e4;
14982
+ var NC_CONFIRM_DEFAULT_TIMEOUT_MS = 8e3;
14983
+ /** Comparison the model's COUNT must satisfy for the notification to fire. */
14984
+ var NcConfirmExpectSchema = object({
14985
+ op: _enum([
14986
+ ">=",
14987
+ ">",
14988
+ "<=",
14989
+ "<",
14990
+ "=="
14991
+ ]),
14992
+ count: number().int().min(0).max(1e3)
14993
+ });
14994
+ /**
14995
+ * AI CONFIRM — a vision model looks at the picture this notification is about
14996
+ * to ship and says whether it agrees with the rule.
14997
+ *
14998
+ * It runs AFTER the attachments resolve, deliberately: the crop JUDGED is the
14999
+ * crop SHIPPED (D52). A verdict about a different pixel rectangle than the one
15000
+ * on the operator's phone is not a verdict about this notification.
15001
+ *
15002
+ * FAIL-OPEN is the only safe default. A gate that cannot reach its model, or
15003
+ * whose model is cold, must not silence a camera — so `onTimeout: 'fire'` is
15004
+ * the default and every fail-open is COUNTED, because a gate that always fails
15005
+ * open looks in the log exactly like a gate that works.
15006
+ *
15007
+ * Every field is `.optional()` rather than relied on as a Zod default at the
15008
+ * runtime seam: a Zod default does NOT run on the addon→addon cap path (three
15009
+ * production failures in one day), so the gate reads absent as the constant
15010
+ * above rather than trusting a parse it may never have seen.
15011
+ */
15012
+ var NcConfirmSchema = object({
15013
+ /** Off unless asked for. An absent `confirm` and `enabled:false` are the
15014
+ * same thing, and both mean "deliver exactly as before". */
15015
+ enabled: boolean().default(false),
15016
+ /** Explicit vision profile; absent = the `purpose:'vision'` cluster default. */
15017
+ profileId: string().optional(),
15018
+ /**
15019
+ * The operator's question, in his own words. Absent = a question derived
15020
+ * from the rule (its class and its expectation).
15021
+ *
15022
+ * NEVER composed with text READ OUT OF THE FRAME. The model reads OSD
15023
+ * banners, signage and plates as instructions if you let them reach the
15024
+ * prompt — proven live — so the authoritative contract stays in the system
15025
+ * turn and only rule-authored words land here.
15026
+ */
15027
+ prompt: string().max(1e3).optional(),
15028
+ /** Fire only when the model's count satisfies this. Absent = the model's
15029
+ * own boolean verdict decides. */
15030
+ expect: NcConfirmExpectSchema.optional(),
15031
+ timeoutMs: number().int().min(NC_CONFIRM_MIN_TIMEOUT_MS).max(NC_CONFIRM_MAX_TIMEOUT_MS).default(NC_CONFIRM_DEFAULT_TIMEOUT_MS),
15032
+ /** What a timeout / unreachable model MEANS. `fire` (default) = fail-open. */
15033
+ onTimeout: _enum(["fire", "suppress"]).default("fire"),
15034
+ /** Longest edge the judged image is downscaled to before it is sent. */
15035
+ maxImagePx: number().int().min(64).max(2048).default(448)
15036
+ });
14811
15037
  /** Client-supplied rule fields (server stamps id/createdBy/createdAt/updatedAt). */
14812
15038
  var NcRuleInputSchema = object({
14813
15039
  name: string().min(1).max(200),
@@ -14868,7 +15094,13 @@ var NcRuleInputSchema = object({
14868
15094
  * `{ cap: 'alarm-panel', method: 'arm', args: { mode: 'away' } }`, the same
14869
15095
  * shape as every other actuation.
14870
15096
  */
14871
- actions: NcRuleActionsSchema.optional()
15097
+ actions: NcRuleActionsSchema.optional(),
15098
+ /**
15099
+ * AI CONFIRM — see {@link NcConfirmSchema}. `.optional()`, never defaulted:
15100
+ * a rule that predates the gate must keep delivering byte-for-byte as it
15101
+ * did, and absent is the only way to say that without a migration.
15102
+ */
15103
+ confirm: NcConfirmSchema.optional()
14872
15104
  });
14873
15105
  /**
14874
15106
  * Partial patch for `updateRule` — any subset of the input fields, plus the
@@ -14879,7 +15111,37 @@ var NcRuleInputSchema = object({
14879
15111
  * still flow through `nc.setRuleTargetEnabled` (owner-checked), never a raw
14880
15112
  * `updateRule` patch.
14881
15113
  */
14882
- var NcRulePatchSchema = NcRuleInputSchema.partial().extend({ disabledTargetIds: array(string()).optional() });
15114
+ var NcRulePatchSchema = NcRuleInputSchema.partial().extend({
15115
+ disabledTargetIds: array(string()).optional(),
15116
+ /**
15117
+ * `.partial()` DOES NOT REMOVE A FIELD'S `.default()`.
15118
+ *
15119
+ * It makes the key optional to SUPPLY; the parse still materialises the
15120
+ * default when the key is absent. And `NcRuleStore.update` merges with
15121
+ * `{ ...existing, ...patch }`, so a materialised key OVERWRITES the stored
15122
+ * one — which made every partial edit destructive:
15123
+ *
15124
+ * nc.updateRule({ throttle }) → conditions reset to `{}`
15125
+ * nc.setRuleTargetEnabled(...) → conditions reset to `{}`
15126
+ * setEnabled(ruleId, false) → conditions reset to `{}`
15127
+ *
15128
+ * A rule scoped to one camera and one zone silently became a rule that
15129
+ * matches EVERY event on EVERY camera, and lost its `media` policy
15130
+ * (zoneCrop / gif / clip / frame) and its `priority` at the same time. Seen
15131
+ * live on 2026-08-12: a rule scoped to device 617 fired on 590 and 615
15132
+ * within a minute of a two-field patch.
15133
+ *
15134
+ * So every defaulted field is re-declared here WITHOUT its default. The
15135
+ * inner defaults still apply when the caller DOES send the key — `{}` for
15136
+ * conditions remains a real instruction ("clear them") — and only the
15137
+ * absent key is now genuinely absent.
15138
+ */
15139
+ enabled: boolean().optional(),
15140
+ conditions: NcConditionsSchema.optional(),
15141
+ media: NcMediaPolicySchema.optional(),
15142
+ throttle: NcThrottleSchema.optional(),
15143
+ priority: number().int().min(1).max(5).optional()
15144
+ });
14883
15145
  /** A persisted rule. */
14884
15146
  var NcRuleSchema = NcRuleInputSchema.extend({
14885
15147
  id: string(),
@@ -15180,6 +15442,25 @@ var NcAlarmSettingsPatchSchema = NcAlarmSettingsSchema.partial();
15180
15442
  * Never authored, never stored — see `alarm-mode-coverage.ts` for why a stored
15181
15443
  * copy would lie the first time a rule is disabled.
15182
15444
  */
15445
+ /**
15446
+ * Why a device a mode NAMES is nonetheless not armed by it.
15447
+ *
15448
+ * Each value is an existing authority, never a new flag (D62): `muted` is the
15449
+ * per-camera notification switch the Notification Center already owns,
15450
+ * `detection-off` is the device's own detection binding being inactive, and
15451
+ * `offline` is the device manager's liveness. A fourth reason would mean a
15452
+ * fourth authority, and inventing one here is how a panel starts disagreeing
15453
+ * with the switches the operator actually used.
15454
+ */
15455
+ var NcAlarmSkipReasonSchema = _enum([
15456
+ "muted",
15457
+ "detection-off",
15458
+ "offline"
15459
+ ]);
15460
+ var NcAlarmSkippedDeviceSchema = object({
15461
+ deviceId: number().int(),
15462
+ reason: NcAlarmSkipReasonSchema
15463
+ });
15183
15464
  var NcAlarmModeCoverageSchema = object({
15184
15465
  mode: AlarmArmModeSchema,
15185
15466
  /** Enabled rules gated on `armed_<mode>`. Zero means the mode does nothing. */
@@ -15187,7 +15468,18 @@ var NcAlarmModeCoverageSchema = object({
15187
15468
  /** At least one covering rule has no device scope, so the mode covers all. */
15188
15469
  allDevices: boolean(),
15189
15470
  /** Ids named by the covering rules. A SUBSET when `allDevices` is true. */
15190
- deviceIds: array(number().int())
15471
+ deviceIds: array(number().int()),
15472
+ /**
15473
+ * Devices this mode NAMES but cannot actually arm, each with the switch that
15474
+ * excludes it.
15475
+ *
15476
+ * "Away armed — 12 cameras" is a promise, and a muted camera among those
15477
+ * twelve makes it false in exactly the way nobody notices until an incident.
15478
+ * Defaulted to `[]` so a coverage answer computed before this field existed
15479
+ * still parses as "nothing known to be skipped" rather than failing the whole
15480
+ * alarm tab.
15481
+ */
15482
+ skippedDevices: array(NcAlarmSkippedDeviceSchema).default([])
15191
15483
  });
15192
15484
  var NcAlarmConfigSchema = object({
15193
15485
  /**
@@ -18019,9 +18311,16 @@ var CameraStatusSchema = object({
18019
18311
  audio: CameraAudioStatusSchema.nullable(),
18020
18312
  recording: CameraRecordingStatusSchema.nullable(),
18021
18313
  /**
18022
- * Per-camera function switches an OPERATOR has turned off
18314
+ * Per-camera functions an OPERATOR has turned off
18023
18315
  * ([D61](../../../../docs/decisions/adr-0067.md)).
18024
18316
  *
18317
+ * Composed from the AUTHORITIES themselves — the wrapper bindings,
18318
+ * `RecordingConfig.enabled`, the notification mute, the broker's audio
18319
+ * policy, the camera's own microphone — via `composeSwitchedOff`, not from
18320
+ * the deprecated `getCameraSwitches` group ([D113](../../../../docs/decisions/adr-0113.md)).
18321
+ * The badge outlives the control panel: the panel was a convenience, this is
18322
+ * the difference between a camera being off and a camera being dead.
18323
+ *
18025
18324
  * This is the difference between DISABLED and BROKEN. A camera whose
18026
18325
  * `detection` block reports zero fps and whose `switchedOff` contains
18027
18326
  * `'object-detection'` was switched off by a person; the same camera with an
@@ -18628,24 +18927,28 @@ var snapshotCapability = {
18628
18927
  *
18629
18928
  * `getSnapshotOverview` is cache-only by contract: it answers from whatever
18630
18929
  * the wrapper happens to hold and never captures. Under D93 the client
18631
- * versions its image URL on that answer, and an image REQUEST is what enrols
18632
- * a camera in the keep-warm loop. Both of those are satisfiable by the
18633
- * client's own image cache — `expo-image` is URL-keyed and never revalidates
18634
- * — so a URL painted in a previous session comes off disk with no network,
18635
- * no enrolment, and nothing warming. Measured on the live hub: reopening
18636
- * after two minutes idle painted 15 of 16 tiles at **168 s old** with zero
18637
- * HTTP requests, and the fleet only recovered because a later poll happened
18638
- * to observe a different identity.
18930
+ * versions its image URL on that answer, and an image REQUEST was the only
18931
+ * demand signal. Both of those are satisfiable by the client's own image
18932
+ * cache — `expo-image` is URL-keyed and never revalidates — so a URL painted
18933
+ * in a previous session comes off disk with no network, no demand, and no
18934
+ * capture. Measured on the live hub: reopening after two minutes idle
18935
+ * painted 15 of 16 tiles at **168 s old** with zero HTTP requests, and the
18936
+ * fleet only recovered because a later poll happened to observe a different
18937
+ * identity.
18639
18938
  *
18640
18939
  * ## The two properties that fix it
18641
18940
  *
18642
18941
  * **It is an RPC, so no client cache can answer it.** The demand signal
18643
- * always reaches the wrapper. This method therefore MAY create keep-warm
18644
- * subscriptions, where `getSnapshotOverview` must never (D93) — the
18645
- * distinction is not "one is newer" but that the overview poll is app-wide
18646
- * (a creating overview would warm every camera on the install) while this is
18647
- * called by a rendered surface naming the tiles it is actually painting, at
18648
- * the width it is painting them.
18942
+ * always reaches the wrapper. This method therefore CAPTURES, where
18943
+ * `getSnapshotOverview` must never (D93) — the distinction is not "one is
18944
+ * newer" but that the overview poll is app-wide (a capturing overview would
18945
+ * dial every camera on the install) while this is called by a rendered
18946
+ * surface naming the tiles it is actually painting, at the width it is
18947
+ * painting them.
18948
+ *
18949
+ * Since 2026-08-11 this is the ONLY thing that refreshes a snapshot: the
18950
+ * server-side keep-warm loop was removed (operator directive — on-demand,
18951
+ * always), so a camera nobody is looking at costs nothing at all.
18649
18952
  *
18650
18953
  * **It waits, briefly and boundedly, for the capture it triggered.** The
18651
18954
  * returned `capturedAt` is the frame the link will serve, not the frame the
@@ -24992,7 +25295,19 @@ var RecordingManifestSchema = object({
24992
25295
  * profiles/subtrees/locations on this node). */
24993
25296
  var RecordingDeviceUsageSchema = object({
24994
25297
  deviceId: number(),
24995
- usedBytes: number()
25298
+ usedBytes: number(),
25299
+ /**
25300
+ * Start of this camera's OLDEST indexed segment, across every profile and
25301
+ * location — the "Oldest footage" column in Recordings → Storage, and the
25302
+ * only honest answer to "is retention actually holding?" per camera.
25303
+ *
25304
+ * `null` = the camera has no footage. OPTIONAL because a recorder that
25305
+ * predates this field omits it entirely, and a hub whose types carry the
25306
+ * field must keep validating that older provider's payload: the framework
25307
+ * (types) and the addon ship on different trains, and the addon is usually
25308
+ * the later of the two.
25309
+ */
25310
+ oldestMs: number().nullable().optional()
24996
25311
  });
24997
25312
  /** Recording storage usage + capacity for one storage location. */
24998
25313
  var RecordingLocationUsageSchema = object({
@@ -25020,6 +25335,57 @@ var RecordingStorageUsageSchema = object({
25020
25335
  locations: array(RecordingLocationUsageSchema)
25021
25336
  });
25022
25337
  /**
25338
+ * The OPERATOR-ARMED half of multi-location recordings (D116).
25339
+ *
25340
+ * The placement plan decides where NEW writes go and moves nothing. A rebalance
25341
+ * is the operator asking for the EXISTING archive to be brought into line with
25342
+ * that plan: one relocate job per (camera, profile) pile that sits on the wrong
25343
+ * location, run FIFO behind the single-flight mover.
25344
+ *
25345
+ * `plan…` and `start…` return the SAME shape deliberately — what the operator
25346
+ * confirms is exactly what gets enqueued, and `jobIds` is the only difference
25347
+ * (empty on the plan).
25348
+ */
25349
+ var RecordingRebalanceMoveSchema = object({
25350
+ deviceId: number(),
25351
+ profile: string(),
25352
+ fromLocationId: string(),
25353
+ toLocationId: string(),
25354
+ bytes: number(),
25355
+ files: number().int()
25356
+ });
25357
+ /** Why a pile that is out of place is staying there. Every refusal is
25358
+ * reported: a rebalance that silently drops a camera reads exactly like one
25359
+ * that had nothing to do. */
25360
+ var RecordingRebalanceSkipReasonSchema = _enum([
25361
+ "unassigned",
25362
+ "target-not-writable",
25363
+ "below-threshold",
25364
+ "no-headroom"
25365
+ ]);
25366
+ var RecordingRebalanceSkipSchema = object({
25367
+ deviceId: number(),
25368
+ profile: string(),
25369
+ fromLocationId: string(),
25370
+ /** The location the plan wants; null when the camera has no assignment. */
25371
+ toLocationId: string().nullable(),
25372
+ bytes: number(),
25373
+ reason: RecordingRebalanceSkipReasonSchema
25374
+ });
25375
+ var RecordingRebalancePlanSchema = object({
25376
+ moves: array(RecordingRebalanceMoveSchema),
25377
+ skipped: array(RecordingRebalanceSkipSchema),
25378
+ bytesToMove: number(),
25379
+ /** Relocate job ids enqueued. Always empty for the plan (dry-run) call. */
25380
+ jobIds: array(string())
25381
+ });
25382
+ var RecordingRebalanceInputSchema = object({
25383
+ /** Copy throttle in MB/s (default 40) — a rebalance is a background chore. */
25384
+ throttleMbps: number().min(1).max(1e3).optional(),
25385
+ /** Ignore piles smaller than this (default 1 GB). */
25386
+ minMoveGb: number().min(0).optional()
25387
+ });
25388
+ /**
25023
25389
  * Result of locating footage at a wall-clock instant for one device/profile.
25024
25390
  * `segment` carries the covering segment's window; `gap` reports the forward
25025
25391
  * nearest covered edge (`null` past the end of footage / when none exists)
@@ -25182,9 +25548,24 @@ method(object({
25182
25548
  }), method(object({ jobId: string() }), RelocateJobSchema.nullable(), { auth: "admin" }), method(object({ jobId: string() }), object({ cancelled: boolean() }), {
25183
25549
  kind: "mutation",
25184
25550
  auth: "admin"
25551
+ }), method(RelocateFootageInputSchema, object({ jobId: string() }), {
25552
+ kind: "mutation",
25553
+ auth: "admin"
25554
+ }), method(object({}), array(RelocateJobSchema).readonly(), {
25555
+ kind: "query",
25556
+ auth: "admin"
25557
+ }), method(object({ jobId: string() }), object({ cancelled: boolean() }), {
25558
+ kind: "mutation",
25559
+ auth: "admin"
25560
+ }), method(RecordingRebalanceInputSchema, RecordingRebalancePlanSchema, {
25561
+ kind: "query",
25562
+ auth: "admin"
25563
+ }), method(RecordingRebalanceInputSchema, RecordingRebalancePlanSchema, {
25564
+ kind: "mutation",
25565
+ auth: "admin"
25185
25566
  });
25186
25567
  /**
25187
- * `recordingExport` cap — render a footage time range into a single downloadable
25568
+ * `recording-export` cap — render a footage time range into a single downloadable
25188
25569
  * MP4 (regular / accelerated / decelerated / timelapse, ± audio), kept for a
25189
25570
  * bounded lifetime with a durable history, auto-expiry, and optional
25190
25571
  * delete-after-download.
@@ -25199,10 +25580,53 @@ method(object({
25199
25580
  */
25200
25581
  /** Playback-speed multiplier for the render (1 = realtime). */
25201
25582
  var ExportSpeedSchema = number().min(.25).max(32);
25583
+ /**
25584
+ * One dense interval, in WALL-CLOCK SECONDS FROM THE EXPORT'S OWN `fromMs`.
25585
+ *
25586
+ * **Wall clock, not ffmpeg's `t`** — and the recorder translates. A caller
25587
+ * derives these bounds from things that happened at a TIME (a track's
25588
+ * `firstSeen`), while `t` runs over the source playlist: the concatenation of
25589
+ * every segment present for the range, with each recording GAP removed. The
25590
+ * two agree only on a window that recorded without one interruption, and only
25591
+ * the render side knows the segments, so the translation lives there
25592
+ * (`export-dense-map.ts`, addon-pipeline).
25593
+ *
25594
+ * It was not always so. These seconds were fed to `between(t,…)` verbatim, and
25595
+ * on a 10 h window holding 29,393 s of footage every range landed late by the
25596
+ * gap accumulated before it — up to 6,607 s, well past EOF. Nothing matched,
25597
+ * the video was a uniform timelapse, and the log line reported the five ranges
25598
+ * that had been ASKED for (2026-08-13, export `57d14363`, camera 615).
25599
+ *
25600
+ * Relative and not absolute epoch, because an absolute epoch would make every
25601
+ * call site responsible for the same subtraction.
25602
+ */
25603
+ var ExportDenseRangeSchema = object({
25604
+ fromSec: number().nonnegative(),
25605
+ toSec: number().nonnegative()
25606
+ }).refine((r) => r.toSec > r.fromSec, { message: "dense range must have toSec > fromSec" });
25607
+ /**
25608
+ * Dense-interval overlay for a timelapse: sample at `dense.everyMs` INSIDE the
25609
+ * listed ranges and at the base `everyMs` everywhere else.
25610
+ *
25611
+ * `everyMs` must be strictly smaller than the base cadence — a dense rate that
25612
+ * is not denser renders a uniform timelapse the operator believes is two-rate.
25613
+ */
25614
+ var ExportDenseSchema = object({
25615
+ everyMs: number().int().positive(),
25616
+ ranges: array(ExportDenseRangeSchema).min(1).max(200)
25617
+ });
25202
25618
  /** Timelapse cadence — sample one source frame per `everyMs`, output at `outputFps`. */
25203
25619
  var ExportTimelapseSchema = object({
25204
25620
  everyMs: number().int().positive(),
25205
- outputFps: number().int().min(1).max(60).optional()
25621
+ outputFps: number().int().min(1).max(60).optional(),
25622
+ /** Optional second, FASTER rate over the intervals that matter. */
25623
+ dense: ExportDenseSchema.optional()
25624
+ }).superRefine((v, ctx) => {
25625
+ if (v.dense !== void 0 && v.dense.everyMs >= v.everyMs) ctx.addIssue({
25626
+ code: ZodIssueCode$16.custom,
25627
+ message: "dense.everyMs must be strictly smaller than the base everyMs",
25628
+ path: ["dense", "everyMs"]
25629
+ });
25206
25630
  });
25207
25631
  /**
25208
25632
  * Render options. `speed` and `timelapse` are mutually exclusive. `includeAudio`
@@ -25260,6 +25684,19 @@ var ExportDownloadSchema = object({
25260
25684
  url: string(),
25261
25685
  endpoints: array(string())
25262
25686
  });
25687
+ /**
25688
+ * A finished export's bytes, inline.
25689
+ *
25690
+ * `bytes` is the DECODED length — the number the caller bounds and logs
25691
+ * against, so nobody has to infer it from the base64 length.
25692
+ */
25693
+ var ExportBytesSchema = object({
25694
+ base64: string(),
25695
+ contentType: string(),
25696
+ /** Suggested filename, extension included. */
25697
+ name: string(),
25698
+ bytes: number().int().nonnegative()
25699
+ });
25263
25700
  method(object({
25264
25701
  deviceId: number(),
25265
25702
  profile: string(),
@@ -25284,6 +25721,9 @@ method(object({
25284
25721
  }), method(object({ exportId: string() }), ExportDownloadSchema, {
25285
25722
  kind: "query",
25286
25723
  auth: "protected"
25724
+ }), method(object({ exportId: string() }), ExportBytesSchema, {
25725
+ kind: "query",
25726
+ auth: "protected"
25287
25727
  });
25288
25728
  /**
25289
25729
  * scene-monitor — device-scoped reference-region state cap. An operator marks
@@ -32252,6 +32692,12 @@ Object.freeze({
32252
32692
  addonId: null,
32253
32693
  access: "create"
32254
32694
  },
32695
+ "recording.cancelRelocateJob": {
32696
+ capName: "recording",
32697
+ capScope: "system",
32698
+ addonId: null,
32699
+ access: "create"
32700
+ },
32255
32701
  "recording.cancelStorageMigrationMove": {
32256
32702
  capName: "recording",
32257
32703
  capScope: "system",
@@ -32306,6 +32752,12 @@ Object.freeze({
32306
32752
  addonId: null,
32307
32753
  access: "view"
32308
32754
  },
32755
+ "recording.listRelocateJobs": {
32756
+ capName: "recording",
32757
+ capScope: "system",
32758
+ addonId: null,
32759
+ access: "view"
32760
+ },
32309
32761
  "recording.locateSegment": {
32310
32762
  capName: "recording",
32311
32763
  capScope: "system",
@@ -32318,6 +32770,12 @@ Object.freeze({
32318
32770
  addonId: null,
32319
32771
  access: "create"
32320
32772
  },
32773
+ "recording.planStorageRebalance": {
32774
+ capName: "recording",
32775
+ capScope: "system",
32776
+ addonId: null,
32777
+ access: "view"
32778
+ },
32321
32779
  "recording.pruneFootage": {
32322
32780
  capName: "recording",
32323
32781
  capScope: "system",
@@ -32342,6 +32800,12 @@ Object.freeze({
32342
32800
  addonId: null,
32343
32801
  access: "create"
32344
32802
  },
32803
+ "recording.relocateFootage": {
32804
+ capName: "recording",
32805
+ capScope: "system",
32806
+ addonId: null,
32807
+ access: "create"
32808
+ },
32345
32809
  "recording.renderClip": {
32346
32810
  capName: "recording",
32347
32811
  capScope: "system",
@@ -32378,38 +32842,50 @@ Object.freeze({
32378
32842
  addonId: null,
32379
32843
  access: "create"
32380
32844
  },
32845
+ "recording.startStorageRebalance": {
32846
+ capName: "recording",
32847
+ capScope: "system",
32848
+ addonId: null,
32849
+ access: "create"
32850
+ },
32381
32851
  "recordingExport.cancelExport": {
32382
- capName: "recordingExport",
32852
+ capName: "recording-export",
32383
32853
  capScope: "system",
32384
32854
  addonId: null,
32385
32855
  access: "create"
32386
32856
  },
32387
32857
  "recordingExport.createExport": {
32388
- capName: "recordingExport",
32858
+ capName: "recording-export",
32389
32859
  capScope: "system",
32390
32860
  addonId: null,
32391
32861
  access: "create"
32392
32862
  },
32393
32863
  "recordingExport.deleteExport": {
32394
- capName: "recordingExport",
32864
+ capName: "recording-export",
32395
32865
  capScope: "system",
32396
32866
  addonId: null,
32397
32867
  access: "delete"
32398
32868
  },
32399
32869
  "recordingExport.getDownloadUrl": {
32400
- capName: "recordingExport",
32870
+ capName: "recording-export",
32401
32871
  capScope: "system",
32402
32872
  addonId: null,
32403
32873
  access: "view"
32404
32874
  },
32405
32875
  "recordingExport.getExport": {
32406
- capName: "recordingExport",
32876
+ capName: "recording-export",
32407
32877
  capScope: "system",
32408
32878
  addonId: null,
32409
32879
  access: "view"
32410
32880
  },
32411
32881
  "recordingExport.listExports": {
32412
- capName: "recordingExport",
32882
+ capName: "recording-export",
32883
+ capScope: "system",
32884
+ addonId: null,
32885
+ access: "view"
32886
+ },
32887
+ "recordingExport.readExportBytes": {
32888
+ capName: "recording-export",
32413
32889
  capScope: "system",
32414
32890
  addonId: null,
32415
32891
  access: "view"
@@ -33786,6 +34262,104 @@ var FramerateField = number().int().min(1).max(60);
33786
34262
  var TargetsField = array(NcRuleTargetSchema).min(1);
33787
34263
  var PriorityField = number().int().min(1).max(5);
33788
34264
  /**
34265
+ * Explicit override of the DENSE sampling cadence, seconds.
34266
+ *
34267
+ * Absent ⇒ derived as `max(1s, cadenceSec / 30)` — a 30 s base samples every
34268
+ * 1 s inside a detection range. (It was `base / 10` until 2026-08-12, which
34269
+ * made that same base 3 s and rendered a person pass as two frames.)
34270
+ *
34271
+ * THE ARITHMETIC. A detection range of `rangeSec` seconds sampled every
34272
+ * `denseCadenceSec` and played at `framerate` occupies
34273
+ *
34274
+ * outputSeconds = (rangeSec / denseCadenceSec) / framerate
34275
+ *
34276
+ * so a 7 s pass at 1 s / 12 fps is 0.58 s of video, and at 0.5 s it is 1.17 s.
34277
+ * Halving this field doubles the frames INSIDE ranges only — the base cadence,
34278
+ * and therefore the length of a quiet night, does not move.
34279
+ *
34280
+ * Floored at {@link TIMELAPSE_DENSE_FLOOR_SEC}: asking for frames faster than
34281
+ * the recording has them returns the same frames, requested twice. Must be
34282
+ * STRICTLY smaller than `cadenceSec` — a dense rate that is not denser renders
34283
+ * a uniform video the operator believes is two-rate — and upsert refuses it
34284
+ * rather than letting the export cap reject the render hours after the window.
34285
+ */
34286
+ var DenseCadenceSecField = number().min(.1).max(3600);
34287
+ /**
34288
+ * Minimum seconds of OUTPUT video each detection range must occupy.
34289
+ *
34290
+ * The operator-facing form of the arithmetic above: instead of solving for a
34291
+ * cadence, state the dwell and let the renderer solve. `minDwellSec: 1` on a
34292
+ * 30 s base at 12 fps turns a 7 s pass into a full second of video by sampling
34293
+ * that range every ~583 ms.
34294
+ *
34295
+ * ONE CADENCE SERVES EVERY RANGE. `ExportDenseSchema.everyMs` is global — the
34296
+ * ranges are terms of a single ffmpeg `select` expression that cannot vary rate
34297
+ * per term — so the MOST DEMANDING (shortest) range sets the rate and longer
34298
+ * ranges are sampled denser than they need. Per-range cadences require a cap
34299
+ * schema change and are the tracked follow-up.
34300
+ *
34301
+ * A range too short to reach the dwell even at {@link TIMELAPSE_DENSE_FLOOR_SEC}
34302
+ * is rendered with every frame that EXISTS and no more: the guarantee is capped
34303
+ * by real footage, never met by duplicating frames into motion that never
34304
+ * happened.
34305
+ */
34306
+ var MinDwellSecField = number().min(0).max(60);
34307
+ /**
34308
+ * Caption burned into the notification's preview frame.
34309
+ *
34310
+ * Same `{{var}}` vocabulary as {@link TimelapseTemplateSchema} (`camera`,
34311
+ * `rule`, `from`, `to`) and rendered by the SAME renderer — a second
34312
+ * templating dialect for one field would be a second thing to explain.
34313
+ *
34314
+ * Absent ⇒ {@link DEFAULT_TIMELAPSE_PREVIEW_TEXT}. An EMPTY STRING is the
34315
+ * operator saying "the frame, no caption" — a distinct, reachable answer, and
34316
+ * the reason this is not `.min(1)`.
34317
+ */
34318
+ var PreviewTextField = string().max(200);
34319
+ /**
34320
+ * Whether the notification's preview is a STILL or a short animation.
34321
+ *
34322
+ * The operator's ask, verbatim: *"inviato come gif o video (come per le altre
34323
+ * rule)"* — his Scrypted advanced-notifier has a `gifRule`, and a ten-hour
34324
+ * night reads better as three seconds of motion than as one frame of it. Both
34325
+ * modes get the SAME treatment (blurred frame, large centred title); `'gif'`
34326
+ * simply applies it to a dozen frames sampled across the render and assembles
34327
+ * them.
34328
+ *
34329
+ * `'image'` is the default and stays the default: a GIF costs a dozen ffmpeg
34330
+ * seeks and a palette pass, and no rule that never asked for one should start
34331
+ * paying that on the deploy that shipped it.
34332
+ *
34333
+ * A GIF that cannot be assembled DEGRADES to the still — never to nothing.
34334
+ */
34335
+ var PreviewModeField = _enum(["image", "gif"]);
34336
+ /**
34337
+ * Which detection classes the notification reports counts for.
34338
+ *
34339
+ * The counts come from the tracks the render ALREADY fetched for its dense-range
34340
+ * plan — no second query — aggregated per class. Absent or empty means "every
34341
+ * class the window actually contained", which is what an operator who never
34342
+ * opened the field wants; a list narrows it (`['person']` on a driveway that
34343
+ * counts cars all night).
34344
+ *
34345
+ * Class names are the tracker's own (`person`, `vehicle`, `animal`, `package`,
34346
+ * …). An unknown name simply never matches and reports nothing — it is not an
34347
+ * error, because a rule may legitimately name a class this camera's model does
34348
+ * not emit.
34349
+ *
34350
+ * The counts are exposed to {@link TimelapseTemplateSchema} as:
34351
+ * - `{{detections}}` — total over the reported classes
34352
+ * - `{{detectionSummary}}` — `2 persone, 1 veicolo`
34353
+ * - `{{count_person}}` / `{{count_vehicle}}` / `{{count_animal}}` / … —
34354
+ * one per class, `count_` + the class name
34355
+ *
34356
+ * With NO custom body template the summary is appended to the derived body, and
34357
+ * only when the total is non-zero: a nightly `0 rilevamenti` is a line nobody
34358
+ * reads. With a custom template the operator owns every word — nothing is
34359
+ * appended, so `{{detectionSummary}}` is how he asks for it.
34360
+ */
34361
+ var ReportClassesField = array(string().min(1).max(40)).max(20);
34362
+ /**
33789
34363
  * Client-supplied timelapse-rule fields. The server stamps id / createdBy /
33790
34364
  * createdAt / updatedAt / ownerUserId / lastGeneratedAt — none of them appear
33791
34365
  * here (see the ownership note above).
@@ -33805,9 +34379,30 @@ var TimelapseRuleInputSchema = object({
33805
34379
  cadenceSec: CadenceSecField.default(15),
33806
34380
  /** Output frames per second of the assembled mp4 (predecessor parity). */
33807
34381
  framerate: FramerateField.default(10),
34382
+ /**
34383
+ * Explicit dense cadence — see {@link DenseCadenceSecField}. Absent ⇒ derived
34384
+ * as `max(1s, cadenceSec / 30)`, which is what every rule written before this
34385
+ * field gets.
34386
+ */
34387
+ denseCadenceSec: DenseCadenceSecField.optional(),
34388
+ /** Output-seconds guarantee per detection range — see {@link MinDwellSecField}. */
34389
+ minDwellSec: MinDwellSecField.optional(),
33808
34390
  /** `notification-output` targets the finished video/thumbnail is sent to. */
33809
34391
  targets: TargetsField,
33810
34392
  template: TimelapseTemplateSchema.optional(),
34393
+ /**
34394
+ * Caption on the notification's PREVIEW FRAME — see {@link PreviewTextField}
34395
+ * and {@link DEFAULT_TIMELAPSE_PREVIEW_TEXT}.
34396
+ *
34397
+ * Deliberately NOT part of {@link TimelapseTemplateSchema}: that object is
34398
+ * the notification's title/body, and clearing it (`template: null`) must not
34399
+ * silently clear the caption too.
34400
+ */
34401
+ previewText: PreviewTextField.optional(),
34402
+ /** Still or animation — see {@link PreviewModeField}. */
34403
+ previewMode: PreviewModeField.default("image"),
34404
+ /** Classes the notification counts — see {@link ReportClassesField}. */
34405
+ reportClasses: ReportClassesField.optional(),
33811
34406
  /** Canonical notification priority ordinal (1..5); per-target overridable. */
33812
34407
  priority: PriorityField.default(3)
33813
34408
  });
@@ -33818,8 +34413,13 @@ object({
33818
34413
  schedule: NcScheduleSchema.optional(),
33819
34414
  cadenceSec: CadenceSecField.optional(),
33820
34415
  framerate: FramerateField.optional(),
34416
+ denseCadenceSec: DenseCadenceSecField.optional(),
34417
+ minDwellSec: MinDwellSecField.optional(),
33821
34418
  targets: TargetsField.optional(),
33822
34419
  template: TimelapseTemplateSchema.nullable().optional(),
34420
+ previewText: PreviewTextField.optional(),
34421
+ previewMode: PreviewModeField.optional(),
34422
+ reportClasses: ReportClassesField.optional(),
33823
34423
  priority: PriorityField.optional()
33824
34424
  });
33825
34425
  TimelapseRuleInputSchema.extend({
@@ -33831,10 +34431,28 @@ TimelapseRuleInputSchema.extend({
33831
34431
  */
33832
34432
  ownerUserId: string().optional(),
33833
34433
  /**
33834
- * Epoch-ms of the last successful generation the 1-hour re-generation
33835
- * guard's durable state (predecessor parity). Absent = never generated.
34434
+ * Epoch-ms of the NEWEST successful generation across every camera of this
34435
+ * rule. What a UI shows, and the compatibility floor for
34436
+ * {@link readTimelapseGeneratedAt}. Absent = never generated.
33836
34437
  */
33837
34438
  lastGeneratedAt: number().optional(),
34439
+ /**
34440
+ * PER-CAMERA generation state, keyed by `String(deviceId)` — the
34441
+ * re-generation guard's real durable state.
34442
+ *
34443
+ * One rule covers several cameras and each renders its own video, so a rule
34444
+ * -wide stamp is wrong in the direction that DESTROYS work: camera A
34445
+ * succeeding at 06:05 tells camera B, whose render failed, that it is
34446
+ * already done — and B's night is gone for good, because the window will not
34447
+ * come back.
34448
+ *
34449
+ * ADDITIVE, so the migration is free: a row written before this field simply
34450
+ * has no map, and {@link readTimelapseGeneratedAt} falls back to
34451
+ * {@link TimelapseRuleSchema.shape.lastGeneratedAt}. Reading an old row as
34452
+ * "never generated" would re-render and re-notify every camera of every rule
34453
+ * once, on the deploy that shipped the map.
34454
+ */
34455
+ generatedByDevice: record(string(), number()).optional(),
33838
34456
  /** userId of the caller who created the rule (server-stamped). */
33839
34457
  createdBy: string(),
33840
34458
  createdAt: number(),
@@ -33885,25 +34503,32 @@ object({
33885
34503
  var NativeLeaseAdmissionSchema = _enum(["all", "inferred"]);
33886
34504
  object({
33887
34505
  /**
33888
- * How long a retained native frame is served before it counts as a miss.
34506
+ * How many delivered frames the worker HOLDS at once, waiting for each one's
34507
+ * detection result.
33889
34508
  *
33890
- * Must cover the FULL late-crop horizon: detection inference + the
33891
- * cross-process inference-result hop to hub post-analysis + tracking + the
33892
- * tRPC crop round-trip back. Below ~500 ms the busiest cameras' subject crops
33893
- * outrun it and fall back to the ≤640 detection frame; above ~3 s the resident
33894
- * RAM per busy camera grows linearly with no measured hit-rate gain.
34509
+ * This replaced a TTL on 2026-08-13, and the replacement is the whole point:
34510
+ * a time window was never related to the event the pixels were waiting for.
34511
+ * A held frame now lives from delivery until the runner has its `FrameResult`
34512
+ * at which moment the runner cuts the subject tiles it actually wanted and
34513
+ * releases the frame. The bound exists only so a runner that stops answering
34514
+ * cannot pin RAM: above it the OLDEST held frame is dropped and counted.
34515
+ *
34516
+ * Sizing: the steady state is `inferenceLatency × deliveredFps`, measured at
34517
+ * 40-160 ms × ≤25 fps = 1-4 frames. The default leaves headroom for a hiccup
34518
+ * without ever approaching the old resident set (43 frames × 24.9 MB at 4K).
34519
+ * Raising it does not buy hit rate — it buys tolerance for a slow runner, and
34520
+ * `holdOverflow` on the metrics line is what says you need it.
33895
34521
  */
33896
- ttlMs: number().int().min(250).max(1e4),
34522
+ holdFrames: number().int().min(1).max(64),
33897
34523
  /**
33898
34524
  * Hard per-decode-worker RAM ceiling for retained native frames, in MB.
33899
34525
  *
33900
- * Intended as a SAFETY ceiling with the TTL as the effective cap — but check
33901
- * which one is actually binding before reasoning from that. At the shipped
33902
- * 1024 MB and a 2 800 ms TTL, a 4K camera hits the CEILING first (~43 frames
33903
- * at ~24 MB each) and the TTL never gets to expire anything; `leaseMb` /
33904
- * `leaseFrames` on the metrics line say which. When the ceiling binds, a
33905
- * change that admits fewer frames buys retention WINDOW at constant RAM
33906
- * rather than giving RAM back — lower this knob if RAM is what you wanted.
34526
+ * Since 2026-08-13 this is a SAFETY ceiling and nothing else: `holdFrames`
34527
+ * is what decides how much is held, and the ceiling is the number above which
34528
+ * something is wrong. Before that it was the effective cap at 1024 MB with
34529
+ * a 2 800 ms TTL a 4K camera sat pinned at `leaseMb:1020, leaseFrames:43`
34530
+ * with the TTL expiring nothing, which is exactly the confusion the hold
34531
+ * removes. `leaseMb` / `leaseFrames` still say what is resident.
33907
34532
  * `0` DISABLES the lease entirely and falls the worker back to the tiny
33908
34533
  * leak-prone GPU surface ring (~85% crop miss; that is what the lease exists
33909
34534
  * to replace).
@@ -33929,22 +34554,45 @@ object({
33929
34554
  * there is the signal that some caller names frames outside the inference set
33930
34555
  * and that this must go back to `all`.
33931
34556
  */
33932
- admission: NativeLeaseAdmissionSchema
34557
+ admission: NativeLeaseAdmissionSchema,
34558
+ /**
34559
+ * RAM ceiling per decode worker, in MB, for the SUBJECT TILES — the
34560
+ * compressed native crops the worker cuts at the moment a frame's detection
34561
+ * result arrives, and keeps long after the frame itself is freed.
34562
+ *
34563
+ * This is the knob that replaced the old retention window, and it buys about
34564
+ * three orders of magnitude more of it: a tile is one subject at native
34565
+ * resolution, JPEG-encoded (~60-120 KB on a 4K person), against ~24.9 MB for
34566
+ * the frame it was cut from. A frame on which nothing was detected costs
34567
+ * nothing at all, which is the real change — the old lease paid per FRAME and
34568
+ * was interrogated per SUBJECT.
34569
+ *
34570
+ * `0` DISABLES tiles, leaving only the hold window and the ≤640 RAM
34571
+ * fallback — i.e. the pre-2026-08-13 miss profile. Set it there only to
34572
+ * reproduce that.
34573
+ */
34574
+ tileBudgetMb: number().int().min(0).max(1024)
33933
34575
  });
33934
34576
  /**
33935
- * The values in force when the operator has set nothing — byte-for-byte the
33936
- * constants the decode worker shipped with as env-var defaults, so making these
33937
- * settings changed no behaviour on the day it landed.
34577
+ * The values in force when the operator has set nothing.
34578
+ *
34579
+ * `budgetMb` stays at 1024 on the day the hold landed, deliberately: it stopped
34580
+ * being the retention window and became the OOM ceiling, and lowering a ceiling
34581
+ * in the same change that redefines it would make a regression and a retune
34582
+ * indistinguishable. Cut it once `tileHits` / `holdOverflow` have been read on
34583
+ * live traffic.
33938
34584
  */
33939
34585
  var DEFAULT_NATIVE_LEASE_SETTINGS = {
33940
- ttlMs: 1200,
34586
+ holdFrames: 8,
33941
34587
  budgetMb: 1024,
33942
34588
  activityMs: 15e3,
34589
+ tileBudgetMb: 64,
33943
34590
  admission: "inferred"
33944
34591
  };
33945
- DEFAULT_NATIVE_LEASE_SETTINGS.ttlMs;
34592
+ DEFAULT_NATIVE_LEASE_SETTINGS.holdFrames;
33946
34593
  DEFAULT_NATIVE_LEASE_SETTINGS.budgetMb;
33947
34594
  DEFAULT_NATIVE_LEASE_SETTINGS.activityMs;
34595
+ DEFAULT_NATIVE_LEASE_SETTINGS.tileBudgetMb;
33948
34596
  DEFAULT_NATIVE_LEASE_SETTINGS.admission;
33949
34597
  //#endregion
33950
34598
  //#region ../../node_modules/undici/lib/core/symbols.js
@@ -223774,6 +224422,47 @@ function isRecoverableBaichuanError(err) {
223774
224422
  return RECOVERABLE_FRAGMENTS.some((fragment) => message.includes(fragment));
223775
224423
  }
223776
224424
  //#endregion
224425
+ //#region src/ptz-zoom.ts
224426
+ /**
224427
+ * Fraction of total zoom travel moved by ONE press. ~8 presses to cross
224428
+ * the full range reads like a zoom rocker.
224429
+ */
224430
+ var ZOOM_STEP_FRACTION = .12;
224431
+ /** `zoomToFactor` expresses an absolute movePos as `factor * 1000`. */
224432
+ var ZOOM_FACTOR_SCALE = 1e3;
224433
+ /** Pause before the retry above — long enough for the lens to settle. */
224434
+ var ZOOM_SET_RETRY_MS = 1500;
224435
+ /**
224436
+ * Resolve the absolute zoom position one press should drive to.
224437
+ *
224438
+ * Only the SIGN of `zoom` is read. Pan/tilt already discard their
224439
+ * magnitude, and the two clients disagree on it anyway — the viewer
224440
+ * sends ±0.2 per press while ui-library sends ±1 — so honouring
224441
+ * magnitude would make the same button travel different distances
224442
+ * depending on which app pressed it.
224443
+ */
224444
+ var resolveZoomStep = (travel, zoom) => {
224445
+ if (!Number.isFinite(travel.minPos) || !Number.isFinite(travel.maxPos)) return {
224446
+ kind: "refused",
224447
+ reason: "no-travel"
224448
+ };
224449
+ if (travel.maxPos <= travel.minPos) return {
224450
+ kind: "refused",
224451
+ reason: "no-travel"
224452
+ };
224453
+ const step = (travel.maxPos - travel.minPos) * ZOOM_STEP_FRACTION;
224454
+ const raw = travel.curPos + Math.sign(zoom) * step;
224455
+ const target = Math.round(Math.min(travel.maxPos, Math.max(travel.minPos, raw)));
224456
+ if (target === travel.curPos) return {
224457
+ kind: "refused",
224458
+ reason: "at-limit"
224459
+ };
224460
+ return {
224461
+ kind: "move",
224462
+ target
224463
+ };
224464
+ };
224465
+ //#endregion
223777
224466
  //#region src/intercom-encoder.ts
223778
224467
  /**
223779
224468
  * IMA ADPCM (DVI4) encoder — Reolink Baichuan talk-back wire format.
@@ -229196,14 +229885,16 @@ var ReolinkCamera = class ReolinkCamera extends BaseDevice {
229196
229885
  }
229197
229886
  }
229198
229887
  /**
229199
- * Translate normalized (-1..1) pan/tilt/zoom to one or more discrete
229200
- * Baichuan PTZ commands. Camstack ptz uses ONVIF-style continuous
229888
+ * Translate normalized (-1..1) pan/tilt to discrete Baichuan
229889
+ * directional commands. Camstack ptz uses ONVIF-style continuous
229201
229890
  * motion vectors; Reolink Baichuan needs discrete directional
229202
- * commands (Left/Right/Up/Down/ZoomIn/ZoomOut). Magnitudes map to
229203
- * speed (0–63 typical). Continuous=true issues 'start' (camera moves
229204
- * until next 'stop'); continuous=false issues 'start' followed by an
229205
- * autoStop after a short window so a single tap of an arrow key
229206
- * results in a tiny nudge.
229891
+ * commands (Left/Right/Up/Down). Magnitudes map to speed (0–63
229892
+ * typical). Continuous=true issues 'start' (camera moves until next
229893
+ * 'stop'); continuous=false issues 'start' followed by an autoStop
229894
+ * after a short window so a single tap of an arrow key results in a
229895
+ * tiny nudge.
229896
+ *
229897
+ * Zoom is NOT a direction on this frame — see `runZoom`.
229207
229898
  */
229208
229899
  async runPtz(pan, tilt, zoom, speed, continuous) {
229209
229900
  const api = await this.ensureApi();
@@ -229211,7 +229902,7 @@ var ReolinkCamera = class ReolinkCamera extends BaseDevice {
229211
229902
  const cmds = [];
229212
229903
  if (pan !== void 0 && Math.abs(pan) > .01) cmds.push(pan > 0 ? "Right" : "Left");
229213
229904
  if (tilt !== void 0 && Math.abs(tilt) > .01) cmds.push(tilt > 0 ? "Up" : "Down");
229214
- if (zoom !== void 0 && Math.abs(zoom) > .01) cmds.push(zoom > 0 ? "ZoomIn" : "ZoomOut");
229905
+ if (zoom !== void 0 && Math.abs(zoom) > .01) await this.runZoom(api, channel, zoom);
229215
229906
  if (cmds.length === 0) return;
229216
229907
  const baichuanSpeed = speed === void 0 ? 32 : Math.max(1, Math.min(63, Math.round(speed * 63)));
229217
229908
  for (const command of cmds) try {
@@ -229231,6 +229922,67 @@ var ReolinkCamera = class ReolinkCamera extends BaseDevice {
229231
229922
  });
229232
229923
  }
229233
229924
  }
229925
+ /**
229926
+ * Step the lens along the camera's own zoom travel.
229927
+ *
229928
+ * Baichuan has NO directional zoom on MSG_ID_PTZ_CONTROL (cmd 18) —
229929
+ * that frame accepts left/right/up/down and nothing else, so every
229930
+ * zoom this provider ever sent threw `Unsupported PTZ command for
229931
+ * MSG_ID_PTZ_CONTROL: ZoomIn` inside the lib, got swallowed into a
229932
+ * WARN, and returned void. The cap reported success and the lens
229933
+ * never moved: zoom has never worked on a Reolink here.
229934
+ *
229935
+ * The step arithmetic lives in `resolveZoomStep` (`./ptz-zoom.js`);
229936
+ * this method is only the I/O around it. A camera whose answer
229937
+ * carries no `<zoom>` block has no zoom to drive — that is a dropped
229938
+ * command and it is logged as one.
229939
+ */
229940
+ async runZoom(api, channel, zoom) {
229941
+ try {
229942
+ const range = (await api.getZoomFocus(channel)).zoom;
229943
+ if (!range) {
229944
+ this.ctx.logger.warn("Baichuan zoom dropped — camera reported no zoom travel", {
229945
+ tags: { deviceId: this.id },
229946
+ meta: { reason: "no-zoom-block" }
229947
+ });
229948
+ return;
229949
+ }
229950
+ const step = resolveZoomStep(range, zoom);
229951
+ if (step.kind === "refused") {
229952
+ this.ctx.logger.warn("Baichuan zoom dropped", {
229953
+ tags: { deviceId: this.id },
229954
+ meta: {
229955
+ reason: step.reason,
229956
+ curPos: range.curPos,
229957
+ minPos: range.minPos,
229958
+ maxPos: range.maxPos
229959
+ }
229960
+ });
229961
+ return;
229962
+ }
229963
+ for (let attempt = 1;; attempt += 1) try {
229964
+ await api.zoomToFactor(channel, step.target / ZOOM_FACTOR_SCALE);
229965
+ break;
229966
+ } catch (err) {
229967
+ if (attempt >= 2) throw err;
229968
+ await new Promise((resolve) => setTimeout(resolve, ZOOM_SET_RETRY_MS));
229969
+ }
229970
+ this.ctx.logger.debug("Baichuan zoom applied", {
229971
+ tags: { deviceId: this.id },
229972
+ meta: {
229973
+ from: range.curPos,
229974
+ to: step.target,
229975
+ minPos: range.minPos,
229976
+ maxPos: range.maxPos
229977
+ }
229978
+ });
229979
+ } catch (err) {
229980
+ this.ctx.logger.warn("Baichuan zoom command failed", {
229981
+ tags: { deviceId: this.id },
229982
+ meta: { error: err instanceof Error ? err.message : String(err) }
229983
+ });
229984
+ }
229985
+ }
229234
229986
  async getStreamSources() {
229235
229987
  return buildStreamIds(this.channelCount()).map((s, i) => ({
229236
229988
  id: s.id,
@@ -229539,6 +230291,10 @@ var ReolinkCamera = class ReolinkCamera extends BaseDevice {
229539
230291
  async materializeStreamSocket(camStreamId) {
229540
230292
  const parts = parseCamStreamId(camStreamId, this.getChannel());
229541
230293
  if (!parts || parts.kind !== "native") return;
230294
+ this.ctx.logger.info("broker requested rfc4571 source refresh — materializing on demand", {
230295
+ tags: { deviceId: this.id },
230296
+ meta: { camStreamId }
230297
+ });
229542
230298
  const server = await this.ensureRfc4571Server(camStreamId, parts.channel, parts.profile);
229543
230299
  if (!server) {
229544
230300
  this.ctx.logger.warn("materializeStreamSocket: ensureRfc4571Server returned null", { tags: {
@@ -234033,10 +234789,6 @@ var ReolinkProviderAddon = class extends BaseDeviceProvider {
234033
234789
  this.ctx.logger.debug("broker requested source refresh without a camStreamId — broker will re-pull the catalog", { tags: { deviceId } });
234034
234790
  return;
234035
234791
  }
234036
- this.ctx.logger.info("broker requested rfc4571 source refresh — materializing on demand", {
234037
- tags: { deviceId },
234038
- meta: { camStreamId }
234039
- });
234040
234792
  await dev.materializeStreamSocket(camStreamId);
234041
234793
  }
234042
234794
  async supportsDiscovery() {