@mega-yfue/eufy-sdk 0.2.0-beta.18 → 0.2.0-beta.19
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
|
@@ -247,7 +247,11 @@ export interface CommandContext extends AvailabilityContext {
|
|
|
247
247
|
adminUserId?: string;
|
|
248
248
|
/** The acting member's short id (`member.short_user_id`, hex, e.g. `"0003"`) — the lock cmd `A5` field. */
|
|
249
249
|
shortUserId?: string;
|
|
250
|
-
/**
|
|
250
|
+
/**
|
|
251
|
+
* The acting name a command attributes itself to — the lock cmd acting-username `A4` field, and the
|
|
252
|
+
* `user_name` of the guard-mode and HomeBase-alarm writes. The logged-in account's display name
|
|
253
|
+
* (email local-part) unless the client pins a different label for it.
|
|
254
|
+
*/
|
|
251
255
|
accountName?: string;
|
|
252
256
|
/**
|
|
253
257
|
* Whether the device has a usable P2P endpoint (a non-empty `p2p_did`). A HomeBase-attached lock
|
|
@@ -32,6 +32,14 @@ export interface MegaClientConfig {
|
|
|
32
32
|
* an explicit value pins a fixed one. Not the account identity — that's `phoneModel`.
|
|
33
33
|
*/
|
|
34
34
|
mediaUserAgent?: string;
|
|
35
|
+
/**
|
|
36
|
+
* Acting name written into the commands that carry an actor field — guard mode and HomeBase alarm
|
|
37
|
+
* output (`user_name`), a lock's acting username. Trimmed, and blank counts as unset: the default
|
|
38
|
+
* is the login email's local-part (the whole string when it has no `@`). Attribution only — the
|
|
39
|
+
* device stores it for its own activity record, and no captured frame shows it being validated
|
|
40
|
+
* against the account.
|
|
41
|
+
*/
|
|
42
|
+
accountName?: string;
|
|
35
43
|
/** Persist + reuse the session (token + session key) across runs. Default: in-memory. */
|
|
36
44
|
store?: SessionStore;
|
|
37
45
|
/** Diagnostics sink. Omit for silence; pass a `Logger` (or `new ConsoleLogger()`) to see logs. */
|
|
@@ -238,10 +246,15 @@ export declare class MegaHttpClient {
|
|
|
238
246
|
/** The active region shard (e.g. `"eu-pr"`, `"us-pr"`), set after {@link login} or a region override. */
|
|
239
247
|
get regionShard(): RegionShard;
|
|
240
248
|
/**
|
|
241
|
-
* The
|
|
242
|
-
*
|
|
243
|
-
*
|
|
244
|
-
* if it has no `@`.
|
|
249
|
+
* The name commands attribute themselves to — {@link MegaClientConfig.accountName} when the config
|
|
250
|
+
* pins one (trimmed; blank counts as unset), otherwise the logged-in account's display name, which
|
|
251
|
+
* is the login email's local-part (e.g. `someone+tag` for `someone+tag@example.com`) and falls back
|
|
252
|
+
* to the whole email if it has no `@`.
|
|
253
|
+
*
|
|
254
|
+
* The local-part is the string the app writes into the ff09 command's acting "username" field
|
|
255
|
+
* (verified against a captured T8531 unlock frame), so it is the faithful default. An override is a
|
|
256
|
+
* different LABEL for the same account, not a different identity: the session authenticates on the
|
|
257
|
+
* token and the device record's member ids, neither of which this touches.
|
|
245
258
|
*/
|
|
246
259
|
get accountName(): string;
|
|
247
260
|
/**
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@mega-yfue/eufy-sdk",
|
|
3
|
-
"version": "0.2.0-beta.
|
|
3
|
+
"version": "0.2.0-beta.19",
|
|
4
4
|
"description": "One typed TypeScript client for the Anker eufy v6 cloud — capability-driven devices, realtime events over P2P/MQTT/push, and live media",
|
|
5
5
|
"license": "Apache-2.0",
|
|
6
6
|
"author": "mega-yfue",
|