@ovok/native 0.4.6 → 0.4.8

package/lib/typescript/module/src/modules/bt-management/services/devices/veroval/veroval.duo-control-device.d.ts

@@ -0,0 +1,19 @@
+import { Device } from "react-native-ble-plx";
+import { CreateDeviceParams } from "../../../types/create-device-params";
+import { CustomDeviceId } from "../../../types/custom-device-id";
+import { CustomDevice } from "../custom/custom.device";
+/**
+ * The Veroval duo control.
+ *
+ * A device class rather than a declaration, because reading it is a conversation: the two
+ * user memories are asked in turn, and the device answers with bare control bytes as often
+ * as with payload. The decoding is still declared - the class supplies the framing and the
+ * walk, and nothing else.
+ *
+ * Readings are stored measurements, not live ones. The device hands over its history when
+ * asked, so what arrives was taken before the connection and may be days old.
+ */
+export declare class VerovalDuoControlDevice extends CustomDevice {
+    constructor(device: Device, params: CreateDeviceParams<CustomDeviceId>);
+}
+//# sourceMappingURL=veroval.duo-control-device.d.ts.map

package/lib/typescript/module/src/modules/bt-management/services/devices/veroval/veroval.duo-control-device.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"veroval.duo-control-device.d.ts","sourceRoot":"","sources":["../../../../../../../../../src/modules/bt-management/services/devices/veroval/veroval.duo-control-device.ts"],"names":[],"mappings":"AACA,OAAO,EAAE,MAAM,EAAE,MAAM,sBAAsB,CAAC;AAE9C,OAAO,EAAE,kBAAkB,EAAE,MAAM,qCAAqC,CAAC;AACzE,OAAO,EAAE,cAAc,EAAE,MAAM,iCAAiC,CAAC;AAEjE,OAAO,EAAE,YAAY,EAAE,MAAM,yBAAyB,CAAC;AAoFvD;;;;;;;;;;GAUG;AACH,qBAAa,uBAAwB,SAAQ,YAAY;gBAErD,MAAM,EAAE,MAAM,EACd,MAAM,EAAE,kBAAkB,CAAC,cAAc,CAAC;CAkB7C"}

package/lib/typescript/module/src/modules/bt-management/services/devices/veroval/veroval.duo-control-sequencer.d.ts

@@ -0,0 +1,45 @@
+import { CommandSequencer } from "../../../types/command-sequencer";
+import { DeviceCommand } from "../../../types/device-command";
+interface DuoControlSequencerParams {
+    /** The characteristic commands are written to. It acknowledges nothing. */
+    write: Omit<DeviceCommand, "frame">;
+    /** Called with why the exchange stopped early. Required, so a refusal is not lost. */
+    onRefused: (reason: string) => void;
+}
+/**
+ * Walks the Veroval duo control through its stored history.
+ *
+ * The device answers one request at a time and holds two user memories, so the exchange is
+ * a fixed walk: ask user one how many records it has, read them, then user two. A memory
+ * that reports none is skipped rather than read.
+ *
+ * Two of its replies are not payload at all. A bare `ACK` means the device has more to send
+ * and is waiting to be asked, which is what `ENQ` does - so an acknowledgement provokes an
+ * enquiry rather than advancing the walk. A bare `NAK` is a refusal and ends it.
+ *
+ * Everything here is derived from HARTMANN's own application. The one part that is an
+ * inference rather than a reading is `ENQ` as flow control: the app writes it on receiving
+ * `ACK`, which is what that pair means in the serial protocol this is descended from, but
+ * the pacing was not observed on hardware.
+ */
+export declare class VerovalDuoControlSequencer implements CommandSequencer {
+    private readonly params;
+    private step;
+    private isDone;
+    constructor(params: DuoControlSequencerParams);
+    initialCommands: () => readonly DeviceCommand[];
+    nextCommand: (frame: readonly string[]) => readonly DeviceCommand[] | undefined;
+    private answerControlByte;
+    /**
+     * A memory reporting no records is skipped. Asking for the data of an empty memory is a
+     * request the device answers with nothing, which would stall the walk on its own reply.
+     */
+    private answerCount;
+    /** Past this memory's data command, to the next memory's count. */
+    private skipMemory;
+    private advance;
+    private stop;
+    private commandFor;
+}
+export {};
+//# sourceMappingURL=veroval.duo-control-sequencer.d.ts.map

package/lib/typescript/module/src/modules/bt-management/services/devices/veroval/veroval.duo-control-sequencer.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"veroval.duo-control-sequencer.d.ts","sourceRoot":"","sources":["../../../../../../../../../src/modules/bt-management/services/devices/veroval/veroval.duo-control-sequencer.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,gBAAgB,EAAE,MAAM,kCAAkC,CAAC;AACpE,OAAO,EAAE,aAAa,EAAE,MAAM,+BAA+B,CAAC;AAyC9D,UAAU,yBAAyB;IAEjC,2EAA2E;IAC3E,KAAK,EAAE,IAAI,CAAC,aAAa,EAAE,OAAO,CAAC,CAAC;IAEpC,sFAAsF;IACtF,SAAS,EAAE,CAAC,MAAM,EAAE,MAAM,KAAK,IAAI,CAAC;CACrC;AAaD;;;;;;;;;;;;;;;GAeG;AACH,qBAAa,0BAA2B,YAAW,gBAAgB;IAI9C,OAAO,CAAC,QAAQ,CAAC,MAAM;IAH1C,OAAO,CAAC,IAAI,CAAK;IACjB,OAAO,CAAC,MAAM,CAAS;gBAEa,MAAM,EAAE,yBAAyB;IAE9D,eAAe,QAAO,SAAS,aAAa,EAAE,CAAyB;IAEvE,WAAW,GAChB,OAAO,SAAS,MAAM,EAAE,KACvB,SAAS,aAAa,EAAE,GAAG,SAAS,CAgBrC;IAEF,OAAO,CAAC,iBAAiB,CAYvB;IAEF;;;OAGG;IACH,OAAO,CAAC,WAAW,CAUjB;IAEF,mEAAmE;IACnE,OAAO,CAAC,UAAU,CAIhB;IAEF,OAAO,CAAC,OAAO,CAUb;IAEF,OAAO,CAAC,IAAI,CAKV;IAEF,OAAO,CAAC,UAAU,CACmC;CACtD"}

package/lib/typescript/module/src/modules/bt-management/services/devices/veroval/veroval.ecg-device.d.ts

