@camstack/addon-provider-wyze 0.2.78 → 0.2.80

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
@@ -7881,17 +7881,29 @@ var HHMM = /^([01]\d|2[0-3]):[0-5]\d$/;
7881
7881
  /**
7882
7882
  * DERIVED per-camera storage summary — the single field cheap consumers read
7883
7883
  * (the viewer's status dot, the camera list) instead of walking `bands`:
7884
- * - `off` — no band covers the camera (or it is disabled).
7885
- * - `events` — every band records around triggers only.
7886
- * - `continuous` — at least one band records continuously.
7887
- *
7888
- * NEVER authored: the recorder stamps it from the authoritative `bands` on
7889
- * every save (`activeModeForConfig`). Writing it has no effect.
7884
+ * - `off` — no band covers the camera (or it is disabled).
7885
+ * - `events` — every band records around triggers only.
7886
+ * - `continuous` — at least one band records continuously.
7887
+ * - `on-device-decision`— the DEVICE decides: recording runs for as long as the
7888
+ * camera raises its own `recording-signal` level (a robot that cleans). There
7889
+ * is no schedule to author, because there is no hour to program — see
7890
+ * {@link RecordingConfigSchema}`.deviceDecision`.
7891
+ *
7892
+ * NEVER authored: the recorder stamps it from the authoritative intent
7893
+ * (`bands` + `deviceDecision`) on every save (`activeModeForConfig`). Writing it
7894
+ * has no effect.
7895
+ *
7896
+ * `on-device-decision` is named for WHO decides, not for how the recording is
7897
+ * requested. `on-demand` was rejected: in this repo's vocabulary a "demand" is
7898
+ * something the operator makes (the live gate is the recorder's own "demand
7899
+ * window"), and a knob whose name suggests the operator starts it while the
7900
+ * device actually does is the D62 shape — a control nobody can predict.
7890
7901
  */
7891
7902
  var RecordingStorageModeSchema = _enum([
7892
7903
  "off",
7893
7904
  "events",
7894
- "continuous"
7905
+ "continuous",
7906
+ "on-device-decision"
7895
7907
  ]);
7896
7908
  /**
7897
7909
  * Le macro classi che possono aprire una finestra di registrazione — le stesse
@@ -7941,22 +7953,7 @@ var RecordingTriggersSchema = object({
7941
7953
  * il livello: un contatto trovato già aperto al riavvio del runner non fa
7942
7954
  * registrare.
7943
7955
  */
7944
- sensorDeviceIds: array(number().int().positive()).min(1).max(16).refine(noDuplicates, { message: "sensorDeviceIds must not repeat a device" }).optional(),
7945
- /**
7946
- * La camera registra per tutta la durata del SEGNALE che lei stessa
7947
- * pubblica — la cap `recording-signal` (`active: true` mentre il device è in
7948
- * funzione: un robot che pulisce). È un LIVELLO, non un fronte: la finestra
7949
- * resta aperta finché il segnale è alto e si chiude `postBufferSec` dopo la
7950
- * caduta, così una pulizia di quaranta minuti è UNA clip.
7951
- *
7952
- * Non nomina un device: il segnale è della camera stessa, tenuto fresco dal
7953
- * suo provider (D224); il recorder lo ascolta su `DeviceStateChanged` e lo
7954
- * riconcilia leggendo la slice via RPC, con un tetto oltre il quale un
7955
- * segnale mai abbassato (un evento perso) non può tenere aperta una
7956
- * registrazione (D11). Vedi `recorder/addon/band-decision.ts`
7957
- * (`holdTrigger` / `releaseTrigger`).
7958
- */
7959
- deviceSignal: boolean().optional()
7956
+ sensorDeviceIds: array(number().int().positive()).min(1).max(16).refine(noDuplicates, { message: "sensorDeviceIds must not repeat a device" }).optional()
7960
7957
  });
7961
7958
  /**
7962
7959
  * Mode of a single recording band — the recorder per-band vocabulary.
@@ -8040,8 +8037,29 @@ var RecordingConfigSchema = object({
8040
8037
  * "off" is the absence of a covering band, never a band value.
8041
8038
  */
8042
8039
  bands: array(RecordingBandSchema).default([]),
8040
+ /**
8041
+ * THE device-decided intent: record for as long as the camera itself raises
8042
+ * `recording-signal` (`active: true` while the device is in function — a
8043
+ * robot that cleans). AUTHORED, unlike `mode`, and the only authored
8044
+ * recording intent that is not a band.
8045
+ *
8046
+ * It carries NO schedule on purpose. A band is an HOUR, and this feature has
8047
+ * no hour to program: the device decides. What it costs the operator is one
8048
+ * flag — "this camera can record on its own" — and what it buys is the same
8049
+ * hold/release the recorder already implements (D371, `holdTrigger` /
8050
+ * `releaseTrigger`): the window opens on the rise, stays open for the whole
8051
+ * job however long it is, and closes one pad after the fall.
8052
+ *
8053
+ * EXCLUSIVE with `bands` (below): two authorities deciding when the same
8054
+ * camera records is the D62 failure. `off` remains `enabled: false`, so an
8055
+ * operator switching this camera off is REPORTED off, never as broken.
8056
+ */
8057
+ deviceDecision: boolean().optional(),
8043
8058
  retention: RecordingRetentionSchema.optional()
