@camstack/types 1.2.211 → 1.2.213

package/dist/addon.js

@@ -1,5 +1,5 @@
 Object.defineProperty(exports, Symbol.toStringTag, { value: "Module" });
-const require_sleep = require("./sleep-OPlow2a9.js");
+const require_sleep = require("./sleep-VlZxDyXq.js");
 const require_event_category = require("./event-category-BVfsrBYA.js");
 const require_err_msg = require("./err-msg-COpsHMw2.js");
 //#region src/generated/cap-input-defaults.ts

package/dist/addon.mjs

@@ -1,4 +1,4 @@
-import { A as DeviceType, Et as normalizeAddonInitResult, G as ReadinessRegistry, H as nodePin, I as expandCapMethods, K as ReadinessTimeoutError, S as DEVICE_CHILDREN_BATCH_MAX, St as DATAPLANE_SECRET_HEADER, T as describeCustomActions, Tt as BaseAddon, U as readNodePin, Y as scopeKey, a as asJsonObject, b as deviceOpsCapability, d as BOOT_RECOVERY_BACKOFF_MS, f as DEVICE_SCOPED_CAPS, h as createEventBusSliceSource, j as adminUiCapability, kt as emitReadiness, m as createDeviceProxy, p as isDeviceScopedCap, s as asString, t as sleep, u as parseJsonUnknown, wt as DisposerChain, x as viewerUiCapability } from "./sleep-Bs3xPtSh.mjs";
+import { A as DeviceType, Et as normalizeAddonInitResult, G as ReadinessRegistry, H as nodePin, I as expandCapMethods, K as ReadinessTimeoutError, S as DEVICE_CHILDREN_BATCH_MAX, St as DATAPLANE_SECRET_HEADER, T as describeCustomActions, Tt as BaseAddon, U as readNodePin, Y as scopeKey, a as asJsonObject, b as deviceOpsCapability, d as BOOT_RECOVERY_BACKOFF_MS, f as DEVICE_SCOPED_CAPS, h as createEventBusSliceSource, j as adminUiCapability, kt as emitReadiness, m as createDeviceProxy, p as isDeviceScopedCap, s as asString, t as sleep, u as parseJsonUnknown, wt as DisposerChain, x as viewerUiCapability } from "./sleep-GU_us3DG.mjs";
 import { t as EventCategory } from "./event-category-BVDXG4tB.mjs";
 import { t as errMsg } from "./err-msg-IQTHeDzc.mjs";
 //#region src/generated/cap-input-defaults.ts

package/dist/capabilities/camera-grid-layout.cap.d.ts

@@ -1,6 +1,6 @@
 import { z } from 'zod';
 import { DeviceType } from '../device/device-type.js';
