@mega-yfue/eufy-sdk 0.2.0-beta.8 → 0.2.0-beta.9

package/dist/index.js

@@ -6916,8 +6916,18 @@ var ArmingMode = {
   away: "away",
   /** Armed for occupancy — reduced/perimeter protection while home (wire value 1). */
   home: "home",
+  /** Scheduled — the station follows the timetable configured in the app (wire value 2). */
+  schedule: "schedule",
   /** Custom 1 — a user-defined posture configured in the app (wire value 3). */
   custom1: "custom1",
+  /** Custom 2 — a user-defined posture configured in the app (wire value 4). */
+  custom2: "custom2",
+  /** Custom 3 — a user-defined posture configured in the app (wire value 5). */
+  custom3: "custom3",
+  /** Off — the station's alarm system is switched off entirely (wire value 6). */
+  off: "off",
+  /** Geofenced — the station follows the app's location-based rules (wire value 47). */
+  geo: "geo",
   /** Disarmed — no alarms; sensors still report state (wire value 63). */
   disarmed: "disarmed"
 };
@@ -6938,10 +6948,10 @@ var ARMING_CMD = {
    *
    * ⚠️ Only 3 of the 9 modes were exercised in that capture — `mode_type` 0 (away), 63 (disarmed), 1
    * (home), all confirmed byte-exact. Re-confirmed live 2026-08-05: each reported its own MODE_SWITCH push
-   * within ~5s of the write. `custom1` 3 joined {@link ArmingMode} on a live confirmation rather than a
-   * capture, making four settable in total. The remaining five are named by the app but never observed
-   * leaving it, so this capability reads them and refuses to send them. See `ARMING_MODE_WIRE` for the
-   * per-value breakdown.
+   * within ~5s of the write. The remaining six are live confirmations rather than captures — `custom1` 3
+   * first, then `schedule` 2, `custom2` 4, `custom3` 5, `off` 6 and `geo` 47 — each sent as this exact
+   * frame and each observed to bring MODE_SWITCH back, so all nine are settable. `ARMING_MODE_WIRE` has
+   * the per-value evidence and the dates.
    */
   SET_ARMING: 1224,
   /**
@@ -6975,20 +6985,14 @@ var ARMING_MODE_WIRE = {
   away: 0,
   home: 1,
   schedule: 2,
-  // ⚠️ reportable, NOT settable — see the doc comment above
   custom1: 3,
   custom2: 4,
-  // ⚠️ reportable, NOT settable — see the doc comment above
   custom3: 5,
-  // ⚠️ reportable, NOT settable — see the doc comment above
   off: 6,
-  // ⚠️ reportable, NOT settable — see the doc comment above
   geo: 47,
-  // ⚠️ reportable, NOT settable — see the doc comment above
   disarmed: 63
 };
 var ARMING_MODE_LABELS = enumLabels(ARMING_MODE_WIRE);
-var SETTABLE_MODES = Object.values(ArmingMode).map((m) => ARMING_MODE_WIRE[m]);
 function armingModeOf(v) {
   const name = String(v);
   if (name in ArmingMode)
@@ -6997,11 +7001,10 @@ function armingModeOf(v) {
   return Object.values(ArmingMode).find((m) => ARMING_MODE_WIRE[m] === wire);
 }
 function armingCommand(mode, ctx) {
-  const modeType = ARMING_MODE_WIRE[mode];
   if (!ctx.accountName) {
     throw new Error(`arming: missing account identity (user_name) [${describeDevice(ctx)}]`);
   }
-  return setPayload(ARMING_CMD.SET_ARMING, { mode_type: modeType, user_name: ctx.accountName }, ctx, 0);
+  return setPayload(ARMING_CMD.SET_ARMING, { mode_type: ARMING_MODE_WIRE[mode], user_name: ctx.accountName }, ctx, 0);
 }
 function alarmDelayCommand(mode, config, ctx) {
   const data = {
@@ -7018,11 +7021,10 @@ function alarmDelayCommand(mode, config, ctx) {
 }
 var ARMING_MEMBERS = {
   /**
-   * The one member whose write domain is NARROWER than its read: `enumValues` names all nine modes a
-   * station can report, and the argument's `values` publishes only the four whose write is confirmed. That
-   * argument IS the domain the derived setter enforces and the refusal names, so an unconfirmed mode is
-   * refused by naming the four that work — nine labels for the read and four for the write, off one
-   * declaration.
+   * Read and write are the same nine modes, so `enumValues` is the whole domain: `writeDomain` falls back
+   * to it, and the derived setter, the refusal message and the offered argument all read from that one
+   * declaration. A member states an `args` entry only where the two sides DIFFER. See
+   * {@link ARMING_MODE_WIRE} for the per-value evidence.
    *
    * `armingCommand` may also throw synchronously (missing account identity) and `bindMembers` turns that
    * into a rejection, so the builder stays plain.
@@ -7041,8 +7043,7 @@ var ARMING_MEMBERS = {
     kind: "enum",
     enumValues: ARMING_MODE_LABELS,
     provenance: "verified",
-    args: [{ name: "mode", kind: "enum", values: SETTABLE_MODES }],
-    description: "Guard mode (verified: param 1224 = GUARD_MODE, read/write mechanism confirmed). Reads all 9 modes the app defines; SETS only the 4 whose write is confirmed (away/home/custom1/disarmed) \u2014 schedule/custom2/custom3/off/geo are named by the app but no capture shows one being sent, so they are refused rather than guessed; see ARMING_MODE_WIRE in arming.ts for the breakdown.",
+    description: "Guard mode (verified: param 1224 = GUARD_MODE, read/write mechanism confirmed). Reads and SETS all 9 modes the app defines \u2014 away/home/schedule/custom1/custom2/custom3/off/geo/disarmed. Three are byte-captured writes and six are live-confirmed (each sent and observed to report its own MODE_SWITCH); see ARMING_MODE_WIRE in arming.ts for the per-value evidence.",
     observation: {
       event: "armingModeChanged",
       reflects: (value) => ({ param: ARMING_CMD.SET_ARMING, expected: ARMING_MODE_WIRE[armingModeOf(value)] }),