8044
- }).strict();
8059
+ }).strict().refine((config) => config.deviceDecision !== true || config.bands.length === 0, {
8060
+ message: "deviceDecision is a whole-config mode and carries no schedule: it cannot be combined with bands",
8061
+ path: ["bands"]
8062
+ });
8045
8063
  /**
8046
8064
  * Entity-relocation job state (storage entity-routing spec, Phase 4).
8047
8065
  *
@@ -21074,11 +21092,7 @@ var CameraAudioStatusSchema = object({
21074
21092
  });
21075
21093
  /** Recording block — null when no recording cap is active for this device. */
21076
21094
  var CameraRecordingStatusSchema = object({
21077
- mode: _enum([
21078
- "off",
21079
- "continuous",
21080
- "events"
21081
- ]),
21095
+ mode: RecordingStorageModeSchema,
21082
21096
  active: boolean(),
21083
21097
  storageBytes: number()
21084
21098
  });
@@ -29444,11 +29458,10 @@ DeviceType.Camera, DeviceType.Sensor, DeviceType.Switch, method(object({ deviceI
29444
29458
  var RecordingStatusSchema = object({
29445
29459
  deviceId: number(),
29446
29460
  enabled: boolean(),
29447
- activeMode: _enum([
29448
- "off",
29449
- "continuous",
29450
- "events"
29451
- ]),
29461
+ /** THE derived storage mode, from the one definition
29462
+ * (`deriveRecordingMode`) — never a second enum. A duplicated list is how
29463
+ * `on-device-decision` could have reached the recorder and not the status. */
29464
+ activeMode: RecordingStorageModeSchema,
29452
29465
  nodeId: string(),
29453
29466
  storageBytes: number()
29454
29467
  });
package/dist/addon.mjs CHANGED
@@ -7860,17 +7860,29 @@ var HHMM = /^([01]\d|2[0-3]):[0-5]\d$/;
7860
7860
  /**
7861
7861
  * DERIVED per-camera storage summary — the single field cheap consumers read
7862
7862
  * (the viewer's status dot, the camera list) instead of walking `bands`:
7863
- * - `off` — no band covers the camera (or it is disabled).
7864
- * - `events` — every band records around triggers only.
7865
- * - `continuous` — at least one band records continuously.
7866
- *
7867
- * NEVER authored: the recorder stamps it from the authoritative `bands` on
7868
- * every save (`activeModeForConfig`). Writing it has no effect.
7863
+ * - `off` — no band covers the camera (or it is disabled).
7864
+ * - `events` — every band records around triggers only.
7865
+ * - `continuous` — at least one band records continuously.
7866
+ * - `on-device-decision`— the DEVICE decides: recording runs for as long as the
7867
+ * camera raises its own `recording-signal` level (a robot that cleans). There
7868
+ * is no schedule to author, because there is no hour to program — see
7869
+ * {@link RecordingConfigSchema}`.deviceDecision`.
7870
+ *
7871
+ * NEVER authored: the recorder stamps it from the authoritative intent
7872
+ * (`bands` + `deviceDecision`) on every save (`activeModeForConfig`). Writing it
7873
+ * has no effect.
7874
+ *
7875
+ * `on-device-decision` is named for WHO decides, not for how the recording is
7876
+ * requested. `on-demand` was rejected: in this repo's vocabulary a "demand" is
7877
+ * something the operator makes (the live gate is the recorder's own "demand
7878
+ * window"), and a knob whose name suggests the operator starts it while the
7879
+ * device actually does is the D62 shape — a control nobody can predict.
7869
7880
  */
7870
7881
  var RecordingStorageModeSchema = _enum([
7871
7882
  "off",
7872
7883
  "events",
7873
- "continuous"
7884
+ "continuous",
7885
+ "on-device-decision"
7874
7886
  ]);
7875
7887
  /**
7876
7888
  * Le macro classi che possono aprire una finestra di registrazione — le stesse
@@ -7920,22 +7932,7 @@ var RecordingTriggersSchema = object({
7920
7932
  * il livello: un contatto trovato già aperto al riavvio del runner non fa
7921
7933
  * registrare.
7922
7934
  */
7923
- sensorDeviceIds: array(number().int().positive()).min(1).max(16).refine(noDuplicates, { message: "sensorDeviceIds must not repeat a device" }).optional(),
7924
- /**
7925
- * La camera registra per tutta la durata del SEGNALE che lei stessa
7926
- * pubblica — la cap `recording-signal` (`active: true` mentre il device è in
7927
- * funzione: un robot che pulisce). È un LIVELLO, non un fronte: la finestra
7928
- * resta aperta finché il segnale è alto e si chiude `postBufferSec` dopo la
7929
- * caduta, così una pulizia di quaranta minuti è UNA clip.
7930
- *
7931
- * Non nomina un device: il segnale è della camera stessa, tenuto fresco dal
7932
- * suo provider (D224); il recorder lo ascolta su `DeviceStateChanged` e lo
7933
- * riconcilia leggendo la slice via RPC, con un tetto oltre il quale un
7934
- * segnale mai abbassato (un evento perso) non può tenere aperta una
7935
- * registrazione (D11). Vedi `recorder/addon/band-decision.ts`
7936
- * (`holdTrigger` / `releaseTrigger`).
7937
- */
7938
- deviceSignal: boolean().optional()
7935
+ sensorDeviceIds: array(number().int().positive()).min(1).max(16).refine(noDuplicates, { message: "sensorDeviceIds must not repeat a device" }).optional()
7939
7936
  });
7940
7937
  /**
7941
7938
  * Mode of a single recording band — the recorder per-band vocabulary.
@@ -8019,8 +8016,29 @@ var RecordingConfigSchema = object({
8019
8016
  * "off" is the absence of a covering band, never a band value.
8020
8017
  */
8021
8018
  bands: array(RecordingBandSchema).default([]),
8019
+ /**
8020
+ * THE device-decided intent: record for as long as the camera itself raises
8021
+ * `recording-signal` (`active: true` while the device is in function — a
8022
+ * robot that cleans). AUTHORED, unlike `mode`, and the only authored
8023
+ * recording intent that is not a band.
8024
+ *
8025
+ * It carries NO schedule on purpose. A band is an HOUR, and this feature has
8026
+ * no hour to program: the device decides. What it costs the operator is one
8027
+ * flag — "this camera can record on its own" — and what it buys is the same
8028
+ * hold/release the recorder already implements (D371, `holdTrigger` /
8029
+ * `releaseTrigger`): the window opens on the rise, stays open for the whole
8030
+ * job however long it is, and closes one pad after the fall.
8031
+ *
8032
+ * EXCLUSIVE with `bands` (below): two authorities deciding when the same
8033
+ * camera records is the D62 failure. `off` remains `enabled: false`, so an
8034
+ * operator switching this camera off is REPORTED off, never as broken.
8035
+ */
8036
+ deviceDecision: boolean().optional(),
8022
8037
  retention: RecordingRetentionSchema.optional()
8023
- }).strict();
8038
+ }).strict().refine((config) => config.deviceDecision !== true || config.bands.length === 0, {
8039
+ message: "deviceDecision is a whole-config mode and carries no schedule: it cannot be combined with bands",
8040
+ path: ["bands"]
8041
+ });
8024
8042
  /**
8025
8043
  * Entity-relocation job state (storage entity-routing spec, Phase 4).
8026
8044
  *
@@ -21053,11 +21071,7 @@ var CameraAudioStatusSchema = object({
21053
21071
  });
21054
21072
  /** Recording block — null when no recording cap is active for this device. */