@@ -0,0 +1,30 @@
+import { Device } from "react-native-ble-plx";
+import { CreateDeviceParams } from "../../../types/create-device-params";
+import { IntegratedDevices } from "../../../types/integrated-devices";
+import { IService } from "../../../types/service.type";
+import { BTManagedDevice } from "../bt-managed-device";
+import { VerovalEcgTransfer } from "./veroval.ecg-transfer";
+/**
+ * The Veroval ECG.
+ *
+ * Reading it is a download rather than a decode, so the whole recording is assembled before
+ * anything is reported: thirty-four seconds of samples at 128 Hz, two bytes each, converted
+ * to millivolts with the device's own calibration.
+ *
+ * The vendor's app plots a thirty-second window of this with a baseline-wander filter
+ * applied. That is a display transform, not calibration, so it is deliberately not
+ * reproduced here - what is reported is what the device recorded.
+ */
+export declare class VerovalEcgDevice extends BTManagedDevice<IntegratedDevices.VEROVAL_ECG> {
+    protected stuckDataTimeout: number;
+    protected preferredMtu: number;
+    protected onStreamStart: undefined;
+    protected mainServices: IService[];
+    protected validatePackage: () => boolean;
+    protected createCommandSequencer: () => VerovalEcgTransfer;
+    constructor(device: Device, params: CreateDeviceParams<IntegratedDevices.VEROVAL_ECG>);
+    /** Nothing is reported per packet; the transfer reports the recording when it is whole. */
+    protected handleSuccessResult(): void;
+    private reportRecording;
+}
+//# sourceMappingURL=veroval.ecg-device.d.ts.map

package/lib/typescript/module/src/modules/bt-management/services/devices/veroval/veroval.ecg-device.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"veroval.ecg-device.d.ts","sourceRoot":"","sources":["../../../../../../../../../src/modules/bt-management/services/devices/veroval/veroval.ecg-device.ts"],"names":[],"mappings":"AACA,OAAO,EAAE,MAAM,EAAE,MAAM,sBAAsB,CAAC;AAG9C,OAAO,EAAE,kBAAkB,EAAE,MAAM,qCAAqC,CAAC;AACzE,OAAO,EAAE,iBAAiB,EAAE,MAAM,mCAAmC,CAAC;AACtE,OAAO,EAAE,QAAQ,EAAE,MAAM,6BAA6B,CAAC;AACvD,OAAO,EAAE,eAAe,EAAE,MAAM,sBAAsB,CAAC;AAMvD,OAAO,EAAE,kBAAkB,EAAE,MAAM,wBAAwB,CAAC;AAgC5D;;;;;;;;;;GAUG;AACH,qBAAa,gBAAiB,SAAQ,eAAe,CAAC,iBAAiB,CAAC,WAAW,CAAC;IAClF,SAAS,CAAC,gBAAgB,SAAoB;IAC9C,UAAmB,YAAY,SAAiB;IAChD,SAAS,CAAC,aAAa,YAAa;IAEpC,SAAS,CAAC,YAAY,EAAE,QAAQ,EAAE,CAKhC;IAEF,UAAmB,eAAe,QAAO,OAAO,CAAS;IAEzD,UAAmB,sBAAsB,2BAIpC;gBAGH,MAAM,EAAE,MAAM,EACd,MAAM,EAAE,kBAAkB,CAAC,iBAAiB,CAAC,WAAW,CAAC;IAK3D,2FAA2F;IAC3F,SAAS,CAAC,mBAAmB,IAAI,IAAI;IAIrC,OAAO,CAAC,eAAe,CAerB;CACH"}

package/lib/typescript/module/src/modules/bt-management/services/devices/veroval/veroval.ecg-samples.d.ts

@@ -0,0 +1,39 @@
+/**
+ * How fast the device samples.
+ *
+ * Not taken on trust: the vendor's own plotting step works out to two two-hundred-and-fifty
+ * sixths of a second, and its transfer is thirty-four segments of sixteen packets of sixteen
+ * bytes - which is 256 bytes, 128 samples, one second per segment. Both say 128 Hz.
+ */
+declare const VEROVAL_ECG_SAMPLE_RATE_HZ = 128;
+/**
+ * The calibration the recording is read with.
+ *
+ * This is the EDF convention - a linear map from counts onto a physical range - and the
+ * device states its own in the header it sends before the curve. These are the values the
+ * vendor's app falls back to, and are what the SDK uses until a header supplies otherwise:
+ * the full signed sixteen-bit range spans plus or minus 27.68 mV.
+ */
+declare const DEFAULT_CALIBRATION: {
+    readonly physicalMinimumMicrovolts: -27680;
+    readonly physicalMaximumMicrovolts: 27680;
+    readonly digitalMinimum: -32768;
+    readonly digitalMaximum: 32767;
+};
+interface EcgCalibration {
+    physicalMinimumMicrovolts: number;
+    physicalMaximumMicrovolts: number;
+    digitalMinimum: number;
+    digitalMaximum: number;
+}
+/**
+ * Turns the bytes of a recording into millivolts.
+ *
+ * A trailing odd byte is ignored: half a sample is not a sample. The conversion is the
+ * device's own, applied as it states it rather than reduced to a single factor, so a header
+ * that reports a different range still decodes correctly.
+ */
+declare const decodeVerovalEcgSamples: (bytes: readonly string[], calibration?: EcgCalibration) => number[];
+export { decodeVerovalEcgSamples, DEFAULT_CALIBRATION, VEROVAL_ECG_SAMPLE_RATE_HZ, };
+export type { EcgCalibration };
+//# sourceMappingURL=veroval.ecg-samples.d.ts.map

package/lib/typescript/module/src/modules/bt-management/services/devices/veroval/veroval.ecg-samples.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"veroval.ecg-samples.d.ts","sourceRoot":"","sources":["../../../../../../../../../src/modules/bt-management/services/devices/veroval/veroval.ecg-samples.ts"],"names":[],"mappings":"AAOA;;;;;;GAMG;AACH,QAAA,MAAM,0BAA0B,MAAM,CAAC;AAEvC;;;;;;;GAOG;AACH,QAAA,MAAM,mBAAmB;;;;;CAKf,CAAC;AAIX,UAAU,cAAc;IACtB,yBAAyB,EAAE,MAAM,CAAC;IAClC,yBAAyB,EAAE,MAAM,CAAC;IAClC,cAAc,EAAE,MAAM,CAAC;IACvB,cAAc,EAAE,MAAM,CAAC;CACxB;AAWD;;;;;;GAMG;AACH,QAAA,MAAM,uBAAuB,GAC3B,OAAO,SAAS,MAAM,EAAE,EACxB,cAAa,cAAoC,KAChD,MAAM,EAsBR,CAAC;AAEF,OAAO,EACL,uBAAuB,EACvB,mBAAmB,EACnB,0BAA0B,GAC3B,CAAC;AACF,YAAY,EAAE,cAAc,EAAE,CAAC"}

package/lib/typescript/module/src/modules/bt-management/services/devices/veroval/veroval.ecg-transfer.d.ts

