@mega-yfue/eufy-sdk 0.5.0-beta.40 → 0.5.0-beta.42

package/dist/index.js

@@ -11191,6 +11191,8 @@ var MODEL_REGISTRY = {
   // shows a parent, so an attached cam never advertises the hub's guard mode.
   T8170: { codec: "camera", caps: ["battery", "arming"], name: "SoloCam" },
   T8171: { codec: "camera", caps: ["battery", "arming"], name: "T8171" },
+  // Baby Monitor E21, vendor deviceType 86 (category eufy_care), standalone.
+  T8354: { codec: "camera", name: "Baby Monitor E21" },
   T8400: { codec: "camera", caps: ["arming"], name: "Indoor Cam" },
   T8410: { codec: "camera", caps: ["arming"], name: "Indoor Cam Pan & Tilt" },
   T8442: { codec: "camera", caps: ["arming"], name: "Indoor/Outdoor Cam 1080p" },
@@ -24275,12 +24277,17 @@ async function probeBrokerInstance(ip, creds, opts) {
     });
     const timer = setTimeout(() => finish({ granted: false, error: "timeout" }), timeoutMs);
     client.on("connect", () => {
-      client.subscribe(opts.topic, { qos: 1 }, (err, granted) => {
-        if (err)
-          return finish({ granted: false, error: err.message });
+      client.subscribe(opts.topic, { qos: 1 }, (err, granted, packet) => {
+        if (err) {
+          const code = packet?.granted?.[0];
+          return finish({
+            granted: false,
+            grantedQos: typeof code === "number" ? code : void 0,
+            error: err.message
+          });
+        }
         const g = granted?.[0];
-        const denied = !g || g.qos === 128;
-        finish({ granted: !denied, grantedQos: g?.qos });
+        finish({ granted: !!g, grantedQos: g?.qos });
       });
     });
     client.on("error", (err) => finish({ granted: false, error: err.message }));
@@ -24706,8 +24713,9 @@ var MqttCommandRouter = class _MqttCommandRouter {
    * One exception is known: a single garage unit whose own-cert SUBSCRIBE was denied on every candidate
    * while a phone-extracted cert granted on the same one, with a sibling of the same model on the same
    * account granting fine. That is a per-device authorization gap on the vendor's backend, not a
-   * broker-instance problem and not something this SDK works around — such a device reports as offline
-   * (the throw below) until the backend grants the account's own credentials.
+   * broker-instance problem and not something this SDK works around — the throw below names each
+   * candidate's outcome (its SUBACK deny code, a timeout or a connection error) until the backend grants
+   * the account's own credentials.
    *
    * One fresh, explicitly non-reconnecting (`reconnectPeriod: 0`) connection per call — it repays the
    * full mTLS handshake every command and tears the socket down right after (see
@@ -24736,7 +24744,7 @@ var MqttCommandRouter = class _MqttCommandRouter {
     });
     const winner = results.find((res) => res.granted);
     if (!winner) {
-      throw new Error(`ensureSecurityMqttFor(${dev.sn}): no broker instance currently holds this device's session (probed ${results.length} candidate IPs, all denied/unreachable) \u2014 the device may be offline.`);
+      throw new Error(`ensureSecurityMqttFor(${dev.sn}): no broker instance currently holds this device's session (probed ${results.length} candidate IPs: ` + results.map((r) => `${r.ip} ${r.grantedQos === void 0 ? "" : `SUBACK 0x${r.grantedQos.toString(16)} `}${r.error ?? "denied"}`).join("; ") + `).`);
     }
     const m = new SecureMqtt({
       credentials: creds,