@camstack/addon-provider-reolink 1.2.168 → 1.2.169

package/dist/addon.js

@@ -7503,7 +7503,7 @@ var DeviceRole = /* @__PURE__ */ function(DeviceRole) {
 	return DeviceRole;
 }({});
 //#endregion
-//#region ../types/dist/composition-43aqsZQj.mjs
+//#region ../types/dist/composition-D7ULvLdD.mjs
 /**
 * The ffmpeg build every CamStack node downloads, per platform and arch.
 *
@@ -7557,20 +7557,20 @@ function portable(target) {
 }
 portable("linux64"), portable("linuxarm64"), portable("macarm64"), portable("mac64");
 /**
-* LA tabella "quale booleano di questo tipo di device conta come ALTO", e il
-* valutatore puro del suo FRONTE.
+* THE table "which boolean of this device type counts as HIGH", and the
+* pure evaluator of its EDGE.
 *
-* UNA tabella per tutti quelli che chiedono "questo device è ALTO?": il
-* trigger `RecordingTriggers.sensorDeviceIds` del recorder, i marker dei
-* sensori della post-analysis, il bridge camera-sensors dell'orchestratore e
-* le sorgenti di un campanello composto (`doorbellFeatureSources`, D671).
-* Una seconda copia divergerebbe alla prima cap aggiunta, e il sintomo — "il
-* sensore fa suonare il campanello ma non registra" — è esattamente D62.
+* ONE table for everyone who asks "is this device HIGH?": the
+* recorder's `RecordingTriggers.sensorDeviceIds` trigger, the post-analysis
+* sensor markers, the orchestrator's camera-sensors bridge and
+* the sources of a composite doorbell (`doorbellFeatureSources`, D671).
+* A second copy would diverge at the first cap added, and the symptom — "the
+* sensor rings the doorbell but does not record" — is exactly D62.
 *
-* ⚠ NON è `DEVICE_STATE_READERS` (`catalogs/device-state-vocabulary.ts`), e le
-* due non vanno unificate: quella risponde a "qual è la PAROLA di stato per una
-* regola" (e include `presence`, `cover`, `alarm-panel`), questa a "qual è il
-* booleano il cui FRONTE conta". Vocabolari deliberatamente diversi.
+* ⚠ NOT `DEVICE_STATE_READERS` (`catalogs/device-state-vocabulary.ts`), and the
+* two must not be unified: that one answers "what is the state WORD for a
+* rule" (and includes `presence`, `cover`, `alarm-panel`), this one "which
+* boolean's EDGE counts". Deliberately different vocabularies.
 */
 /**
 * Known binary / switch source caps → the boolean slice field whose
@@ -9197,22 +9197,22 @@ var CLASS_MAP_MACRO_TARGETS = [
 	"package"
 ];
 /**
-* Le macro classi di PRIMO LIVELLO: quelle che un object detector emette e che
-* un operatore può selezionare.
+* The FIRST-LEVEL macro classes: those an object detector emits and that
+* an operator can select.
 *
-* Sono le tre offerte dallo step `object-detection`
+* They are the three offered by the `object-detection` step
 * (`addon-pipeline/src/detection-pipeline/registry/step-definitions.ts`,
-* `enabledMacroClasses`). `package` sta in {@link CLASS_MAP_MACRO_TARGETS} e in
-* `MACRO_LABELS` — è una macro vera — ma NON qui: appartiene allo step
-* `package-detection`, la cui abilitazione è guidata dalle zone, e offrire la
-* stessa parola due volte ha già fatto accendere a un operatore il proxy COCO
+* `enabledMacroClasses`). `package` is in {@link CLASS_MAP_MACRO_TARGETS} and in
+* `MACRO_LABELS` — it is a true macro — but NOT here: it belongs to the step
+* `package-detection`, whose enablement is driven by zones, and offering the
+* same word twice has already made an operator turn on the COCO proxy
 * (suitcase/backpack/handbag) lasciando spento il detector dedicato.
 *
-* UNA lista. Prima di oggi le stesse tre erano scritte a mano nell'offerta
-* dello step e una seconda volta come union `FirstLevelMacro`
-* (`types/detection.ts`); una terza copia per il trigger di registrazione
-* (`RecordingTriggers.objectClasses`) avrebbe reso invisibile la divergenza
-* successiva.
+* ONE list. Before today the same three were hand-written in the step's offer
+* and a second time as the union `FirstLevelMacro`
+* (`types/detection.ts`); a third copy for the recording trigger
+* (`RecordingTriggers.objectClasses`) would have made the later divergence
+* invisible.
 */
 var FIRST_LEVEL_MACRO_CLASSES = [
 	"person",
@@ -9277,17 +9277,17 @@ var RecordingStorageModeSchema = _enum([
 	"on-device-decision"
 ]);
 /**
-* Le macro classi che possono aprire una finestra di registrazione — le stesse
-* tre offerte dallo step `object-detection`, da UNA lista
+* The macro classes that can open a recording window — the same
+* three offered by the `object-detection` step, from ONE list
 * ({@link FIRST_LEVEL_MACRO_CLASSES}).
 */
 var RecordingObjectTriggerClassSchema = _enum(FIRST_LEVEL_MACRO_CLASSES);
 /**
-* True quando `values` non ripete un elemento.
+* True when `values` does not repeat an element.
 *
-* Un duplicato non è innocuo: ogni voce di `objectClasses` / `sensorDeviceIds`
-* diventa una SORGENTE in `bandTriggerSources`, e la stessa sorgente due volte
-* conterebbe due volte le sue finestre in `segmentMissedByMs`.
+* A duplicate is not harmless: every entry of `objectClasses` / `sensorDeviceIds`
+* becomes a SOURCE in `bandTriggerSources`, and the same source twice
+* would count its windows twice in `segmentMissedByMs`.
 */
 var noDuplicates = (values) => new Set(values).size === values.length;
 /** Which detectors trigger an `events`-mode band. */
@@ -9295,34 +9295,34 @@ var RecordingTriggersSchema = object({
 	motion: boolean().optional(),
 	audioThresholdDbfs: number().optional(),
 	/**
-	* Le macro classi la cui detection apre una finestra. ASSENTE = la sorgente
-	* non è ascoltata; un array VUOTO è rifiutato, perché "banda events, trigger
-	* object acceso, nessuna classe" è la stessa forma "abilitata e non registra
-	* nulla, per sempre" contro cui è scritto `eventsBandCanEverDemand`.
+	* The macro classes whose detection opens a window. ABSENT = the source
+	* is not listened to; an EMPTY array is rejected, because "events band, object
+	* trigger on, no class" is the same shape "enabled and records
+	* nothing, forever" that `eventsBandCanEverDemand` is written against.
 	*
-	* Il segnale letto è GIÀ FILTRATO: solo detection `source: 'pipeline'`, cioè
-	* quelle che hanno attraversato `enabledMacroClasses`, i
-	* `minConfidence<Macro>` e il full-frame guard. L'AI a bordo camera
-	* (`source: 'onboard'`) non attraversa nessuno di quei gate e NON apre
-	* finestre — vedi `recorder/object-trigger.ts`.
+	* The signal read is ALREADY FILTERED: only `source: 'pipeline'` detections, i.e.
+	* those that went through `enabledMacroClasses`, the
+	* `minConfidence<Macro>` and the full-frame guard. The camera's onboard AI
+	* (`source: 'onboard'`) goes through none of those gates and does NOT open
+	* windows — see `recorder/object-trigger.ts`.
 	*/
 	objectClasses: array(RecordingObjectTriggerClassSchema).min(1).refine(noDuplicates, { message: "objectClasses must not repeat a class" }).optional(),
 	/**
-	* I device LINKED il cui FRONTE ALTO apre una finestra. Assente = la sorgente
-	* non è ascoltata; un array vuoto è rifiutato per la stessa ragione di
+	* The LINKED devices whose RISING EDGE opens a window. Absent = the source
+	* is not listened to; an empty array is rejected for the same reason as
 	* `objectClasses`.
 	*
-	* Sono id di device SORGENTE, non camere: la banda li nomina, quindi il
-	* percorso caldo (`DeviceStateChanged`, a ritmo di bus su tutta la flotta)
-	* non fa RPC. L'OFFERTA da cui l'operatore li sceglie è un'altra domanda, e
-	* si risolve con `deviceManager.getLinkedDevices` + `getBindingsBatch` per
-	* device (D12) — mai un elenco globale di cap.
+	* These are SOURCE device ids, not cameras: the band names them, so the
+	* hot path (`DeviceStateChanged`, at bus rate across the whole fleet)
+	* does no RPC. The OFFER from which the operator picks them is another question, and
+	* is resolved with `deviceManager.getLinkedDevices` + `getBindingsBatch` per
+	* device (D12) — never a global list of caps.
 	*
-	* Cosa vuol dire "alto" dipende dal TIPO di device e non è deciso qui:
-	* `SOURCE_CAP_ACTIVE_FIELD` (`catalogs/sensor-active-state.ts`) è LA tabella,
-	* la stessa del campanello composto (D671). Ed è il FRONTE, non
-	* il livello: un contatto trovato già aperto al riavvio del runner non fa
-	* registrare.
+	* What "high" means depends on the device TYPE and is not decided here:
+	* `SOURCE_CAP_ACTIVE_FIELD` (`catalogs/sensor-active-state.ts`) is THE table,
+	* the same one as the composite doorbell (D671). And it is the EDGE, not
+	* the level: a contact found already open at runner restart does not
+	* record.
 	*/
 	sensorDeviceIds: array(number().int().positive()).min(1).max(16).refine(noDuplicates, { message: "sensorDeviceIds must not repeat a device" }).optional()
 });
@@ -10574,7 +10574,7 @@ function findTimezone(id) {
 * - **VALUE** — at which level, for which scope, until when. That stays ONE
 *   thing: the logging settings document on the `system` cap. Two authorities
 *   over the values is the exact defect
-*   `docs/design/plans/2026-08-26-logging-per-componente.md` was written to
+*   `docs/design/plans/2026-08-26-per-component-logging.md` was written to
 *   remove; re-introducing it from the cure side would be grotesque.
 *
 * Nothing in this file reads a clock, an env var or a store. The registry is
@@ -14486,7 +14486,7 @@ method(_void(), EngineInfoSchema, { auth: "admin" }), method(object({
 	*
 	* ⚠ An earlier version of this comment blamed Zod stripping, and that
 	* was wrong — corrected 2026-08-26 after the hop map
-	* (`docs/design/2026-08-26-mappa-hop-argomenti.md`) traced the path.
+	* (`docs/design/2026-08-26-topic-hop-map.md`) traced the path.
 	* There is **no Zod parse at all** between the door and the engine: the
 	* dispatcher forwards the payload verbatim and UDS carries it whole. A
 	* field declared here reaches `SqliteSettingsBackend` either way.
@@ -16689,7 +16689,7 @@ method(object({
 * per-device window, `KeyFrameCaptureLog`, `bumpCropMetric`. Every one of them
 * ends in a log line, and a log line is the thing the operator asked to stop
 * needing: *"possiamo armare questi errori intanto? Così al prossimo giro
-* ricontrolliamo tutti questi punti"*. Reading them meant grepping Loki and
+* ricontrolliamo tutti questi punti"* [can we instrument these errors in the meantime? That way next round we recheck all these points]. Reading them meant grepping Loki and
 * hand-correlating timestamps, which is how a 22% thumbnail gap and a 3-hour
 * media blackout were both diagnosed. The counters stay; this is where they can
 * be READ.
@@ -22436,14 +22436,14 @@ var TrackSchema = object({
 	* `derive-returned-null tile=standin`,
 	* `native-tile tile=native no-key-frame-at-close`, …) written at close and
 	* CLEARED by the late-keyFrame upgrade when a native tile lands after all.
-	* The operator-facing answer to "perché manca l'immagine?" on a track whose
+	* The operator-facing answer to "perché manca l'immagine?" [why is the image missing?] on a track whose
 	* tile is a face/plate stand-in, a raster crop, or an icon.
 	*
 	* **`no-key-frame-at-close` (D400).** The line used to be written ONLY when
 	* the TILE ranked below native, so a track whose thumbnail landed natively
 	* while its key frame missed carried no reason at all — three of the four
 	* `MISSING_KEYFRAME` tracks in the 2026-09-07 operator audit were exactly
-	* that shape, and their "niente ultimo" had no cause anywhere on the row.
+	* that shape, and their "niente ultimo" [no last frame] had no cause anywhere on the row.
 	* The key frame is the head of a cascade (`keyFrame ⇒ keyFrameSmall ⇒ the
 	* lastFrame copy source`), so its absence is now on this line whatever the
 	* tile ended up being.
@@ -22530,7 +22530,7 @@ var MotionEventSchema = object({
 	/**
 	* Ms offsets from `timestamp` (the episode's own first rising edge, so the
 	* first entry is always `0`) of every genuine off→on transition the
-	* episode saw — "ogni evento on si deve salvare" (D475). NOT one entry per
+	* episode saw — "ogni evento on si deve salvare" [every ON event must be saved] (D475). NOT one entry per
 	* push: a firmware source that keepalives at ~1 Hz for the whole burst
 	* (Reolink, Hikvision) produces exactly one edge; a source that reports an
 	* explicit `false` mid-episode and then resumes before the quiet window
@@ -27987,7 +27987,7 @@ var ClipPlaybackSchema = object({
 * **One authorised yes is one wake.** `next-natural` — take the clip the next
 * time the camera is awake for its own reasons — is deliberately not a member:
 * it was proposed, it is free on the battery, and the operator declined it on
-* 2026-09-20 (*"Quando un export viene richiesto si sveglia la camera."*,
+* 2026-09-20 (*"Quando un export viene richiesto si sveglia la camera."* [When an export is requested the camera wakes up],
 * D558 "Considered and not taken").
 */
 var ClipWakeSchema = _enum(["authorised"]);
@@ -28383,7 +28383,7 @@ var videoclipsCapability = {
 	* **It is a SECTION of the Recording tab, at the end of it — not a tab of
 	* its own.** It shipped as a `clips` top-tab and the operator rejected the
 	* placement: *"utilizzerei la stessa tab recordings, lì abbiamo già tutto il
-	* necessario, una nuova sezione alla fine per le clips"*. The Recording tab
+	* necessario, una nuova sezione alla fine per le clips"* [I would use the same recordings tab, there we already have everything necessary, a new section at the end for the clips]. The Recording tab
 	* already holds the recorder's panel, the schedule bands and the unified
 	* retention policy; footage the camera itself holds is the same question,
 	* asked of a different store. `order: 100` puts it after all of them with
@@ -28444,7 +28444,7 @@ var videoclipsCapability = {
 			* It replaced `sources?: string[]`, a VIEW filter over source ids that
 			* assumed the answer was a fan-out over everything a camera has. The
 			* operator settled otherwise on 2026-09-20 — *"l'utilizzatore è uno
-			* solo"* — so the list is asked of one provider at a time and there is
+			* solo"* [there is only one user] — so the list is asked of one provider at a time and there is
 			* nothing to filter out of it.
 			*/
 			provider: string().min(1)
@@ -36765,7 +36765,7 @@ var ReadGopBytesResultSchema = object({
 /**
 * A time WINDOW of one finalized segment, cut by byte range — the multi-GOP
 * twin of {@link ReadGopBytesResultSchema}'s single instant. Built for the
-* replay clip's `recording` source (`docs/design/plans/2026-08-26-replay-clip-su-pipeline.md`):
+* replay clip's `recording` source (`docs/design/plans/2026-08-26-clip-replay-on-pipeline.md`):
 * a replay needs several seconds of native pixels, not one frame.
 *
 * `ok.data` is standalone-demuxable, same as a GOP read. `ok.reachesRequestedEnd`
@@ -53467,7 +53467,7 @@ var PreviewTextField = string().max(200);
 * Whether the notification's preview is a STILL or a short animation.
 *
 * The operator's ask, verbatim: *"inviato come gif o video (come per le altre
-* rule)"* — the other rules already offer an animated preview, and a ten-hour
+* rule)"* [sent as a gif or video (as for the other rules)] — the other rules already offer an animated preview, and a ten-hour
 * night reads better as three seconds of motion than as one frame of it. Both
 * modes get the SAME treatment (blurred frame, large centred title); `'gif'`
 * simply applies it to a dozen frames sampled across the render and assembles
@@ -161136,37 +161136,37 @@ function buildOnboardWrites(patch, schedule) {
 //#endregion
 //#region src/battery-charging.ts
 /**
-* Da `adapterStatus` + `chargeStatus` alla sorgente di alimentazione.
-*
-* I due campi rispondono a DUE domande diverse, e confonderle è il bug che
-* questo modulo esiste per chiudere:
-*
-*  - `adapterStatus` — l'alimentazione è COLLEGATA? Il firmware manda 0/1/2
-*    (nessuna · adattatore DC · pannello solare) e il confine dell'hub lo
-*    traduce in `'none' | 'dc' | 'solarPanel'` (`mapHubChargeStatus` e
-*    `mapHubAdapterStatus` in `reolink-hub.ts`), perché il vocabolario del
-*    percorso standalone è già a stringhe.
-*  - `chargeStatus` — la CELLA cosa sta facendo? 0 ferma · 1 in carica ·
-*    2 carica completa.
-*
-* La vecchia derivazione consultava l'adattatore SOLO per cercarci 'solar', e
-* un DC collegato cadeva nel ripiego `'none'`. Due Argus 3E lo nascondevano per
-* caso: piene e collegate rispondono `chargeStatus: 2`, che il ramo `isCharging`
-* mappava su `'dc'` per la ragione sbagliata. La Argus MagiCam (batteryVersion
-* 1, firmware 2026) collegata in permanenza risponde `chargeStatus: 0`, e per
-* tutta la sua vita è stata riportata NON in carica.
-*
-* Che `adapterStatus` sia un segnale vero e non una costante è MISURATO: il
-* 2026-09-05 l'operatore ha staccato il device 3628 e il payload grezzo è
-* passato da `adapterStatus: 1` a `0`, con `chargeStatus: 0` da entrambe le
-* parti — cioè `chargeStatus` da solo NON distingue i due stati.
-*
-* Due campi assenti NON sono `'none'`: `'none'` è un negativo che il firmware
-* ha detto ("nessun adattatore, cella ferma"), l'assenza di entrambi è
-* `'unknown'` — lo stesso confine che `percentage` ha chiuso diventando
-* `nullable` (D315). Il chiamante (`mapBatteryInfo`) non arriva qui con un
-* push che non parla di alimentazione: `reportsPowerSource` lo filtra prima e
-* conserva la convinzione precedente.
+* From `adapterStatus` + `chargeStatus` to the power source.
+*
+* The two fields answer TWO different questions, and confusing them is the bug that
+* this module exists to close:
+*
+*  - `adapterStatus` — is the power CONNECTED? The firmware sends 0/1/2
+*    (none · DC adapter · solar panel) and the hub boundary
+*    translates it into `'none' | 'dc' | 'solarPanel'` (`mapHubChargeStatus` and
+*    `mapHubAdapterStatus` in `reolink-hub.ts`), because the vocabulary of the
+*    standalone path is already strings.
+*  - `chargeStatus` — what is the CELL doing? 0 stopped · 1 charging ·
+*    2 fully charged.
+*
+* The old derivation consulted the adapter ONLY to look for 'solar' in it, and
+* a connected DC fell into the fallback `'none'`. Two Argus 3E units hid it by
+* chance: full and connected they answer `chargeStatus: 2`, which the `isCharging`
+* branch mapped to `'dc'` for the wrong reason. The Argus MagiCam (batteryVersion
+* 1, firmware 2026) permanently connected answers `chargeStatus: 0`, and for
+* its whole life it was reported as NOT charging.
+*
+* That `adapterStatus` is a real signal and not a constant is MEASURED: on
+* 2026-09-05 the operator unplugged device 3628 and the raw payload
+* went from `adapterStatus: 1` to `0`, with `chargeStatus: 0` on both
+* sides — i.e. `chargeStatus` alone does NOT distinguish the two states.
+*
+* Two absent fields are NOT `'none'`: `'none'` is a negative the firmware
+* has stated ("no adapter, cell stopped"), the absence of both is
+* `'unknown'` — the same boundary `percentage` closed by becoming
+* `nullable` (D315). The caller (`mapBatteryInfo`) does not arrive here with a
+* push that says nothing about power: `reportsPowerSource` filters it out first and
+* keeps the previous belief.
 */
 function deriveChargingSource(adapterStatus, chargeStatus) {
 	if (adapterStatus === void 0 && chargeStatus === void 0) return "unknown";

package/dist/addon.mjs

@@ -7496,7 +7496,7 @@ var DeviceRole = /* @__PURE__ */ function(DeviceRole) {
 	return DeviceRole;
 }({});
 //#endregion
-//#region ../types/dist/composition-43aqsZQj.mjs
+//#region ../types/dist/composition-D7ULvLdD.mjs
 /**
 * The ffmpeg build every CamStack node downloads, per platform and arch.
 *
@@ -7550,20 +7550,20 @@ function portable(target) {
 }
 portable("linux64"), portable("linuxarm64"), portable("macarm64"), portable("mac64");
 /**
-* LA tabella "quale booleano di questo tipo di device conta come ALTO", e il
-* valutatore puro del suo FRONTE.
+* THE table "which boolean of this device type counts as HIGH", and the
+* pure evaluator of its EDGE.
 *
-* UNA tabella per tutti quelli che chiedono "questo device è ALTO?": il
-* trigger `RecordingTriggers.sensorDeviceIds` del recorder, i marker dei
-* sensori della post-analysis, il bridge camera-sensors dell'orchestratore e
-* le sorgenti di un campanello composto (`doorbellFeatureSources`, D671).
-* Una seconda copia divergerebbe alla prima cap aggiunta, e il sintomo — "il
-* sensore fa suonare il campanello ma non registra" — è esattamente D62.
+* ONE table for everyone who asks "is this device HIGH?": the
+* recorder's `RecordingTriggers.sensorDeviceIds` trigger, the post-analysis
+* sensor markers, the orchestrator's camera-sensors bridge and
+* the sources of a composite doorbell (`doorbellFeatureSources`, D671).
+* A second copy would diverge at the first cap added, and the symptom — "the
+* sensor rings the doorbell but does not record" — is exactly D62.
 *
-* ⚠ NON è `DEVICE_STATE_READERS` (`catalogs/device-state-vocabulary.ts`), e le
-* due non vanno unificate: quella risponde a "qual è la PAROLA di stato per una
-* regola" (e include `presence`, `cover`, `alarm-panel`), questa a "qual è il
-* booleano il cui FRONTE conta". Vocabolari deliberatamente diversi.
+* ⚠ NOT `DEVICE_STATE_READERS` (`catalogs/device-state-vocabulary.ts`), and the
+* two must not be unified: that one answers "what is the state WORD for a
+* rule" (and includes `presence`, `cover`, `alarm-panel`), this one "which
+* boolean's EDGE counts". Deliberately different vocabularies.
 */
 /**
 * Known binary / switch source caps → the boolean slice field whose
@@ -9190,22 +9190,22 @@ var CLASS_MAP_MACRO_TARGETS = [
 	"package"
 ];
 /**
-* Le macro classi di PRIMO LIVELLO: quelle che un object detector emette e che
-* un operatore può selezionare.
+* The FIRST-LEVEL macro classes: those an object detector emits and that
+* an operator can select.
 *
-* Sono le tre offerte dallo step `object-detection`
+* They are the three offered by the `object-detection` step
 * (`addon-pipeline/src/detection-pipeline/registry/step-definitions.ts`,
-* `enabledMacroClasses`). `package` sta in {@link CLASS_MAP_MACRO_TARGETS} e in
-* `MACRO_LABELS` — è una macro vera — ma NON qui: appartiene allo step
-* `package-detection`, la cui abilitazione è guidata dalle zone, e offrire la
-* stessa parola due volte ha già fatto accendere a un operatore il proxy COCO
+* `enabledMacroClasses`). `package` is in {@link CLASS_MAP_MACRO_TARGETS} and in
+* `MACRO_LABELS` — it is a true macro — but NOT here: it belongs to the step
+* `package-detection`, whose enablement is driven by zones, and offering the
+* same word twice has already made an operator turn on the COCO proxy
 * (suitcase/backpack/handbag) lasciando spento il detector dedicato.
 *
-* UNA lista. Prima di oggi le stesse tre erano scritte a mano nell'offerta
-* dello step e una seconda volta come union `FirstLevelMacro`
-* (`types/detection.ts`); una terza copia per il trigger di registrazione
-* (`RecordingTriggers.objectClasses`) avrebbe reso invisibile la divergenza
-* successiva.
+* ONE list. Before today the same three were hand-written in the step's offer
+* and a second time as the union `FirstLevelMacro`
+* (`types/detection.ts`); a third copy for the recording trigger
+* (`RecordingTriggers.objectClasses`) would have made the later divergence
+* invisible.
 */
 var FIRST_LEVEL_MACRO_CLASSES = [
 	"person",
@@ -9270,17 +9270,17 @@ var RecordingStorageModeSchema = _enum([
 	"on-device-decision"
 ]);
 /**
-* Le macro classi che possono aprire una finestra di registrazione — le stesse
-* tre offerte dallo step `object-detection`, da UNA lista
+* The macro classes that can open a recording window — the same
+* three offered by the `object-detection` step, from ONE list
 * ({@link FIRST_LEVEL_MACRO_CLASSES}).
 */
 var RecordingObjectTriggerClassSchema = _enum(FIRST_LEVEL_MACRO_CLASSES);
 /**
-* True quando `values` non ripete un elemento.
+* True when `values` does not repeat an element.
 *
-* Un duplicato non è innocuo: ogni voce di `objectClasses` / `sensorDeviceIds`
-* diventa una SORGENTE in `bandTriggerSources`, e la stessa sorgente due volte
-* conterebbe due volte le sue finestre in `segmentMissedByMs`.
+* A duplicate is not harmless: every entry of `objectClasses` / `sensorDeviceIds`
+* becomes a SOURCE in `bandTriggerSources`, and the same source twice
+* would count its windows twice in `segmentMissedByMs`.
 */
 var noDuplicates = (values) => new Set(values).size === values.length;
 /** Which detectors trigger an `events`-mode band. */
@@ -9288,34 +9288,34 @@ var RecordingTriggersSchema = object({
 	motion: boolean().optional(),
 	audioThresholdDbfs: number().optional(),
 	/**
-	* Le macro classi la cui detection apre una finestra. ASSENTE = la sorgente
-	* non è ascoltata; un array VUOTO è rifiutato, perché "banda events, trigger
-	* object acceso, nessuna classe" è la stessa forma "abilitata e non registra
-	* nulla, per sempre" contro cui è scritto `eventsBandCanEverDemand`.
+	* The macro classes whose detection opens a window. ABSENT = the source
+	* is not listened to; an EMPTY array is rejected, because "events band, object
+	* trigger on, no class" is the same shape "enabled and records
+	* nothing, forever" that `eventsBandCanEverDemand` is written against.
 	*
-	* Il segnale letto è GIÀ FILTRATO: solo detection `source: 'pipeline'`, cioè
-	* quelle che hanno attraversato `enabledMacroClasses`, i
-	* `minConfidence<Macro>` e il full-frame guard. L'AI a bordo camera
-	* (`source: 'onboard'`) non attraversa nessuno di quei gate e NON apre
-	* finestre — vedi `recorder/object-trigger.ts`.
+	* The signal read is ALREADY FILTERED: only `source: 'pipeline'` detections, i.e.
+	* those that went through `enabledMacroClasses`, the
+	* `minConfidence<Macro>` and the full-frame guard. The camera's onboard AI
+	* (`source: 'onboard'`) goes through none of those gates and does NOT open
+	* windows — see `recorder/object-trigger.ts`.
 	*/
 	objectClasses: array(RecordingObjectTriggerClassSchema).min(1).refine(noDuplicates, { message: "objectClasses must not repeat a class" }).optional(),
 	/**
-	* I device LINKED il cui FRONTE ALTO apre una finestra. Assente = la sorgente
-	* non è ascoltata; un array vuoto è rifiutato per la stessa ragione di
+	* The LINKED devices whose RISING EDGE opens a window. Absent = the source
+	* is not listened to; an empty array is rejected for the same reason as
 	* `objectClasses`.
 	*
-	* Sono id di device SORGENTE, non camere: la banda li nomina, quindi il
-	* percorso caldo (`DeviceStateChanged`, a ritmo di bus su tutta la flotta)
-	* non fa RPC. L'OFFERTA da cui l'operatore li sceglie è un'altra domanda, e
-	* si risolve con `deviceManager.getLinkedDevices` + `getBindingsBatch` per
-	* device (D12) — mai un elenco globale di cap.
+	* These are SOURCE device ids, not cameras: the band names them, so the
+	* hot path (`DeviceStateChanged`, at bus rate across the whole fleet)
+	* does no RPC. The OFFER from which the operator picks them is another question, and
+	* is resolved with `deviceManager.getLinkedDevices` + `getBindingsBatch` per
+	* device (D12) — never a global list of caps.
 	*
-	* Cosa vuol dire "alto" dipende dal TIPO di device e non è deciso qui:
-	* `SOURCE_CAP_ACTIVE_FIELD` (`catalogs/sensor-active-state.ts`) è LA tabella,
-	* la stessa del campanello composto (D671). Ed è il FRONTE, non
-	* il livello: un contatto trovato già aperto al riavvio del runner non fa
-	* registrare.
+	* What "high" means depends on the device TYPE and is not decided here:
+	* `SOURCE_CAP_ACTIVE_FIELD` (`catalogs/sensor-active-state.ts`) is THE table,
+	* the same one as the composite doorbell (D671). And it is the EDGE, not
+	* the level: a contact found already open at runner restart does not
+	* record.
 	*/
 	sensorDeviceIds: array(number().int().positive()).min(1).max(16).refine(noDuplicates, { message: "sensorDeviceIds must not repeat a device" }).optional()
 });
@@ -10567,7 +10567,7 @@ function findTimezone(id) {
 * - **VALUE** — at which level, for which scope, until when. That stays ONE
 *   thing: the logging settings document on the `system` cap. Two authorities
 *   over the values is the exact defect
-*   `docs/design/plans/2026-08-26-logging-per-componente.md` was written to
+*   `docs/design/plans/2026-08-26-per-component-logging.md` was written to
 *   remove; re-introducing it from the cure side would be grotesque.
 *
 * Nothing in this file reads a clock, an env var or a store. The registry is
@@ -14479,7 +14479,7 @@ method(_void(), EngineInfoSchema, { auth: "admin" }), method(object({
 	*
 	* ⚠ An earlier version of this comment blamed Zod stripping, and that
 	* was wrong — corrected 2026-08-26 after the hop map
-	* (`docs/design/2026-08-26-mappa-hop-argomenti.md`) traced the path.
+	* (`docs/design/2026-08-26-topic-hop-map.md`) traced the path.
 	* There is **no Zod parse at all** between the door and the engine: the
 	* dispatcher forwards the payload verbatim and UDS carries it whole. A
 	* field declared here reaches `SqliteSettingsBackend` either way.
@@ -16682,7 +16682,7 @@ method(object({
 * per-device window, `KeyFrameCaptureLog`, `bumpCropMetric`. Every one of them
 * ends in a log line, and a log line is the thing the operator asked to stop
 * needing: *"possiamo armare questi errori intanto? Così al prossimo giro
-* ricontrolliamo tutti questi punti"*. Reading them meant grepping Loki and
+* ricontrolliamo tutti questi punti"* [can we instrument these errors in the meantime? That way next round we recheck all these points]. Reading them meant grepping Loki and
 * hand-correlating timestamps, which is how a 22% thumbnail gap and a 3-hour
 * media blackout were both diagnosed. The counters stay; this is where they can
 * be READ.
@@ -22429,14 +22429,14 @@ var TrackSchema = object({
 	* `derive-returned-null tile=standin`,
 	* `native-tile tile=native no-key-frame-at-close`, …) written at close and
 	* CLEARED by the late-keyFrame upgrade when a native tile lands after all.
-	* The operator-facing answer to "perché manca l'immagine?" on a track whose
+	* The operator-facing answer to "perché manca l'immagine?" [why is the image missing?] on a track whose
 	* tile is a face/plate stand-in, a raster crop, or an icon.
 	*
 	* **`no-key-frame-at-close` (D400).** The line used to be written ONLY when
 	* the TILE ranked below native, so a track whose thumbnail landed natively
 	* while its key frame missed carried no reason at all — three of the four
 	* `MISSING_KEYFRAME` tracks in the 2026-09-07 operator audit were exactly
-	* that shape, and their "niente ultimo" had no cause anywhere on the row.
+	* that shape, and their "niente ultimo" [no last frame] had no cause anywhere on the row.
 	* The key frame is the head of a cascade (`keyFrame ⇒ keyFrameSmall ⇒ the
 	* lastFrame copy source`), so its absence is now on this line whatever the
 	* tile ended up being.
@@ -22523,7 +22523,7 @@ var MotionEventSchema = object({
 	/**
 	* Ms offsets from `timestamp` (the episode's own first rising edge, so the
 	* first entry is always `0`) of every genuine off→on transition the
-	* episode saw — "ogni evento on si deve salvare" (D475). NOT one entry per
+	* episode saw — "ogni evento on si deve salvare" [every ON event must be saved] (D475). NOT one entry per
 	* push: a firmware source that keepalives at ~1 Hz for the whole burst
 	* (Reolink, Hikvision) produces exactly one edge; a source that reports an
 	* explicit `false` mid-episode and then resumes before the quiet window
@@ -27980,7 +27980,7 @@ var ClipPlaybackSchema = object({
 * **One authorised yes is one wake.** `next-natural` — take the clip the next
 * time the camera is awake for its own reasons — is deliberately not a member:
 * it was proposed, it is free on the battery, and the operator declined it on
-* 2026-09-20 (*"Quando un export viene richiesto si sveglia la camera."*,
+* 2026-09-20 (*"Quando un export viene richiesto si sveglia la camera."* [When an export is requested the camera wakes up],
 * D558 "Considered and not taken").
 */
 var ClipWakeSchema = _enum(["authorised"]);
@@ -28376,7 +28376,7 @@ var videoclipsCapability = {
 	* **It is a SECTION of the Recording tab, at the end of it — not a tab of
 	* its own.** It shipped as a `clips` top-tab and the operator rejected the
 	* placement: *"utilizzerei la stessa tab recordings, lì abbiamo già tutto il
-	* necessario, una nuova sezione alla fine per le clips"*. The Recording tab
+	* necessario, una nuova sezione alla fine per le clips"* [I would use the same recordings tab, there we already have everything necessary, a new section at the end for the clips]. The Recording tab
 	* already holds the recorder's panel, the schedule bands and the unified
 	* retention policy; footage the camera itself holds is the same question,
 	* asked of a different store. `order: 100` puts it after all of them with
@@ -28437,7 +28437,7 @@ var videoclipsCapability = {
 			* It replaced `sources?: string[]`, a VIEW filter over source ids that
 			* assumed the answer was a fan-out over everything a camera has. The
 			* operator settled otherwise on 2026-09-20 — *"l'utilizzatore è uno
-			* solo"* — so the list is asked of one provider at a time and there is
+			* solo"* [there is only one user] — so the list is asked of one provider at a time and there is
 			* nothing to filter out of it.
 			*/
 			provider: string().min(1)
@@ -36758,7 +36758,7 @@ var ReadGopBytesResultSchema = object({
 /**
 * A time WINDOW of one finalized segment, cut by byte range — the multi-GOP
 * twin of {@link ReadGopBytesResultSchema}'s single instant. Built for the
-* replay clip's `recording` source (`docs/design/plans/2026-08-26-replay-clip-su-pipeline.md`):
+* replay clip's `recording` source (`docs/design/plans/2026-08-26-clip-replay-on-pipeline.md`):
 * a replay needs several seconds of native pixels, not one frame.
 *
 * `ok.data` is standalone-demuxable, same as a GOP read. `ok.reachesRequestedEnd`
@@ -53460,7 +53460,7 @@ var PreviewTextField = string().max(200);
 * Whether the notification's preview is a STILL or a short animation.
 *
 * The operator's ask, verbatim: *"inviato come gif o video (come per le altre
-* rule)"* — the other rules already offer an animated preview, and a ten-hour
+* rule)"* [sent as a gif or video (as for the other rules)] — the other rules already offer an animated preview, and a ten-hour
 * night reads better as three seconds of motion than as one frame of it. Both
 * modes get the SAME treatment (blurred frame, large centred title); `'gif'`
 * simply applies it to a dozen frames sampled across the render and assembles
@@ -161129,37 +161129,37 @@ function buildOnboardWrites(patch, schedule) {
 //#endregion
 //#region src/battery-charging.ts
 /**
-* Da `adapterStatus` + `chargeStatus` alla sorgente di alimentazione.
-*
-* I due campi rispondono a DUE domande diverse, e confonderle è il bug che
-* questo modulo esiste per chiudere:
-*
-*  - `adapterStatus` — l'alimentazione è COLLEGATA? Il firmware manda 0/1/2
-*    (nessuna · adattatore DC · pannello solare) e il confine dell'hub lo
-*    traduce in `'none' | 'dc' | 'solarPanel'` (`mapHubChargeStatus` e
-*    `mapHubAdapterStatus` in `reolink-hub.ts`), perché il vocabolario del
-*    percorso standalone è già a stringhe.
-*  - `chargeStatus` — la CELLA cosa sta facendo? 0 ferma · 1 in carica ·
-*    2 carica completa.
-*
-* La vecchia derivazione consultava l'adattatore SOLO per cercarci 'solar', e
-* un DC collegato cadeva nel ripiego `'none'`. Due Argus 3E lo nascondevano per
-* caso: piene e collegate rispondono `chargeStatus: 2`, che il ramo `isCharging`
-* mappava su `'dc'` per la ragione sbagliata. La Argus MagiCam (batteryVersion
-* 1, firmware 2026) collegata in permanenza risponde `chargeStatus: 0`, e per
-* tutta la sua vita è stata riportata NON in carica.
-*
-* Che `adapterStatus` sia un segnale vero e non una costante è MISURATO: il
-* 2026-09-05 l'operatore ha staccato il device 3628 e il payload grezzo è
-* passato da `adapterStatus: 1` a `0`, con `chargeStatus: 0` da entrambe le
-* parti — cioè `chargeStatus` da solo NON distingue i due stati.
-*
-* Due campi assenti NON sono `'none'`: `'none'` è un negativo che il firmware
-* ha detto ("nessun adattatore, cella ferma"), l'assenza di entrambi è
-* `'unknown'` — lo stesso confine che `percentage` ha chiuso diventando
-* `nullable` (D315). Il chiamante (`mapBatteryInfo`) non arriva qui con un
-* push che non parla di alimentazione: `reportsPowerSource` lo filtra prima e
-* conserva la convinzione precedente.
+* From `adapterStatus` + `chargeStatus` to the power source.
+*
+* The two fields answer TWO different questions, and confusing them is the bug that
+* this module exists to close:
+*
+*  - `adapterStatus` — is the power CONNECTED? The firmware sends 0/1/2
+*    (none · DC adapter · solar panel) and the hub boundary
+*    translates it into `'none' | 'dc' | 'solarPanel'` (`mapHubChargeStatus` and
+*    `mapHubAdapterStatus` in `reolink-hub.ts`), because the vocabulary of the
+*    standalone path is already strings.
+*  - `chargeStatus` — what is the CELL doing? 0 stopped · 1 charging ·
+*    2 fully charged.
+*
+* The old derivation consulted the adapter ONLY to look for 'solar' in it, and
+* a connected DC fell into the fallback `'none'`. Two Argus 3E units hid it by
+* chance: full and connected they answer `chargeStatus: 2`, which the `isCharging`
+* branch mapped to `'dc'` for the wrong reason. The Argus MagiCam (batteryVersion
+* 1, firmware 2026) permanently connected answers `chargeStatus: 0`, and for
+* its whole life it was reported as NOT charging.
+*
+* That `adapterStatus` is a real signal and not a constant is MEASURED: on
+* 2026-09-05 the operator unplugged device 3628 and the raw payload
+* went from `adapterStatus: 1` to `0`, with `chargeStatus: 0` on both
+* sides — i.e. `chargeStatus` alone does NOT distinguish the two states.
+*
+* Two absent fields are NOT `'none'`: `'none'` is a negative the firmware
+* has stated ("no adapter, cell stopped"), the absence of both is
+* `'unknown'` — the same boundary `percentage` closed by becoming
+* `nullable` (D315). The caller (`mapBatteryInfo`) does not arrive here with a
+* push that says nothing about power: `reportsPowerSource` filters it out first and
+* keeps the previous belief.
 */
 function deriveChargingSource(adapterStatus, chargeStatus) {
 	if (adapterStatus === void 0 && chargeStatus === void 0) return "unknown";

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@camstack/addon-provider-reolink",
-  "version": "1.2.168",
+  "version": "1.2.169",
   "description": "Reolink camera device provider addon for CamStack — native Baichuan protocol",
   "keywords": [
     "camstack",