@@ -0,0 +1,35 @@
+import { CommandSequencer } from "../../../types/command-sequencer";
+import { DeviceCommand } from "../../../types/device-command";
+interface EcgTransferParams {
+    /** The characteristic requests are written to. */
+    write: Omit<DeviceCommand, "frame">;
+    /** Called once, with the recording's bytes, when every segment has arrived. */
+    onRecording: (bytes: readonly string[]) => void;
+}
+/**
+ * Downloads a recording from the Veroval ECG.
+ *
+ * The exchange is a fixed walk rather than a conversation: ask for the download mode, then
+ * the header, then each second of the recording in turn. The device answers each request
+ * with a known number of twenty-byte packets, sixteen payload bytes each, so the transfer is
+ * paced by counting them - which is how the vendor's own app paces it, and is the only thing
+ * that distinguishes one phase's packets from another's.
+ *
+ * A recording is thirty-four seconds at 128 Hz. Nothing is reported until all of it has
+ * arrived: a partial ECG that looked whole would be worse than none, and the count is what
+ * says it is whole.
+ */
+export declare class VerovalEcgTransfer implements CommandSequencer {
+    private readonly params;
+    private phase;
+    private packets;
+    private segment;
+    private recording;
+    constructor(params: EcgTransferParams);
+    initialCommands: () => readonly DeviceCommand[];
+    nextCommand: (frame: readonly string[]) => readonly DeviceCommand[] | undefined;
+    private finishSegment;
+    private requestSegment;
+}
+export {};
+//# sourceMappingURL=veroval.ecg-transfer.d.ts.map

package/lib/typescript/module/src/modules/bt-management/services/devices/veroval/veroval.ecg-transfer.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"veroval.ecg-transfer.d.ts","sourceRoot":"","sources":["../../../../../../../../../src/modules/bt-management/services/devices/veroval/veroval.ecg-transfer.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,gBAAgB,EAAE,MAAM,kCAAkC,CAAC;AACpE,OAAO,EAAE,aAAa,EAAE,MAAM,+BAA+B,CAAC;AAgD9D,UAAU,iBAAiB;IAEzB,kDAAkD;IAClD,KAAK,EAAE,IAAI,CAAC,aAAa,EAAE,OAAO,CAAC,CAAC;IAEpC,+EAA+E;IAC/E,WAAW,EAAE,CAAC,KAAK,EAAE,SAAS,MAAM,EAAE,KAAK,IAAI,CAAC;CACjD;AAID;;;;;;;;;;;;GAYG;AACH,qBAAa,kBAAmB,YAAW,gBAAgB;IAMtC,OAAO,CAAC,QAAQ,CAAC,MAAM;IAL1C,OAAO,CAAC,KAAK,CAAiB;IAC9B,OAAO,CAAC,OAAO,CAAK;IACpB,OAAO,CAAC,OAAO,CAAK;IACpB,OAAO,CAAC,SAAS,CAAgB;gBAEG,MAAM,EAAE,iBAAiB;IAEtD,eAAe,QAAO,SAAS,aAAa,EAAE,CAEnD;IAEK,WAAW,GAChB,OAAO,SAAS,MAAM,EAAE,KACvB,SAAS,aAAa,EAAE,GAAG,SAAS,CAyBrC;IAEF,OAAO,CAAC,aAAa,CAWnB;IAEF,OAAO,CAAC,cAAc,CAQpB;CACH"}

package/lib/typescript/module/src/modules/bt-management/services/devices/viatom/viatom.bp-monitors.d.ts

@@ -0,0 +1,44 @@
+import { CustomDeviceDefinition } from "../../../types/custom-device-definition";
+interface ViatomBpParams {
+    /** Reported back as deviceData.name, and must not collide with a built-in device. */
+    id: string;
+    /**
+     * The advertised name, defaulting to a matcher for this product that cannot also match a
+     * longer one in the family.
+     */
+    nameMatch?: string | RegExp;
+    /**
+     * The models this declaration may poll, once they are known. Left empty the advertised
+     * name is the identification, which is what the vendor's own SDK binds on.
+     */
+    expectedDeviceTypes?: number[];
+}
+/**
+ * Declares one monitor of the BP2 series.
+ *
+ * `advertisedName` is the name the vendor's SDK matches - `BP2A`, `BP2T` - and the matcher
+ * derived from it excludes every longer name in the family, so a declaration for `BP2`
+ * cannot pick up a `BP2W`.
+ */
+declare const viatomBpMonitor: (advertisedName: string, params: ViatomBpParams) => CustomDeviceDefinition;
+/** BP2A, the arm-cuff monitor of the series. */
+declare const bp2aMonitor: (params: ViatomBpParams) => CustomDeviceDefinition;
+/** BP2T, documented by the vendor alongside BP2 and BP2A as the same protocol. */
+declare const bp2tMonitor: (params: ViatomBpParams) => CustomDeviceDefinition;
+/** BP2W. Documented in its own section, but decoding the same realtime struct. */
+declare const bp2wMonitor: (params: ViatomBpParams) => CustomDeviceDefinition;
+/**
+ * The names the BP3 range advertises.
+ *
+ * Fifteen products differing in cuff and casing rather than in protocol, so declaring the
+ * range is one line per name:
+ *
+ * ```typescript
+ * const bp3Devices = BP3_MODEL_NAMES.map((name) =>
+ *   viatomBpMonitor(name, { id: `viatom-${name.toLowerCase()}` }),
+ * );
+ * ```
+ */
+declare const BP3_MODEL_NAMES: readonly string[];
+export { bp2aMonitor, bp2tMonitor, bp2wMonitor, BP3_MODEL_NAMES, viatomBpMonitor, };
+//# sourceMappingURL=viatom.bp-monitors.d.ts.map

package/lib/typescript/module/src/modules/bt-management/services/devices/viatom/viatom.bp-monitors.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"viatom.bp-monitors.d.ts","sourceRoot":"","sources":["../../../../../../../../../src/modules/bt-management/services/devices/viatom/viatom.bp-monitors.ts"],"names":[],"mappings":"AAGA,OAAO,EAAE,sBAAsB,EAAE,MAAM,yCAAyC,CAAC;AAsFjF,UAAU,cAAc;IAEtB,qFAAqF;IACrF,EAAE,EAAE,MAAM,CAAC;IAEX;;;OAGG;IACH,SAAS,CAAC,EAAE,MAAM,GAAG,MAAM,CAAC;IAE5B;;;OAGG;IACH,mBAAmB,CAAC,EAAE,MAAM,EAAE,CAAC;CAChC;AAED;;;;;;GAMG;AACH,QAAA,MAAM,eAAe,GACnB,gBAAgB,MAAM,EACtB,QAAQ,cAAc,KACrB,sBAWC,CAAC;AAEL,gDAAgD;AAChD,QAAA,MAAM,WAAW,GAAI,QAAQ,cAAc,KAAG,sBACb,CAAC;AAElC,kFAAkF;AAClF,QAAA,MAAM,WAAW,GAAI,QAAQ,cAAc,KAAG,sBACb,CAAC;AAElC,kFAAkF;AAClF,QAAA,MAAM,WAAW,GAAI,QAAQ,cAAc,KAAG,sBACb,CAAC;AAElC;;;;;;;;;;;GAWG;AACH,QAAA,MAAM,eAAe,EAAE,SAAS,MAAM,EAgBrC,CAAC;AAEF,OAAO,EACL,WAAW,EACX,WAAW,EACX,WAAW,EACX,eAAe,EACf,eAAe,GAChB,CAAC"}

