@camstack/addon-provider-homematic 1.2.76 → 1.2.77

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
@@ -7858,17 +7858,29 @@ var HHMM = /^([01]\d|2[0-3]):[0-5]\d$/;
7858
7858
  /**
7859
7859
  * DERIVED per-camera storage summary — the single field cheap consumers read
7860
7860
  * (the viewer's status dot, the camera list) instead of walking `bands`:
7861
- * - `off` — no band covers the camera (or it is disabled).
7862
- * - `events` — every band records around triggers only.
7863
- * - `continuous` — at least one band records continuously.
7864
- *
7865
- * NEVER authored: the recorder stamps it from the authoritative `bands` on
7866
- * every save (`activeModeForConfig`). Writing it has no effect.
7861
+ * - `off` — no band covers the camera (or it is disabled).
7862
+ * - `events` — every band records around triggers only.
7863
+ * - `continuous` — at least one band records continuously.
7864
+ * - `on-device-decision`— the DEVICE decides: recording runs for as long as the
7865
+ * camera raises its own `recording-signal` level (a robot that cleans). There
7866
+ * is no schedule to author, because there is no hour to program — see
7867
+ * {@link RecordingConfigSchema}`.deviceDecision`.
7868
+ *
7869
+ * NEVER authored: the recorder stamps it from the authoritative intent
7870
+ * (`bands` + `deviceDecision`) on every save (`activeModeForConfig`). Writing it
7871
+ * has no effect.
7872
+ *
7873
+ * `on-device-decision` is named for WHO decides, not for how the recording is
7874
+ * requested. `on-demand` was rejected: in this repo's vocabulary a "demand" is
7875
+ * something the operator makes (the live gate is the recorder's own "demand
7876
+ * window"), and a knob whose name suggests the operator starts it while the
7877
+ * device actually does is the D62 shape — a control nobody can predict.
7867
7878
  */
7868
7879
  var RecordingStorageModeSchema = _enum([
7869
7880
  "off",
7870
7881
  "events",
7871
- "continuous"
7882
+ "continuous",
7883
+ "on-device-decision"
7872
7884
  ]);
7873
7885
  /**
7874
7886
  * Le macro classi che possono aprire una finestra di registrazione — le stesse
@@ -7918,22 +7930,7 @@ var RecordingTriggersSchema = object({
7918
7930
  * il livello: un contatto trovato già aperto al riavvio del runner non fa
7919
7931
  * registrare.
7920
7932
  */
7921
- sensorDeviceIds: array(number().int().positive()).min(1).max(16).refine(noDuplicates, { message: "sensorDeviceIds must not repeat a device" }).optional(),
7922
- /**
7923
- * La camera registra per tutta la durata del SEGNALE che lei stessa
7924
- * pubblica — la cap `recording-signal` (`active: true` mentre il device è in
7925
- * funzione: un robot che pulisce). È un LIVELLO, non un fronte: la finestra
7926
- * resta aperta finché il segnale è alto e si chiude `postBufferSec` dopo la
7927
- * caduta, così una pulizia di quaranta minuti è UNA clip.
7928
- *
7929
- * Non nomina un device: il segnale è della camera stessa, tenuto fresco dal
7930
- * suo provider (D224); il recorder lo ascolta su `DeviceStateChanged` e lo
7931
- * riconcilia leggendo la slice via RPC, con un tetto oltre il quale un
7932
- * segnale mai abbassato (un evento perso) non può tenere aperta una
7933
- * registrazione (D11). Vedi `recorder/addon/band-decision.ts`
7934
- * (`holdTrigger` / `releaseTrigger`).
7935
- */
7936
- deviceSignal: boolean().optional()
7933
+ sensorDeviceIds: array(number().int().positive()).min(1).max(16).refine(noDuplicates, { message: "sensorDeviceIds must not repeat a device" }).optional()
7937
7934
  });
7938
7935
  /**
7939
7936
  * Mode of a single recording band — the recorder per-band vocabulary.
@@ -8017,8 +8014,29 @@ var RecordingConfigSchema = object({
8017
8014
  * "off" is the absence of a covering band, never a band value.
8018
8015
  */
8019
8016
  bands: array(RecordingBandSchema).default([]),
8017
+ /**
8018
+ * THE device-decided intent: record for as long as the camera itself raises
8019
+ * `recording-signal` (`active: true` while the device is in function — a
8020
+ * robot that cleans). AUTHORED, unlike `mode`, and the only authored
8021
+ * recording intent that is not a band.
8022
+ *
8023
+ * It carries NO schedule on purpose. A band is an HOUR, and this feature has
8024
+ * no hour to program: the device decides. What it costs the operator is one
8025
+ * flag — "this camera can record on its own" — and what it buys is the same
8026
+ * hold/release the recorder already implements (D371, `holdTrigger` /
8027
+ * `releaseTrigger`): the window opens on the rise, stays open for the whole
8028
+ * job however long it is, and closes one pad after the fall.
8029
+ *
8030
+ * EXCLUSIVE with `bands` (below): two authorities deciding when the same
8031
+ * camera records is the D62 failure. `off` remains `enabled: false`, so an
8032
+ * operator switching this camera off is REPORTED off, never as broken.
8033
+ */
8034
+ deviceDecision: boolean().optional(),
8020
8035
  retention: RecordingRetentionSchema.optional()