-import { type InferNativeProvider } from './capability-definition.js';
+import { type InferNativeProvider, type InferProvider } from './capability-definition.js';
 /**
  * camera-grid-layout — the geometry of a COMPOSITE camera, on the camera's own
  * page.
@@ -17,11 +17,15 @@ import { type InferNativeProvider } from './capability-definition.js';
  *
  * 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 — which is exactly where the
- * framework already puts a widget, when the widget is declared on a CAPABILITY.
- * `deviceConfig.ui` is the mechanism (`motion-zones`, `ptz`, `ptz-autotrack`
- * all use it): the framework emits the structural section and the widget
- * self-persists through the cap's own mutations.
+ * 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
  *
@@ -151,15 +155,24 @@ export declare const cameraGridLayoutCapability: {
     readonly deviceNative: true;
     readonly mode: "singleton";
     readonly deviceTypes: readonly [DeviceType.Camera];
-    readonly deviceConfig: {
-        readonly ui: {
-            readonly kind: "widget";
-            readonly widgetId: "host/camera-grid-layout";
-            readonly tab: "streaming";
-            readonly label: "Grid layout";
-            readonly order: 20;
-        };
-    };
+    /**
+     * The section is built by the ADDON and returned from
+     * `getDeviceSettingsContribution`, not derived by the framework from a
+     * `deviceConfig.ui` block.
+     *
+     * Both mechanisms render the same widget. This one hands the addon two
+     * things the framework-derived route cannot give it:
+     *
+     *  - it chooses its own section, `tab`, `location` and `order`, the way any
+     *    other setting does, instead of receiving them from a cap declaration;
+     *  - it can DECLINE per device. A camera that is not a grid gets no section
+     *    at all, rather than a widget that renders its own "not a grid" state.
+     *
+     * `recording` is the precedent (`recorder/recording-device-settings.ts`): it
+     * returns `null` for anything that is not a camera, so the Recording tab
+     * never appears there.
+     */
+    readonly exposesDeviceSettings: true;
     readonly methods: {
         /**
          * The grid behind this device.
@@ -258,5 +271,21 @@ export declare const cameraGridLayoutCapability: {
         }, z.core.$strip>, "mutation">;
     };
 };
+/**
+ * The DEVICE's provider: the data methods only.
+ *
+ * `InferNativeProvider` deliberately omits the device-settings contribution —
+ * the framework expects a native provider to hold the data and a WRAPPER to
+ * describe the UI, which is why `getProviderByAddon` (not
+ * `getProviderForDevice`) is what the aggregation resolves with.
+ */
 export type ICameraGridLayoutProvider = InferNativeProvider<typeof cameraGridLayoutCapability>;
+/**
+ * The ADDON's provider: the same methods plus the contribution surface that
+ * `exposesDeviceSettings` adds. This is the one that carries the section, and
+ * the one that can decline for a device that is not a grid.
+ *
+ * Two types for two roles, the same split `doorbell` and `snapshot` use.
+ */
+export type ICameraGridLayoutSettingsProvider = InferProvider<typeof cameraGridLayoutCapability>;
 export {};

package/dist/capabilities/index.d.ts

@@ -169,7 +169,7 @@ export { type IMediaPlayerProvider, type MediaInfo, type MediaPlayerRepeat, Medi
 export { type IMeshNetworkProvider, type MeshEndpoint, type MeshPeer, MeshPeerSchema, type MeshStatus, MeshStatusSchema, meshNetworkCapability, } from './mesh-network.cap.js';
 export { type IMotionProvider, MOTION_CLOSE_AFTER_MS, type MotionOnMotionChangedData, MotionOnMotionChangedDataSchema, type MotionStatus, MotionStatusSchema, motionCapability, } from './motion.cap.js';
 export { type IMotionTriggerProvider, type MotionTriggerRuntimeState, MotionTriggerRuntimeStateSchema, type MotionTriggerStatus, MotionTriggerStatusSchema, motionTriggerCapability, } from './motion-trigger.cap.js';
-export { type GridLayoutCell, type GridLayoutPatch, GridLayoutPatchSchema, type GridNormalizedRect, type GridProfileOffer, type GridLayoutView, GridLayoutViewSchema, type ICameraGridLayoutProvider, cameraGridLayoutCapability, } from './camera-grid-layout.cap.js';
+export { type GridLayoutCell, type GridLayoutPatch, GridLayoutPatchSchema, type GridNormalizedRect, type GridProfileOffer, type GridLayoutView, GridLayoutViewSchema, type ICameraGridLayoutProvider, type ICameraGridLayoutSettingsProvider, cameraGridLayoutCapability, } from './camera-grid-layout.cap.js';
 export { type IMotionZonesProvider, type MotionZoneOptions, MotionZoneOptionsSchema, type MotionZonePatch, MotionZonePatchSchema, type MotionZoneRegion, MotionZoneRegionSchema, type MotionZoneStatus, MotionZoneStatusSchema, motionZonesCapability, } from './motion-zones.cap.js';
 export { type INativeObjectDetectionProvider, type NativeDetection, NativeDetectionSchema, type NativeObjectClass, NativeObjectClassEnum, type NativeObjectDetectionOptions, NativeObjectDetectionOptionsSchema, type NativeObjectDetectionRuntimeState, NativeObjectDetectionRuntimeStateSchema, type NativeObjectDetectionSettingsPatch, NativeObjectDetectionSettingsPatchSchema, type NativeObjectDetectionStatus, NativeObjectDetectionStatusSchema, type NativeObjectGeometry, NativeObjectGeometryEnum, nativeObjectDetectionCapability, } from './native-object-detection.cap.js';
 export { type INavigationProvider, NAVIGATION_ACTION_CATALOG, NAVIGATION_LIGHT_LEVEL_MAX, NAVIGATION_LIGHT_LEVEL_MIN, type NavigationActionEntry, NavigationActionEntrySchema, type NavigationActionId, NavigationActionIdSchema, type NavigationEntryKind, NavigationEntryKindSchema, type NavigationFeatures, NavigationFeaturesSchema, type NavigationLightMode, NavigationLightModeSchema, type NavigationMode, NavigationModeSchema, type NavigationMoveCommand, NavigationMoveCommandSchema, type NavigationPoint, NavigationPointSchema, type NavigationRuntimeState, NavigationRuntimeStateSchema, type NavigationStatus, NavigationStatusSchema, navigationCapability, } from './navigation.cap.js';

package/dist/ffmpeg/invocation.d.ts

@@ -210,9 +210,22 @@ export interface FfmpegFmp4Sink {
 export type FfmpegSink = {
     readonly kind: 'rtsp-listen';
     readonly url: string;
-} | {
+}
+/**
+ * A container written to stdout.
+ *
+ * `flv` exists for a producer whose consumer is the broker's ffmpeg source
+ * reader: that reader re-muxes with `-c copy -f mpegts`, and the bundled
+ * ffmpeg 7.0.2 static SEGFAULTS on an MPEG-TS input on that path — measured
+ * on the hub 2026-09-17, on a synthetic three-second stream as readily as on
+ * a real one, while RTSP→TS and FLV→TS copy both exit 0. A producer that
+ * hands the broker MPEG-TS therefore hands it a crash; FLV is the format the
+ * broker already documents as "always ingested through the ffmpeg source
+ * reader" (`pull-flv`).
+ */
+ | {
     readonly kind: 'stdout';
-    readonly container: 'h264' | 'hevc' | 'mpegts';
+    readonly container: 'h264' | 'hevc' | 'mpegts' | 'flv';
 } | FfmpegFmp4Sink
 /**
  * Two independent mapped RTP outputs. Generic ffmpeg RTP vocabulary — the

package/dist/generated/addon-api.d.ts

@@ -1199,6 +1199,27 @@ export type AppRouter = TrpcCoreRouter<{
         errorShape: AugmentedErrorShape;
         transformer: true;
     }, TRPCDecorateCreateRouterOptions<{
+        getDeviceSettingsContribution: TRPCQueryProcedure<{
+            input: {
+                [x: string]: unknown;
+            } & z.input<typeof DEVICE_SETTINGS_CONTRIBUTION_METHODS.getDeviceSettingsContribution.input>;
+            output: z.infer<typeof DEVICE_SETTINGS_CONTRIBUTION_METHODS.getDeviceSettingsContribution.output>;
+            meta: object;
+        }>;
+        getDeviceLiveContribution: TRPCQueryProcedure<{
+            input: {
+                [x: string]: unknown;
+            } & z.input<typeof DEVICE_SETTINGS_CONTRIBUTION_METHODS.getDeviceLiveContribution.input>;
+            output: z.infer<typeof DEVICE_SETTINGS_CONTRIBUTION_METHODS.getDeviceLiveContribution.output>;
+            meta: object;
+        }>;
+        applyDeviceSettingsPatch: TRPCMutationProcedure<{
+            input: {
+                [x: string]: unknown;
+            } & z.input<typeof DEVICE_SETTINGS_CONTRIBUTION_METHODS.applyDeviceSettingsPatch.input>;
+            output: z.infer<typeof DEVICE_SETTINGS_CONTRIBUTION_METHODS.applyDeviceSettingsPatch.output>;
+            meta: object;
+        }>;
         getLayout: TRPCQueryProcedure<{
             input: {
                 [x: string]: unknown;

package/dist/index.js

@@ -1,5 +1,5 @@
 Object.defineProperty(exports, Symbol.toStringTag, { value: "Module" });
-const require_sleep = require("./sleep-OPlow2a9.js");
+const require_sleep = require("./sleep-VlZxDyXq.js");
 const require_event_category = require("./event-category-BVfsrBYA.js");
 const require_canonical_hash = require("./canonical-hash-CZ2JqJc3.js");
 const require_enums = require("./enums.js");
@@ -32455,11 +32455,15 @@ var motionTriggerCapability = {
 *
 * 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 — which is exactly where the
-* framework already puts a widget, when the widget is declared on a CAPABILITY.
-* `deviceConfig.ui` is the mechanism (`motion-zones`, `ptz`, `ptz-autotrack`
-* all use it): the framework emits the structural section and the widget
-* self-persists through the cap's own mutations.
+* 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
 *
@@ -32549,13 +32553,24 @@ var cameraGridLayoutCapability = {
 	deviceNative: true,
 	mode: "singleton",
 	deviceTypes: [require_sleep.DeviceType.Camera],
-	deviceConfig: { ui: {
-		kind: "widget",
-		widgetId: "host/camera-grid-layout",
-		tab: "streaming",
-		label: "Grid layout",
-		order: 20
-	} },
+	/**
+	* The section is built by the ADDON and returned from
+	* `getDeviceSettingsContribution`, not derived by the framework from a
+	* `deviceConfig.ui` block.
+	*
+	* Both mechanisms render the same widget. This one hands the addon two
+	* things the framework-derived route cannot give it:
+	*
+	*  - it chooses its own section, `tab`, `location` and `order`, the way any
+	*    other setting does, instead of receiving them from a cap declaration;
+	*  - it can DECLINE per device. A camera that is not a grid gets no section
+	*    at all, rather than a widget that renders its own "not a grid" state.
+	*
+	* `recording` is the precedent (`recorder/recording-device-settings.ts`): it
+	* returns `null` for anything that is not a camera, so the Recording tab
+	* never appears there.
+	*/
+	exposesDeviceSettings: true,
 	methods: {
 		/**
 		* The grid behind this device.

package/dist/index.mjs

@@ -1,4 +1,4 @@
-import { $ as CAM_PROFILE_ORDER, A as DeviceType, At as isEvent, B as systemMethod, Bt as isAudioChunkFormat, C as customAction, Ct as SHARE_VIEW_KINDS, D as ChargingStatus, Dt as createDurableState, E as deviceCustomAction, Et as normalizeAddonInitResult, F as event, Ft as hydrateSchema, G as ReadinessRegistry, H as nodePin, I as expandCapMethods, It as resolveHydratedFieldValue, J as readinessKey, K as ReadinessTimeoutError, L as isDeviceConfigCap, Lt as AUDIO_CHUNK_FORMATS, M as DEFAULT_RUNTIME_STATE_DURABILITY, Mt as WELL_KNOWN_TAB_MAP, N as DEVICE_SETTINGS_CONTRIBUTION_METHODS, Nt as collectHydratedFieldEntries, O as DeviceFeature, Ot as createEvent, P as DEVICE_STATUS_METHOD, Pt as collectHydratedFieldValues, Q as BrokerStatusSchema, R as method, Rt as audioChunkBytesPerSample, S as DEVICE_CHILDREN_BATCH_MAX, St as DATAPLANE_SECRET_HEADER, T as describeCustomActions, Tt as BaseAddon, U as readNodePin, V as CAP_NODE_PIN_CONTEXT_KEY, W as toNodeId, X as AudioChunkFormatSchema, Y as scopeKey, Z as BrokerStatsSchema, _ as createMirrorSource, _t as SubscribeFramesResultSchema, a as asJsonObject, at as DecodedFrameSchema, b as deviceOpsCapability, bt as parseProfileBrokerId, c as parseJsonArray, ct as FrameHandleSchema, d as BOOT_RECOVERY_BACKOFF_MS, dt as ProfileSlotStatusSchema, et as CamProfileSchema, f as DEVICE_SCOPED_CAPS, ft as StreamSourceEntrySchema, g as createLazyTrpcSource, gt as SubscribeFramesInputSchema, h as createEventBusSliceSource, ht as SubscribeAudioChunksResultSchema, i as asJsonArray, it as DecodedAudioChunkSchema, j as adminUiCapability, jt as WELL_KNOWN_TABS, k as DeviceRole, kt as emitReadiness, l as parseJsonObject, lt as ProfileRtspEntrySchema, m as createDeviceProxy, mt as SubscribeAudioChunksInputSchema, n as sleepCancellable, nt as CamStreamResolutionSchema, o as asNumber, ot as EncodedPacketSchema, p as isDeviceScopedCap, pt as StreamSourceSchema, q as emitDownForOwnedCaps, r as asBoolean, rt as CameraStreamSchema, s as asString, st as FrameHandleFormatSchema, t as sleep, tt as CamStreamKindSchema, u as parseJsonUnknown, ut as ProfileSlotSchema, v as createSliceHandle, vt as makeProfileBrokerId, w as defineCustomActions, wt as DisposerChain, x as viewerUiCapability, xt as selectAssignedProfileSlots, y as RawStateResultSchema, yt as makeSourceBrokerId, z as resolveCapMount, zt as expandAudioChunkToF32le } from "./sleep-Bs3xPtSh.mjs";
+import { $ as CAM_PROFILE_ORDER, A as DeviceType, At as isEvent, B as systemMethod, Bt as isAudioChunkFormat, C as customAction, Ct as SHARE_VIEW_KINDS, D as ChargingStatus, Dt as createDurableState, E as deviceCustomAction, Et as normalizeAddonInitResult, F as event, Ft as hydrateSchema, G as ReadinessRegistry, H as nodePin, I as expandCapMethods, It as resolveHydratedFieldValue, J as readinessKey, K as ReadinessTimeoutError, L as isDeviceConfigCap, Lt as AUDIO_CHUNK_FORMATS, M as DEFAULT_RUNTIME_STATE_DURABILITY, Mt as WELL_KNOWN_TAB_MAP, N as DEVICE_SETTINGS_CONTRIBUTION_METHODS, Nt as collectHydratedFieldEntries, O as DeviceFeature, Ot as createEvent, P as DEVICE_STATUS_METHOD, Pt as collectHydratedFieldValues, Q as BrokerStatusSchema, R as method, Rt as audioChunkBytesPerSample, S as DEVICE_CHILDREN_BATCH_MAX, St as DATAPLANE_SECRET_HEADER, T as describeCustomActions, Tt as BaseAddon, U as readNodePin, V as CAP_NODE_PIN_CONTEXT_KEY, W as toNodeId, X as AudioChunkFormatSchema, Y as scopeKey, Z as BrokerStatsSchema, _ as createMirrorSource, _t as SubscribeFramesResultSchema, a as asJsonObject, at as DecodedFrameSchema, b as deviceOpsCapability, bt as parseProfileBrokerId, c as parseJsonArray, ct as FrameHandleSchema, d as BOOT_RECOVERY_BACKOFF_MS, dt as ProfileSlotStatusSchema, et as CamProfileSchema, f as DEVICE_SCOPED_CAPS, ft as StreamSourceEntrySchema, g as createLazyTrpcSource, gt as SubscribeFramesInputSchema, h as createEventBusSliceSource, ht as SubscribeAudioChunksResultSchema, i as asJsonArray, it as DecodedAudioChunkSchema, j as adminUiCapability, jt as WELL_KNOWN_TABS, k as DeviceRole, kt as emitReadiness, l as parseJsonObject, lt as ProfileRtspEntrySchema, m as createDeviceProxy, mt as SubscribeAudioChunksInputSchema, n as sleepCancellable, nt as CamStreamResolutionSchema, o as asNumber, ot as EncodedPacketSchema, p as isDeviceScopedCap, pt as StreamSourceSchema, q as emitDownForOwnedCaps, r as asBoolean, rt as CameraStreamSchema, s as asString, st as FrameHandleFormatSchema, t as sleep, tt as CamStreamKindSchema, u as parseJsonUnknown, ut as ProfileSlotSchema, v as createSliceHandle, vt as makeProfileBrokerId, w as defineCustomActions, wt as DisposerChain, x as viewerUiCapability, xt as selectAssignedProfileSlots, y as RawStateResultSchema, yt as makeSourceBrokerId, z as resolveCapMount, zt as expandAudioChunkToF32le } from "./sleep-GU_us3DG.mjs";
 import { t as EventCategory } from "./event-category-BVDXG4tB.mjs";
 import { a as buildAudioArgs, c as buildVideoArgs, d as logBannerArgs, f as pickVideoEncoder, i as audioPlanFromEncodeProfile, l as invocationFromEncodeProfile, n as Fmp4BoxSplitter, o as buildFfmpegArgs, p as resolveStreamMaps, r as AUDIO_PRESETS, s as buildInputArgs, t as canonicalHash, u as isSoftwareDecode } from "./canonical-hash-DBkl8q6V.mjs";
 import { EventSourceType } from "./enums.mjs";
@@ -32454,11 +32454,15 @@ var motionTriggerCapability = {
 *
 * 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 — which is exactly where the
-* framework already puts a widget, when the widget is declared on a CAPABILITY.
-* `deviceConfig.ui` is the mechanism (`motion-zones`, `ptz`, `ptz-autotrack`
-* all use it): the framework emits the structural section and the widget
-* self-persists through the cap's own mutations.
+* 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
 *
@@ -32548,13 +32552,24 @@ var cameraGridLayoutCapability = {
 	deviceNative: true,
 	mode: "singleton",
 	deviceTypes: [DeviceType.Camera],
-	deviceConfig: { ui: {
-		kind: "widget",
-		widgetId: "host/camera-grid-layout",
-		tab: "streaming",
-		label: "Grid layout",
-		order: 20
-	} },
+	/**
+	* The section is built by the ADDON and returned from
+	* `getDeviceSettingsContribution`, not derived by the framework from a
+	* `deviceConfig.ui` block.
+	*
+	* Both mechanisms render the same widget. This one hands the addon two
+	* things the framework-derived route cannot give it:
+	*
+	*  - it chooses its own section, `tab`, `location` and `order`, the way any
+	*    other setting does, instead of receiving them from a cap declaration;
+	*  - it can DECLINE per device. A camera that is not a grid gets no section
+	*    at all, rather than a widget that renders its own "not a grid" state.
+	*
+	* `recording` is the precedent (`recorder/recording-device-settings.ts`): it
+	* returns `null` for anything that is not a camera, so the Recording tab
+	* never appears there.
+	*/
+	exposesDeviceSettings: true,
 	methods: {
 		/**
 		* The grid behind this device.

package/dist/{sleep-Bs3xPtSh.mjs → sleep-GU_us3DG.mjs}

@@ -3459,7 +3459,10 @@ function createDeviceProxy(api, binding, opts) {
 		},
 		cameraGridLayout: {
 			getLayout: (input) => dispatch("camera-grid-layout", "cameraGridLayout", "getLayout", "query", input),
-			saveLayout: (input) => dispatch("camera-grid-layout", "cameraGridLayout", "saveLayout", "mutation", input)
+			saveLayout: (input) => dispatch("camera-grid-layout", "cameraGridLayout", "saveLayout", "mutation", input),
+			getDeviceSettingsContribution: (input) => dispatch("camera-grid-layout", "cameraGridLayout", "getDeviceSettingsContribution", "query", input),
+			getDeviceLiveContribution: (input) => dispatch("camera-grid-layout", "cameraGridLayout", "getDeviceLiveContribution", "query", input),
+			applyDeviceSettingsPatch: (input) => dispatch("camera-grid-layout", "cameraGridLayout", "applyDeviceSettingsPatch", "mutation", input)
 		},
 		cameraStreams: {
 			getCameraStreams: (input) => dispatch("camera-streams", "cameraStreams", "getCameraStreams", "query", input),

package/dist/{sleep-OPlow2a9.js → sleep-VlZxDyXq.js}

@@ -3459,7 +3459,10 @@ function createDeviceProxy(api, binding, opts) {
 		},
 		cameraGridLayout: {
 			getLayout: (input) => dispatch("camera-grid-layout", "cameraGridLayout", "getLayout", "query", input),
-			saveLayout: (input) => dispatch("camera-grid-layout", "cameraGridLayout", "saveLayout", "mutation", input)
+			saveLayout: (input) => dispatch("camera-grid-layout", "cameraGridLayout", "saveLayout", "mutation", input),
+			getDeviceSettingsContribution: (input) => dispatch("camera-grid-layout", "cameraGridLayout", "getDeviceSettingsContribution", "query", input),
+			getDeviceLiveContribution: (input) => dispatch("camera-grid-layout", "cameraGridLayout", "getDeviceLiveContribution", "query", input),
+			applyDeviceSettingsPatch: (input) => dispatch("camera-grid-layout", "cameraGridLayout", "applyDeviceSettingsPatch", "mutation", input)
 		},
 		cameraStreams: {
 			getCameraStreams: (input) => dispatch("camera-streams", "cameraStreams", "getCameraStreams", "query", input),

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@camstack/types",
-  "version": "1.2.211",
+  "version": "1.2.213",
   "description": "Shared types, interfaces, and model catalogs for the CamStack detection ecosystem",
   "keywords": [
     "camstack",