@mega-yfue/eufy-sdk 0.4.0-beta.10 → 0.4.0-beta.11

package/dist/transport/http/passport.d.ts

@@ -0,0 +1,21 @@
+/**
+ * The `algo_ecdh` passport steps the eufy and Solix clients share byte for byte. Hosts, header sets, key
+ * caching, 2FA delivery and the `gtoken` id differ per app line and stay in each client.
+ */
+import { type SessionEntry } from "../../core/index.js";
+/** The credential fields every `/passport/login` body starts with; each client adds its own challenge fields. */
+export declare function loginCredentials(email: string, password: string, country: string): Record<string, unknown>;
+/**
+ * Read a decrypted `/passport/login` reply; `undefined` when it carries no id or no token. `twoFactorPending`
+ * is true while `fa_info.info` is non-empty and false once 2FA is satisfied.
+ */
+export declare function readLoginReply(data: Record<string, unknown>): {
+    userId: string;
+    accountUserId: string | undefined;
+    authToken: string;
+    geoKey: string | undefined;
+    tokenExpiresAt: number;
+    twoFactorPending: boolean;
+} | undefined;
+/** The headers that mark `encBody` as `algo_ecdh`-encrypted under `entry` and sign it. */
+export declare function signedHeaders(entry: SessionEntry, encBody: string): Record<string, string>;

package/dist/transport/http/solix-client.d.ts

@@ -3,12 +3,11 @@
  * eufy client uses.
  *
  * Why this is separate from the eufy device client: Solix shares Anker's `algo_ecdh` passport (so
- * {@link prepareKeyExchange} / {@link encryptLoginPassword} / {@link signRequest} are reused verbatim
- * for the login handshake) but exposes a different device backend — its own `app-name`, host, and
- * bootstrap key (`SOLIX_APP_NAME`, `SOLIX_DEFAULT_API_HOST`, {@link SOLIX_LOCAL_KEY_HEX}) —
- * and its authenticated resource reads are PLAIN JSON, carrying only the auth token and a
- * `gtoken = md5(user_id)`, with no per-request encryption or signature. This client therefore does
- * the encrypted passport handshake to obtain a token, then makes plain authenticated reads.
+ * {@link prepareKeyExchange} and the steps in `./passport.ts` are shared with it) but exposes a different device
+ * backend — its own `app-name`, host, and bootstrap key (`SOLIX_APP_NAME`, `SOLIX_DEFAULT_API_HOST`,
+ * {@link SOLIX_LOCAL_KEY_HEX}) — and its authenticated resource reads are PLAIN JSON, carrying only the auth token
+ * and a `gtoken = md5(user_id)`, with no per-request encryption or signature. This client therefore does the
+ * encrypted passport handshake to obtain a token, then makes plain authenticated reads.
  *
  * This is the wire client (transport layer): it returns the vendor's typed JSON as received. Building
  * those records into capability-driven `SolixDevice` models is the model layer's job — see

package/package.json

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