@camstack/addon-provider-dreame 0.2.114 → 0.2.116

package/dist/addon.js

@@ -58137,7 +58137,7 @@ var ZodIssueCode = {
 var ZodFirstPartyTypeKind;
 ZodFirstPartyTypeKind || (ZodFirstPartyTypeKind = {});
 //#endregion
-//#region ../types/dist/sleep-Dk-BdnBf.mjs
+//#region ../types/dist/sleep-GU_us3DG.mjs
 /**
 * The audio chunk plane's byte format, and the ONE expansion from a coded
 * window to float samples (D455).
@@ -64627,6 +64627,24 @@ var GetStreamWithCodecInputSchema = object({
 });
 var RtpSourceSchema = object({
 	url: string(),
+	/**
+	* The SENTRY counterpart of {@link url} — the dial that asks for the stream
+	* WITHOUT asking for the camera — or `null` when this camera offers none.
+	*
+	* The broker answers it because the broker is the only thing that can:
+	* eligibility is `sentryEligible` (a BATTERY camera that DECLARES the signals
+	* cap), asked of facts only the broker holds. A consumer re-deriving it from
+	* cap bindings would be a second authority, and two authorities on the same
+	* question is how a composite camera ends up dialling a sleeping camera
+	* because its own copy of the rule was a release behind.
+	*
+	* `null` is a real answer and is never a live url in disguise: a consumer
+	* that silently fell back to {@link url} would perform exactly the wake this
+	* field exists to prevent. Only a PASSTHROUGH acquisition can offer one — a
+	* transcode hands back an egress the broker is feeding itself, which has no
+	* sentry counterpart.
+	*/
+	sentryUrl: string().nullable().optional(),
 	videoCodec: _enum(["H264", "H265"]),
 	audioCodec: string(),
 	resolution: object({
@@ -81690,6 +81708,118 @@ var motionTriggerCapability = {
 	durability: "session"
 };
 /**
+* camera-grid-layout — the geometry of a COMPOSITE camera, on the camera's own
+* page.
+*
+* ## Why this is a capability and not an addon settings schema
+*
+* It was one, and it did not render. The addon declared the editor as a
+* `type: 'widget'` field inside its own `deviceSettingsSchema()`; the hub
+* returned that section correctly and `ConfigFormField` renders `type:'widget'`
+* perfectly well — and nothing ever asked camera-grid for it. The Cluster →
+* Pipeline → Device Overrides page interrogates a HAND-WRITTEN list of four
+* addons (`PIPELINE_CLUSTER_DEVICE_ADDONS`), whose own comment says an addon
+* not on it "falls off silently".
+*
+* Adding a fifth name to that list would have been the wrong fix twice over:
+* that page is per-camera DETECTION tuning, and a grid's geometry belongs
+* beside PTZ and motion zones on the camera itself. The device page is
+* BINDING-driven (D12), so the way in is a capability bound to the device —
+* and this cap carries its section the way `recording` does, by RETURNING it
+* from `getDeviceSettingsContribution`.
+*
+* Seven other widgets are still declared the other way, through a
+* `deviceConfig.ui` block the framework derives a section from. That route
+* gives the addon no say in where its own panel lands and no way to decline
+* for a device the panel does not suit, which is why this one does not use it.
+*
+* ## Why one addon may implement it
+*
+* It is a device-scoped NATIVE cap, registered by the grid camera device
+* itself. Nothing else declares a composite camera, so nothing else has a
+* layout — and the device-scoped route means the widget asks THE camera, not
+* "the camera-grid addon", which is what let the old custom-action pair be
+* reached only by a caller that already knew the addon id.
+*
+* ## The tab
+*
+* `streaming`, not a top-tab of its own. A grid's geometry IS what its stream
+* is, so the Streaming tab is where it belongs; a `grid` top-tab would need an
+* entry in `WELL_KNOWN_TAB_MAP` or the device page renders the raw id as the
+* label (measured on the robot camera, 2026-09-06 — a tab called "navigation"
+* next to "PTZ").
+*/
+/** A rectangle in normalized [0,1] coordinates of whatever contains it. */
+var GridNormalizedRectSchema = object({
+	x: number().min(0).max(1),
+	y: number().min(0).max(1),
+	width: number().gt(0).max(1),
+	height: number().gt(0).max(1)
+});
+/**
+* One source camera, the part of its picture taken, and where that part lands.
+*
+* Both rectangles are NORMALIZED (D519): a source camera can change resolution
+* — a profile switch, a firmware update, a substream that comes back different
+* — and a stored PIXEL rectangle would quietly start cutting the wrong region,
+* which is the class of bug nobody files.
+*/
+var GridLayoutCellSchema = object({
+	deviceId: number().int().positive(),
+	/** The part of the SOURCE taken, normalized against the source. */
+	source: GridNormalizedRectSchema,
+	/** Where it lands, normalized against the CANVAS. */
+	cell: GridNormalizedRectSchema
+});
+/**
+* Which profiles this grid can actually compose, and why not.
+*
+* A grid's `high` composes its sources' `high` and its `low` their `low`, so a
+* profile is on offer only when EVERY source can serve it. The refusal NAMES
+* the sources, because "this grid has no low" is not a finding — "615 has no
+* low" is, and it is the one an operator can act on.
+*/
+var GridProfileOfferSchema = object({
+	profile: _enum([
+		"high",
+		"mid",
+		"low"
+	]),
+	offered: boolean(),
+	/** Sources that cannot serve it. Empty when it is offered, or when there are no cells. */
+	missingSources: array(number().int().positive())
+});
+var GridLayoutViewSchema = object({
+	/** The persisted grid row this camera was declared from. */
+	instanceId: string(),
+	deviceId: number().int().nonnegative(),
+	name: string(),
+	/** The canvas the operator laid out — this grid's `high`. mid/low are scaled from it. */
+	width: number().int(),
+	height: number().int(),
+	fps: number().int(),
+	cells: array(GridLayoutCellSchema),
+	/** What the catalog will publish, and what it refuses to. Read-only. */
+	profiles: array(GridProfileOfferSchema)
+});
+var GridLayoutPatchSchema = object({
+	deviceId: number().int().nonnegative(),
+	name: string().min(1).max(160).optional(),
+	width: number().int().min(160).max(7680).optional(),
+	height: number().int().min(120).max(4320).optional(),
+	fps: number().int().min(1).max(60).optional(),
+	/**
+	* The whole cell list at once. A per-cell patch would need an ordering the
+	* editor does not have, and a half-applied layout is a picture nobody asked
+	* for.
+	*/
+	cells: array(GridLayoutCellSchema).max(16)
+});
+DeviceType.Camera, method(object({ deviceId: number().int().nonnegative() }), GridLayoutViewSchema.nullable(), { auth: "admin" }), method(GridLayoutPatchSchema, GridLayoutViewSchema, {
+	kind: "mutation",
+	auth: "admin"
+});
+/**
 * Motion-zones share the same MaskShape vocabulary as privacy-mask — the
 * on-camera motion-detection mask is a single `grid` region (a row-major
 * boolean cell lattice the camera's onboard VMD evaluates). Composing it as
@@ -89564,6 +89694,18 @@ Object.freeze({
 		addonId: null,
 		access: "view"
 	},
+	"cameraGridLayout.getLayout": {
+		capName: "camera-grid-layout",
+		capScope: "device",
+		addonId: null,
+		access: "view"
+	},
+	"cameraGridLayout.saveLayout": {
+		capName: "camera-grid-layout",
+		capScope: "device",
+		addonId: null,
+		access: "create"
+	},
 	"cameraStreams.getBrokerStreams": {
 		capName: "camera-streams",
 		capScope: "device",
@@ -95263,6 +95405,21 @@ Object.freeze({
 		form: "single",
 		optional: false
 	}],
+	"cameraGridLayout.getLayout": [{
+		name: "deviceId",
+		form: "single",
+		optional: false
+	}],
+	"cameraGridLayout.saveLayout": [{
+		name: "cells",
+		form: "object-array",
+		optional: false,
+		itemField: "deviceId"
+	}, {
+		name: "deviceId",
+		form: "single",
+		optional: false
+	}],
 	"cameraStreams.getBrokerStreams": [{
 		name: "deviceId",
 		form: "single",

package/dist/addon.mjs

@@ -58134,7 +58134,7 @@ var ZodIssueCode = {
 var ZodFirstPartyTypeKind;
 ZodFirstPartyTypeKind || (ZodFirstPartyTypeKind = {});
 //#endregion
-//#region ../types/dist/sleep-Dk-BdnBf.mjs
+//#region ../types/dist/sleep-GU_us3DG.mjs
 /**
 * The audio chunk plane's byte format, and the ONE expansion from a coded
 * window to float samples (D455).
@@ -64624,6 +64624,24 @@ var GetStreamWithCodecInputSchema = object({
 });
 var RtpSourceSchema = object({
 	url: string(),
+	/**
+	* The SENTRY counterpart of {@link url} — the dial that asks for the stream
+	* WITHOUT asking for the camera — or `null` when this camera offers none.
+	*
+	* The broker answers it because the broker is the only thing that can:
+	* eligibility is `sentryEligible` (a BATTERY camera that DECLARES the signals
+	* cap), asked of facts only the broker holds. A consumer re-deriving it from
+	* cap bindings would be a second authority, and two authorities on the same
+	* question is how a composite camera ends up dialling a sleeping camera
+	* because its own copy of the rule was a release behind.
+	*
+	* `null` is a real answer and is never a live url in disguise: a consumer
+	* that silently fell back to {@link url} would perform exactly the wake this
+	* field exists to prevent. Only a PASSTHROUGH acquisition can offer one — a
+	* transcode hands back an egress the broker is feeding itself, which has no
+	* sentry counterpart.
+	*/
+	sentryUrl: string().nullable().optional(),
 	videoCodec: _enum(["H264", "H265"]),
 	audioCodec: string(),
 	resolution: object({
@@ -81687,6 +81705,118 @@ var motionTriggerCapability = {
 	durability: "session"
 };
 /**
+* camera-grid-layout — the geometry of a COMPOSITE camera, on the camera's own
+* page.
+*
+* ## Why this is a capability and not an addon settings schema
+*
+* It was one, and it did not render. The addon declared the editor as a
+* `type: 'widget'` field inside its own `deviceSettingsSchema()`; the hub
+* returned that section correctly and `ConfigFormField` renders `type:'widget'`
+* perfectly well — and nothing ever asked camera-grid for it. The Cluster →
+* Pipeline → Device Overrides page interrogates a HAND-WRITTEN list of four
+* addons (`PIPELINE_CLUSTER_DEVICE_ADDONS`), whose own comment says an addon
+* not on it "falls off silently".
+*
+* Adding a fifth name to that list would have been the wrong fix twice over:
+* that page is per-camera DETECTION tuning, and a grid's geometry belongs
+* beside PTZ and motion zones on the camera itself. The device page is
+* BINDING-driven (D12), so the way in is a capability bound to the device —
+* and this cap carries its section the way `recording` does, by RETURNING it
+* from `getDeviceSettingsContribution`.
+*
+* Seven other widgets are still declared the other way, through a
+* `deviceConfig.ui` block the framework derives a section from. That route
+* gives the addon no say in where its own panel lands and no way to decline
+* for a device the panel does not suit, which is why this one does not use it.
+*
+* ## Why one addon may implement it
+*
+* It is a device-scoped NATIVE cap, registered by the grid camera device
+* itself. Nothing else declares a composite camera, so nothing else has a
+* layout — and the device-scoped route means the widget asks THE camera, not
+* "the camera-grid addon", which is what let the old custom-action pair be
+* reached only by a caller that already knew the addon id.
+*
+* ## The tab
+*
+* `streaming`, not a top-tab of its own. A grid's geometry IS what its stream
+* is, so the Streaming tab is where it belongs; a `grid` top-tab would need an
+* entry in `WELL_KNOWN_TAB_MAP` or the device page renders the raw id as the
+* label (measured on the robot camera, 2026-09-06 — a tab called "navigation"
+* next to "PTZ").
+*/
+/** A rectangle in normalized [0,1] coordinates of whatever contains it. */
+var GridNormalizedRectSchema = object({
+	x: number().min(0).max(1),
+	y: number().min(0).max(1),
+	width: number().gt(0).max(1),
+	height: number().gt(0).max(1)
+});
+/**
+* One source camera, the part of its picture taken, and where that part lands.
+*
+* Both rectangles are NORMALIZED (D519): a source camera can change resolution
+* — a profile switch, a firmware update, a substream that comes back different
+* — and a stored PIXEL rectangle would quietly start cutting the wrong region,
+* which is the class of bug nobody files.
+*/
+var GridLayoutCellSchema = object({
+	deviceId: number().int().positive(),
+	/** The part of the SOURCE taken, normalized against the source. */
+	source: GridNormalizedRectSchema,
+	/** Where it lands, normalized against the CANVAS. */
+	cell: GridNormalizedRectSchema
+});
+/**
+* Which profiles this grid can actually compose, and why not.
+*
+* A grid's `high` composes its sources' `high` and its `low` their `low`, so a
+* profile is on offer only when EVERY source can serve it. The refusal NAMES
+* the sources, because "this grid has no low" is not a finding — "615 has no
+* low" is, and it is the one an operator can act on.
+*/
+var GridProfileOfferSchema = object({
+	profile: _enum([
+		"high",
+		"mid",
+		"low"
+	]),
+	offered: boolean(),
+	/** Sources that cannot serve it. Empty when it is offered, or when there are no cells. */
+	missingSources: array(number().int().positive())
+});
+var GridLayoutViewSchema = object({
+	/** The persisted grid row this camera was declared from. */
+	instanceId: string(),
+	deviceId: number().int().nonnegative(),
+	name: string(),
+	/** The canvas the operator laid out — this grid's `high`. mid/low are scaled from it. */
+	width: number().int(),
+	height: number().int(),
+	fps: number().int(),
+	cells: array(GridLayoutCellSchema),
+	/** What the catalog will publish, and what it refuses to. Read-only. */
+	profiles: array(GridProfileOfferSchema)
+});
+var GridLayoutPatchSchema = object({
+	deviceId: number().int().nonnegative(),
+	name: string().min(1).max(160).optional(),
+	width: number().int().min(160).max(7680).optional(),
+	height: number().int().min(120).max(4320).optional(),
+	fps: number().int().min(1).max(60).optional(),
+	/**
+	* The whole cell list at once. A per-cell patch would need an ordering the
+	* editor does not have, and a half-applied layout is a picture nobody asked
+	* for.
+	*/
+	cells: array(GridLayoutCellSchema).max(16)
+});
+DeviceType.Camera, method(object({ deviceId: number().int().nonnegative() }), GridLayoutViewSchema.nullable(), { auth: "admin" }), method(GridLayoutPatchSchema, GridLayoutViewSchema, {
+	kind: "mutation",
+	auth: "admin"
+});
+/**
 * Motion-zones share the same MaskShape vocabulary as privacy-mask — the
 * on-camera motion-detection mask is a single `grid` region (a row-major
 * boolean cell lattice the camera's onboard VMD evaluates). Composing it as
@@ -89561,6 +89691,18 @@ Object.freeze({
 		addonId: null,
 		access: "view"
 	},
+	"cameraGridLayout.getLayout": {
+		capName: "camera-grid-layout",
+		capScope: "device",
+		addonId: null,
+		access: "view"
+	},
+	"cameraGridLayout.saveLayout": {
+		capName: "camera-grid-layout",
+		capScope: "device",
+		addonId: null,
+		access: "create"
+	},
 	"cameraStreams.getBrokerStreams": {
 		capName: "camera-streams",
 		capScope: "device",
@@ -95260,6 +95402,21 @@ Object.freeze({
 		form: "single",
 		optional: false
 	}],
+	"cameraGridLayout.getLayout": [{
+		name: "deviceId",
+		form: "single",
+		optional: false
+	}],
+	"cameraGridLayout.saveLayout": [{
+		name: "cells",
+		form: "object-array",
+		optional: false,
+		itemField: "deviceId"
+	}, {
+		name: "deviceId",
+		form: "single",
+		optional: false
+	}],
 	"cameraStreams.getBrokerStreams": [{
 		name: "deviceId",
 		form: "single",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@camstack/addon-provider-dreame",
-  "version": "0.2.114",
+  "version": "0.2.116",
   "description": "Dreame robot-vacuum / lawn-mower device-provider addon for CamStack — wraps the @apocaliss92/nodedreame Dreamehome cloud client",
   "keywords": [
     "camstack",