package/lib/typescript/module/src/modules/bt-management/services/devices/viatom/viatom.ecg-recorders.d.ts

@@ -0,0 +1,32 @@
+import { CustomDeviceDefinition } from "../../../types/custom-device-definition";
+interface ViatomEcgParams {
+    /** Reported back as deviceData.name, and must not collide with a built-in device. */
+    id: string;
+    /**
+     * The advertised name, defaulting to a matcher for this product that cannot also match a
+     * longer one in the family.
+     */
+    nameMatch?: string | RegExp;
+    /**
+     * The models this declaration may poll, once they are known. Worth more here than
+     * elsewhere in the family, because of what these opcodes mean on the wrong hardware.
+     */
+    expectedDeviceTypes?: number[];
+}
+/** The ER1, and the handheld recorders sold under other names on the same protocol. */
+declare const er1Recorder: (advertisedName: string, params: ViatomEcgParams) => CustomDeviceDefinition;
+/**
+ * The ER2, which reads the same block but over a link that grants nothing beyond the
+ * minimum. Asking it for the MTU the rest of the family grants is what the vendor's own SDK
+ * declines to do, and a command longer than the link carries is truncated rather than
+ * refused.
+ */
+declare const er2Recorder: (advertisedName: string, params: ViatomEcgParams) => CustomDeviceDefinition;
+/** The ER3, which reads the same parameter block from a different opcode. */
+declare const er3Recorder: (advertisedName: string, params: ViatomEcgParams) => CustomDeviceDefinition;
+/** The names the ER1 recorders advertise. */
+declare const ER1_MODEL_NAMES: readonly string[];
+/** The names the ER2 recorders advertise, all of them on the small-MTU link. */
+declare const ER2_MODEL_NAMES: readonly string[];
+export { er1Recorder, ER1_MODEL_NAMES, er2Recorder, ER2_MODEL_NAMES, er3Recorder, };
+//# sourceMappingURL=viatom.ecg-recorders.d.ts.map

package/lib/typescript/module/src/modules/bt-management/services/devices/viatom/viatom.ecg-recorders.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"viatom.ecg-recorders.d.ts","sourceRoot":"","sources":["../../../../../../../../../src/modules/bt-management/services/devices/viatom/viatom.ecg-recorders.ts"],"names":[],"mappings":"AAEA,OAAO,EAAE,sBAAsB,EAAE,MAAM,yCAAyC,CAAC;AAqDjF,UAAU,eAAe;IAEvB,qFAAqF;IACrF,EAAE,EAAE,MAAM,CAAC;IAEX;;;OAGG;IACH,SAAS,CAAC,EAAE,MAAM,GAAG,MAAM,CAAC;IAE5B;;;OAGG;IACH,mBAAmB,CAAC,EAAE,MAAM,EAAE,CAAC;CAChC;AA4CD,uFAAuF;AACvF,QAAA,MAAM,WAAW,GACf,gBAAgB,MAAM,EACtB,QAAQ,eAAe,KACtB,sBASA,CAAC;AAEJ;;;;;GAKG;AACH,QAAA,MAAM,WAAW,GACf,gBAAgB,MAAM,EACtB,QAAQ,eAAe,KACtB,sBASA,CAAC;AAEJ,6EAA6E;AAC7E,QAAA,MAAM,WAAW,GACf,gBAAgB,MAAM,EACtB,QAAQ,eAAe,KACtB,sBASA,CAAC;AAEJ,6CAA6C;AAC7C,QAAA,MAAM,eAAe,EAAE,SAAS,MAAM,EASrC,CAAC;AAEF,gFAAgF;AAChF,QAAA,MAAM,eAAe,EAAE,SAAS,MAAM,EAA+C,CAAC;AAEtF,OAAO,EACL,WAAW,EACX,eAAe,EACf,WAAW,EACX,eAAe,EACf,WAAW,GACZ,CAAC"}

package/lib/typescript/module/src/modules/bt-management/services/devices/viatom/viatom.lepod.d.ts

@@ -0,0 +1,25 @@
+import { CustomDeviceDefinition } from "../../../types/custom-device-definition";
+interface LepodParams {
+    /** Reported back as deviceData.name, and must not collide with a built-in device. */
+    id: string;
+    /**
+     * The advertised name, defaulting to a matcher for this product that cannot also match a
+     * longer one in the family.
+     */
+    nameMatch?: string | RegExp;
+    /** The models this declaration may poll, once they are known. */
+    expectedDeviceTypes?: number[];
+}
+/**
+ * Declares a Lepod, reporting every reading its realtime frame carries.
+ *
+ * An instrument that is not attached reports a value outside the physiological range for
+ * what it measures, so that reading is discarded and reported while the others in the same
+ * frame are still delivered. The device also marks those conditions in bits of a lead-off
+ * byte, which a declaration cannot select on - reading them quietly needs a device class.
+ */
+declare const lepodMonitor: (advertisedName: string, params: LepodParams) => CustomDeviceDefinition;
+/** The names the Lepod range advertises. */
+declare const LEPOD_MODEL_NAMES: readonly string[];
+export { LEPOD_MODEL_NAMES, lepodMonitor };
+//# sourceMappingURL=viatom.lepod.d.ts.map

package/lib/typescript/module/src/modules/bt-management/services/devices/viatom/viatom.lepod.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"viatom.lepod.d.ts","sourceRoot":"","sources":["../../../../../../../../../src/modules/bt-management/services/devices/viatom/viatom.lepod.ts"],"names":[],"mappings":"AAEA,OAAO,EAAE,sBAAsB,EAAE,MAAM,yCAAyC,CAAC;AAoGjF,UAAU,WAAW;IAEnB,qFAAqF;IACrF,EAAE,EAAE,MAAM,CAAC;IAEX;;;OAGG;IACH,SAAS,CAAC,EAAE,MAAM,GAAG,MAAM,CAAC;IAE5B,iEAAiE;IACjE,mBAAmB,CAAC,EAAE,MAAM,EAAE,CAAC;CAChC;AAED;;;;;;;GAOG;AACH,QAAA,MAAM,YAAY,GAChB,gBAAgB,MAAM,EACtB,QAAQ,WAAW,KAClB,sBAsBC,CAAC;AAEL,4CAA4C;AAC5C,QAAA,MAAM,iBAAiB,EAAE,SAAS,MAAM,EAA0B,CAAC;AAEnE,OAAO,EAAE,iBAAiB,EAAE,YAAY,EAAE,CAAC"}

