@camstack/addon-matter-broker 0.2.108 → 0.2.110

package/dist/addon.js

@@ -5374,7 +5374,7 @@ var ZodIssueCode = {
 var ZodFirstPartyTypeKind;
 ZodFirstPartyTypeKind || (ZodFirstPartyTypeKind = {});
 //#endregion
-//#region ../types/dist/sleep-BDR76Ykr.mjs
+//#region ../types/dist/sleep-B1y0Fo1U.mjs
 /**
 * The audio chunk plane's byte format, and the ONE expansion from a coded
 * window to float samples (D455).
@@ -30966,14 +30966,81 @@ var privacyMaskCapability = {
 	*  whether persisting is worth a SQLite commit. */
 	volatileStateFields: ["lastFetchedAt"]
 };
+/**
+* What a preset id DOES on this camera.
+*
+* On several PTZ firmwares the preset namespace is shared: low ids are stored
+* positions, a reserved band triggers camera FUNCTIONS. The dispensa camera
+* (Hikvision) returns its own reserved band in the preset list, named by the
+* firmware:
+*
+*   34 Back to origin · 39 Day mode · 40 Night mode · 46 Day/Night Auto Mode
+*   92 Set manual limits · 93 Save manual limits · 94 Remote reboot
+*   95 Call OSD menu
+*
+* We used to hand all of these to the UI as ordinary presets. Saving over one
+* is what produced `PUT /ISAPI/PTZCtrl/channels/1/presets/34 -> HTTP 500`: the
+* camera refusing to let "Back to origin" be overwritten, surfaced to the
+* operator as a transport failure.
+*
+* A function preset stays fully usable as a DESTINATION -- `goToPreset('34')`
+* is the single most useful thing that camera can do. Only `savePreset` and
+* `deletePreset` are gated.
+*/
+var PtzPresetFunctionSchema = _enum([
+	"home",
+	"day-mode",
+	"night-mode",
+	"day-night-auto",
+	"set-limits",
+	"save-limits",
+	"reboot",
+	"osd-menu"
+]);
 var PtzPresetSchema = object({
 	id: string$2(),
-	name: string$2()
+	name: string$2(),
+	/**
+	* The firmware function this id performs, when the provider KNOWS the id is
+	* reserved. `null` = an ordinary stored position, OR a reserved id this
+	* provider does not recognise -- the two are told apart by `writable`.
+	*/
+	fn: PtzPresetFunctionSchema.nullable(),
+	/**
+	* Whether `savePreset` / `deletePreset` may target this id. A provider sets
+	* it false only for a band it KNOWS is reserved; where the firmware is not
+	* documented it stays true and a refusal comes from the camera, named.
+	*/
+	writable: boolean()
 });
