@mega-yfue/eufy-sdk 0.5.0-beta.7 → 0.5.0-beta.71

package/dist/transport/rtc/peer.d.ts

@@ -0,0 +1,122 @@
+/**
+ * The WebRTC peer for a T9000 session: libdatachannel through `node-datachannel`, driven the way the
+ * portal drives a browser's RTCPeerConnection.
+ *
+ * The hub is the offerer: it sends its SDP once it has granted the session, and the peer answers. Six
+ * data channels are declared in the portal's order (`WebrtcDataChannel` first, the command channel,
+ * then audio, idr, video, notify, download). Every one carries PTCS-framed portal packets; which logical
+ * channel a reassembled frame belongs to is the PTCS header's channel, not the data channel it rode on.
+ *
+ * ICE defaults to relay-only. The T9000 grants a TURN allocation in its `scall 100` reply and completes DTLS only
+ * over the relay pair; on a host pair ICE connects and the DTLS handshake never completes. The peer
+ * plays the DTLS client (`active`) and opens its channels on the client's even SCTP stream ids, which
+ * is what the hub pairs with.
+ *
+ * With {@link RtcPeerOptions.mediaTrack} the remote is a T8223 doorbell instead: its offer bundles an Opus
+ * audio, an H.264 video and an `m=application` section, but it never completes the SCTP association. The
+ * application section is rejected before the offer is applied, no data channel is declared, and the
+ * video m-line's RTP is emitted as `rtp`.
+ *
+ * The native peer is injectable.
+ */
+import { EventEmitter } from "node:events";
+import type { PeerConnection, RtcConfig } from "node-datachannel";
+import { type Logger } from "../../core/logger.js";
+export interface TurnConfig {
+    turn_addr: string;
+    turn_port: number;
+    turn_user: string;
+    turn_password: string;
+    alt_turn_addr?: string;
+    alt_turn_port?: number;
+}
+export type NativePeerFactory = (name: string, config: RtcConfig) => PeerConnection;
+export interface RtcPeerOptions {
+    createPeer?: NativePeerFactory;
+    /** Candidate policy for the station's exchange; the default is relay-only. */
+    iceTransportPolicy?: "relay" | "all";
+    /**
+     * The remote streams its video as RTP on the offer's video m-line and serves no data channel: the
+     * offer's application section is rejected and the video track's packets are emitted as `rtp`.
+     */
+    mediaTrack?: boolean;
+    logger?: Logger;
+}
+export interface RtcPeerEvents {
+    commandChannelOpen: [];
+    /** The command channel went away while the peer itself may still be up. */
+    commandChannelClosed: [];
+    data: [frame: Buffer, linkType: number];
+    /** The hub echoed the portal keepalive on the command channel. */
+    keepaliveEcho: [];
+    /** One RTP (or multiplexed RTCP) packet from the offer's video m-line, in a {@link RtcPeerOptions.mediaTrack} peer. */
+    rtp: [packet: Buffer];
+    iceCandidate: [candidate: string];
+    iceGatheringComplete: [];
+    connectionState: [state: string];
+    error: [err: Error];
+}
+/** The portal's channel list; index 0 is the command channel. */
+export declare const DATA_CHANNEL_LABELS: readonly ["WebrtcDataChannel", "audio", "idr", "video", "notify", "download"];
+export declare const COMMAND_CHANNEL: "WebrtcDataChannel";
+export declare class RtcPeer extends EventEmitter<RtcPeerEvents> {
+    private readonly opts;
+    private pc?;
+    private readonly channels;
+    private framer?;
+    private readonly wireTally;
+    private commandOpen;
+    private remoteSet;
+    private remoteMid;
+    private handlingOffer;
+    private channelsCreated;
+    private videoMid?;
+    private videoTrack?;
+    private gatheringDone;
+    /** Set by the framer's wire callback when the native channel refused a packet mid-send. */
+    private wireSendFailed;
+    private readonly pending;
+    private localAnswer?;
+    private readonly logger;
+    constructor(opts?: RtcPeerOptions);
+    /** Create the native peer on the relay the hub granted in `scall 100`. */
+    init(turn: TurnConfig): Promise<void>;
+    /**
+     * The hub offered: apply the offer, declare the channels, return the answer SDP to signal back.
+     *
+     * The offer is pinned to `passive` before it is applied, so the native peer has one legal answer,
+     * `active`: the role is fixed where it is decided, since rewriting the answer afterwards would change
+     * only what is announced. The offer goes in before the channels are declared: `createDataChannel` on
+     * a peer without a remote description starts its own negotiation and leaves it in `have-local-offer`.
+     * The data channels need no m-line of their own; the offer's SCTP m-line carries them. Only an ANSWER
+     * is taken as the local description: one read in `have-local-offer` is an offer. A
+     * {@link RtcPeerOptions.mediaTrack} peer applies the offer with its application section rejected,
+     * declares no channels, and adds remote candidates on the offer's first (bundle-tagged) mid.
+     */
+    handleRemoteOffer(offerSdp: string): Promise<string>;
+    addRemoteCandidate(candidate: string): void;
+    /**
+     * Send bytes on the command channel as they are, without PTCS framing; false when it isn't open. The
+     * portal's data-channel keepalive rides the wire unframed.
+     */
+    sendRaw(bytes: Buffer): boolean;
+    /**
+     * Send one portal packet on the command channel, through the framer. False when the channel is not
+     * usable or the native send refused a wire packet, so a dropped frame does not read as success.
+     */
+    sendCommand(portalPacket: Buffer): boolean;
+    /** Tear the peer down. A pending answer is rejected, so a `handleRemoteOffer` in flight settles. */
+    close(): void;
+    private acceptsCandidate;
+    private createChannels;
+    /**
+     * Wire one data channel. Every channel feeds the framer once the command channel has opened it; a
+     * message before that has nothing to reassemble into and is dropped. The hub's echo of the portal
+     * keepalive on the command channel is unframed and surfaces as `keepaliveEcho` instead.
+     */
+    private wireChannel;
+    /** Take the offer's video m-line as the one track whose RTP is emitted; any other track is left alone. */
+    private wireVideoTrack;
+    private addNow;
+    private flushPending;
+}