package/lib/typescript/module/src/modules/bt-management/services/devices/viatom/viatom.oximeters.d.ts

@@ -0,0 +1,39 @@
+import { CustomDeviceDefinition } from "../../../types/custom-device-definition";
+interface ViatomOximeterParams {
+    /** Reported back as deviceData.name, and must not collide with a built-in device. */
+    id: string;
+    /**
+     * The advertised name, defaulting to a matcher for this product that cannot also match a
+     * longer one in the family.
+     */
+    nameMatch?: string | RegExp;
+    /**
+     * The models this declaration may poll, once they are known. Left empty the advertised
+     * name is the identification, which is what the vendor's own SDK binds on.
+     */
+    expectedDeviceTypes?: number[];
+}
+/**
+ * Declares one oximeter of the range.
+ *
+ * **A finger that is not in the sensor yields no reading, reported as an error.** The device
+ * answers every poll whether or not it is measuring, and marks an unusable reading in two
+ * bits of a status byte - which a declaration cannot read, because a case is selected by
+ * whole bytes. What it can do is refuse the number: an oxygen saturation measured off the
+ * finger falls outside the physiological range, so it is discarded rather than reported.
+ * The reading is therefore never wrong, but a device left connected with nobody wearing it
+ * reports a decoding failure on each poll. Reading those bits quietly needs a device class.
+ */
+declare const viatomOximeter: (advertisedName: string, params: ViatomOximeterParams) => CustomDeviceDefinition;
+/**
+ * The names the oximeter range advertises.
+ *
+ * ```typescript
+ * const oximeters = VIATOM_OXIMETER_NAMES.map((name) =>
+ *   viatomOximeter(name, { id: `viatom-${name.toLowerCase()}` }),
+ * );
+ * ```
+ */
+declare const VIATOM_OXIMETER_NAMES: readonly string[];
+export { VIATOM_OXIMETER_NAMES, viatomOximeter };
+//# sourceMappingURL=viatom.oximeters.d.ts.map

package/lib/typescript/module/src/modules/bt-management/services/devices/viatom/viatom.oximeters.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"viatom.oximeters.d.ts","sourceRoot":"","sources":["../../../../../../../../../src/modules/bt-management/services/devices/viatom/viatom.oximeters.ts"],"names":[],"mappings":"AAEA,OAAO,EAAE,sBAAsB,EAAE,MAAM,yCAAyC,CAAC;AA2BjF,UAAU,oBAAoB;IAE5B,qFAAqF;IACrF,EAAE,EAAE,MAAM,CAAC;IAEX;;;OAGG;IACH,SAAS,CAAC,EAAE,MAAM,GAAG,MAAM,CAAC;IAE5B;;;OAGG;IACH,mBAAmB,CAAC,EAAE,MAAM,EAAE,CAAC;CAChC;AAED;;;;;;;;;;GAUG;AACH,QAAA,MAAM,cAAc,GAClB,gBAAgB,MAAM,EACtB,QAAQ,oBAAoB,KAC3B,sBAkCC,CAAC;AAEL;;;;;;;;GAQG;AACH,QAAA,MAAM,qBAAqB,EAAE,SAAS,MAAM,EAqB3C,CAAC;AAEF,OAAO,EAAE,qBAAqB,EAAE,cAAc,EAAE,CAAC"}

package/lib/typescript/module/src/modules/bt-management/types/command-sequencer.d.ts

@@ -0,0 +1,26 @@
+import { DeviceCommand } from "./device-command";
+/**
+ * Decides what to send a device, and when.
+ *
+ * These protocols are self-clocking: the device answers a request, and the answer is what
+ * says which request comes next. A file read walks its offsets that way, and an identity
+ * check gates everything after it on the reply to the first command. Neither can be
+ * expressed by re-sending one fixed frame, which is all the SDK could do before.
+ *
+ * At most one command is outstanding at a time. The transport serialises writes, so an
+ * implementation may assume the frame it is answering is the reply to the command it last
+ * returned.
+ */
+export interface CommandSequencer {
+    /** Sent once every characteristic is subscribed. Empty starts a device that only listens. */
+    initialCommands(): readonly DeviceCommand[];
+    /**
+     * Answers one complete frame.
+     *
+     * Returning `undefined` sends nothing, which is how a sequencer waits: an unidentified
+     * device is left alone rather than addressed with an opcode that may mean something else
+     * on the hardware actually present.
+     */
+    nextCommand(frame: readonly string[]): readonly DeviceCommand[] | undefined;
+}
+//# sourceMappingURL=command-sequencer.d.ts.map

package/lib/typescript/module/src/modules/bt-management/types/command-sequencer.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"command-sequencer.d.ts","sourceRoot":"","sources":["../../../../../../../src/modules/bt-management/types/command-sequencer.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,aAAa,EAAE,MAAM,kBAAkB,CAAC;AAEjD;;;;;;;;;;;GAWG;AACH,MAAM,WAAW,gBAAgB;IAE/B,6FAA6F;IAC7F,eAAe,IAAI,SAAS,aAAa,EAAE,CAAC;IAE5C;;;;;;OAMG;IACH,WAAW,CAAC,KAAK,EAAE,SAAS,MAAM,EAAE,GAAG,SAAS,aAAa,EAAE,GAAG,SAAS,CAAC;CAC7E"}

package/lib/typescript/module/src/modules/bt-management/types/custom-case-spec.d.ts

@@ -1,6 +1,7 @@
 import { MeasurementTypeKey } from "@ovok/core";
 import { CustomCaseKind } from "./custom-case-kind";
 import { CustomFieldSpec } from "./custom-field-spec";
