@camstack/system 1.2.179 → 1.2.181

package/dist/{dist-L_39vRmH.mjs → dist-DbnNk4Lw.mjs}

@@ -7164,6 +7164,89 @@ var LocationStatSchema = z.object({
 	fileCount: z.number(),
 	present: z.boolean()
 });
+/** Lifecycle of a backup run. Terminal states: succeeded / failed / cancelled. */
+var BackupRunStateSchema = z.enum([
+	"queued",
+	"running",
+	"succeeded",
+	"failed",
+	"cancelled"
+]);
+/**
+* Where a running backup currently is. `queued` before it starts,
+* `building` while the tar.gz is being staged, `uploading` during the
+* per-destination fan-out, `done` once terminal.
+*/
+var BackupRunPhaseSchema = z.enum([
+	"queued",
+	"building",
+	"uploading",
+	"done"
+]);
+/**
+* Observable state of one backup run — readable WHILE it runs via
+* `backup.listRuns`. This is what makes the execution queue and
+* `backup.cancel` usable: the 2026-09-04 incident (two concurrent
+* multi-GB builds, staging 5.1 GB → 18 GB, load 62) was only
+* diagnosable with `du` because nothing reported that runs existed or
+* how large the staged archive had grown.
+*/
+var BackupRunSchema = z.object({
+	/** Stable run id — the handle `backup.cancel` takes. */
+	id: z.string(),
+	state: BackupRunStateSchema,
+	phase: BackupRunPhaseSchema,
+	/**
+	* Resolved destination location ids. Empty while queued (targets are
+	* resolved when the run starts, against the then-current policies).
+	*/
+	destinationIds: z.array(z.string()).readonly(),
+	label: z.string().optional(),
+	/** ms-epoch when the run was submitted (trigger call / schedule fire). */
+	requestedAt: z.number(),
+	/** ms-epoch when the run left the queue and started building. */
+	startedAt: z.number().optional(),
+	/** ms-epoch when the run reached a terminal state. */
+	finishedAt: z.number().optional(),
+	/** Compressed bytes of the staging archive written so far. */
+	stagedBytes: z.number(),
+	/** Final staged archive size, once the build phase completes. */
+	archiveSizeBytes: z.number().optional(),
+	/** Bytes pushed to the destination currently uploading. */
+	uploadedBytes: z.number(),
+	/** Destinations where the archive fully landed (uploaded + indexed). */
+	completedDestinationIds: z.array(z.string()).readonly(),
+	/** Destinations that failed during the fan-out. */
+	failedDestinationIds: z.array(z.string()).readonly(),
+	/** Failure message when `state === 'failed'`. */
+	error: z.string().optional(),
+	/**
+	* 1-based place in the execution queue — 1 = runs next. Present only
+	* while `state === 'queued'`. Stamped by the orchestrator from the
+	* queue's OWN pending order, never derived from timestamps, so the
+	* UI cannot show an order the executor will not honour.
+	*/
+	queuePosition: z.number().int().min(1).optional()
+});
+/**
+* Result of `backup.trigger`. The call still resolves when the run
+* terminates (compat with schedule-driven runs and the admin UI), but
+* it now names the run and says whether it had to WAIT: a trigger that
+* arrives while another run is in flight is enqueued (or joined onto
+* an identical already-queued run), never started concurrently.
+*/
+var BackupTriggerResultSchema = z.object({
+	/** The run this trigger mapped to — poll it via `listRuns`, stop it via `cancel`. */
+	runId: z.string(),
+	/** True when the run waited behind an in-flight run instead of starting immediately. */
+	queued: z.boolean(),
+	/** True when this trigger was coalesced onto an identical already-queued run. */
+	joined: z.boolean(),
+	/** True when the run was cancelled before completing every destination. */
+	cancelled: z.boolean(),
+	/** One entry per destination the archive landed at (partial on cancel). */
+	entries: z.array(BackupEntrySchema).readonly()
+});
 /**
 * A backup schedule — the N:M "entry" that binds one cron cadence to a
 * SET of destination locations. Supersedes the per-location cron on
@@ -7221,6 +7304,11 @@ var backupCapability = {
 		* Trigger a backup. Without `destinations` the orchestrator fans
 		* out to every destination flagged as enabled in the routing
 		* config; with it, only the listed addons receive the archive.
+		*
+		* At most ONE backup run executes at a time — the source tree and
+		* the staging disk are shared by every run, so a second trigger
+		* while one is in flight is enqueued (or joined onto an identical
+		* queued run) and the result says so. See D342.
 		*/
 		trigger: method(z.object({
 			/** Subset of registered `backup-destination` addon ids to write to. */
@@ -7234,7 +7322,30 @@ var backupCapability = {
 			* retention (manual runs).
 			*/
 			retentionCount: z.number().int().min(1).max(1e3).optional()
-		}).optional(), z.array(BackupEntrySchema).readonly(), {
+		}).optional(), BackupTriggerResultSchema, {
+			kind: "mutation",
+			auth: "admin"
+		}),
+		/**
+		* Every run the orchestrator knows about, in EXECUTION order: the
+		* running run first, then queued runs in the exact order they will
+		* execute (each with `queuePosition`, 1 = next), then the bounded
+		* finished history newest-first. Only one run executes at a time
+		* (D342) — the queued section IS the line. Each run carries live
+		* phase + byte counters so a runaway build is visible in seconds,
+		* not via `du`.
+		*/
+		listRuns: method(z.void(), z.array(BackupRunSchema).readonly(), { auth: "admin" }),
+		/**
+		* Stop a backup run. Mirrors `storage-migration.cancel` semantics:
+		* id in, `{ cancelled }` out — `false` when the run is unknown or
+		* already terminal. A QUEUED run is removed before it ever starts;
+		* the RUNNING run has its tar/upload stream actually aborted, the
+		* half-written staging archive is deleted, and the in-flight
+		* destination upload is aborted server-side (partial discarded).
+		* Destinations that already completed keep their archive.
+		*/
+		cancel: method(z.object({ runId: z.string() }), z.object({ cancelled: z.boolean() }), {
 			kind: "mutation",
 			auth: "admin"
 		}),
