@mega-yfue/eufy-sdk 0.5.0-beta.43 → 0.5.0-beta.44

package/dist/index.js

@@ -7891,6 +7891,10 @@ var ARMING_MEMBERS = {
     };
   }, "Turn the push notification of the device on a channel on or off in a guard mode (home/away).", (ctx) => ctx.model === "T8010")
 };
+function decodeAlarmPhase(signal) {
+  const type = signal.source === "push" ? signal.payload?.["type"] : void 0;
+  return type === CusPushAlarmType.HUB_STOP_BY_APP ? { phase: "stopped" } : {};
+}
 var ARMING = {
   capability: "arming",
   description: "Station/device guard (arming) mode.",
@@ -7905,8 +7909,9 @@ var ARMING = {
    * generic `CusPushEvent` channel, so these ids are shared with other families and resolve by
    * capability (see the barrel's event index).
    *
-   * The alarm ids carry a static `phase` so one event name covers the whole lifecycle, the same shape
-   * `battery` uses for its threshold pushes. The mode-switch push is known to identify WHICH mode and
+   * The alarm ids carry a `phase` so one event name covers the whole lifecycle: the countdown push a
+   * static `"delayed"`, the alarm push a `"triggered"` or `"stopped"` read from its alarm type (see
+   * {@link decodeAlarmPhase}). The mode-switch push is known to identify WHICH mode and
    * what triggered the change, but neither has been observed on the wire here, so this emits the bare
    * transition and refreshes the `mode` read rather than trusting a decoded field.
    */
@@ -7917,7 +7922,13 @@ var ARMING = {
       emit: "armingModeChanged",
       refresh: { member: "mode" }
     },
-    { source: "push", match: CusPushEvent.ALARM, emit: "alarm", payload: { phase: "triggered" } },
+    {
+      source: "push",
+      match: CusPushEvent.ALARM,
+      emit: "alarm",
+      payload: { phase: "triggered" },
+      derive: decodeAlarmPhase
+    },
     { source: "push", match: CusPushEvent.ALARM_DELAY, emit: "alarm", payload: { phase: "delayed" } }
   ]
 };