package/dist/transport/rtc/portal-keepalive.d.ts

@@ -0,0 +1,11 @@
+/**
+ * The portal's data-channel keepalive for an RTC session.
+ *
+ * {@link PORTAL_KEEPALIVE} is the 36 bytes the portal sends unframed on the data channel — a 20-byte
+ * prefix then a bare `XZYH 1139`, no portal packet header — and the hub echoes it. Sent every
+ * {@link PORTAL_KEEPALIVE_MS}, it stops the hub idling the session out.
+ */
+/** The portal's 36-byte data-channel keepalive: a 20-byte prefix and a bare `XZYH 1139`. */
+export declare const PORTAL_KEEPALIVE: Buffer<ArrayBuffer>;
+/** How often {@link PORTAL_KEEPALIVE} goes out on an RTC session. */
+export declare const PORTAL_KEEPALIVE_MS = 29000;

package/dist/transport/rtc/portal-packet.d.ts

@@ -0,0 +1,72 @@
+/**
+ * The command framing a HomeBase S1 Pro (T9000) speaks over its WebRTC data channel — the wire the
+ * security.eufy.com web client builds, reproduced byte-exact.
+ *
+ * A packet is a 16-byte header behind the ASCII magic `XZYH`, then a JSON body, sent in the clear (the
+ * DTLS channel is the encryption). Replies come back with `isResponse = 1`, the same `segment` the
+ * request carried, and a body whose first four bytes are a little-endian result code.
+ *
+ * Every offset is the portal bundle's header builder and parser (`Gr()` / `Qr()`) and its
+ * `worker_sctp_send`.
+ */
+export declare const PORTAL_HEADER_LENGTH = 16;
+/** The SET_PAYLOAD envelope. */
+export declare const PORTAL_CMD_SET_PAYLOAD = 1350;
+/** The channel a station-wide command is addressed to. */
+export declare const PORTAL_STATION_CHANNEL = 255;
+/** Portal link types — which logical channel a frame belongs to (`worker_sctp_send`). */
+export declare const PortalLinkType: {
+    /** Command channel: requests out, acknowledgements back. */
+    readonly COMMAND: 1;
+    /** Station-originated frames: pushes, notify payloads, control results. */
+    readonly NOTIFY: 3;
+    /** Live video. */
+    readonly LIVE: 5;
+};
+export interface PortalHeader {
+    commandId: number;
+    paramLength: number;
+    segment: number;
+    channel: number;
+    isResponse: number;
+    devType: number;
+}
+export interface PortalRequest {
+    commandId: number;
+    channel: number;
+    /** 1..255, wraps; echoed by the reply so it can be matched. */
+    segment: number;
+    payload: Record<string, unknown>;
+    isResponse?: number;
+    devType?: number;
+}
+export interface PortalResponse {
+    commandId: number;
+    channel: number;
+    segment: number;
+    isResponse: number;
+    linkType: number;
+    /** Command-channel replies only: the int32 result code (0 = ok). */
+    errCode?: number;
+    /** Notify frames: the nested `cmd` the JSON body carries. */
+    cmd?: number;
+    data?: unknown;
+}
+/** The 16-byte header (portal `Gr()`). */
+export declare function buildPortalHeader(commandId: number, paramLength: number, channel: number, segment: number, isResponse?: number, devType?: number): Buffer;
+/** Parse the header (portal `Qr()`); `undefined` when the magic is missing or the buffer is short. */
+export declare function parsePortalHeader(buf: Buffer): PortalHeader | undefined;
+/** Whether a buffer starts a portal packet. */
+export declare function isPortalPacket(buf: Buffer): boolean;
+/** A complete request packet: header + body. */
+export declare function buildPortalPacket(req: PortalRequest): Buffer;
+/**
+ * Parse an inbound packet. On the command channel the body opens with the int32 result code and may
+ * carry JSON after it; on the notify channel the whole body is JSON with a nested `cmd`.
+ */
+export declare function parsePortalPacket(buf: Buffer, linkType?: number): PortalResponse | undefined;
+/** A 1..255 segment counter that never yields 0 (the portal reserves it). */
+export declare class SegmentCounter {
+    private current;
+    next(): number;
+}

