@mega-yfue/eufy-sdk 0.4.0-beta.31 → 0.4.0-beta.33

package/dist/model/capabilities/camera.d.ts

@@ -1,5 +1,5 @@
 import { type Surface } from "./members.js";
-import type { CapabilityModule, CommandContext } from "./types.js";
+import type { AvailabilityContext, CapabilityModule, CommandContext } from "./types.js";
 import { type Command, type MediaProvider } from "../../core/contracts.js";
 /**
  * The P2P **feature-command ids** this camera capability drives (direct-binary switches + `1350`
@@ -8,8 +8,10 @@ import { type Command, type MediaProvider } from "../../core/contracts.js";
  * `transport/p2p/commands.ts`). Each entry notes its app `CommandType` name.
  */
 export declare const CAMERA_CMD: {
-    /** Camera on/off. switch is inverted: camera ON ⇒ 0, OFF ⇒ 1. */
+    /** Camera on/off. Read and write polarity depend on the family and topology. */
     readonly CAMERA_ENABLE: 1035;
+    /** Wrapped T8410 power switch on HomeBase 3. */
+    readonly PRIVACY_MODE: 6250;
     /**
      * Camera status LED on/off — the "power/recording" indicator. The
      * app JS has a sibling param `1056` (`APP_CMD_LIVEVIEW_LED_SWITCH`) for the SAME UI "Status Light"
@@ -270,17 +272,17 @@ export type CameraActions = Surface<typeof CAMERA_MEMBERS> & {
  */
 export declare const CAMERA_MEMBERS: {
     /**
-     * The READ is the *disable*-bit convention (1035 "0" ⇒ ON, 2001 direct); the WRITE polarity is
+     * The default READ is the *disable*-bit convention (1035 "0" ⇒ ON, 2001 direct); the WRITE polarity is
      * family-dependent — see `powerValue` / `isEnableBitPolarity`. Battery/solo cams report the state under
      * 1035, standalone indoor/outdoor cams under 2001 OPEN_DEVICE with direct polarity, so 2001 is a
      * read-alias. Both verified live, and the write polarity is confirmed against the app's own frames.
      *
-     * The read and the setter observe the SAME wire on every family — see `powerCommand` — which is what
-     * makes this value track what it is told, and what lets `enablementReflection` confirm a write.
+     * T8410 on HomeBase 3 reports 1035 as an enable bit ("1" ⇒ ON). That reported state does not reliably
+     * reflect the privacy command. `readReflectsWrite` states this distinction.
      *
      * The privacy param (6250) is reported by the outdoor-PT family and by no other camera measured, and both
      * of its polarities are observed. It is deliberately NOT aliased here: it moved in the same step as 1035, so
-     * the reading cannot say whether power and privacy are one state or two, and the app drives 1035 — so
+     * the reading cannot say whether power and privacy are one state or two — so
      * aliasing a second param could only fold two possible states into one getter for no gain.
      */
     readonly enabled: {
@@ -289,10 +291,12 @@ export declare const CAMERA_MEMBERS: {
         readonly kind: "boolean";
         readonly provenance: "verified";
         readonly invert: true;
+        readonly invertFor: (ctx: AvailabilityContext) => false | undefined;
         readonly readAliases: readonly [{
             readonly paramType: 2001;
             readonly invert: false;
         }];
+        readonly readReflectsWrite: (ctx: CommandContext) => boolean;
         readonly description: string;
         readonly observation: {
             readonly event: "cameraEnabledChanged";
@@ -512,10 +516,10 @@ export declare const CAMERA_MEMBERS: {
         readonly type: "bool";
         readonly kind: "boolean";
         readonly provenance: "verified";
-        readonly readAvailable: (ctx: import("./types.js").AvailabilityContext) => boolean;
+        readonly readAvailable: (ctx: AvailabilityContext) => boolean;
         readonly readAliases: readonly [{
             readonly paramType: 1716;
-            readonly available: (ctx: import("./types.js").AvailabilityContext) => boolean;
+            readonly available: (ctx: AvailabilityContext) => boolean;
         }];
         readonly requiresRead: true;
         readonly description: "Camera status LED. Video doorbells report the same state under their button-ring LED parameter.";
@@ -526,7 +530,7 @@ export declare const CAMERA_MEMBERS: {
      * value, and it exists only on a device bound to a provider. Each is declared once, with its
      * signature taken FROM {@link MediaProvider} — so a change there is a compile error here, not a drift.
      *
-     * Every pull is refused where {@link CAMERA_MEMBERS.enabled} reads false, with {@link CameraDisabledError} —
+     * Every pull is refused where a reliable {@link CAMERA_MEMBERS.enabled} reads false, with {@link CameraDisabledError} —
      * `live`, `snapshotLive`, `record`, `openReadable` and `recordFragments` alike, since each opens media on a
      * camera that serves none. That reading is the on/off source; a live probe is not one, since a disabled
      * camera answers a start with audio and never a video frame.

package/dist/model/capabilities/members.d.ts

@@ -48,6 +48,8 @@ export interface ValueMember {
     enumValuesFor?: (ctx: AvailabilityContext) => Record<number, string> | undefined;
     provenance?: PropertySpec["provenance"];
     invert?: boolean;
+    /** Per-device read polarity; undefined retains the static default. */
+    invertFor?: (ctx: AvailabilityContext) => boolean | undefined;
     description: string;
     /** The wire, or absent for read-only. `undefined` from it = this value is not one we accept. */
     write?: (value: boolean | number | string, ctx: CommandContext) => Command | undefined;

package/dist/model/capabilities/types.d.ts

@@ -245,6 +245,8 @@ export interface AvailabilityContext {
      * cannot do what its name promises there.
      */
     homeBaseAttached?: boolean;
+    /** Serial of the covering station, when the device record names one. */
+    stationSerial?: string;
 }
 export interface CommandContext extends AvailabilityContext {
     /** Device channel (0 for standalone, `device_channel` on a HomeBase). */

package/dist/transport/p2p/p2p-session.d.ts

@@ -435,8 +435,17 @@ export declare class P2PSession extends EventEmitter {
      * "direct" commands (e.g. CAMERA_SWITCH 1035) carry a binary struct, not JSON.
      */
     sendRawLevel2Bytes(payload: Buffer, channel: number, outerCmd?: number, signCode?: number): boolean;
-    /** Stop the realtime media stream (`CMD_STOP_REALTIME_MEDIA`, 1004) on a camera `channel`. */
-    stopLiveMedia(channel?: number, accountId?: string): void;
+    /**
+     * Stop the realtime media stream (`CMD_STOP_REALTIME_MEDIA`, 1004) on a camera `channel`, in the shape
+     * its runtime topology takes, as {@link startLiveMedia} selects its start:
+     *  - `homeBaseAttached`: `CMD_SET_PAYLOAD` (1350) wrapping `{cmd:1004, mChannel:channel}` at level-2.
+     *  - own-session at level-2: the direct 1004 frame whose entire plaintext is the camera channel as a
+     *    `uint32`, the same 4-byte body as the attached talkback frames. The app sends this frame on closing
+     *    an own-session camera's live view; the camera stops streaming on it within a second, and keeps
+     *    streaming through the 1350-wrapped form.
+     *  - without a level-2 key: the bare 1004 command.
+     */
+    stopLiveMedia(channel?: number, accountId?: string, homeBaseAttached?: boolean): void;
     /**
      * Open the device's talkback (host→device audio) path on a camera `channel`, after which
      * {@link sendAudioFrame} is accepted until {@link stopTalkback}. Two protocols, selected by runtime

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mega-yfue/eufy-sdk",
-  "version": "0.4.0-beta.31",
+  "version": "0.4.0-beta.33",
   "description": "One typed TypeScript client for the Anker eufy v6 cloud — capability-driven devices, realtime events over P2P/MQTT/push, and live media",
   "license": "Apache-2.0",
   "author": "mega-yfue",