+import { CustomMeasurementSpec } from "./custom-measurement-spec";
 /** One frame shape the device emits, selected by the monitor's `caseSelectorBytes`. */
 export interface CustomCaseSpec {
     /**
@@ -13,6 +14,48 @@ export interface CustomCaseSpec {
     measurementTypeKey?: MeasurementTypeKey;
     /** Required and non-empty for a "result" case, forbidden otherwise. */
     fields?: CustomFieldSpec[];
+    /**
+     * The frame is a run of fixed-width records, each decoded the same way.
+     *
+     * A device that hands over its stored history answers one request with every record it
+     * holds, back to back. Those are separate readings taken at separate times, so each is
+     * reported on its own rather than merged.
+     *
+     * **Byte indexes are relative to a record, not to the frame**, and are bounds-checked
+     * against `recordBytes`. A trailing part-record is ignored: a whole number of records is
+     * what the device sends, and half of one is not a reading.
+     */
+    repeatedRecords?: {
+        /** Width of one record. */
+        recordBytes: number;
+        /** Byte the first record starts at. Defaults to 0. */
+        from?: number;
+    };
+    /**
+     * Shortest frame of this shape, when it is longer than the characteristic's minimum.
+     *
+     * A selector byte often decides how long the frame is: the Bluetooth blood-pressure
+     * profile puts a timestamp and a pulse rate behind flag bits, so one shape is seven bytes
+     * and another is sixteen. Without this, every case is bounded by the shortest of them and
+     * the later fields cannot be declared at all - which is how a pulse rate gets dropped from
+     * a device that reports one.
+     *
+     * Must be at least the characteristic's `frame.minLengthBytes`. A frame that arrives
+     * shorter than the case it selected decodes nothing and is reported, not guessed at.
+     */
+    minLengthBytes?: number;
+    /**
+     * Further readings the same frame carries.
+     *
+     * A multi-parameter monitor sends one frame holding a heart rate, an oxygen saturation
+     * and a temperature at once. Those are three measurements, not one with nine properties,
+     * so each is declared with its own type and its own fields and each is reported
+     * separately. Property names must still be unique across the whole frame, because the
+     * decoded object is flat.
+     *
+     * Only meaningful on a "result" case.
+     */
+    additionalMeasurements?: CustomMeasurementSpec[];
     description?: string;
 }
 //# sourceMappingURL=custom-case-spec.d.ts.map

package/lib/typescript/module/src/modules/bt-management/types/custom-case-spec.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"custom-case-spec.d.ts","sourceRoot":"","sources":["../../../../../../../src/modules/bt-management/types/custom-case-spec.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,kBAAkB,EAAE,MAAM,YAAY,CAAC;AAEhD,OAAO,EAAE,cAAc,EAAE,MAAM,oBAAoB,CAAC;AACpD,OAAO,EAAE,eAAe,EAAE,MAAM,qBAAqB,CAAC;AAEtD,uFAAuF;AACvF,MAAM,WAAW,cAAc;IAE7B;;;OAGG;IACH,QAAQ,EAAE,MAAM,CAAC;IAEjB,IAAI,EAAE,cAAc,CAAC;IAErB,qFAAqF;IACrF,kBAAkB,CAAC,EAAE,kBAAkB,CAAC;IAExC,uEAAuE;IACvE,MAAM,CAAC,EAAE,eAAe,EAAE,CAAC;IAE3B,WAAW,CAAC,EAAE,MAAM,CAAC;CACtB"}
+{"version":3,"file":"custom-case-spec.d.ts","sourceRoot":"","sources":["../../../../../../../src/modules/bt-management/types/custom-case-spec.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,kBAAkB,EAAE,MAAM,YAAY,CAAC;AAEhD,OAAO,EAAE,cAAc,EAAE,MAAM,oBAAoB,CAAC;AACpD,OAAO,EAAE,eAAe,EAAE,MAAM,qBAAqB,CAAC;AACtD,OAAO,EAAE,qBAAqB,EAAE,MAAM,2BAA2B,CAAC;AAElE,uFAAuF;AACvF,MAAM,WAAW,cAAc;IAE7B;;;OAGG;IACH,QAAQ,EAAE,MAAM,CAAC;IAEjB,IAAI,EAAE,cAAc,CAAC;IAErB,qFAAqF;IACrF,kBAAkB,CAAC,EAAE,kBAAkB,CAAC;IAExC,uEAAuE;IACvE,MAAM,CAAC,EAAE,eAAe,EAAE,CAAC;IAE3B;;;;;;;;;;OAUG;IACH,eAAe,CAAC,EAAE;QAEhB,2BAA2B;QAC3B,WAAW,EAAE,MAAM,CAAC;QAEpB,sDAAsD;QACtD,IAAI,CAAC,EAAE,MAAM,CAAC;KACf,CAAC;IAEF;;;;;;;;;;;OAWG;IACH,cAAc,CAAC,EAAE,MAAM,CAAC;IAExB;;;;;;;;;;OAUG;IACH,sBAAsB,CAAC,EAAE,qBAAqB,EAAE,CAAC;IAEjD,WAAW,CAAC,EAAE,MAAM,CAAC;CACtB"}

package/lib/typescript/module/src/modules/bt-management/types/custom-checksum-algorithm.d.ts

@@ -0,0 +1,10 @@
+/**
+ * The checksums a declared device is allowed to claim.
+ *
+ * Deliberately short. Every algorithm here has one agreed definition, so a declaration that
+ * names one cannot mean two different things on two devices. A vendor scheme needing a seed,
+ * a reflected table or a width other than a byte belongs in a device class, where it can be
+ * written down and tested as code rather than inferred from a name.
+ */
+export type CustomChecksumAlgorithm = "crc8" | "xor" | "sum";
+//# sourceMappingURL=custom-checksum-algorithm.d.ts.map

package/lib/typescript/module/src/modules/bt-management/types/custom-checksum-algorithm.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"custom-checksum-algorithm.d.ts","sourceRoot":"","sources":["../../../../../../../src/modules/bt-management/types/custom-checksum-algorithm.ts"],"names":[],"mappings":"AAAA;;;;;;;GAOG;AACH,MAAM,MAAM,uBAAuB,GAAG,MAAM,GAAG,KAAK,GAAG,KAAK,CAAC"}

package/lib/typescript/module/src/modules/bt-management/types/custom-checksum-spec.d.ts

@@ -0,0 +1,23 @@
+import { CustomChecksumAlgorithm } from "./custom-checksum-algorithm";
+/**
+ * How a declared frame proves it arrived intact.
+ *
+ * Without one a declaration has no integrity check at all: a corrupted notification whose
+ * header and length still look right is decoded, and the wrong number is reported as a
+ * reading. Every vendor driver examined for this fleet authenticates its frames, so a
+ * declaration that omits one trusts the radio further than the vendor does.
+ *
+ * The covered range is stated rather than assumed. A trailing checksum over everything
+ * before it is the common shape and is the default, but devices that cover only the payload
+ * exist, and a convention hidden in the validator would silently mis-verify them.
+ */
+export interface CustomChecksumSpec {
+    algorithm: CustomChecksumAlgorithm;
+    /** Byte offset holding the checksum. */
+    index: number;
+    /** First covered byte. Defaults to 0. */
+    from?: number;
+    /** Covered byte count. Defaults to every byte between `from` and `index`. */
+    byteCount?: number;
+}
+//# sourceMappingURL=custom-checksum-spec.d.ts.map

package/lib/typescript/module/src/modules/bt-management/types/custom-checksum-spec.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"custom-checksum-spec.d.ts","sourceRoot":"","sources":["../../../../../../../src/modules/bt-management/types/custom-checksum-spec.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,uBAAuB,EAAE,MAAM,6BAA6B,CAAC;AAEtE;;;;;;;;;;;GAWG;AACH,MAAM,WAAW,kBAAkB;IACjC,SAAS,EAAE,uBAAuB,CAAC;IAEnC,wCAAwC;IACxC,KAAK,EAAE,MAAM,CAAC;IAEd,yCAAyC;IACzC,IAAI,CAAC,EAAE,MAAM,CAAC;IAEd,6EAA6E;IAC7E,SAAS,CAAC,EAAE,MAAM,CAAC;CACpB"}

