@mega-yfue/eufy-sdk 0.5.0-beta.52 → 0.5.0-beta.54

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

@@ -112,8 +112,11 @@ export declare const ARMING_CMD: {
      */
     readonly SET_ALL_ACTION: 1255;
 };
-/** The guard modes whose device notification is read and written: both replayed on a T8010. */
-export type DeviceNotificationMode = Extract<AlarmDelayMode, "home" | "away">;
+/**
+ * The guard modes whose device notification is read and written. Home and away are replayed on a T8010;
+ * `custom1` (wire 3) is captured on a T8170, whose own params report it on 1148.
+ */
+export type DeviceNotificationMode = Extract<ArmingMode, "home" | "away" | "custom1">;
 /**
  * Alarm-delay durations the app's OWN picker UI offers — `AlarmDelaySeconds` is both the const
  * value-object (`AlarmDelaySeconds.sec45`) and the union type of its values, so callers pass the
@@ -237,7 +240,8 @@ export declare const ARMING_MEMBERS: {
     /**
      * Whether the device on `channel` sends a push notification in `mode`: its {@link DEVICE_NOTIFY_FLAG}
      * in the action table the station reports for that mode. `undefined` where the station reports no table
-     * or the table does not list `channel`. A device's channel is `EufyDevice.channel`.
+     * or the table does not list `channel`. A standalone camera answers from its own 1225/1239/1148 flags,
+     * for its own channel only. A device's channel is `EufyDevice.channel`.
      */
     readonly deviceNotification: import("./members.js").MethodMember<(mode: DeviceNotificationMode, channel: number) => boolean | undefined> & {
         available: (ctx: CommandContext) => boolean;
@@ -245,9 +249,11 @@ export declare const ARMING_MEMBERS: {
     /**
      * Turn the push notification of the device on `channel` on or off in `mode` (cmd
      * {@link ARMING_CMD.SET_ALL_ACTION}): the station's reported table written back with that one flag
-     * changed. Rejects, sending nothing, where the table does not list `channel`. A write builds on the last
-     * one sent for that mode until the station reports a table observed 15 s after it, so a second write does
-     * not revert it; a write whose dispatch rejects is not built on.
+     * changed. A standalone camera is sent a one-entry `{mode_id, devices}` table built from its own flags,
+     * for its own channel only. Rejects, sending nothing, where the table does not list `channel`. A write
+     * builds on the last one sent for that mode until the device reports a table (`${mode}Action` on a
+     * standalone camera) observed 15 s after it, so a second write does not revert it; a write whose dispatch
+     * rejects is not built on.
      */
     readonly setDeviceNotification: import("./members.js").MethodMember<(mode: DeviceNotificationMode, channel: number, on: boolean) => Promise<void>> & {
         available: (ctx: CommandContext) => boolean;

package/dist/transport/tuya/dp-codec.d.ts

@@ -1,14 +1,9 @@
 /**
- * Inbound Tuya DP event parsing and routing for eufy Home/Clean (`eufy_home_tuya`) devices.
+ * Inbound Tuya DP parsing and routing for eufy Home/Clean (`eufy_home_tuya`) devices.
  *
- * {@link parseTuyaDpReport} unwraps the Anker MQTT `{head, payload}` envelope and extracts the
- * raw DP map. {@link parseTuyaDpEvent} then validates and normalises it to a numeric-keyed record.
+ * {@link parseTuyaDpEvent} validates a Tuya cloud DP map and normalises it to a numeric-keyed record.
  * {@link TuyaDpRouter} delivers the result to the registered {@link TuyaDpInbound} listener so the
  * capability layer can consume Tuya state through the same typed getters as AIoT.
- *
- * Inbound messages arrive on `cmd/eufy_home/{model}/{sn}/res` with `sign_code: 0` (no additional
- * encryption — confirmed from clean-device captures). If a future capture shows `sign_code ≠ 0` the
- * payload will be AES-128-ECB encrypted with the device's localKey before the JSON can be parsed.
  */
 import type { TuyaDpInbound } from "../../core/contracts.js";
 /**
@@ -21,22 +16,6 @@ import type { TuyaDpInbound } from "../../core/contracts.js";
  * valid DP entry was found.
  */
 export declare function parseTuyaDpEvent(payload: unknown): Record<number, boolean | number | string> | null;
-/**
- * Extract a raw DP map from an inbound Anker MQTT message for a `eufy_home_tuya` device.
- *
- * Messages arrive in the same `{head, payload}` envelope the AIoT path uses, where `payload` is a
- * JSON **string**:
- * ```json
- * { "head": { "cmd": 65537, "cmd_status": 2, "sign_code": 0, ... },
- *   "payload": "{\"t\":\"…\",\"protocol\":2,\"data\":{\"104\":80,\"106\":0}}" }
- * ```
- * Two DP layouts inside the decoded payload are handled: Tuya-native (`data.dps`) and AIoT-direct
- * (`data` with integer-keyed DP ids). Falls back to flat `envelope.dps` / `envelope.data.dps`
- * shapes for any pre-parsed delivery. Returns `undefined` when no recognised shape is found.
- *
- * @internal
- */
-export declare function parseTuyaDpReport(raw: unknown): Record<string, unknown> | undefined;
 /**
  * Routes validated inbound Tuya DP events to the registered {@link TuyaDpInbound} listener.
  *

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mega-yfue/eufy-sdk",
-  "version": "0.5.0-beta.52",
+  "version": "0.5.0-beta.54",
   "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",