package/dist/transport/rtc/ptcs-framer.d.ts

@@ -0,0 +1,86 @@
+/**
+ * The PTCS packetiser: a clean-room implementation of the framing the portal wraps around every portal
+ * packet on `WebrtcDataChannel` (the portal's `libsctp` module). Nothing of that module ships here.
+ *
+ * Every wire packet is the same size, `28 + payload bytes`, zero-padded. The size is carried per packet,
+ * so the receiver accepts any:
+ *
+ *   0   "PTCS"
+ *   4   u8   3              constant
+ *   5   u8   channel        the logical channel the frame belongs to: 0 command, 2 notify, 5 live
+ *   6   u16  sequence       a frame counter: every packet of a frame carries the same value, and it
+ *                           steps once per frame
+ *   8   u32  frame id       one value per frame, shared by all its packets — the portal uses a ms clock
+ *   12  u32  frame length   total bytes of the frame
+ *   16  u16  packet index   0-based position of this packet in the frame
+ *   18  u16  0x4000 | (last ? 0x0400 : 0) | payload length      (payload ≤ 1023 fits the low bits)
+ *   20  8 × 0
+ *   28  payload             `payload length` bytes, then zeros to the packet size
+ *
+ * The format carries no forward error correction. The receiver completes a frame only when every index
+ * up to the `last` one is present and their lengths add up; frames whose packets stop arriving are
+ * dropped after {@link PTCS_STALE_MS}.
+ */
+export declare const PTCS_HEADER_LENGTH = 28;
+/** The portal's packet payload size: 1028-byte packets, 1000 bytes of payload after the header. */
+export declare const PTCS_DEFAULT_PAYLOAD_BYTES = 1000;
+/** SCTP channel ids as the portal numbers them, and the link type each maps to on receive. */
+export declare const PtcsChannel: {
+    readonly COMMAND: 0;
+    readonly NOTIFY: 2;
+    readonly LIVE: 5;
+};
+/** The link type a received frame belongs to: notify and live on their channels, command otherwise. */
+export declare function linkTypeForChannel(channel: number): number;
+/** How long a partly received frame is kept before it is dropped. */
+export declare const PTCS_STALE_MS = 15000;
+export interface PtcsHeader {
+    channel: number;
+    /** The sender's running packet counter — see the header map. */
+    sequence: number;
+    frameId: number;
+    frameLength: number;
+    index: number;
+    last: boolean;
+    payloadLength: number;
+}
+export declare function parsePtcsHeader(packet: Buffer): PtcsHeader | undefined;
+/** Split one frame into wire packets. */
+export declare function packetize(frame: Buffer, opts: {
+    channel?: number;
+    frameId: number;
+    payloadBytes?: number;
+    sequence?: number;
+}): Buffer[];
+/** Reassemble frames from wire packets, in any order, one frame at a time per (channel, id). */
+export declare class PtcsReassembler {
+    private readonly onFrame;
+    private readonly now;
+    private readonly partials;
+    constructor(onFrame: (frame: Buffer, channel: number) => void, now?: () => number);
+    push(packet: Buffer): boolean;
+    /** Drop frames that stopped arriving; call periodically. */
+    expire(): void;
+}
+/** Frame ids the way the portal draws them — a millisecond clock, nudged forward on a collision. */
+export declare function frameIdClock(now?: () => number): () => number;
+/**
+ * The framer between portal packets and the data channel: PTCS out, PTCS in, with the portal's channel
+ * mapping. An inbound bare `XZYH` packet, which the hub sometimes answers with, passes through as a
+ * command frame. Frame ids are a millisecond clock and the frame counter starts at 0.
+ */
+export declare class PtcsFramer {
+    private onWire?;
+    private onFrame?;
+    private reassembler?;
+    private sweep?;
+    private ready;
+    private readonly nextFrameId;
+    private sequence;
+    /** Arm the two callbacks; `sendFrame` may be called from here on. */
+    init(onWirePacket: (packet: Buffer) => void, onFrame: (frame: Buffer, linkType: number) => void): void;
+    isReady(): boolean;
+    sendFrame(portalPacket: Buffer): void;
+    recvPacket(wirePacket: Buffer): void;
+    destroy(): void;
+}