21055
21073
  var CameraRecordingStatusSchema = object({
21056
- mode: _enum([
21057
- "off",
21058
- "continuous",
21059
- "events"
21060
- ]),
21074
+ mode: RecordingStorageModeSchema,
21061
21075
  active: boolean(),
21062
21076
  storageBytes: number()
21063
21077
  });
@@ -29423,11 +29437,10 @@ DeviceType.Camera, DeviceType.Sensor, DeviceType.Switch, method(object({ deviceI
29423
29437
  var RecordingStatusSchema = object({
29424
29438
  deviceId: number(),
29425
29439
  enabled: boolean(),
29426
- activeMode: _enum([
29427
- "off",
29428
- "continuous",
29429
- "events"
29430
- ]),
29440
+ /** THE derived storage mode, from the one definition
29441
+ * (`deriveRecordingMode`) — never a second enum. A duplicated list is how
29442
+ * `on-device-decision` could have reached the recorder and not the status. */
29443
+ activeMode: RecordingStorageModeSchema,
29431
29444
  nodeId: string(),
29432
29445
  storageBytes: number()
29433
29446
  });
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@camstack/addon-provider-wyze",
3
- "version": "0.2.78",
3
+ "version": "0.2.80",
4
4
  "description": "Wyze camera device-provider addon for CamStack — wraps the @apocaliss92/wyze-bridge-js P2P/DTLS client, feeding the stream-broker via the pull-rfc4571 lazy-publish path (a structural twin of addon-provider-reolink)",
5
5
  "keywords": [
6
6
  "camstack",