@@ -8112,6 +8223,38 @@ var streamBrokerCapability = {
 			auth: "admin"
 		}),
 		/**
+		* The HARDWARE behind a device number was replaced
+		* (`deviceManager.migrateDevice`). Forget every piece of broker state that
+		* described the old box, so the next catalog pull derives everything from
+		* the camera that is actually there:
+		*
+		*  - every `derived:*` stream definition — a derived is authored against a
+		*    specific profile layout, and against the wrong hardware its feeder
+		*    respawns forever (observed at attempt 2732 on the live hub,
+		*    2026-09-01);
+		*  - the profile-slot assignment entry, PURGED (not unassigned — unassign
+		*    marks the slot manual, which would pin the stale choice instead of
+		*    letting `computeInitialAssignment` re-derive it);
+		*  - the probe snapshots (`<deviceId>/…` — probed codec/resolution of the
+		*    old hardware);
+		*  - the persisted RTSP token rows for the device's brokers (keyed
+		*    `<deviceId>/<camStreamId>`; the stream ids change with the hardware,
+		*    so the rows are dead URLs).
+		*
+		* An RPC, deliberately — an event is telemetry and may be dropped (D8),
+		* and a dropped forget leaves a feeder respawning against a stream that
+		* does not exist.
+		*/
+		forgetDeviceHardware: method(z.object({ deviceId: z.number().int().nonnegative() }), z.object({
+			derivedStreamsDeleted: z.array(z.string()).readonly(),
+			assignmentsPurged: z.boolean(),
+			probeSnapshotsDropped: z.number().int().nonnegative(),
+			rtspTokenRowsDeleted: z.number().int().nonnegative()
+		}), {
+			kind: "mutation",
+			auth: "admin"
+		}),
+		/**
 		* Render a short GIF or MP4 from the broker's PRE-BUFFER around an instant.
 		*
 		* The pre-buffer is the only source that already holds the seconds BEFORE
@@ -10336,6 +10479,35 @@ var deviceProviderCapability = {
 			name: z.string(),
 			type: z.string()
 		}))),
+		/**
+		* Tear down and reconstruct ONE device in place from its persisted rows —
+		* touching no other device this provider owns.
+		*
+		* The primitive `deviceManager.migrateDevice` uses to flush the two
+		* migrated numbers: after `swapIds` the runner's live instance still
+		* carries the PRE-swap numeric id (baked into the object, its native-cap
+		* registrations and its log tags), and a live object cannot be renumbered.
+		* Before this method the only flush was restarting the whole owning addon
+		* — which took every camera the provider owns down with it (28 devices
+		* for one migrated camera, measured 2026-09-04, and the morning of the
+		* same day ~27 devices' native caps did not come back on their own).
+		*
+		* Keyed by `stableId`, deliberately: the numeric id is exactly the thing
+		* that changes. The reply carries the id the device answers on NOW.
+		* Implemented once in `BaseDeviceProvider` — decommission the live
+		* instance (if any), then re-create from the persisted row: the same
+		* teardown/rehydrate pair every graceful shutdown + boot already uses.
+		* An RPC, never an event: a dropped event would leave the runner writing
+		* against the wrong camera (D8).
+		*
+		* Construction can dial hardware, and the migrated source is
+		* characteristically dead — the timeout covers a full activate window
+		* rather than the 60 s default.
+		*/
+		reloadDevice: method(z.object({ stableId: z.string() }), z.object({ deviceId: z.number() }), {
+			kind: "mutation",
+			timeoutMs: 3 * 6e4
+		}),
 		supportsDiscovery: method(z.object({}), z.boolean()),
 		/**
 		* Run a network scan. `params` carries optional provider-specific scan
@@ -10688,13 +10860,21 @@ var deviceManagerCapability = {
 		* `sourceStillLive` names what stayed live; empty is the only value that
 		* means the old hardware is quiet. The migration proceeds either way —
 		* refusing would refuse the case this exists for.
+		*
+		* **Safe to retry.** A duplicate call while a migration involving either
+		* device is in flight is REFUSED, never queued; a repeat of a swap that
+		* already completed (matched against the `addonId`/`stableId` fingerprint
+		* the swap left on the rows, within 15 min) is a no-op returning the
+		* original report. A blind re-run can no longer silently undo the
+		* migration it retried.
 		*/
 		migrateDevice: method(z.object({
 			sourceId: z.number(),
 			targetId: z.number()
 		}), MigrateDeviceResultSchema, {
 			kind: "mutation",
-			auth: "admin"
+			auth: "admin",
+			timeoutMs: 12 * 6e4
 		}),
 		/** Register a device in the DB + in-memory registry. Called by DeviceManagerApi.register(). */
 		registerDevice: method(DeviceRegisterPayloadSchema, z.void(), { kind: "mutation" }),