package/dist/transport/rtc/scall-sdp.d.ts

@@ -0,0 +1,50 @@
+/**
+ * The T9000's signalling does not carry SDP text: an `info` message carries a small JSON — DTLS setup
+ * role, ICE ufrag/pwd, fingerprint and candidates — and each side rebuilds the one-m-line SDP from it.
+ * This is the portal's own translation (security.eufy.com): the SDP handed to the native peer is the one
+ * the hub meant, and the JSON sent back is the one the hub parses.
+ */
+export interface ScallSdpJson {
+    setup?: string;
+    ice?: {
+        ufrag?: string;
+        pwd?: string;
+        fingerprint_type?: string;
+        fingerprint?: string;
+    };
+    candidate?: string[];
+}
+/** The hub's SDP is one SCTP application m-line bundled under mid 2, as the portal template has it. */
+export declare const HUB_SDP_MID = "2";
+/** The max message size the hub advertises; the answer carries the same. */
+export declare const ANKER_MAX_MESSAGE_SIZE = 262144;
+/**
+ * Rebuild the hub's offer (or answer) SDP from its scall JSON. The JSON carries the fingerprint as bare
+ * hex; the SDP gets colon-separated byte pairs.
+ */
+export declare function scallJsonToSdp(json: ScallSdpJson, now?: () => number): string;
+/** Reduce our local SDP to the JSON the hub parses. `actpass` is left out: the hub wants a concrete role. */
+export declare function sdpToScallJson(sdp: string): ScallSdpJson;
+/** The candidate type (`host` / `srflx` / `relay`) named inside an ICE candidate line. */
+export declare function iceCandidateType(candidate: string): string;
+/** Pin `a=max-message-size` to what the hub advertises, whatever libdatachannel wrote. */
+export declare function pinMaxMessageSize(sdp: string): string;
+/**
+ * Force a concrete DTLS role into an SDP. The hub offers `actpass`; the peer pins that offer to
+ * `passive`, which leaves one legal answer, `active`. The DTLS client opens its data channels on the
+ * even SCTP stream ids (RFC 8832), and the hub pairs with those: its command channel is stream 0.
+ */
+export declare function forceDtlsRole(sdp: string, role: "active" | "passive"): string;
+/**
+ * The wire form of a trickled ICE candidate: `candidate:...`, the attribute's value, which is the shape
+ * the hub sends and parses. The native peer hands out the SDP attribute line (`a=candidate:...`).
+ */
+export declare function toWireCandidate(candidate: string): string;
+/** The `a=mid` of the first m-section of `kind` in an SDP; `undefined` when it has none. */
+export declare function midOf(sdp: string, kind: "audio" | "video" | "application"): string | undefined;
+/**
+ * Reject an offer's `m=application` (data channel) section: port 0 and out of the BUNDLE group. The
+ * remote never completes the SCTP association, so a peer waiting on it fails; without it the peer
+ * connects on DTLS-SRTP alone.
+ */
+export declare function rejectDataSection(sdp: string): string;

