@mega-yfue/eufy-sdk 0.6.0-beta.25 → 0.6.0-beta.27

package/dist/model/capabilities/battery.d.ts

@@ -144,6 +144,9 @@ export declare const BATTERY_MEMBERS: {
      * The headline percentage, and this capability's detection evidence: reporting 1101 is what proves a
      * device is battery-powered, which is also the fact `MediaProvider` reads to decide a stream needs a
      * power budget. Published flat as `battery` — `level` alone is claimed by `suction` too.
+     *
+     * Withheld on a device that resolved `lock`, whose own `battery` member reads the same param 1101 and
+     * owns the `battery` property there, so the two do not both claim it.
      */
     readonly level: {
         readonly param: 1101;
@@ -152,6 +155,7 @@ export declare const BATTERY_MEMBERS: {
         readonly unit: "%";
         readonly kind: "percent";
         readonly provenance: "verified";
+        readonly available: (ctx: AvailabilityContext) => boolean;
         readonly description: "Battery level 0-100 (verified: param 1101).";
     };
     /**
@@ -170,7 +174,7 @@ export declare const BATTERY_MEMBERS: {
     /**
      * 1293 is the READABLE indicator (6445 is write-only/cloud-hidden). Verified live on a T8124R via an
      * app-toggle before/after diff: 0 = Battery, 1 = External Solar Panel. Values beyond 0/1 (some models
-     * report 5) are shown raw — `enumValues` only labels the two that are confirmed.
+     * report 5) read as `undefined` — `enumValues` holds only the two that are confirmed.
      *
      * The write is a `1350` SET_PAYLOAD, inner cmd 1293, `{charge_mode:N}`, `mValue3` 0 (the app uses 0,
      * not the cmd id), and the setter accepts a NAME as well as the index the getter answers.

package/dist/model/capabilities/camera.d.ts

@@ -439,6 +439,10 @@ export declare const CAMERA_MEMBERS: {
      * sensor omits it, and the wire accepts the value regardless — the device's own reported set is the
      * only statement of which of the three it has. `coerceEnumValue` rejects a value outside
      * {@link NightVision} rather than coercing it. The payload key on the wire is `night_sion`.
+     *
+     * 1277 carries more than these three on some models: the V6 app's per-model mappings put modes on
+     * 3, 5, 6 and 8 as well, and which model takes which mapping is not in the app bundle. A reported value
+     * outside the published options reads as `undefined` rather than as an unnamed number.
      */
     readonly nightVision: {
         readonly param: 1277;

package/dist/model/capabilities/members.d.ts

@@ -576,12 +576,14 @@ export declare function memberWrite(name: string, m: ValueMember, value: boolean
  * is stored as a decoded object. Handing either through a getter typed `number` is the one lie this
  * table exists to prevent.
  *
+ * A number outside `values`, the options published for this device, answers `undefined`.
+ *
  * Exported so the ONE narrowing the getters use is also the one a property-change announcement carries.
  * A second conversion of the wire value is precisely how a payload comes to disagree with the getter
  * beside it, which would defeat the point of announcing the change at all.
  * @internal
  */
-export declare function narrow(type: PropertyValueType, read: CapabilityStateReader, prop: string): boolean | number | string | undefined;
+export declare function narrow(type: PropertyValueType, read: CapabilityStateReader, prop: string, values?: Record<number, string>): boolean | number | string | undefined;
 /**
  * Both presence gates at once: the params a member requires, and its own {@link ValueMember.available}.
  *

package/package.json

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