@camstack/types 1.2.214 → 1.2.215

package/dist/capabilities/ptz-autotrack.cap.d.ts

@@ -66,6 +66,25 @@ export declare const ptzAutotrackCapability: {
     readonly scope: "device";
     readonly deviceNative: true;
     readonly mode: "singleton";
+    /**
+     * Two kinds of provider behind one name, the same shape `snapshot` and
+     * `doorbell` use:
+     *
+     *  - **Native**: the camera's own firmware autotrack, registered per device by
+     *    the driver when the probe says it exists (Reolink: yes; Hikvision:
+     *    model-dependent).
+     *  - **Wrapper**: the emulated implementation (`@camstack/addon-autotrack`),
+     *    which follows a subject with `ptz.move` pulses driven by the detection
+     *    pipeline. `defaultActive: false` — the operator binds it per camera in
+     *    the bindings UI, exactly as `virtual-doorbell` is bound.
+     *
+     * The binding chooses WHICH implementation answers; `setEnabled` stays the
+     * one switch for the function either way. A camera never has both driving its
+     * head, which is the whole reason this is not a second cap with a second
+     * toggle (D62, D520).
+     */
+    readonly kind: "wrapper";
+    readonly defaultActive: false;
     readonly deviceTypes: readonly [DeviceType.Camera];
     readonly deviceConfig: {
         readonly ui: {

package/dist/index.js

@@ -35444,6 +35444,25 @@ var ptzAutotrackCapability = {
 	scope: "device",
 	deviceNative: true,
 	mode: "singleton",
+	/**
+	* Two kinds of provider behind one name, the same shape `snapshot` and
+	* `doorbell` use:
+	*
+	*  - **Native**: the camera's own firmware autotrack, registered per device by
+	*    the driver when the probe says it exists (Reolink: yes; Hikvision:
+	*    model-dependent).
+	*  - **Wrapper**: the emulated implementation (`@camstack/addon-autotrack`),
+	*    which follows a subject with `ptz.move` pulses driven by the detection
+	*    pipeline. `defaultActive: false` — the operator binds it per camera in
+	*    the bindings UI, exactly as `virtual-doorbell` is bound.
+	*
+	* The binding chooses WHICH implementation answers; `setEnabled` stays the
+	* one switch for the function either way. A camera never has both driving its
+	* head, which is the whole reason this is not a second cap with a second
+	* toggle (D62, D520).
+	*/
+	kind: "wrapper",
+	defaultActive: false,
 	deviceTypes: [require_sleep.DeviceType.Camera],
 	deviceConfig: { ui: {
 		kind: "widget",

package/dist/index.mjs

@@ -35443,6 +35443,25 @@ var ptzAutotrackCapability = {
 	scope: "device",
 	deviceNative: true,
 	mode: "singleton",
+	/**
+	* Two kinds of provider behind one name, the same shape `snapshot` and
+	* `doorbell` use:
+	*
+	*  - **Native**: the camera's own firmware autotrack, registered per device by
+	*    the driver when the probe says it exists (Reolink: yes; Hikvision:
+	*    model-dependent).
+	*  - **Wrapper**: the emulated implementation (`@camstack/addon-autotrack`),
+	*    which follows a subject with `ptz.move` pulses driven by the detection
+	*    pipeline. `defaultActive: false` — the operator binds it per camera in
+	*    the bindings UI, exactly as `virtual-doorbell` is bound.
+	*
+	* The binding chooses WHICH implementation answers; `setEnabled` stays the
+	* one switch for the function either way. A camera never has both driving its
+	* head, which is the whole reason this is not a second cap with a second
+	* toggle (D62, D520).
+	*/
+	kind: "wrapper",
+	defaultActive: false,
 	deviceTypes: [DeviceType.Camera],
 	deviceConfig: { ui: {
 		kind: "widget",

package/package.json

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