package/lib/typescript/module/src/modules/bt-management/types/custom-device-definition.d.ts

@@ -3,6 +3,7 @@ import { CompiledCustomField } from "./compiled-custom-field";
 import { CustomDeviceId } from "./custom-device-id";
 import { CustomDeviceSpec } from "./custom-device-spec";
 import { CustomFrameSpec } from "./custom-frame-spec";
+import { CustomLepuSpec } from "./custom-lepu-spec";
 import { IService } from "./service.type";
 /**
  * A validated, ready-to-run custom device. Only defineCustomDevice produces one.
@@ -18,5 +19,9 @@ export interface CustomDeviceDefinition {
     readonly fields: ReadonlyMap<string, CompiledCustomField>;
     /** Frame declaration of every monitor characteristic, keyed by its 128-bit UUID. */
     readonly frames: ReadonlyMap<string, CustomFrameSpec>;
+    /** MTU to request once connected, when the declaration asked for one. */
+    readonly preferredMtu?: number;
+    /** Validated Lepu protocol declaration, with its UUIDs normalised. */
+    readonly lepu?: CustomLepuSpec;
 }
 //# sourceMappingURL=custom-device-definition.d.ts.map

package/lib/typescript/module/src/modules/bt-management/types/custom-device-definition.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"custom-device-definition.d.ts","sourceRoot":"","sources":["../../../../../../../src/modules/bt-management/types/custom-device-definition.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,mBAAmB,EAAE,MAAM,kCAAkC,CAAC;AAEvE,OAAO,EAAE,mBAAmB,EAAE,MAAM,yBAAyB,CAAC;AAC9D,OAAO,EAAE,cAAc,EAAE,MAAM,oBAAoB,CAAC;AACpD,OAAO,EAAE,gBAAgB,EAAE,MAAM,sBAAsB,CAAC;AACxD,OAAO,EAAE,eAAe,EAAE,MAAM,qBAAqB,CAAC;AACtD,OAAO,EAAE,QAAQ,EAAE,MAAM,gBAAgB,CAAC;AAE1C;;GAEG;AACH,MAAM,WAAW,sBAAsB;IACrC,QAAQ,CAAC,CAAC,mBAAmB,CAAC,EAAE,IAAI,CAAC;IAErC,QAAQ,CAAC,EAAE,EAAE,cAAc,CAAC;IAE5B,QAAQ,CAAC,IAAI,EAAE,gBAAgB,CAAC;IAEhC,QAAQ,CAAC,SAAS,EAAE,MAAM,CAAC;IAE3B,QAAQ,CAAC,YAAY,EAAE,QAAQ,EAAE,CAAC;IAElC,QAAQ,CAAC,gBAAgB,EAAE,MAAM,CAAC;IAElC,yFAAyF;IACzF,QAAQ,CAAC,MAAM,EAAE,WAAW,CAAC,MAAM,EAAE,mBAAmB,CAAC,CAAC;IAE1D,oFAAoF;IACpF,QAAQ,CAAC,MAAM,EAAE,WAAW,CAAC,MAAM,EAAE,eAAe,CAAC,CAAC;CACvD"}
+{"version":3,"file":"custom-device-definition.d.ts","sourceRoot":"","sources":["../../../../../../../src/modules/bt-management/types/custom-device-definition.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,mBAAmB,EAAE,MAAM,kCAAkC,CAAC;AAEvE,OAAO,EAAE,mBAAmB,EAAE,MAAM,yBAAyB,CAAC;AAC9D,OAAO,EAAE,cAAc,EAAE,MAAM,oBAAoB,CAAC;AACpD,OAAO,EAAE,gBAAgB,EAAE,MAAM,sBAAsB,CAAC;AACxD,OAAO,EAAE,eAAe,EAAE,MAAM,qBAAqB,CAAC;AACtD,OAAO,EAAE,cAAc,EAAE,MAAM,oBAAoB,CAAC;AACpD,OAAO,EAAE,QAAQ,EAAE,MAAM,gBAAgB,CAAC;AAE1C;;GAEG;AACH,MAAM,WAAW,sBAAsB;IACrC,QAAQ,CAAC,CAAC,mBAAmB,CAAC,EAAE,IAAI,CAAC;IAErC,QAAQ,CAAC,EAAE,EAAE,cAAc,CAAC;IAE5B,QAAQ,CAAC,IAAI,EAAE,gBAAgB,CAAC;IAEhC,QAAQ,CAAC,SAAS,EAAE,MAAM,CAAC;IAE3B,QAAQ,CAAC,YAAY,EAAE,QAAQ,EAAE,CAAC;IAElC,QAAQ,CAAC,gBAAgB,EAAE,MAAM,CAAC;IAElC,yFAAyF;IACzF,QAAQ,CAAC,MAAM,EAAE,WAAW,CAAC,MAAM,EAAE,mBAAmB,CAAC,CAAC;IAE1D,oFAAoF;IACpF,QAAQ,CAAC,MAAM,EAAE,WAAW,CAAC,MAAM,EAAE,eAAe,CAAC,CAAC;IAEtD,yEAAyE;IACzE,QAAQ,CAAC,YAAY,CAAC,EAAE,MAAM,CAAC;IAE/B,sEAAsE;IACtE,QAAQ,CAAC,IAAI,CAAC,EAAE,cAAc,CAAC;CAChC"}

package/lib/typescript/module/src/modules/bt-management/types/custom-device-spec.d.ts

@@ -1,3 +1,4 @@
+import { CustomLepuSpec } from "./custom-lepu-spec";
 import { CustomServiceSpec } from "./custom-service-spec";
 /** Plain, JSON-shaped declaration of a Bluetooth device the SDK has no class for. */
 export interface CustomDeviceSpec {
@@ -8,5 +9,16 @@ export interface CustomDeviceSpec {
     /** Milliseconds without a usable frame before the read is abandoned. 1000-6000000. */
     stuckDataTimeoutMs: number;
     services: CustomServiceSpec[];
+    /**
+     * MTU to ask for once connected. A larger one carries a frame in fewer notifications and
+     * a command in fewer writes. Omit it to keep whatever the platform negotiates.
+     */
+    preferredMtu?: number;
+    /**
+     * Declares the Lepu/Viatom framed protocol, which brings its own frame reader and its own
+     * command sequence. A declaration with this needs no `services[].write`: commands are
+     * built rather than written down, and are addressed through `lepu.write`.
+     */
+    lepu?: CustomLepuSpec;
 }
 //# sourceMappingURL=custom-device-spec.d.ts.map

package/lib/typescript/module/src/modules/bt-management/types/custom-device-spec.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"custom-device-spec.d.ts","sourceRoot":"","sources":["../../../../../../../src/modules/bt-management/types/custom-device-spec.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,iBAAiB,EAAE,MAAM,uBAAuB,CAAC;AAE1D,qFAAqF;AACrF,MAAM,WAAW,gBAAgB;IAE/B,sFAAsF;IACtF,EAAE,EAAE,MAAM,CAAC;IAEX,sGAAsG;IACtG,SAAS,EAAE,MAAM,GAAG,MAAM,CAAC;IAE3B,sFAAsF;IACtF,kBAAkB,EAAE,MAAM,CAAC;IAE3B,QAAQ,EAAE,iBAAiB,EAAE,CAAC;CAC/B"}
+{"version":3,"file":"custom-device-spec.d.ts","sourceRoot":"","sources":["../../../../../../../src/modules/bt-management/types/custom-device-spec.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,cAAc,EAAE,MAAM,oBAAoB,CAAC;AACpD,OAAO,EAAE,iBAAiB,EAAE,MAAM,uBAAuB,CAAC;AAE1D,qFAAqF;AACrF,MAAM,WAAW,gBAAgB;IAE/B,sFAAsF;IACtF,EAAE,EAAE,MAAM,CAAC;IAEX,sGAAsG;IACtG,SAAS,EAAE,MAAM,GAAG,MAAM,CAAC;IAE3B,sFAAsF;IACtF,kBAAkB,EAAE,MAAM,CAAC;IAE3B,QAAQ,EAAE,iBAAiB,EAAE,CAAC;IAE9B;;;OAGG;IACH,YAAY,CAAC,EAAE,MAAM,CAAC;IAEtB;;;;OAIG;IACH,IAAI,CAAC,EAAE,cAAc,CAAC;CACvB"}

package/lib/typescript/module/src/modules/bt-management/types/custom-field-encoding.d.ts

@@ -5,6 +5,12 @@
  * - "int"    two's complement signed integer, 1-6 bytes
  * - "sfloat" IEEE-11073 16-bit SFLOAT, exactly 2 bytes (standard GATT vitals)
  * - "float"  IEEE-11073 32-bit FLOAT, exactly 4 bytes (standard GATT thermometer)
+ * - "ascii"  decimal digits written as text, one digit per byte
+ *
+ * "ascii" is not a numeric encoding at all: the bytes are characters, so `"120"` arrives as
+ * 0x31 0x32 0x30. Serial-derived devices report whole records this way. Digits read
+ * left to right, so the field may not be declared little-endian - reversing them would
+ * turn 120 into 21.
  */
-export type CustomFieldEncoding = "uint" | "int" | "sfloat" | "float";
+export type CustomFieldEncoding = "uint" | "int" | "sfloat" | "float" | "ascii";
 //# sourceMappingURL=custom-field-encoding.d.ts.map

package/lib/typescript/module/src/modules/bt-management/types/custom-field-encoding.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"custom-field-encoding.d.ts","sourceRoot":"","sources":["../../../../../../../src/modules/bt-management/types/custom-field-encoding.ts"],"names":[],"mappings":"AAAA;;;;;;;GAOG;AACH,MAAM,MAAM,mBAAmB,GAAG,MAAM,GAAG,KAAK,GAAG,QAAQ,GAAG,OAAO,CAAC"}
+{"version":3,"file":"custom-field-encoding.d.ts","sourceRoot":"","sources":["../../../../../../../src/modules/bt-management/types/custom-field-encoding.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;GAaG;AACH,MAAM,MAAM,mBAAmB,GAAG,MAAM,GAAG,KAAK,GAAG,QAAQ,GAAG,OAAO,GAAG,OAAO,CAAC"}

package/lib/typescript/module/src/modules/bt-management/types/custom-frame-spec.d.ts

@@ -1,4 +1,5 @@
 import { CustomByteOrder } from "./custom-byte-order";
+import { CustomChecksumSpec } from "./custom-checksum-spec";
 /**
  * How a notification buffer is recognised as a complete frame.
  *
@@ -23,5 +24,12 @@ export interface CustomFrameSpec {
         /** Bytes in the frame the length field does not count (header, checksum, ...). */
         overheadBytes: number;
     };
+    /**
+     * How the frame proves it arrived intact.
+     *
+     * Optional because some devices genuinely send none, but a declaration without one accepts
+     * whatever the radio delivered. Declare it wherever the device has one.
+     */
+    checksum?: CustomChecksumSpec;
 }
 //# sourceMappingURL=custom-frame-spec.d.ts.map

package/lib/typescript/module/src/modules/bt-management/types/custom-frame-spec.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"custom-frame-spec.d.ts","sourceRoot":"","sources":["../../../../../../../src/modules/bt-management/types/custom-frame-spec.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,eAAe,EAAE,MAAM,qBAAqB,CAAC;AAEtD;;;;;;GAMG;AACH,MAAM,WAAW,eAAe;IAE9B,wDAAwD;IACxD,MAAM,CAAC,EAAE,MAAM,EAAE,CAAC;IAElB;;;OAGG;IACH,cAAc,EAAE,MAAM,CAAC;IAEvB,yDAAyD;IACzD,MAAM,CAAC,EAAE;QAEP,uCAAuC;QACvC,KAAK,EAAE,MAAM,CAAC;QAEd,UAAU,EAAE,CAAC,GAAG,CAAC,CAAC;QAElB,SAAS,EAAE,eAAe,CAAC;QAE3B,kFAAkF;QAClF,aAAa,EAAE,MAAM,CAAC;KACvB,CAAC;CACH"}
+{"version":3,"file":"custom-frame-spec.d.ts","sourceRoot":"","sources":["../../../../../../../src/modules/bt-management/types/custom-frame-spec.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,eAAe,EAAE,MAAM,qBAAqB,CAAC;AACtD,OAAO,EAAE,kBAAkB,EAAE,MAAM,wBAAwB,CAAC;AAE5D;;;;;;GAMG;AACH,MAAM,WAAW,eAAe;IAE9B,wDAAwD;IACxD,MAAM,CAAC,EAAE,MAAM,EAAE,CAAC;IAElB;;;OAGG;IACH,cAAc,EAAE,MAAM,CAAC;IAEvB,yDAAyD;IACzD,MAAM,CAAC,EAAE;QAEP,uCAAuC;QACvC,KAAK,EAAE,MAAM,CAAC;QAEd,UAAU,EAAE,CAAC,GAAG,CAAC,CAAC;QAElB,SAAS,EAAE,eAAe,CAAC;QAE3B,kFAAkF;QAClF,aAAa,EAAE,MAAM,CAAC;KACvB,CAAC;IAEF;;;;;OAKG;IACH,QAAQ,CAAC,EAAE,kBAAkB,CAAC;CAC/B"}