@camstack/addon-provider-rademacher 0.2.74 → 0.2.75

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/dist/addon.js CHANGED
@@ -8834,17 +8834,29 @@ var HHMM = /^([01]\d|2[0-3]):[0-5]\d$/;
8834
8834
  /**
8835
8835
  * DERIVED per-camera storage summary — the single field cheap consumers read
8836
8836
  * (the viewer's status dot, the camera list) instead of walking `bands`:
8837
- * - `off` — no band covers the camera (or it is disabled).
8838
- * - `events` — every band records around triggers only.
8839
- * - `continuous` — at least one band records continuously.
8840
- *
8841
- * NEVER authored: the recorder stamps it from the authoritative `bands` on
8842
- * every save (`activeModeForConfig`). Writing it has no effect.
8837
+ * - `off` — no band covers the camera (or it is disabled).
8838
+ * - `events` — every band records around triggers only.
8839
+ * - `continuous` — at least one band records continuously.
8840
+ * - `on-device-decision`— the DEVICE decides: recording runs for as long as the
8841
+ * camera raises its own `recording-signal` level (a robot that cleans). There
8842
+ * is no schedule to author, because there is no hour to program — see
8843
+ * {@link RecordingConfigSchema}`.deviceDecision`.
8844
+ *
8845
+ * NEVER authored: the recorder stamps it from the authoritative intent
8846
+ * (`bands` + `deviceDecision`) on every save (`activeModeForConfig`). Writing it
8847
+ * has no effect.
8848
+ *
8849
+ * `on-device-decision` is named for WHO decides, not for how the recording is
8850
+ * requested. `on-demand` was rejected: in this repo's vocabulary a "demand" is
8851
+ * something the operator makes (the live gate is the recorder's own "demand
8852
+ * window"), and a knob whose name suggests the operator starts it while the
8853
+ * device actually does is the D62 shape — a control nobody can predict.
8843
8854
  */
8844
8855
  var RecordingStorageModeSchema = _enum([
8845
8856
  "off",
8846
8857
  "events",
8847
- "continuous"
8858
+ "continuous",
8859
+ "on-device-decision"
8848
8860
  ]);
8849
8861
  /**
8850
8862
  * Le macro classi che possono aprire una finestra di registrazione — le stesse
@@ -8894,22 +8906,7 @@ var RecordingTriggersSchema = object({
8894
8906
  * il livello: un contatto trovato già aperto al riavvio del runner non fa
8895
8907
  * registrare.
8896
8908
  */
8897
- sensorDeviceIds: array(number().int().positive()).min(1).max(16).refine(noDuplicates, { message: "sensorDeviceIds must not repeat a device" }).optional(),
8898
- /**
8899
- * La camera registra per tutta la durata del SEGNALE che lei stessa
8900
- * pubblica — la cap `recording-signal` (`active: true` mentre il device è in
8901
- * funzione: un robot che pulisce). È un LIVELLO, non un fronte: la finestra
8902
- * resta aperta finché il segnale è alto e si chiude `postBufferSec` dopo la
8903
- * caduta, così una pulizia di quaranta minuti è UNA clip.
8904
- *
8905
- * Non nomina un device: il segnale è della camera stessa, tenuto fresco dal
8906
- * suo provider (D224); il recorder lo ascolta su `DeviceStateChanged` e lo
8907
- * riconcilia leggendo la slice via RPC, con un tetto oltre il quale un
8908
- * segnale mai abbassato (un evento perso) non può tenere aperta una
8909
- * registrazione (D11). Vedi `recorder/addon/band-decision.ts`
8910
- * (`holdTrigger` / `releaseTrigger`).
8911
- */
8912
- deviceSignal: boolean().optional()
8909
+ sensorDeviceIds: array(number().int().positive()).min(1).max(16).refine(noDuplicates, { message: "sensorDeviceIds must not repeat a device" }).optional()
8913
8910
  });
8914
8911
  /**
8915
8912
  * Mode of a single recording band — the recorder per-band vocabulary.
@@ -8993,8 +8990,29 @@ var RecordingConfigSchema = object({
8993
8990
  * "off" is the absence of a covering band, never a band value.
8994
8991
  */
8995
8992
  bands: array(RecordingBandSchema).default([]),
8993
+ /**
8994
+ * THE device-decided intent: record for as long as the camera itself raises
8995
+ * `recording-signal` (`active: true` while the device is in function — a
8996
+ * robot that cleans). AUTHORED, unlike `mode`, and the only authored
8997
+ * recording intent that is not a band.
8998
+ *
8999
+ * It carries NO schedule on purpose. A band is an HOUR, and this feature has
9000
+ * no hour to program: the device decides. What it costs the operator is one
9001
+ * flag — "this camera can record on its own" — and what it buys is the same
9002
+ * hold/release the recorder already implements (D371, `holdTrigger` /
9003
+ * `releaseTrigger`): the window opens on the rise, stays open for the whole
9004
+ * job however long it is, and closes one pad after the fall.
9005
+ *
9006
+ * EXCLUSIVE with `bands` (below): two authorities deciding when the same
9007
+ * camera records is the D62 failure. `off` remains `enabled: false`, so an
9008
+ * operator switching this camera off is REPORTED off, never as broken.
9009
+ */
9010
+ deviceDecision: boolean().optional(),
8996
9011
  retention: RecordingRetentionSchema.optional()