package/dist/transport/rtc/session.d.ts

@@ -0,0 +1,95 @@
+/**
+ * One T9000 command session end to end: sign → signalling socket → `scall` → the hub's SDP offer →
+ * our answer → ICE → DTLS → the command data channel open.
+ *
+ * The signalling exchange, as the portal runs it and as confirmed live:
+ *
+ *   → scall                          (action 3, channel 0, the hub's own session)
+ *   ← scall {status: 100, turn}      the hub granted the session and handed out TURN credentials
+ *   ← info  {sdp | format:"SDP"}     the hub's offer, as scall JSON
+ *   → info  {sdp}                    the answer
+ *   ↔ info  {candidate}              trickle ICE on the same channel; "" ends it
+ *   ← scall {status: 200}            → ack
+ *   ← scall {status: 486 | 408}      busy / timeout: the session fails
+ *   ← hangup                         the hub ended it
+ *
+ * The command data channel is the session: `close` fires once, when the channel closes, the peer fails,
+ * the signalling socket drops or {@link RtcSession.close} is called, even while the peer connection is
+ * nominally up.
+ *
+ * A session whose peer is a {@link RtcPeerOptions.mediaTrack} peer has no command channel: `close` fires
+ * when the peer fails or closes, and the video track's packets are emitted as `rtp`.
+ *
+ * Both the signalling client and the peer are injectable.
+ */
+import { EventEmitter } from "node:events";
+import { RtcPeer, type RtcPeerOptions } from "./peer.js";
+import { RtcSignalingClient, type RtcSignalingOptions } from "./signaling.js";
+export interface RtcSessionOptions extends RtcSignalingOptions {
+    peer?: RtcPeerOptions;
+    createSignaling?: (opts: RtcSignalingOptions) => RtcSignalingClient;
+    createPeer?: (opts: RtcPeerOptions) => RtcPeer;
+}
+export interface RtcSessionEvents {
+    connected: [];
+    close: [];
+    error: [err: Error];
+    /** A reassembled command or notify frame: portal packet bytes + the link type it arrived on. */
+    commandData: [frame: Buffer, linkType: number];
+    /** A reassembled live-video frame. */
+    mediaData: [frame: Buffer];
+    /** The hub echoed the portal keepalive on the command channel. */
+    keepaliveEcho: [];
+    /** One packet of the video track, in a {@link RtcPeerOptions.mediaTrack} session. */
+    rtp: [packet: Buffer];
+}
+export declare class RtcSession extends EventEmitter<RtcSessionEvents> {
+    private readonly opts;
+    private readonly signaling;
+    private readonly peer;
+    private readonly logger;
+    private turn?;
+    private authOk;
+    private authWaiter?;
+    private connected;
+    private closed;
+    private closeAnnounced;
+    private sdpHandled;
+    private chain;
+    constructor(opts: RtcSessionOptions);
+    get isConnected(): boolean;
+    /**
+     * Start the sequence; resolves once the call is sent. `connected` fires when the channel opens. A session
+     * closed by the time the sign fetch or the auth completes rejects instead of opening the socket or
+     * placing the call.
+     */
+    connect(): Promise<void>;
+    /** Send one portal packet; false when the command channel isn't open. */
+    sendCommand(portalPacket: Buffer): boolean;
+    /** Send unframed bytes on the command channel; false when it isn't open. */
+    sendRaw(bytes: Buffer): boolean;
+    /**
+     * Hang up and tear both sides down; `close` fires once, here if nothing announced it before. A
+     * `connect()` still waiting for the signalling auth is rejected and its timer stopped.
+     */
+    close(): void;
+    /**
+     * Trickle one local candidate, or the empty end-of-candidates. The native peer can report one after the
+     * signalling socket has closed, and sending then throws inside a native callback, where the throw can't
+     * be caught and aborts the process. A candidate with no open socket is dropped.
+     */
+    private trickle;
+    private announceClose;
+    private waitForAuth;
+    /** Settle a pending auth wait: resolve it, or reject it with `err`; either way its timer stops. */
+    private settleAuth;
+    private onSignaling;
+    /** A `scall` status: `100` grants the relay, `200` is acknowledged, `486`/`408` fail the session. */
+    private onCall;
+    /**
+     * An `info`: trickle ICE, in either of the two shapes the hub sends, or the hub's SDP offer. The offer
+     * is answered only once a TURN grant is in: the peer is relay-only, so an offer ahead of `scall 100`
+     * is reported and left unanswered.
+     */
+    private onInfo;
+}

