@mega-yfue/eufy-sdk 0.2.0-beta.1 → 0.2.0-beta.2

package/dist/index.js

@@ -6890,6 +6890,16 @@ var KEYPAD = {
 // dist/model/capabilities/arming.js
 var STATION_CHANNEL2 = 255;
 var ArmingMode = {
+  /** Armed — full protection, nobody home (wire value 0). */
+  away: "away",
+  /** Armed for occupancy — reduced/perimeter protection while home (wire value 1). */
+  home: "home",
+  /** Custom 1 — a user-defined posture configured in the app (wire value 3). */
+  custom1: "custom1",
+  /** Disarmed — no alarms; sensors still report state (wire value 63). */
+  disarmed: "disarmed"
+};
+var AlarmDelayMode = {
   /** Armed — full protection, nobody home (wire value 0). */
   away: "away",
   /** Armed for occupancy — reduced/perimeter protection while home (wire value 1). */
@@ -6905,10 +6915,11 @@ var ARMING_CMD = {
    * mValue3:0, `payload:{mode_type:<int>, user_name:<string>}`.
    *
    * ⚠️ Only 3 of the 9 modes were exercised in that capture — `mode_type` 0 (away), 63 (disarmed), 1
-   * (home), all confirmed byte-exact, and those three are the whole of {@link ArmingMode}. Re-confirmed
-   * live 2026-08-05: each reported its own MODE_SWITCH push within ~5s of the write. The remaining six 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.
+   * (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.
    */
   SET_ARMING: 1224,
   /**
@@ -6944,7 +6955,6 @@ var ARMING_MODE_WIRE = {
   schedule: 2,
   // ⚠️ reportable, NOT settable — see the doc comment above
   custom1: 3,
-  // ⚠️ reportable, NOT settable — see the doc comment above
   custom2: 4,
   // ⚠️ reportable, NOT settable — see the doc comment above
   custom3: 5,
@@ -6987,9 +6997,9 @@ 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 three whose wire was captured. That
-   * argument IS the domain the derived setter enforces and the refusal names, so an uncaptured mode is
-   * refused by naming the three that work — nine labels for the read and three for the write, off one
+   * 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.
    *
    * `armingCommand` may also throw synchronously (missing account identity) and `bindMembers` turns that
@@ -7010,7 +7020,7 @@ var ARMING_MEMBERS = {
     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 3 whose write is wire-captured (away/home/disarmed) \u2014 schedule/custom1/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 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.",
     observation: {
       event: "armingModeChanged",
       reflects: (value) => ({ param: ARMING_CMD.SET_ARMING, expected: ARMING_MODE_WIRE[armingModeOf(value)] }),
@@ -7031,9 +7041,10 @@ var ARMING_MEMBERS = {
    * this mode — there is no known GET to fetch it automatically, and a wrong guess here can silently
    * misconfigure which sensors arm/trigger for real.
    *
-   * Takes {@link ArmingMode}, so a delay can only be configured for a mode whose `mode_id` integer is
-   * captured. The frame carries that same integer, so a schedule/custom mode would be the identical guess
-   * `setMode` refuses.
+   * Takes {@link AlarmDelayMode}, not {@link ArmingMode}: a delay is configurable only for a mode whose
+   * integer is captured on THIS command, and `custom1` is confirmed on cmd 1224 only. The frame carries
+   * that integer in `mode_id` with no runtime validation and no readback, so a mode outside this union
+   * would be the same unverified guess `setMode` refuses.
    */
   setAlarmDelayConfig: method(({ ctx, sink }) => (mode, config) => {
     try {
@@ -25312,6 +25323,7 @@ export {
   AUDIO_MEMBERS,
   AccessUnitAssembler,
   AiDetectType,
+  AlarmDelayMode,
   ArmingMode,
   BATTERY_MEMBERS,
   BIZ_CHANNEL,