8997
- }).strict();
9012
+ }).strict().refine((config) => config.deviceDecision !== true || config.bands.length === 0, {
9013
+ message: "deviceDecision is a whole-config mode and carries no schedule: it cannot be combined with bands",
9014
+ path: ["bands"]
9015
+ });
8998
9016
  /**
8999
9017
  * Entity-relocation job state (storage entity-routing spec, Phase 4).
9000
9018
  *
@@ -22010,11 +22028,7 @@ var CameraAudioStatusSchema = object({
22010
22028
  });
22011
22029
  /** Recording block — null when no recording cap is active for this device. */
22012
22030
  var CameraRecordingStatusSchema = object({
22013
- mode: _enum([
22014
- "off",
22015
- "continuous",
22016
- "events"
22017
- ]),
22031
+ mode: RecordingStorageModeSchema,
22018
22032
  active: boolean(),
22019
22033
  storageBytes: number()
22020
22034
  });
@@ -30268,11 +30282,10 @@ DeviceType.Camera, DeviceType.Sensor, DeviceType.Switch, method(object({ deviceI
30268
30282
  var RecordingStatusSchema = object({
30269
30283
  deviceId: number(),
30270
30284
  enabled: boolean(),
30271
- activeMode: _enum([
30272
- "off",
30273
- "continuous",
30274
- "events"
30275
- ]),
30285
+ /** THE derived storage mode, from the one definition
30286
+ * (`deriveRecordingMode`) — never a second enum. A duplicated list is how
30287
+ * `on-device-decision` could have reached the recorder and not the status. */
30288
+ activeMode: RecordingStorageModeSchema,
30276
30289
  nodeId: string(),
30277
30290
  storageBytes: number()
30278
30291
  });
package/dist/addon.mjs CHANGED
@@ -8833,17 +8833,29 @@ var HHMM = /^([01]\d|2[0-3]):[0-5]\d$/;
8833
8833
  /**
8834
8834
  * DERIVED per-camera storage summary — the single field cheap consumers read
8835
8835
  * (the viewer's status dot, the camera list) instead of walking `bands`:
8836
- * - `off` — no band covers the camera (or it is disabled).
8837
- * - `events` — every band records around triggers only.
8838
- * - `continuous` — at least one band records continuously.
8839
- *
8840
- * NEVER authored: the recorder stamps it from the authoritative `bands` on
8841
- * every save (`activeModeForConfig`). Writing it has no effect.
8836
+ * - `off` — no band covers the camera (or it is disabled).
8837
+ * - `events` — every band records around triggers only.
8838
+ * - `continuous` — at least one band records continuously.
8839
+ * - `on-device-decision`— the DEVICE decides: recording runs for as long as the
8840
+ * camera raises its own `recording-signal` level (a robot that cleans). There
8841
+ * is no schedule to author, because there is no hour to program — see
8842
+ * {@link RecordingConfigSchema}`.deviceDecision`.
8843
+ *
8844
+ * NEVER authored: the recorder stamps it from the authoritative intent
8845
+ * (`bands` + `deviceDecision`) on every save (`activeModeForConfig`). Writing it
8846
+ * has no effect.
8847
+ *
8848
+ * `on-device-decision` is named for WHO decides, not for how the recording is
8849
+ * requested. `on-demand` was rejected: in this repo's vocabulary a "demand" is
8850
+ * something the operator makes (the live gate is the recorder's own "demand
8851
+ * window"), and a knob whose name suggests the operator starts it while the
8852
+ * device actually does is the D62 shape — a control nobody can predict.
8842
8853
  */
8843
8854
  var RecordingStorageModeSchema = _enum([
8844
8855
  "off",
8845
8856
  "events",
8846
- "continuous"
8857
+ "continuous",
8858
+ "on-device-decision"
8847
8859
  ]);
8848
8860
  /**
8849
8861
  * Le macro classi che possono aprire una finestra di registrazione — le stesse
@@ -8893,22 +8905,7 @@ var RecordingTriggersSchema = object({
8893
8905
  * il livello: un contatto trovato già aperto al riavvio del runner non fa
8894
8906
  * registrare.
8895
8907
  */
8896
- sensorDeviceIds: array(number().int().positive()).min(1).max(16).refine(noDuplicates, { message: "sensorDeviceIds must not repeat a device" }).optional(),
8897
- /**
8898
- * La camera registra per tutta la durata del SEGNALE che lei stessa
8899
- * pubblica — la cap `recording-signal` (`active: true` mentre il device è in
8900
- * funzione: un robot che pulisce). È un LIVELLO, non un fronte: la finestra
8901
- * resta aperta finché il segnale è alto e si chiude `postBufferSec` dopo la
8902
- * caduta, così una pulizia di quaranta minuti è UNA clip.
8903
- *
8904
- * Non nomina un device: il segnale è della camera stessa, tenuto fresco dal
8905
- * suo provider (D224); il recorder lo ascolta su `DeviceStateChanged` e lo
8906
- * riconcilia leggendo la slice via RPC, con un tetto oltre il quale un
8907
- * segnale mai abbassato (un evento perso) non può tenere aperta una
8908
- * registrazione (D11). Vedi `recorder/addon/band-decision.ts`
8909
- * (`holdTrigger` / `releaseTrigger`).
8910
- */
8911
- deviceSignal: boolean().optional()
8908
+ sensorDeviceIds: array(number().int().positive()).min(1).max(16).refine(noDuplicates, { message: "sensorDeviceIds must not repeat a device" }).optional()
8912
8909
  });
8913
8910
  /**
8914
8911
  * Mode of a single recording band — the recorder per-band vocabulary.
@@ -8992,8 +8989,29 @@ var RecordingConfigSchema = object({
8992
8989
  * "off" is the absence of a covering band, never a band value.
8993
8990
  */
8994
8991
  bands: array(RecordingBandSchema).default([]),
8992
+ /**
8993
+ * THE device-decided intent: record for as long as the camera itself raises
8994
+ * `recording-signal` (`active: true` while the device is in function — a
8995
+ * robot that cleans). AUTHORED, unlike `mode`, and the only authored
8996
+ * recording intent that is not a band.
8997
+ *
8998
+ * It carries NO schedule on purpose. A band is an HOUR, and this feature has
8999
+ * no hour to program: the device decides. What it costs the operator is one
9000
+ * flag — "this camera can record on its own" — and what it buys is the same
9001
+ * hold/release the recorder already implements (D371, `holdTrigger` /
9002
+ * `releaseTrigger`): the window opens on the rise, stays open for the whole
9003
+ * job however long it is, and closes one pad after the fall.
9004
+ *
9005
+ * EXCLUSIVE with `bands` (below): two authorities deciding when the same
9006
+ * camera records is the D62 failure. `off` remains `enabled: false`, so an
9007
+ * operator switching this camera off is REPORTED off, never as broken.
9008
+ */
9009
+ deviceDecision: boolean().optional(),
8995
9010
  retention: RecordingRetentionSchema.optional()
8996
- }).strict();
9011
+ }).strict().refine((config) => config.deviceDecision !== true || config.bands.length === 0, {
9012
+ message: "deviceDecision is a whole-config mode and carries no schedule: it cannot be combined with bands",
9013
+ path: ["bands"]
9014
+ });
8997
9015
  /**
8998
9016
  * Entity-relocation job state (storage entity-routing spec, Phase 4).
8999
9017
  *
@@ -22009,11 +22027,7 @@ var CameraAudioStatusSchema = object({
22009
22027
  });
22010
22028
  /** Recording block — null when no recording cap is active for this device. */
