@camstack/addon-provider-wyze 0.2.86 → 0.2.87

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
@@ -29355,8 +29355,27 @@ var PrivacyMaskRegionSchema = object({
29355
29355
  /** Current on-camera privacy state — mask master enable + zones + microphone. */
29356
29356
  var PrivacyMaskStatusSchema = object({
29357
29357
  enabled: boolean(),
29358
- /** Active zones (normalized 0..1). Length ≤ maxRegions. */
29359
- regions: array(PrivacyMaskRegionSchema),
29358
+ /**
29359
+ * Active zones (normalized 0..1). Length ≤ maxRegions.
29360
+ *
29361
+ * `null` means "no answer" — the provider has never reached this camera
29362
+ * (a cold `runtimeState` slice, a battery camera asleep) or the read
29363
+ * failed. A consumer must render it as UNKNOWN and never as "this camera
29364
+ * has no zones": those two look identical to an operator right up to the
29365
+ * moment one of them is acted on, and acting on them differs completely.
29366
+ * The switch group turned an unanswered read into *"nothing is set up for
29367
+ * it to act on"* — an instruction to go and draw a zone that already
29368
+ * exists — and this editor seeded an EMPTY canvas from it, one Save away
29369
+ * from deleting the mask it could not read.
29370
+ *
29371
+ * Empty-and-answered is `[]` and stays a real answer: this camera genuinely
29372
+ * has no zones. The distinction is the same one {@link
29373
+ * PrivacyMaskStatusSchema.shape.audioEnabled} already draws for the
29374
+ * microphone, on the very same payload — both planes come from ONE refresh,
29375
+ * so it was never coherent for one of them to be able to say "unknown"
29376
+ * while the other could not.
29377
+ */
29378
+ regions: array(PrivacyMaskRegionSchema).nullable(),
29360
29379
  /**
29361
29380
  * Is the camera capturing sound right now? Read from the camera, never from
29362
29381
  * a server-side mirror.
package/dist/addon.mjs CHANGED
@@ -29334,8 +29334,27 @@ var PrivacyMaskRegionSchema = object({
29334
29334
  /** Current on-camera privacy state — mask master enable + zones + microphone. */
29335
29335
  var PrivacyMaskStatusSchema = object({
29336
29336
  enabled: boolean(),
29337
- /** Active zones (normalized 0..1). Length ≤ maxRegions. */
29338
- regions: array(PrivacyMaskRegionSchema),
29337
+ /**
29338
+ * Active zones (normalized 0..1). Length ≤ maxRegions.
29339
+ *
29340
+ * `null` means "no answer" — the provider has never reached this camera
29341
+ * (a cold `runtimeState` slice, a battery camera asleep) or the read
29342
+ * failed. A consumer must render it as UNKNOWN and never as "this camera
29343
+ * has no zones": those two look identical to an operator right up to the
29344
+ * moment one of them is acted on, and acting on them differs completely.
29345
+ * The switch group turned an unanswered read into *"nothing is set up for
29346
+ * it to act on"* — an instruction to go and draw a zone that already
29347
+ * exists — and this editor seeded an EMPTY canvas from it, one Save away
29348
+ * from deleting the mask it could not read.
29349
+ *
29350
+ * Empty-and-answered is `[]` and stays a real answer: this camera genuinely
29351
+ * has no zones. The distinction is the same one {@link
29352
+ * PrivacyMaskStatusSchema.shape.audioEnabled} already draws for the
29353
+ * microphone, on the very same payload — both planes come from ONE refresh,
29354
+ * so it was never coherent for one of them to be able to say "unknown"
29355
+ * while the other could not.
29356
+ */
29357
+ regions: array(PrivacyMaskRegionSchema).nullable(),
29339
29358
  /**
29340
29359
  * Is the camera capturing sound right now? Read from the camera, never from
29341
29360
  * a server-side mirror.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@camstack/addon-provider-wyze",
3
- "version": "0.2.86",
3
+ "version": "0.2.87",
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",