8021
- }).strict();
8036
+ }).strict().refine((config) => config.deviceDecision !== true || config.bands.length === 0, {
8037
+ message: "deviceDecision is a whole-config mode and carries no schedule: it cannot be combined with bands",
8038
+ path: ["bands"]
8039
+ });
8022
8040
  /**
8023
8041
  * Entity-relocation job state (storage entity-routing spec, Phase 4).
8024
8042
  *
@@ -21100,11 +21118,7 @@ var CameraAudioStatusSchema = object({
21100
21118
  });
21101
21119
  /** Recording block — null when no recording cap is active for this device. */
21102
21120
  var CameraRecordingStatusSchema = object({
21103
- mode: _enum([
21104
- "off",
21105
- "continuous",
21106
- "events"
21107
- ]),
21121
+ mode: RecordingStorageModeSchema,
21108
21122
  active: boolean(),
21109
21123
  storageBytes: number()
21110
21124
  });
@@ -29358,11 +29372,10 @@ DeviceType.Camera, DeviceType.Sensor, DeviceType.Switch, method(object({ deviceI
29358
29372
  var RecordingStatusSchema = object({
29359
29373
  deviceId: number(),
29360
29374
  enabled: boolean(),
29361
- activeMode: _enum([
29362
- "off",
29363
- "continuous",
29364
- "events"
29365
- ]),
29375
+ /** THE derived storage mode, from the one definition
29376
+ * (`deriveRecordingMode`) — never a second enum. A duplicated list is how
29377
+ * `on-device-decision` could have reached the recorder and not the status. */
29378
+ activeMode: RecordingStorageModeSchema,
29366
29379
  nodeId: string(),
29367
29380
  storageBytes: number()
29368
29381
  });
package/dist/addon.mjs CHANGED
@@ -7859,17 +7859,29 @@ var HHMM = /^([01]\d|2[0-3]):[0-5]\d$/;
7859
7859
  /**
7860
7860
  * DERIVED per-camera storage summary — the single field cheap consumers read
7861
7861
  * (the viewer's status dot, the camera list) instead of walking `bands`:
7862
- * - `off` — no band covers the camera (or it is disabled).
7863
- * - `events` — every band records around triggers only.
7864
- * - `continuous` — at least one band records continuously.
7865
- *
7866
- * NEVER authored: the recorder stamps it from the authoritative `bands` on
7867
- * every save (`activeModeForConfig`). Writing it has no effect.
7862
+ * - `off` — no band covers the camera (or it is disabled).
7863
+ * - `events` — every band records around triggers only.
7864
+ * - `continuous` — at least one band records continuously.
7865
+ * - `on-device-decision`— the DEVICE decides: recording runs for as long as the
7866
+ * camera raises its own `recording-signal` level (a robot that cleans). There
7867
+ * is no schedule to author, because there is no hour to program — see
7868
+ * {@link RecordingConfigSchema}`.deviceDecision`.
7869
+ *
7870
+ * NEVER authored: the recorder stamps it from the authoritative intent
7871
+ * (`bands` + `deviceDecision`) on every save (`activeModeForConfig`). Writing it
7872
+ * has no effect.
7873
+ *
7874
+ * `on-device-decision` is named for WHO decides, not for how the recording is
7875
+ * requested. `on-demand` was rejected: in this repo's vocabulary a "demand" is
7876
+ * something the operator makes (the live gate is the recorder's own "demand
7877
+ * window"), and a knob whose name suggests the operator starts it while the
7878
+ * device actually does is the D62 shape — a control nobody can predict.
7868
7879
  */
7869
7880
  var RecordingStorageModeSchema = _enum([
7870
7881
  "off",
7871
7882
  "events",
7872
- "continuous"
7883
+ "continuous",
7884
+ "on-device-decision"
7873
7885
  ]);
7874
7886
  /**
7875
7887
  * Le macro classi che possono aprire una finestra di registrazione — le stesse
@@ -7919,22 +7931,7 @@ var RecordingTriggersSchema = object({
7919
7931
  * il livello: un contatto trovato già aperto al riavvio del runner non fa
7920
7932
  * registrare.
7921
7933
  */
7922
- sensorDeviceIds: array(number().int().positive()).min(1).max(16).refine(noDuplicates, { message: "sensorDeviceIds must not repeat a device" }).optional(),
7923
- /**
7924
- * La camera registra per tutta la durata del SEGNALE che lei stessa
7925
- * pubblica — la cap `recording-signal` (`active: true` mentre il device è in
7926
- * funzione: un robot che pulisce). È un LIVELLO, non un fronte: la finestra
7927
- * resta aperta finché il segnale è alto e si chiude `postBufferSec` dopo la
7928
- * caduta, così una pulizia di quaranta minuti è UNA clip.
7929
- *
7930
- * Non nomina un device: il segnale è della camera stessa, tenuto fresco dal
7931
- * suo provider (D224); il recorder lo ascolta su `DeviceStateChanged` e lo
7932
- * riconcilia leggendo la slice via RPC, con un tetto oltre il quale un
7933
- * segnale mai abbassato (un evento perso) non può tenere aperta una
7934
- * registrazione (D11). Vedi `recorder/addon/band-decision.ts`
7935
- * (`holdTrigger` / `releaseTrigger`).
7936
- */
7937
- deviceSignal: boolean().optional()
7934
+ sensorDeviceIds: array(number().int().positive()).min(1).max(16).refine(noDuplicates, { message: "sensorDeviceIds must not repeat a device" }).optional()
7938
7935
  });
7939
7936
  /**
7940
7937
  * Mode of a single recording band — the recorder per-band vocabulary.
@@ -8018,8 +8015,29 @@ var RecordingConfigSchema = object({
8018
8015
  * "off" is the absence of a covering band, never a band value.
8019
8016
  */
8020
8017
  bands: array(RecordingBandSchema).default([]),
8018
+ /**
8019
+ * THE device-decided intent: record for as long as the camera itself raises
8020
+ * `recording-signal` (`active: true` while the device is in function — a
8021
+ * robot that cleans). AUTHORED, unlike `mode`, and the only authored
8022
+ * recording intent that is not a band.
8023
+ *
8024
+ * It carries NO schedule on purpose. A band is an HOUR, and this feature has
8025
+ * no hour to program: the device decides. What it costs the operator is one
8026
+ * flag — "this camera can record on its own" — and what it buys is the same
8027
+ * hold/release the recorder already implements (D371, `holdTrigger` /
8028
+ * `releaseTrigger`): the window opens on the rise, stays open for the whole
8029
+ * job however long it is, and closes one pad after the fall.
8030
+ *
8031
+ * EXCLUSIVE with `bands` (below): two authorities deciding when the same
8032
+ * camera records is the D62 failure. `off` remains `enabled: false`, so an
8033
+ * operator switching this camera off is REPORTED off, never as broken.
8034
+ */
8035
+ deviceDecision: boolean().optional(),
8021
8036
  retention: RecordingRetentionSchema.optional()
8022
- }).strict();
8037
+ }).strict().refine((config) => config.deviceDecision !== true || config.bands.length === 0, {
8038
+ message: "deviceDecision is a whole-config mode and carries no schedule: it cannot be combined with bands",
8039
+ path: ["bands"]
8040
+ });
8023
8041
  /**
8024
8042
  * Entity-relocation job state (storage entity-routing spec, Phase 4).
8025
8043
  *
@@ -21101,11 +21119,7 @@ var CameraAudioStatusSchema = object({
21101
21119
  });
21102
21120
  /** Recording block — null when no recording cap is active for this device. */
