@mega-yfue/eufy-sdk 0.5.0-beta.19 → 0.5.0-beta.20
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.
- package/dist/index.js +14 -11
- package/dist/index.js.map +2 -2
- package/dist/model/capabilities/camera.d.ts +14 -10
- package/package.json +1 -1
|
@@ -445,25 +445,29 @@ export declare const CAMERA_MEMBERS: {
|
|
|
445
445
|
* Live-view quality, the pair to {@link CAMERA_MEMBERS.recordingQuality} and a different setting on a
|
|
446
446
|
* different wire: changing one leaves the other's parameter untouched.
|
|
447
447
|
*
|
|
448
|
-
* The READ is 1020, which reports the resolved tier as a plain integer
|
|
449
|
-
*
|
|
450
|
-
*
|
|
448
|
+
* The READ is 1020, which reports the resolved tier as a plain integer, while the WRITE rides 2730's
|
|
449
|
+
* `1350` payload. They are two ids for one setting because 2730 carries a per-mode config and 1020
|
|
450
|
+
* carries the tier in force; the tier is what this property means. 1020 is also the name the param
|
|
451
|
+
* dictionary already gives that id, and `Device` keys state by NAME — a member claiming 2730 under
|
|
452
|
+
* this name would collide with it on a device reporting both.
|
|
451
453
|
*
|
|
452
|
-
* `
|
|
453
|
-
*
|
|
454
|
-
* 2731 write on the same envelope and the same session does land. The one difference the capture
|
|
455
|
-
* shows is that the app's frame carries no `mChannel`/`mValue3`, which this envelope always emits.
|
|
456
|
-
* Until a send is confirmed, the setter is absent — a control that silently does nothing is worse
|
|
457
|
-
* than none — and the read ships ahead of it, which verification per direction allows.
|
|
454
|
+
* `transaction` is part of the frame that was captured, so it is sent. The recording sibling's own
|
|
455
|
+
* confirmed frame carries no such field; neither is inferred from the other.
|
|
458
456
|
*/
|
|
459
457
|
readonly streamingQuality: {
|
|
458
|
+
readonly accepts: StreamingQualityName;
|
|
460
459
|
readonly param: 1020;
|
|
461
460
|
readonly type: "number";
|
|
462
461
|
readonly kind: "enum";
|
|
463
462
|
readonly enumValues: Readonly<Record<number, string>>;
|
|
464
463
|
readonly provenance: "verified";
|
|
465
|
-
readonly
|
|
464
|
+
readonly args: readonly [{
|
|
465
|
+
readonly name: "quality";
|
|
466
|
+
readonly kind: "enum";
|
|
467
|
+
readonly description: "A tier, or the name it maps to. 0 is Auto.";
|
|
468
|
+
}];
|
|
466
469
|
readonly description: string;
|
|
470
|
+
readonly write: (v: string | number | boolean, ctx: CommandContext) => Command | undefined;
|
|
467
471
|
};
|
|
468
472
|
/**
|
|
469
473
|
* `type` is how the value is STORED, and 2731 stores the whole config — the ACTIVE tier is lifted out
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@mega-yfue/eufy-sdk",
|
|
3
|
-
"version": "0.5.0-beta.
|
|
3
|
+
"version": "0.5.0-beta.20",
|
|
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",
|