22011
22029
  var CameraRecordingStatusSchema = object({
22012
- mode: _enum([
22013
- "off",
22014
- "continuous",
22015
- "events"
22016
- ]),
22030
+ mode: RecordingStorageModeSchema,
22017
22031
  active: boolean(),
22018
22032
  storageBytes: number()
22019
22033
  });
@@ -30267,11 +30281,10 @@ DeviceType.Camera, DeviceType.Sensor, DeviceType.Switch, method(object({ deviceI
30267
30281
  var RecordingStatusSchema = object({
30268
30282
  deviceId: number(),
30269
30283
  enabled: boolean(),
30270
- activeMode: _enum([
30271
- "off",
30272
- "continuous",
30273
- "events"
30274
- ]),
30284
+ /** THE derived storage mode, from the one definition
30285
+ * (`deriveRecordingMode`) — never a second enum. A duplicated list is how
30286
+ * `on-device-decision` could have reached the recorder and not the status. */
30287
+ activeMode: RecordingStorageModeSchema,
30275
30288
  nodeId: string(),
30276
30289
  storageBytes: number()
30277
30290
  });
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@camstack/addon-provider-rademacher",
3
- "version": "0.2.74",
3
+ "version": "0.2.75",
4
4
  "description": "Rademacher HomePilot device-provider addon for CamStack — wraps the @apocaliss92/noderademacher local-hub client (roller shutters over the cover cap)",
5
5
  "keywords": [
6
6
  "camstack",