+/**
+* Where the head is pointing -- per axis, and `null` when the driver cannot
+* read it.
+*
+* It used to be three REQUIRED numbers, which left a provider that cannot read
+* position no way to say so. All four said `0`:
+*
+*   reolink   `return { pan: 0, tilt: 0, zoom: 0 }`  "until a position-query
+*                                                     path lands upstream"
+*   hikvision stub, "firmware-dependent and frequently absent"
+*   amcrest   stub, "no generic absolute-position read for this model family"
+*   onvif     throws
+*
+* So every consumer asking where a camera points was told "perfectly centred"
+* by four cameras that had never looked. That is D393 -- a measurement that
+* FAILED is `null`, never `0`, and the type says so all the way to the
+* decision -- the same shape as the unreadable `statfs` folded into "0 bytes of
+* headroom", which evacuated a healthy disk.
+*
+* D393 also says to check for a narrower structural TWIN of the result type.
+* There is one: `PtzStatusSchema` extends this, so the lie had already
+* propagated into `getStatus`, which is the surface `getPosition`'s own comment
+* tells callers to migrate to.
+*/
 var PtzPositionSchema = object({
-	pan: number(),
-	tilt: number(),
-	zoom: number()
+	pan: number().nullable(),
+	tilt: number().nullable(),
+	zoom: number().nullable()
 });
 var PtzMoveCommandSchema = object({
 	pan: number().optional(),
@@ -30992,7 +31059,72 @@ var PtzOptionsSchema = object({
 	maxPresets: number().optional(),
 	/** Whether the camera exposes a controllable autofocus toggle
 	*  (boolean `hasX` per the getOptions availability convention). */
-	hasAutofocus: boolean()
+	hasAutofocus: boolean(),
+	/**
+	* How many distinct speeds this camera's NATIVE scale offers.
+	*
+	* The cap's `speed` is normalized 0..1 and each provider maps it down --
+	* Baichuan 1..63, Dahua 1..8, ISAPI's percentage -100..100. The normalized
+	* value hides how coarse that really is: asking an amcrest for `0.37` is
+	* meaningless, because it has eight steps and three of them round to the
+	* same one. A loop that tunes its own gain has to know the granularity of
+	* the knob it is turning.
+	*
+	* `null` = the driver does not know, or the scale is continuous (ONVIF takes
+	* a float). Never a made-up number.
+	*/
+	speedSteps: number().int().positive().nullable(),
+	/**
+	* How long ONE `move` pulse runs on this driver, ms.
+	*
+	* `move` is a self-terminating burst everywhere, but every provider hardcoded
+	* its own duration in private -- 200 reolink, 350 amcrest, 500 hikvision,
+	* 1000 onvif -- so no caller could read it. It is the DENOMINATOR of "how far
+	* did the head travel per pulse": without it a measured displacement has no
+	* gain to be divided into.
+	*
+	* `null` = the driver cannot say.
+	*/
+	moveImpulseMs: number().int().positive().nullable()
+});
+/**
+* Which preset `goHome` goes to, and WHO decided.
+*
+* `goHome` used to be three vendor "conventions" written in three comments --
+* Reolink preset 0, Hikvision preset '1', Dahua preset 1 -- and on this fleet
+* not one of the three cameras honours its own:
+*
+*   592  Videocamera camera Daniel (reolink)   preset 0 holds "stanza"
+*   1438 Videocamera dispensa (hikvision)      preset 1 holds "Credenza"
+*   3836 Videocamera studio (amcrest)          preset 1 holds "Preset1"
+*
+* So `goHome` meant "go wherever the operator happened to save in slot 0 or 1",
+* and two of the three swallowed the failure in a bare `catch`. For autotrack
+* this is the HOTTEST path -- it runs every time a subject is released -- so it
+* needs an answer that is true per camera and audible when it is missing.
+*
+* `source` is what makes it honest:
+*   - `operator` -- picked in the UI, stored by the provider.
+*   - `firmware` -- the camera itself named a preset `fn: 'home'` (Hikvision's
+*     "Back to origin"), adopted as the default with nothing to configure.
+*   - `native`   -- the driver homes WITHOUT a preset at all. ONVIF does:
+*     `goHome` is `ptzAbsoluteMove({x:0, y:0, zoom:0})`. `presetId` is null and
+*     that is not a failure -- there is nothing to pick, and the UI must offer
+*     no picker.
+*   - `none`     -- nothing is configured and the camera names nothing.
+*     `goHome` REFUSES rather than moving the head somewhere arbitrary.
+*
+* `source === 'none'` is the refusal condition, NOT `presetId === null`: the
+* native case has no preset and homes perfectly well.
+*/
+var PtzHomePresetSchema = object({
+	presetId: string$2().nullable(),
+	source: _enum([
+		"operator",
+		"firmware",
+		"native",
+		"none"
+	])
 });
 DeviceType.Camera, method(PtzMoveCommandSchema.extend({ deviceId: number() }), _void(), { kind: "mutation" }), method(PtzMoveCommandSchema.extend({ deviceId: number() }), _void(), { kind: "mutation" }), method(object({ deviceId: number() }), _void(), { kind: "mutation" }), method(object({ deviceId: number() }), array(PtzPresetSchema)), method(object({
 	deviceId: number(),
@@ -31010,7 +31142,13 @@ DeviceType.Camera, method(PtzMoveCommandSchema.extend({ deviceId: number() }), _
 }), _void(), {
 	kind: "mutation",
 	auth: "admin"
-}), method(object({ deviceId: number() }), PtzOptionsSchema), method(object({ deviceId: number() }), _void(), { kind: "mutation" }), method(object({ deviceId: number() }), PtzPositionSchema), method(object({
+}), method(object({ deviceId: number() }), PtzOptionsSchema), method(object({ deviceId: number() }), _void(), { kind: "mutation" }), method(object({ deviceId: number() }), PtzHomePresetSchema), method(object({
+	deviceId: number(),
+	presetId: string$2().nullable()
+}), _void(), {
+	kind: "mutation",
+	auth: "admin"
+}), method(object({ deviceId: number() }), PtzPositionSchema), method(object({
 	deviceId: number(),
 	enabled: boolean()
 }), _void(), { kind: "mutation" });
@@ -40264,6 +40402,12 @@ Object.freeze({
 		addonId: null,
 		access: "delete"
 	},
+	"ptz.getHomePreset": {
+		capName: "ptz",
+		capScope: "device",
+		addonId: null,
+		access: "view"
+	},
 	"ptz.getOptions": {
 		capName: "ptz",
 		capScope: "device",
@@ -40312,6 +40456,12 @@ Object.freeze({
 		addonId: null,
 		access: "create"
 	},
+	"ptz.setHomePreset": {
+		capName: "ptz",
+		capScope: "device",
+		addonId: null,
+		access: "create"
+	},
 	"ptz.stop": {
 		capName: "ptz",
 		capScope: "device",
@@ -43485,6 +43635,11 @@ Object.freeze({
 		form: "single",
 		optional: false
 	}],
+	"ptz.getHomePreset": [{
+		name: "deviceId",
+		form: "single",
+		optional: false
+	}],
 	"ptz.getOptions": [{
 		name: "deviceId",
 		form: "single",
@@ -43525,6 +43680,11 @@ Object.freeze({
 		form: "single",
 		optional: false
 	}],
+	"ptz.setHomePreset": [{
+		name: "deviceId",
+		form: "single",
+		optional: false
+	}],
 	"ptz.stop": [{
 		name: "deviceId",
 		form: "single",

package/dist/addon.mjs

@@ -5372,7 +5372,7 @@ var ZodIssueCode = {
 var ZodFirstPartyTypeKind;
 ZodFirstPartyTypeKind || (ZodFirstPartyTypeKind = {});
 //#endregion
-//#region ../types/dist/sleep-BDR76Ykr.mjs
+//#region ../types/dist/sleep-B1y0Fo1U.mjs
 /**
 * The audio chunk plane's byte format, and the ONE expansion from a coded
 * window to float samples (D455).
@@ -30964,14 +30964,81 @@ var privacyMaskCapability = {
 	*  whether persisting is worth a SQLite commit. */
 	volatileStateFields: ["lastFetchedAt"]
 };
+/**
+* What a preset id DOES on this camera.
+*
+* On several PTZ firmwares the preset namespace is shared: low ids are stored
+* positions, a reserved band triggers camera FUNCTIONS. The dispensa camera
+* (Hikvision) returns its own reserved band in the preset list, named by the
+* firmware:
+*
+*   34 Back to origin · 39 Day mode · 40 Night mode · 46 Day/Night Auto Mode
+*   92 Set manual limits · 93 Save manual limits · 94 Remote reboot
+*   95 Call OSD menu
+*
+* We used to hand all of these to the UI as ordinary presets. Saving over one
+* is what produced `PUT /ISAPI/PTZCtrl/channels/1/presets/34 -> HTTP 500`: the
+* camera refusing to let "Back to origin" be overwritten, surfaced to the
+* operator as a transport failure.
+*
+* A function preset stays fully usable as a DESTINATION -- `goToPreset('34')`
+* is the single most useful thing that camera can do. Only `savePreset` and
+* `deletePreset` are gated.
+*/
+var PtzPresetFunctionSchema = _enum([
+	"home",
+	"day-mode",
+	"night-mode",
+	"day-night-auto",
+	"set-limits",
+	"save-limits",
+	"reboot",
+	"osd-menu"
+]);
 var PtzPresetSchema = object({
 	id: string$2(),
-	name: string$2()
+	name: string$2(),
+	/**
+	* The firmware function this id performs, when the provider KNOWS the id is
+	* reserved. `null` = an ordinary stored position, OR a reserved id this
+	* provider does not recognise -- the two are told apart by `writable`.
+	*/
+	fn: PtzPresetFunctionSchema.nullable(),
+	/**
+	* Whether `savePreset` / `deletePreset` may target this id. A provider sets
+	* it false only for a band it KNOWS is reserved; where the firmware is not
+	* documented it stays true and a refusal comes from the camera, named.
+	*/
+	writable: boolean()
 });
+/**
+* Where the head is pointing -- per axis, and `null` when the driver cannot
+* read it.
+*
+* It used to be three REQUIRED numbers, which left a provider that cannot read
+* position no way to say so. All four said `0`:
+*
+*   reolink   `return { pan: 0, tilt: 0, zoom: 0 }`  "until a position-query
+*                                                     path lands upstream"
+*   hikvision stub, "firmware-dependent and frequently absent"
+*   amcrest   stub, "no generic absolute-position read for this model family"
+*   onvif     throws
+*
+* So every consumer asking where a camera points was told "perfectly centred"
+* by four cameras that had never looked. That is D393 -- a measurement that
+* FAILED is `null`, never `0`, and the type says so all the way to the
+* decision -- the same shape as the unreadable `statfs` folded into "0 bytes of
+* headroom", which evacuated a healthy disk.
+*
+* D393 also says to check for a narrower structural TWIN of the result type.
+* There is one: `PtzStatusSchema` extends this, so the lie had already
+* propagated into `getStatus`, which is the surface `getPosition`'s own comment
+* tells callers to migrate to.
+*/
 var PtzPositionSchema = object({
-	pan: number(),
-	tilt: number(),
-	zoom: number()
+	pan: number().nullable(),
+	tilt: number().nullable(),
+	zoom: number().nullable()
 });
 var PtzMoveCommandSchema = object({
 	pan: number().optional(),
@@ -30990,7 +31057,72 @@ var PtzOptionsSchema = object({
 	maxPresets: number().optional(),
 	/** Whether the camera exposes a controllable autofocus toggle
 	*  (boolean `hasX` per the getOptions availability convention). */
-	hasAutofocus: boolean()
+	hasAutofocus: boolean(),
+	/**
+	* How many distinct speeds this camera's NATIVE scale offers.
+	*
+	* The cap's `speed` is normalized 0..1 and each provider maps it down --
+	* Baichuan 1..63, Dahua 1..8, ISAPI's percentage -100..100. The normalized
+	* value hides how coarse that really is: asking an amcrest for `0.37` is
+	* meaningless, because it has eight steps and three of them round to the
+	* same one. A loop that tunes its own gain has to know the granularity of
+	* the knob it is turning.
+	*
+	* `null` = the driver does not know, or the scale is continuous (ONVIF takes
+	* a float). Never a made-up number.
+	*/
+	speedSteps: number().int().positive().nullable(),
+	/**
+	* How long ONE `move` pulse runs on this driver, ms.
+	*
+	* `move` is a self-terminating burst everywhere, but every provider hardcoded
+	* its own duration in private -- 200 reolink, 350 amcrest, 500 hikvision,
+	* 1000 onvif -- so no caller could read it. It is the DENOMINATOR of "how far
+	* did the head travel per pulse": without it a measured displacement has no
+	* gain to be divided into.
+	*
+	* `null` = the driver cannot say.
+	*/
+	moveImpulseMs: number().int().positive().nullable()
+});
+/**
+* Which preset `goHome` goes to, and WHO decided.
+*
+* `goHome` used to be three vendor "conventions" written in three comments --
+* Reolink preset 0, Hikvision preset '1', Dahua preset 1 -- and on this fleet
+* not one of the three cameras honours its own:
+*
+*   592  Videocamera camera Daniel (reolink)   preset 0 holds "stanza"
+*   1438 Videocamera dispensa (hikvision)      preset 1 holds "Credenza"
+*   3836 Videocamera studio (amcrest)          preset 1 holds "Preset1"
+*
+* So `goHome` meant "go wherever the operator happened to save in slot 0 or 1",
+* and two of the three swallowed the failure in a bare `catch`. For autotrack
+* this is the HOTTEST path -- it runs every time a subject is released -- so it
+* needs an answer that is true per camera and audible when it is missing.
+*
+* `source` is what makes it honest:
+*   - `operator` -- picked in the UI, stored by the provider.
+*   - `firmware` -- the camera itself named a preset `fn: 'home'` (Hikvision's
+*     "Back to origin"), adopted as the default with nothing to configure.
+*   - `native`   -- the driver homes WITHOUT a preset at all. ONVIF does:
+*     `goHome` is `ptzAbsoluteMove({x:0, y:0, zoom:0})`. `presetId` is null and
+*     that is not a failure -- there is nothing to pick, and the UI must offer
+*     no picker.
+*   - `none`     -- nothing is configured and the camera names nothing.
+*     `goHome` REFUSES rather than moving the head somewhere arbitrary.
+*
+* `source === 'none'` is the refusal condition, NOT `presetId === null`: the
+* native case has no preset and homes perfectly well.
+*/
+var PtzHomePresetSchema = object({
+	presetId: string$2().nullable(),
+	source: _enum([
+		"operator",
+		"firmware",
+		"native",
+		"none"
+	])
 });
 DeviceType.Camera, method(PtzMoveCommandSchema.extend({ deviceId: number() }), _void(), { kind: "mutation" }), method(PtzMoveCommandSchema.extend({ deviceId: number() }), _void(), { kind: "mutation" }), method(object({ deviceId: number() }), _void(), { kind: "mutation" }), method(object({ deviceId: number() }), array(PtzPresetSchema)), method(object({
 	deviceId: number(),
@@ -31008,7 +31140,13 @@ DeviceType.Camera, method(PtzMoveCommandSchema.extend({ deviceId: number() }), _
 }), _void(), {
 	kind: "mutation",
 	auth: "admin"
-}), method(object({ deviceId: number() }), PtzOptionsSchema), method(object({ deviceId: number() }), _void(), { kind: "mutation" }), method(object({ deviceId: number() }), PtzPositionSchema), method(object({
+}), method(object({ deviceId: number() }), PtzOptionsSchema), method(object({ deviceId: number() }), _void(), { kind: "mutation" }), method(object({ deviceId: number() }), PtzHomePresetSchema), method(object({
+	deviceId: number(),
+	presetId: string$2().nullable()
+}), _void(), {
+	kind: "mutation",
+	auth: "admin"
+}), method(object({ deviceId: number() }), PtzPositionSchema), method(object({
 	deviceId: number(),
 	enabled: boolean()
 }), _void(), { kind: "mutation" });
@@ -40262,6 +40400,12 @@ Object.freeze({
 		addonId: null,
 		access: "delete"
 	},
+	"ptz.getHomePreset": {
+		capName: "ptz",
+		capScope: "device",
+		addonId: null,
+		access: "view"
+	},
 	"ptz.getOptions": {
 		capName: "ptz",
 		capScope: "device",
@@ -40310,6 +40454,12 @@ Object.freeze({
 		addonId: null,
 		access: "create"
 	},
+	"ptz.setHomePreset": {
+		capName: "ptz",
+		capScope: "device",
+		addonId: null,
+		access: "create"
+	},
 	"ptz.stop": {
 		capName: "ptz",
 		capScope: "device",
@@ -43483,6 +43633,11 @@ Object.freeze({
 		form: "single",
 		optional: false
 	}],
+	"ptz.getHomePreset": [{
+		name: "deviceId",
+		form: "single",
+		optional: false
+	}],
 	"ptz.getOptions": [{
 		name: "deviceId",
 		form: "single",
@@ -43523,6 +43678,11 @@ Object.freeze({
 		form: "single",
 		optional: false
 	}],
+	"ptz.setHomePreset": [{
+		name: "deviceId",
+		form: "single",
+		optional: false
+	}],
 	"ptz.stop": [{
 		name: "deviceId",
 		form: "single",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@camstack/addon-matter-broker",
-  "version": "0.2.108",
+  "version": "0.2.110",
   "description": "Matter broker addon for CamStack — owns a Matter fabric (commissioning + the long-lived controller) via the matter.js controller and brokers commissioned Matter nodes into CamStack",
   "keywords": [
     "camstack",