@camstack/addon-provider-amcrest 0.2.111 → 0.2.113

package/dist/addon.js

@@ -5367,7 +5367,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).
@@ -31059,14 +31059,81 @@ function summarisePrivacyAudio(profiles) {
 	if (profiles.length === 0) return null;
 	return profiles.some((p) => p.audioEnabled);
 }
+/**
+* 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(),
-	name: string()
+	name: string(),
+	/**
+	* 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(),
@@ -31088,7 +31155,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().nullable(),
+	source: _enum([
+		"operator",
+		"firmware",
+		"native",
+		"none"
+	])
 });
 var ptzCapability = {
 	name: "ptz",
@@ -31129,7 +31261,25 @@ var ptzCapability = {
 			auth: "admin"
 		}),
 		getOptions: method(object({ deviceId: number() }), PtzOptionsSchema),
+		/**
+		* Move to the camera's configured home preset. THROWS when
+		* `getHomePreset()` resolves to `none` -- a head that did not move must
+		* never look like a head that went home.
+		*/
 		goHome: method(object({ deviceId: number() }), _void(), { kind: "mutation" }),
+		/** Which preset `goHome` targets, and who decided it. */
+		getHomePreset: method(object({ deviceId: number() }), PtzHomePresetSchema),
+		/**
+		* Pin the home preset for this camera. `null` clears the operator's choice
+		* and falls back to whatever the firmware names, or to `none`.
+		*/
+		setHomePreset: method(object({
+			deviceId: number(),
+			presetId: string().nullable()
+		}), _void(), {
+			kind: "mutation",
+			auth: "admin"
+		}),
 		/**
 		* Pull the current PTZ position. Redundant with the auto-injected
 		* `getStatus` method (see `status` below); kept for callers that
@@ -40803,6 +40953,12 @@ Object.freeze({
 		addonId: null,
 		access: "delete"
 	},
+	"ptz.getHomePreset": {
+		capName: "ptz",
+		capScope: "device",
+		addonId: null,
+		access: "view"
+	},
 	"ptz.getOptions": {
 		capName: "ptz",
 		capScope: "device",
@@ -40851,6 +41007,12 @@ Object.freeze({
 		addonId: null,
 		access: "create"
 	},
+	"ptz.setHomePreset": {
+		capName: "ptz",
+		capScope: "device",
+		addonId: null,
+		access: "create"
+	},
 	"ptz.stop": {
 		capName: "ptz",
 		capScope: "device",
@@ -44024,6 +44186,11 @@ Object.freeze({
 		form: "single",
 		optional: false
 	}],
+	"ptz.getHomePreset": [{
+		name: "deviceId",
+		form: "single",
+		optional: false
+	}],
 	"ptz.getOptions": [{
 		name: "deviceId",
 		form: "single",
@@ -44064,6 +44231,11 @@ Object.freeze({
 		form: "single",
 		optional: false
 	}],
+	"ptz.setHomePreset": [{
+		name: "deviceId",
+		form: "single",
+		optional: false
+	}],
 	"ptz.stop": [{
 		name: "deviceId",
 		form: "single",
@@ -46139,6 +46311,17 @@ var amcrestDeviceCacheSchema = object({
 * carries only the technical connection knobs.
 */
 var amcrestCameraSchema = object({
+	/**
+	* Which preset `ptz.goHome` targets on THIS camera.
+	*
+	* Empty = nothing configured, and `goHome` then REFUSES. It used to go to a
+	* hardcoded slot on a vendor "convention" this fleet contradicts: reolink
+	* went to preset 0, which on device 592 holds "stanza"; amcrest went to
+	* preset 1, which on device 3836 holds "Preset1". Both swallowed the failure
+	* in a bare catch, so a head that never moved was indistinguishable from a
+	* head that went home.
+	*/
+	homePresetId: string().default("").describe("Preset id ptz.goHome targets (empty = goHome refuses)"),
 	host: string().describe("Camera IP / hostname"),
 	port: number().int().min(1).max(65535).default(80).describe("HTTP CGI port"),
 	https: boolean().default(false).describe("Use HTTPS for CGI"),
@@ -46246,6 +46429,24 @@ var AmcrestCamera = class AmcrestCamera extends BaseDevice {
 	get channel() {
 		return this.config.get("channel") ?? 1;
 	}
+	/**
+	* Which preset `goHome` targets, and who decided it.
+	*
+	* Dahua names no home of its own that we have probed, so the operator's pick
+	* is the only answer. With none, `none` -- and `goHome` refuses rather than
+	* moving the head to whatever happens to sit in slot 1.
+	*/
+	async resolveHomePreset() {
+		const chosen = this.config.get("homePresetId") ?? "";
+		if (chosen === "") return {
+			presetId: null,
+			source: "none"
+		};
+		return {
+			presetId: chosen,
+			source: "operator"
+		};
+	}
 	ensureClient() {
 		if (this.client) return this.client;
 		this.client = this.buildClient();
@@ -46751,6 +46952,19 @@ var AmcrestCamera = class AmcrestCamera extends BaseDevice {
 	*  auto-stop fires. The `usePTZ` UI hook already issues its own paired
 	*  `stop` after a client-side pulse window; this timer is a backstop so
 	*  a lone `move` (no following `stop`) can't leave the head gliding. */
+	/**
+	* Dahua's native PTZ speed scale is 1..8; `resolvePtzCodes` maps the cap's
+	* normalized 0..1 onto it. Eight steps is COARSE -- three neighbouring
+	* normalized requests round to the same one -- which is exactly why the
+	* granularity is reported through `getOptions` instead of being hidden
+	* behind a 0..1 float.
+	*/
+	static DAHUA_SPEED_STEPS = 8;
+	/**
+	* How long one `ptz.move` pulse runs, ms. The DENOMINATOR of "how far did
+	* the head travel per pulse", so it leaves the provider through
+	* `getOptions` rather than staying a private literal.
+	*/
 	static PTZ_PULSE_MS = 350;
 	/** Short per-call deadline (ms) for the PTZ start/stop CGI so a slow or
 	*  blocked camera round-trip fails fast instead of exceeding the
@@ -46876,7 +47090,9 @@ var AmcrestCamera = class AmcrestCamera extends BaseDevice {
 				if (deviceId !== this.id) return [];
 				return (await this.ensureClient().getPtzPresets(this.channel)).map((p) => ({
 					id: String(p.id),
-					name: p.name
+					name: p.name,
+					fn: null,
+					writable: true
 				}));
 			},
 			goToPreset: async ({ deviceId, presetId }) => {
@@ -46912,7 +47128,9 @@ var AmcrestCamera = class AmcrestCamera extends BaseDevice {
 					hasTilt: false,
 					hasZoom: false,
 					supportsPresets: false,
-					hasAutofocus: false
+					hasAutofocus: false,
+					speedSteps: AmcrestCamera.DAHUA_SPEED_STEPS,
+					moveImpulseMs: AmcrestCamera.PTZ_PULSE_MS
 				};
 				if (deviceId !== this.id) return cold;
 				const caps = await this.ensureClient().getPtzCaps(this.channel);
@@ -46923,26 +47141,43 @@ var AmcrestCamera = class AmcrestCamera extends BaseDevice {
 					hasZoom: caps.hasZoom,
 					supportsPresets: caps.supportsPreset,
 					hasAutofocus: false,
+					speedSteps: AmcrestCamera.DAHUA_SPEED_STEPS,
+					moveImpulseMs: AmcrestCamera.PTZ_PULSE_MS,
 					...caps.maxPresets !== null ? { maxPresets: caps.maxPresets } : {}
 				};
 			},
 			goHome: async ({ deviceId }) => {
 				if (deviceId !== this.id) return;
+				const home = await this.resolveHomePreset();
+				if (home.source === "none" || home.presetId === null) throw new Error("No home preset configured for this camera — set one in the PTZ settings");
+				const id = Number.parseInt(home.presetId, 10);
+				if (!Number.isFinite(id) || id < 1) throw new Error(`Configured home preset is not a Dahua preset id: ${home.presetId}`);
 				const client = this.ensureClient();
-				this.enqueuePtz("goHome", () => client.ptzGotoPreset(this.channel, 1, AmcrestCamera.PTZ_CGI_TIMEOUT_MS));
+				this.enqueuePtz("goHome", () => client.ptzGotoPreset(this.channel, id, AmcrestCamera.PTZ_CGI_TIMEOUT_MS));
+			},
+			getHomePreset: async ({ deviceId }) => {
+				if (deviceId !== this.id) return {
+					presetId: null,
+					source: "none"
+				};
+				return this.resolveHomePreset();
+			},
+			setHomePreset: async ({ deviceId, presetId }) => {
+				if (deviceId !== this.id) return;
+				await this.config.setAll({ homePresetId: presetId ?? "" });
 			},
 			getPosition: async () => {
 				return {
-					pan: 0,
-					tilt: 0,
-					zoom: 0
+					pan: null,
+					tilt: null,
+					zoom: null
 				};
 			},
 			getStatus: async () => {
 				return {
-					pan: 0,
-					tilt: 0,
-					zoom: 0,
+					pan: null,
+					tilt: null,
+					zoom: null,
 					autofocus: false
 				};
 			},

package/dist/addon.mjs

@@ -5368,7 +5368,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).
@@ -31060,14 +31060,81 @@ function summarisePrivacyAudio(profiles) {
 	if (profiles.length === 0) return null;
 	return profiles.some((p) => p.audioEnabled);
 }
+/**
+* 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(),
-	name: string()
+	name: string(),
+	/**
+	* 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(),
@@ -31089,7 +31156,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().nullable(),
+	source: _enum([
+		"operator",
+		"firmware",
+		"native",
+		"none"
+	])
 });
 var ptzCapability = {
 	name: "ptz",
@@ -31130,7 +31262,25 @@ var ptzCapability = {
 			auth: "admin"
 		}),
 		getOptions: method(object({ deviceId: number() }), PtzOptionsSchema),
+		/**
+		* Move to the camera's configured home preset. THROWS when
+		* `getHomePreset()` resolves to `none` -- a head that did not move must
+		* never look like a head that went home.
+		*/
 		goHome: method(object({ deviceId: number() }), _void(), { kind: "mutation" }),
+		/** Which preset `goHome` targets, and who decided it. */
+		getHomePreset: method(object({ deviceId: number() }), PtzHomePresetSchema),
+		/**
+		* Pin the home preset for this camera. `null` clears the operator's choice
+		* and falls back to whatever the firmware names, or to `none`.
+		*/
+		setHomePreset: method(object({
+			deviceId: number(),
+			presetId: string().nullable()
+		}), _void(), {
+			kind: "mutation",
+			auth: "admin"
+		}),
 		/**
 		* Pull the current PTZ position. Redundant with the auto-injected
 		* `getStatus` method (see `status` below); kept for callers that
@@ -40804,6 +40954,12 @@ Object.freeze({
 		addonId: null,
 		access: "delete"
 	},
+	"ptz.getHomePreset": {
+		capName: "ptz",
+		capScope: "device",
+		addonId: null,
+		access: "view"
+	},
 	"ptz.getOptions": {
 		capName: "ptz",
 		capScope: "device",
@@ -40852,6 +41008,12 @@ Object.freeze({
 		addonId: null,
 		access: "create"
 	},
+	"ptz.setHomePreset": {
+		capName: "ptz",
+		capScope: "device",
+		addonId: null,
+		access: "create"
+	},
 	"ptz.stop": {
 		capName: "ptz",
 		capScope: "device",
@@ -44025,6 +44187,11 @@ Object.freeze({
 		form: "single",
 		optional: false
 	}],
+	"ptz.getHomePreset": [{
+		name: "deviceId",
+		form: "single",
+		optional: false
+	}],
 	"ptz.getOptions": [{
 		name: "deviceId",
 		form: "single",
@@ -44065,6 +44232,11 @@ Object.freeze({
 		form: "single",
 		optional: false
 	}],
+	"ptz.setHomePreset": [{
+		name: "deviceId",
+		form: "single",
+		optional: false
+	}],
 	"ptz.stop": [{
 		name: "deviceId",
 		form: "single",
@@ -46140,6 +46312,17 @@ var amcrestDeviceCacheSchema = object({
 * carries only the technical connection knobs.
 */
 var amcrestCameraSchema = object({
+	/**
+	* Which preset `ptz.goHome` targets on THIS camera.
+	*
+	* Empty = nothing configured, and `goHome` then REFUSES. It used to go to a
+	* hardcoded slot on a vendor "convention" this fleet contradicts: reolink
+	* went to preset 0, which on device 592 holds "stanza"; amcrest went to
+	* preset 1, which on device 3836 holds "Preset1". Both swallowed the failure
+	* in a bare catch, so a head that never moved was indistinguishable from a
+	* head that went home.
+	*/
+	homePresetId: string().default("").describe("Preset id ptz.goHome targets (empty = goHome refuses)"),
 	host: string().describe("Camera IP / hostname"),
 	port: number().int().min(1).max(65535).default(80).describe("HTTP CGI port"),
 	https: boolean().default(false).describe("Use HTTPS for CGI"),
@@ -46247,6 +46430,24 @@ var AmcrestCamera = class AmcrestCamera extends BaseDevice {
 	get channel() {
 		return this.config.get("channel") ?? 1;
 	}
+	/**
+	* Which preset `goHome` targets, and who decided it.
+	*
+	* Dahua names no home of its own that we have probed, so the operator's pick
+	* is the only answer. With none, `none` -- and `goHome` refuses rather than
+	* moving the head to whatever happens to sit in slot 1.
+	*/
+	async resolveHomePreset() {
+		const chosen = this.config.get("homePresetId") ?? "";
+		if (chosen === "") return {
+			presetId: null,
+			source: "none"
+		};
+		return {
+			presetId: chosen,
+			source: "operator"
+		};
+	}
 	ensureClient() {
 		if (this.client) return this.client;
 		this.client = this.buildClient();
@@ -46752,6 +46953,19 @@ var AmcrestCamera = class AmcrestCamera extends BaseDevice {
 	*  auto-stop fires. The `usePTZ` UI hook already issues its own paired
 	*  `stop` after a client-side pulse window; this timer is a backstop so
 	*  a lone `move` (no following `stop`) can't leave the head gliding. */
+	/**
+	* Dahua's native PTZ speed scale is 1..8; `resolvePtzCodes` maps the cap's
+	* normalized 0..1 onto it. Eight steps is COARSE -- three neighbouring
+	* normalized requests round to the same one -- which is exactly why the
+	* granularity is reported through `getOptions` instead of being hidden
+	* behind a 0..1 float.
+	*/
+	static DAHUA_SPEED_STEPS = 8;
+	/**
+	* How long one `ptz.move` pulse runs, ms. The DENOMINATOR of "how far did
+	* the head travel per pulse", so it leaves the provider through
+	* `getOptions` rather than staying a private literal.
+	*/
 	static PTZ_PULSE_MS = 350;
 	/** Short per-call deadline (ms) for the PTZ start/stop CGI so a slow or
 	*  blocked camera round-trip fails fast instead of exceeding the
@@ -46877,7 +47091,9 @@ var AmcrestCamera = class AmcrestCamera extends BaseDevice {
 				if (deviceId !== this.id) return [];
 				return (await this.ensureClient().getPtzPresets(this.channel)).map((p) => ({
 					id: String(p.id),
-					name: p.name
+					name: p.name,
+					fn: null,
+					writable: true
 				}));
 			},
 			goToPreset: async ({ deviceId, presetId }) => {
@@ -46913,7 +47129,9 @@ var AmcrestCamera = class AmcrestCamera extends BaseDevice {
 					hasTilt: false,
 					hasZoom: false,
 					supportsPresets: false,
-					hasAutofocus: false
+					hasAutofocus: false,
+					speedSteps: AmcrestCamera.DAHUA_SPEED_STEPS,
+					moveImpulseMs: AmcrestCamera.PTZ_PULSE_MS
 				};
 				if (deviceId !== this.id) return cold;
 				const caps = await this.ensureClient().getPtzCaps(this.channel);
@@ -46924,26 +47142,43 @@ var AmcrestCamera = class AmcrestCamera extends BaseDevice {
 					hasZoom: caps.hasZoom,
 					supportsPresets: caps.supportsPreset,
 					hasAutofocus: false,
+					speedSteps: AmcrestCamera.DAHUA_SPEED_STEPS,
+					moveImpulseMs: AmcrestCamera.PTZ_PULSE_MS,
 					...caps.maxPresets !== null ? { maxPresets: caps.maxPresets } : {}
 				};
 			},
 			goHome: async ({ deviceId }) => {
 				if (deviceId !== this.id) return;
+				const home = await this.resolveHomePreset();
+				if (home.source === "none" || home.presetId === null) throw new Error("No home preset configured for this camera — set one in the PTZ settings");
+				const id = Number.parseInt(home.presetId, 10);
+				if (!Number.isFinite(id) || id < 1) throw new Error(`Configured home preset is not a Dahua preset id: ${home.presetId}`);
 				const client = this.ensureClient();
-				this.enqueuePtz("goHome", () => client.ptzGotoPreset(this.channel, 1, AmcrestCamera.PTZ_CGI_TIMEOUT_MS));
+				this.enqueuePtz("goHome", () => client.ptzGotoPreset(this.channel, id, AmcrestCamera.PTZ_CGI_TIMEOUT_MS));
+			},
+			getHomePreset: async ({ deviceId }) => {
+				if (deviceId !== this.id) return {
+					presetId: null,
+					source: "none"
+				};
+				return this.resolveHomePreset();
+			},
+			setHomePreset: async ({ deviceId, presetId }) => {
+				if (deviceId !== this.id) return;
+				await this.config.setAll({ homePresetId: presetId ?? "" });
 			},
 			getPosition: async () => {
 				return {
-					pan: 0,
-					tilt: 0,
-					zoom: 0
+					pan: null,
+					tilt: null,
+					zoom: null
 				};
 			},
 			getStatus: async () => {
 				return {
-					pan: 0,
-					tilt: 0,
-					zoom: 0,
+					pan: null,
+					tilt: null,
+					zoom: null,
 					autofocus: false
 				};
 			},

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@camstack/addon-provider-amcrest",
-  "version": "0.2.111",
+  "version": "0.2.113",
   "description": "Amcrest/Dahua camera device provider addon for CamStack — Dahua CGI over HTTP(S) with digest auth (snapshot, RTSP catalog, PTZ, image/day-night config)",
   "keywords": [
     "camstack",