package/dist/transport/rtc/signaling.d.ts

@@ -0,0 +1,139 @@
+/**
+ * The T9000's signalling channel: the WebSocket through which a client and a HomeBase S1 Pro agree on a
+ * WebRTC session. It is the wire the security.eufy.com web client uses (`/v1/rtc/ws/join`), and the hub
+ * accepts it from any client presenting the account's mega token.
+ *
+ * Sequence:
+ *
+ *   1. `GET https://<smart host>/v1/smart/nvr/ws/sign` with the mega token → a `sign` blob.
+ *   2. WebSocket to `wss://<smart host>/v1/rtc/ws/join?reqtype=nvr`, subprotocols `["v1", <base64url
+ *      JSON>]` carrying the cluster region, station serial, token, `gtoken` and the sign. HTTP headers on
+ *      the upgrade alone are refused: the JSON subprotocol is what authenticates.
+ *   3. `action 1` auth on open; `action 3` session messages after: `scall` (start), `info` (SDP and
+ *      trickle ICE), `ack`, `hangup`. Every session message carries an HMAC-SHA256 `account` over
+ *      `channelId + adminUserId + ts`, keyed by the token.
+ *
+ * Region is two values: the HTTP sign request names the account's **country** (`Web-Country`), the
+ * WebSocket payload names the **cluster**, the shard prefix uppercased (`ie-pr` → `IE`). The smart host
+ * is `security-smart` for `us` and `security-smart-<prefix>` for any other shard.
+ *
+ * `fetch` and the `WebSocket` constructor are injectable.
+ */
+import { EventEmitter } from "node:events";
+import { type Logger } from "../../core/logger.js";
+/** The portal's origin; the sign endpoint and the socket upgrade both check it. */
+export declare const PORTAL_ORIGIN = "https://security.eufy.com";
+/** The hub drops an idle signalling socket after ~83 s; re-sending auth inside that keeps it. */
+export declare const SIGNALING_KEEPALIVE_MS = 25000;
+/** How long the socket has to open after the sign. */
+export declare const SIGNALING_CONNECT_TIMEOUT_MS = 15000;
+/** Outer wire envelope. */
+export interface RtcWsEnvelope {
+    msgid: string;
+    data: string;
+}
+/** Inner message (the envelope's `data`, JSON-parsed). */
+export interface RtcInnerMessage {
+    code?: number;
+    action?: number;
+    sessionId?: string;
+    sn?: string;
+    subSn?: string;
+    channelId?: number;
+    isResponse?: number;
+    dataType?: string;
+    source?: string;
+    ts?: number;
+    data?: string;
+    msgid?: string;
+}
+/** What a socket event carries; only the fields each event type fills are read. */
+export interface SignalingSocketEvent {
+    data?: unknown;
+    code?: number;
+    reason?: string;
+}
+/** The subset of a `WebSocket` the client uses. */
+export interface SignalingSocket {
+    readonly readyState: number;
+    send(data: string): void;
+    close(code?: number, reason?: string): void;
+    addEventListener(type: "open" | "message" | "close" | "error", listener: (ev: SignalingSocketEvent) => void): void;
+}
+export interface SignalingSocketInit {
+    /** The subprotocols; slot 2 carries the base64url auth JSON. */
+    protocols: string[];
+    /** The upgrade Origin, which the server checks like the sign call. */
+    origin: string;
+}
+export type SignalingSocketFactory = (url: string, init: SignalingSocketInit) => SignalingSocket;
+export interface RtcSignalingOptions {
+    /** Full SDP (`call`) or compact SDP (`scall`, the default). */
+    signalingMode?: "call" | "scall";
+    /** The mega session's auth token. */
+    authToken: string;
+    /** The `gtoken` header value the mega session's authed HTTP calls carry. */
+    gtoken: string;
+    stationSn: string;
+    /** The station's `member.admin_user_id`, the account the session HMAC names. */
+    adminUserId: string;
+    /** The mega shard the account lives on; picks the host and the cluster name. */
+    shard: string;
+    /** The account's ISO country, sent on the sign request (`Web-Country`). */
+    country: string;
+    fetch?: typeof fetch;
+    createSocket?: SignalingSocketFactory;
+    logger?: Logger;
+    now?: () => number;
+    makeMsgId?: () => string;
+}
+export interface RtcSignalingEvents {
+    message: [inner: RtcInnerMessage, envelope: RtcWsEnvelope];
+    open: [];
+    close: [code: number, reason: string];
+    error: [err: Error];
+}
+/** The portal's `account` field: HMAC-SHA256 of `channelId + adminUserId + ts`, keyed by the token. */
+export declare function sessionAccount(channelId: number, adminUserId: string, ts: number, authToken: string): string;
+export declare class RtcSignalingClient extends EventEmitter<RtcSignalingEvents> {
+    private readonly opts;
+    private ws?;
+    private sign?;
+    private keepalive?;
+    private readonly wsUrl;
+    private readonly signUrl;
+    private readonly wsRegion;
+    private readonly fetchImpl;
+    private readonly createSocket;
+    private readonly logger;
+    private readonly now;
+    private readonly makeMsgId;
+    constructor(opts: RtcSignalingOptions);
+    get isOpen(): boolean;
+    /** Step 1: the sign blob the socket and every auth message carry. A non-JSON body is reported by status. */
+    fetchSign(): Promise<string>;
+    /**
+     * Step 2: open the socket and send the first auth; resolves on `open`. A socket that closes or errors
+     * before it ever opened rejects, so the call always settles.
+     */
+    connect(): Promise<void>;
+    /** `action 1`, also what keeps the socket alive when re-sent. */
+    sendAuth(sign?: string): void;
+    /**
+     * `action 3`, a session message on channel 0, the hub's own session; `scall` opens the negotiation.
+     * `subSn` is empty for the hub's session.
+     */
+    sendSession(dataType: string, payload?: Record<string, unknown>): void;
+    sendCall(): void;
+    sendAck(): void;
+    /** The SDP answer, encoded for the negotiated call format, in an `info`. */
+    sendInfoSdp(sdp: string): void;
+    /** Trickle a candidate on the session's channel, like its SDP answer. An empty candidate ends them. */
+    sendInfoCandidate(candidate: string): void;
+    sendHangup(): void;
+    close(): void;
+    private startKeepalive;
+    private stopKeepalive;
+    private sendEnvelope;
+    private handleWireMessage;
+}