@@ -34933,6 +35113,12 @@ var METHOD_ACCESS_MAP = Object.freeze({
 		addonId: null,
 		access: "create"
 	},
+	"backup.cancel": {
+		capName: "backup",
+		capScope: "system",
+		addonId: null,
+		access: "create"
+	},
 	"backup.delete": {
 		capName: "backup",
 		capScope: "system",
@@ -34975,6 +35161,12 @@ var METHOD_ACCESS_MAP = Object.freeze({
 		addonId: null,
 		access: "view"
 	},
+	"backup.listRuns": {
+		capName: "backup",
+		capScope: "system",
+		addonId: null,
+		access: "view"
+	},
 	"backup.listSchedules": {
 		capName: "backup",
 		capScope: "system",
@@ -36175,6 +36367,12 @@ var METHOD_ACCESS_MAP = Object.freeze({
 		addonId: null,
 		access: "view"
 	},
+	"deviceProvider.reloadDevice": {
+		capName: "device-provider",
+		capScope: "system",
+		addonId: null,
+		access: "create"
+	},
 	"deviceProvider.start": {
 		capName: "device-provider",
 		capScope: "system",
@@ -39541,6 +39739,12 @@ var METHOD_ACCESS_MAP = Object.freeze({
 		addonId: null,
 		access: "create"
 	},
+	"streamBroker.forgetDeviceHardware": {
+		capName: "stream-broker",
+		capScope: "system",
+		addonId: null,
+		access: "delete"
+	},
 	"streamBroker.getAllRtspEntries": {
 		capName: "stream-broker",
 		capScope: "system",
@@ -41999,6 +42203,11 @@ Object.freeze({
 		form: "single",
 		optional: false
 	}],
+	"streamBroker.forgetDeviceHardware": [{
+		name: "deviceId",
+		form: "single",
+		optional: false
+	}],
 	"streamBroker.getDeviceAudioMute": [{
 		name: "deviceId",
 		form: "single",

package/dist/{dist-C7qWwrK1.js → dist-whe0b4_3.js}

@@ -7164,6 +7164,89 @@ var LocationStatSchema = zod.z.object({
 	fileCount: zod.z.number(),
 	present: zod.z.boolean()
 });
+/** Lifecycle of a backup run. Terminal states: succeeded / failed / cancelled. */
+var BackupRunStateSchema = zod.z.enum([
+	"queued",
+	"running",
+	"succeeded",
+	"failed",
+	"cancelled"
+]);
+/**
+* Where a running backup currently is. `queued` before it starts,
+* `building` while the tar.gz is being staged, `uploading` during the
+* per-destination fan-out, `done` once terminal.
+*/
+var BackupRunPhaseSchema = zod.z.enum([
+	"queued",
+	"building",
+	"uploading",
+	"done"
+]);
+/**
+* Observable state of one backup run — readable WHILE it runs via
+* `backup.listRuns`. This is what makes the execution queue and
+* `backup.cancel` usable: the 2026-09-04 incident (two concurrent
+* multi-GB builds, staging 5.1 GB → 18 GB, load 62) was only
+* diagnosable with `du` because nothing reported that runs existed or
+* how large the staged archive had grown.
+*/
+var BackupRunSchema = zod.z.object({
+	/** Stable run id — the handle `backup.cancel` takes. */
+	id: zod.z.string(),
+	state: BackupRunStateSchema,
+	phase: BackupRunPhaseSchema,
+	/**
+	* Resolved destination location ids. Empty while queued (targets are
+	* resolved when the run starts, against the then-current policies).
+	*/
+	destinationIds: zod.z.array(zod.z.string()).readonly(),
+	label: zod.z.string().optional(),
+	/** ms-epoch when the run was submitted (trigger call / schedule fire). */
+	requestedAt: zod.z.number(),
+	/** ms-epoch when the run left the queue and started building. */
+	startedAt: zod.z.number().optional(),
+	/** ms-epoch when the run reached a terminal state. */
+	finishedAt: zod.z.number().optional(),
+	/** Compressed bytes of the staging archive written so far. */
+	stagedBytes: zod.z.number(),
+	/** Final staged archive size, once the build phase completes. */
+	archiveSizeBytes: zod.z.number().optional(),
+	/** Bytes pushed to the destination currently uploading. */
+	uploadedBytes: zod.z.number(),
+	/** Destinations where the archive fully landed (uploaded + indexed). */
+	completedDestinationIds: zod.z.array(zod.z.string()).readonly(),
+	/** Destinations that failed during the fan-out. */
+	failedDestinationIds: zod.z.array(zod.z.string()).readonly(),
+	/** Failure message when `state === 'failed'`. */
+	error: zod.z.string().optional(),
+	/**
+	* 1-based place in the execution queue — 1 = runs next. Present only
+	* while `state === 'queued'`. Stamped by the orchestrator from the
+	* queue's OWN pending order, never derived from timestamps, so the
+	* UI cannot show an order the executor will not honour.
+	*/
+	queuePosition: zod.z.number().int().min(1).optional()
+});
+/**
+* Result of `backup.trigger`. The call still resolves when the run
+* terminates (compat with schedule-driven runs and the admin UI), but
+* it now names the run and says whether it had to WAIT: a trigger that
+* arrives while another run is in flight is enqueued (or joined onto
+* an identical already-queued run), never started concurrently.
+*/
+var BackupTriggerResultSchema = zod.z.object({
+	/** The run this trigger mapped to — poll it via `listRuns`, stop it via `cancel`. */
+	runId: zod.z.string(),
+	/** True when the run waited behind an in-flight run instead of starting immediately. */
+	queued: zod.z.boolean(),
+	/** True when this trigger was coalesced onto an identical already-queued run. */
+	joined: zod.z.boolean(),
+	/** True when the run was cancelled before completing every destination. */
+	cancelled: zod.z.boolean(),
+	/** One entry per destination the archive landed at (partial on cancel). */
+	entries: zod.z.array(BackupEntrySchema).readonly()
+});
 /**
 * A backup schedule — the N:M "entry" that binds one cron cadence to a
 * SET of destination locations. Supersedes the per-location cron on
@@ -7221,6 +7304,11 @@ var backupCapability = {
 		* Trigger a backup. Without `destinations` the orchestrator fans
 		* out to every destination flagged as enabled in the routing
 		* config; with it, only the listed addons receive the archive.
+		*
+		* At most ONE backup run executes at a time — the source tree and
+		* the staging disk are shared by every run, so a second trigger
+		* while one is in flight is enqueued (or joined onto an identical
+		* queued run) and the result says so. See D342.
 		*/
 		trigger: method(zod.z.object({
 			/** Subset of registered `backup-destination` addon ids to write to. */
@@ -7234,7 +7322,30 @@ var backupCapability = {
 			* retention (manual runs).
 			*/
 			retentionCount: zod.z.number().int().min(1).max(1e3).optional()
-		}).optional(), zod.z.array(BackupEntrySchema).readonly(), {
+		}).optional(), BackupTriggerResultSchema, {
+			kind: "mutation",
+			auth: "admin"
+		}),
+		/**
+		* Every run the orchestrator knows about, in EXECUTION order: the
+		* running run first, then queued runs in the exact order they will
+		* execute (each with `queuePosition`, 1 = next), then the bounded
+		* finished history newest-first. Only one run executes at a time
+		* (D342) — the queued section IS the line. Each run carries live
+		* phase + byte counters so a runaway build is visible in seconds,
+		* not via `du`.
+		*/
+		listRuns: method(zod.z.void(), zod.z.array(BackupRunSchema).readonly(), { auth: "admin" }),
+		/**
+		* Stop a backup run. Mirrors `storage-migration.cancel` semantics:
+		* id in, `{ cancelled }` out — `false` when the run is unknown or
+		* already terminal. A QUEUED run is removed before it ever starts;
+		* the RUNNING run has its tar/upload stream actually aborted, the
+		* half-written staging archive is deleted, and the in-flight
+		* destination upload is aborted server-side (partial discarded).
+		* Destinations that already completed keep their archive.
+		*/
+		cancel: method(zod.z.object({ runId: zod.z.string() }), zod.z.object({ cancelled: zod.z.boolean() }), {
 			kind: "mutation",
 			auth: "admin"
 		}),
@@ -8112,6 +8223,38 @@ var streamBrokerCapability = {
 			auth: "admin"
 		}),
 		/**
+		* The HARDWARE behind a device number was replaced
+		* (`deviceManager.migrateDevice`). Forget every piece of broker state that
+		* described the old box, so the next catalog pull derives everything from
+		* the camera that is actually there:
+		*
+		*  - every `derived:*` stream definition — a derived is authored against a
+		*    specific profile layout, and against the wrong hardware its feeder
+		*    respawns forever (observed at attempt 2732 on the live hub,
+		*    2026-09-01);
+		*  - the profile-slot assignment entry, PURGED (not unassigned — unassign
+		*    marks the slot manual, which would pin the stale choice instead of
+		*    letting `computeInitialAssignment` re-derive it);
+		*  - the probe snapshots (`<deviceId>/…` — probed codec/resolution of the
+		*    old hardware);
+		*  - the persisted RTSP token rows for the device's brokers (keyed
+		*    `<deviceId>/<camStreamId>`; the stream ids change with the hardware,
+		*    so the rows are dead URLs).
+		*
+		* An RPC, deliberately — an event is telemetry and may be dropped (D8),
+		* and a dropped forget leaves a feeder respawning against a stream that
+		* does not exist.
+		*/
+		forgetDeviceHardware: method(zod.z.object({ deviceId: zod.z.number().int().nonnegative() }), zod.z.object({
+			derivedStreamsDeleted: zod.z.array(zod.z.string()).readonly(),
+			assignmentsPurged: zod.z.boolean(),
+			probeSnapshotsDropped: zod.z.number().int().nonnegative(),
+			rtspTokenRowsDeleted: zod.z.number().int().nonnegative()
+		}), {
+			kind: "mutation",
+			auth: "admin"
+		}),
+		/**
 		* Render a short GIF or MP4 from the broker's PRE-BUFFER around an instant.
 		*
 		* The pre-buffer is the only source that already holds the seconds BEFORE
@@ -10336,6 +10479,35 @@ var deviceProviderCapability = {
 			name: zod.z.string(),
 			type: zod.z.string()
 		}))),
+		/**
+		* Tear down and reconstruct ONE device in place from its persisted rows —
+		* touching no other device this provider owns.
+		*
+		* The primitive `deviceManager.migrateDevice` uses to flush the two
+		* migrated numbers: after `swapIds` the runner's live instance still
+		* carries the PRE-swap numeric id (baked into the object, its native-cap
+		* registrations and its log tags), and a live object cannot be renumbered.
+		* Before this method the only flush was restarting the whole owning addon
+		* — which took every camera the provider owns down with it (28 devices
+		* for one migrated camera, measured 2026-09-04, and the morning of the
+		* same day ~27 devices' native caps did not come back on their own).
+		*
+		* Keyed by `stableId`, deliberately: the numeric id is exactly the thing
+		* that changes. The reply carries the id the device answers on NOW.
+		* Implemented once in `BaseDeviceProvider` — decommission the live
+		* instance (if any), then re-create from the persisted row: the same
+		* teardown/rehydrate pair every graceful shutdown + boot already uses.
+		* An RPC, never an event: a dropped event would leave the runner writing
+		* against the wrong camera (D8).
+		*
+		* Construction can dial hardware, and the migrated source is
+		* characteristically dead — the timeout covers a full activate window
+		* rather than the 60 s default.
+		*/
+		reloadDevice: method(zod.z.object({ stableId: zod.z.string() }), zod.z.object({ deviceId: zod.z.number() }), {
+			kind: "mutation",
+			timeoutMs: 3 * 6e4
+		}),
 		supportsDiscovery: method(zod.z.object({}), zod.z.boolean()),
 		/**
 		* Run a network scan. `params` carries optional provider-specific scan
@@ -10688,13 +10860,21 @@ var deviceManagerCapability = {
 		* `sourceStillLive` names what stayed live; empty is the only value that
 		* means the old hardware is quiet. The migration proceeds either way —
 		* refusing would refuse the case this exists for.
+		*
+		* **Safe to retry.** A duplicate call while a migration involving either
+		* device is in flight is REFUSED, never queued; a repeat of a swap that
+		* already completed (matched against the `addonId`/`stableId` fingerprint
+		* the swap left on the rows, within 15 min) is a no-op returning the
+		* original report. A blind re-run can no longer silently undo the
+		* migration it retried.
 		*/
 		migrateDevice: method(zod.z.object({
 			sourceId: zod.z.number(),
 			targetId: zod.z.number()
 		}), MigrateDeviceResultSchema, {
 			kind: "mutation",
-			auth: "admin"
+			auth: "admin",
+			timeoutMs: 12 * 6e4
 		}),
 		/** Register a device in the DB + in-memory registry. Called by DeviceManagerApi.register(). */
 		registerDevice: method(DeviceRegisterPayloadSchema, zod.z.void(), { kind: "mutation" }),
@@ -34933,6 +35113,12 @@ var METHOD_ACCESS_MAP = Object.freeze({
 		addonId: null,
 		access: "create"
 	},
+	"backup.cancel": {
+		capName: "backup",
+		capScope: "system",
+		addonId: null,
+		access: "create"
+	},
 	"backup.delete": {
 		capName: "backup",
 		capScope: "system",
@@ -34975,6 +35161,12 @@ var METHOD_ACCESS_MAP = Object.freeze({
 		addonId: null,
 		access: "view"
 	},
+	"backup.listRuns": {
+		capName: "backup",
+		capScope: "system",
+		addonId: null,
+		access: "view"
+	},
 	"backup.listSchedules": {
 		capName: "backup",
 		capScope: "system",
@@ -36175,6 +36367,12 @@ var METHOD_ACCESS_MAP = Object.freeze({
 		addonId: null,
 		access: "view"
 	},
+	"deviceProvider.reloadDevice": {
+		capName: "device-provider",
+		capScope: "system",
+		addonId: null,
+		access: "create"
+	},
 	"deviceProvider.start": {
 		capName: "device-provider",
 		capScope: "system",
@@ -39541,6 +39739,12 @@ var METHOD_ACCESS_MAP = Object.freeze({
 		addonId: null,
 		access: "create"
 	},
+	"streamBroker.forgetDeviceHardware": {
+		capName: "stream-broker",
+		capScope: "system",
+		addonId: null,
+		access: "delete"
+	},
 	"streamBroker.getAllRtspEntries": {
 		capName: "stream-broker",
 		capScope: "system",
@@ -41999,6 +42203,11 @@ Object.freeze({
 		form: "single",
 		optional: false
 	}],
+	"streamBroker.forgetDeviceHardware": [{
+		name: "deviceId",
+		form: "single",
+		optional: false
+	}],
 	"streamBroker.getDeviceAudioMute": [{
 		name: "deviceId",
 		form: "single",