@mega-yfue/eufy-sdk 0.5.0-beta.87 → 0.5.0-beta.89

package/dist/client/eufy-mega.d.ts

@@ -435,8 +435,10 @@ export declare class EufyMega extends EventEmitter {
      * Choose the transport stack for one command — the routing half of {@link commandSinkFor}.
      *
      * The `ff09-*` kinds share ONE frame that rides either transport, so each stack is asked whether it
-     * drives this device (`claimsDevice`) rather than inferring from the kind. `registry.require` throws
-     * on an unloaded serial, so a routing decision never silently falls through to the wrong transport.
+     * drives this device (`claimsDevice`) rather than inferring from the kind; `keyed-payload-actuate` (the
+     * classic Wi-Fi lock) is routed the same way, a channel-less actuation claimed by the stack that drives
+     * the lock. `registry.require` throws on an unloaded serial, so a routing decision never silently falls
+     * through to the wrong transport.
      * The `eufy_life` DP writes (smart lights) are secure-MQTT-only. `aiot-dp` routes to either the
      * Anker AIoT MQTT stack or the legacy Tuya REST router depending on the device's category
      * (`eufy_home_tuya` → Tuya, everything else → MQTT). The capability layer emits a single `aiot-dp`

package/dist/core/contracts.d.ts

@@ -264,10 +264,11 @@ export declare class StateConvergenceError extends Error {
  */
 export type ScalarForm = "auto" | "int-string" | "direct-binary";
 /**
- * The identity fields the `ff09` frame is built from — the AES key/IV inputs (`adminUserId`/`deviceSn`)
- * plus the frame's own direction bit and user-attribution fields (`A3`/`A4`/`A5`). Shared by the
- * actuate intent; the settings intents carry a narrower subset (the GET/SET frames omit the
- * user-attribution fields).
+ * The identity fields an actuation frame is built from — for `ff09`, the AES key/IV inputs
+ * (`adminUserId`/`deviceSn`) plus the frame's own direction bit and user-attribution fields
+ * (`A3`/`A4`/`A5`); for the keyed-payload envelope, the same five fields, sealed into its inner JSON.
+ * Shared by both actuate intents; the `ff09` settings intents carry a narrower subset (the GET/SET frames
+ * omit the user-attribution fields).
  */
 export interface Ff09Identity {
     /** Actuation direction: `true` = engage (lock / close), `false` = release (unlock / open) — the frame's `A3` byte. */
@@ -353,6 +354,14 @@ export type Command = {
     channel: number;
 } | ({
     kind: "ff09-actuate";
+} & Ff09Identity)
+/**
+ * `keyed-payload-actuate` — a `SET_PAYLOAD` envelope whose inner JSON is sealed with a fresh AES key
+ * that the envelope itself carries, wrapped for the device's own public key. P2P-only; the router
+ * resolves the device key and the member display name from the device record.
+ */
+ | ({
+    kind: "keyed-payload-actuate";
 } & Ff09Identity) | {
     kind: "ff09-autolock";
     adminUserId: string;