21103
21121
  var CameraRecordingStatusSchema = object({
21104
- mode: _enum([
21105
- "off",
21106
- "continuous",
21107
- "events"
21108
- ]),
21122
+ mode: RecordingStorageModeSchema,
21109
21123
  active: boolean(),
21110
21124
  storageBytes: number()
21111
21125
  });
@@ -29359,11 +29373,10 @@ DeviceType.Camera, DeviceType.Sensor, DeviceType.Switch, method(object({ deviceI
29359
29373
  var RecordingStatusSchema = object({
29360
29374
  deviceId: number(),
29361
29375
  enabled: boolean(),
29362
- activeMode: _enum([
29363
- "off",
29364
- "continuous",
29365
- "events"
29366
- ]),
29376
+ /** THE derived storage mode, from the one definition
29377
+ * (`deriveRecordingMode`) — never a second enum. A duplicated list is how
29378
+ * `on-device-decision` could have reached the recorder and not the status. */
29379
+ activeMode: RecordingStorageModeSchema,
29367
29380
  nodeId: string(),
29368
29381
  storageBytes: number()
29369
29382
  });
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@camstack/addon-provider-homematic",
3
- "version": "1.2.76",
3
+ "version": "1.2.77",
4
4
  "description": "Homematic / HomematicIP (CCU3 / RaspberryMatic) device-provider addon for CamStack — wraps the nodehomematic library",
5
5
  "keywords": [
6
6
  "camstack",