package/dist/transport/token-echo.d.ts

@@ -0,0 +1,8 @@
+/**
+ * Strip a token the gateway echoed back into its own error message.
+ *
+ * `"token not exist, token = <the rejected token>"` is the vendor's wording, and that message travels into the
+ * error the SDK surfaces. A credential that has just been rejected is still a credential, and it is
+ * never the part of the message that explains anything.
+ */
+export declare function withoutTokenEcho(text: string): string;

package/dist/transport/tuya/account.d.ts

@@ -1,14 +1,17 @@
-/** Username/plaintext prefix the app prepends to the eufy user id. */
-export declare const TUYA_USERNAME_PREFIX = "eufyhome-";
+/**
+ * Username/plaintext prefix the app prepends to the eufy user id. The production app uses `eh-`;
+ * `eufyhome-` is the prefix of its QA environment only.
+ */
+export declare const TUYA_USERNAME_PREFIX = "eh-";
 /** AES-128-CBC key used to derive the Tuya password (16 bytes). */
 export declare const TUYA_PASSWORD_KEY: Buffer<ArrayBuffer>;
 /** AES-128-CBC IV used to derive the Tuya password (16 bytes). */
 export declare const TUYA_PASSWORD_IV: Buffer<ArrayBuffer>;
-/** The Tuya username for a eufy user id (`"eufyhome-" + eufyUserId`). */
+/** The Tuya username for a eufy user id (`"eh-" + eufyUserId`). */
 export declare function tuyaUsername(eufyUserId: string): string;
 /**
  * Derive the Tuya password for a eufy user id:
- * `UPPERCASE-HEX( AES-128-CBC-NoPadding( pad16("eufyhome-"+eufyUserId), KEY, IV ) )`.
+ * `UPPERCASE-HEX( AES-128-CBC-NoPadding( pad16("eh-"+eufyUserId), KEY, IV ) )`.
  * Deterministic (fixed KEY/IV) — the same user id always yields the same password.
  */
 export declare function deriveTuyaPassword(eufyUserId: string): string;
@@ -29,7 +32,7 @@ export declare function isoToDialCode(iso: string): string | undefined;
 export declare function resolveCountryCode(phoneCode?: string, region?: string, isoCode?: string): string;
 /** A derived Tuya login identity — everything needed to call the uid token/password login actions. */
 export interface TuyaAccount {
-    /** `"eufyhome-" + eufyUserId`. */
+    /** `"eh-" + eufyUserId`. */
     username: string;
     /** AES-derived password (uppercase hex). See {@link deriveTuyaPassword}. */
     password: string;

package/dist/transport/tuya/client.d.ts

@@ -50,8 +50,21 @@ export declare class TuyaClient {
      * Requires a working signer (the sign step).
      */
     buildRequest(action: TuyaAction): Record<string, string>;
-    /** Build + POST an action, returning the parsed envelope. Requires a working signer. */
+    /**
+     * Build + POST an action, returning the parsed envelope. Requires a working signer.
+     *
+     * On an `et=3` reply the envelope's `result` is a base64 AES-128-GCM blob, not an object; this
+     * decrypts it (keyed off the request's `requestId` and the session's `ecode`) and returns the
+     * decrypted inner envelope, so callers read `result` as an object regardless. A non-string `result`
+     * (an error, or an already-plain reply) passes through untouched.
+     */
     call<T = unknown>(action: TuyaAction): Promise<TuyaEnvelope<T>>;
+    /**
+     * Decode an et=3 reply. When `result` is a non-empty string it is the encrypted blob: decrypt and
+     * parse it (a wrong key or tampered blob fails the GCM tag in {@link decryptReply} and throws). The
+     * plaintext is itself the standard `{success, t, result}` envelope, which becomes the returned one.
+     */
+    private decodeReply;
     /**
      * Log into the Tuya cloud from a eufy user id (wire-confirmed from the eufy Security app).
      *
@@ -68,12 +81,13 @@ export declare class TuyaClient {
      */
     login(eufyUserId: string, phoneCode?: string): Promise<TuyaLoginResult>;
     /**
-     * READ/dump a device's cached data-points (`thing.m.device.cache.dp.get`).
-     * Builds the request without needing a working signer; the signer is only exercised on send.
+     * READ a device's current data-points (`smartlife.m.device.dp.get`). The envelope's `result` is a
+     * flat `{ "<dpId>": value }` map. Builds the request without needing a working signer; the signer is
+     * only exercised on send.
      */
-    getDeviceDps<T = unknown>(devId: string, dpCacheType?: number): Promise<TuyaEnvelope<T>>;
+    getDeviceDps<T = unknown>(devId: string): Promise<TuyaEnvelope<T>>;
     /**
-     * CONTROL: publish data-points to a device (`thing.m.device.dp.publish`). `dps` is
+     * CONTROL: publish data-points to a device (`smartlife.m.device.dp.publish`). `dps` is
      * `{ "<dpId>": <value> }`. `gwId` is the gateway/parent id (equals `devId` for a standalone gw).
      *
      * ⚠️ UNVERIFIED write — refuses to send by default. The `dp.publish` param shape