/**
 * Map a sensor key from AWN's `lastData` to the name of the `batt*`
 * field that reports the battery state of that sensor's physical
 * probe. Used by the platform layer to bundle battery state with
 * each sensor's value update, so wrappers can expose a HomeKit
 * `Battery` sub-service with a meaningful `StatusLowBattery` boolean.
 *
 * Why per-sensor and not per-station? AWN stations are modular —
 * the outdoor base, the indoor display, the AQIN module, the WH31L
 * lightning sensor, and each WH31 channel probe all have separate
 * batteries. A single station can have 7+ independently-batteried
 * components.
 *
 * IMPORTANT: in HomeKit only ONE Battery sub-service per probe is
 * exposed, attached to a designated "canonical" sensor accessory
 * (see CANONICAL_SENSOR_FOR_BATTERY below). Without this dedup, a
 * fully-populated WS-2000 produces 30+ battery tiles in Apple Home
 * (one per accessory the probe powers) — overwhelming and
 * redundant. With dedup, each physical probe shows ONE battery
 * status, attached to its most representative sensor (outdoor
 * temp, indoor temp, channel temp, CO2 for AQIN, lightning_day
 * for the WH31L).
 *
 * AWN's batt* field convention:
 *   battout         — outdoor combo array (wind, rain, solar, UV,
 *                     outdoor temp/humidity, feels-like, dew point)
 *   battin          — indoor display console (indoor temp/humidity,
 *                     feels-like-in, dew-point-in, both pressure fields)
 *   batt{1..N}      — WH31 numbered probe channels 1..N (per-probe
 *                     temperature and humidity)
 *   batt_co2        — AQIN indoor air quality module (PM2.5, PM10,
 *                     CO2, AQIN's internal temp/humid housing
 *                     sensors). Despite the name, this powers the
 *                     whole AQIN module, not just CO2.
 *   batt_lightning  — WH31L lightning sensor (strike count, distance,
 *                     timestamp). AWN catalogs this sensor as the
 *                     WH31L; Ecowitt catalogs the same hardware as
 *                     the WH57.
 *
 * Returns the batt-field name as a string, or undefined when the
 * sensor key doesn't correspond to a known physical probe. Callers
 * should treat undefined as "no battery for this sensor" and skip
 * the Battery sub-service entirely.
 */
/**
 * Whether this sensor key is the canonical one for displaying the
 * HomeKit Battery sub-service for the given battery field. Used by
 * the platform layer to suppress redundant battery sub-services on
 * non-canonical accessories sharing the same physical probe.
 */
export declare function isCanonicalSensorForBattery(sensorKey: string, batteryField: string): boolean;
export declare function batteryFieldForSensor(sensorKey: string): string | undefined;
/**
 * Battery fields the VENDOR declares with INVERTED polarity
 * (sensor-map.md §19.6): the published dictionary states
 * "1=Low 0=OK" for the lightning detector and the leak detectors,
 * opposite to every other field's "1=OK 0=Low". The live-device
 * observation (payload 0 on a healthy detector, shown low by the
 * uniform decoder) supports the declaration.
 */
export declare const VENDOR_INVERTED_BATTERY_FIELDS: ReadonlySet<string>;
/**
 * The battery-decoder polarity policy for a given adopted catalog
 * version (§19.6). The SINGLE source of truth shared by the runtime
 * decoder (`readBatteryLow`) and the adoption-preview consequence model
 * (PR #67 review R2-F2), so the two can never disagree. The caller
 * decides WHEN the v2 runtime is driving (the platform's
 * `decoderAdopted()` passes 1 for flag-off / safe mode); this maps the
 * effective adopted version to a policy.
 */
export declare function batteryDecoderPolicy(catalogAdopted: number): 'standard' | 'vendor-inverted';
/**
 * Helper: read a battery field's raw value from a lastData object
 * and return the HomeKit-aligned "low" boolean.
 *
 * Standard AWN convention: 0 = low / 1 = good; HomeKit's is true =
 * low. For the vendor-declared INVERTED fields the correct decode is
 * the opposite — and applying it is ADOPTION-GATED (§19.6): only a
 * configuration whose `catalogAdopted` covers catalog 3 gets the
 * vendor-correct polarity. Un-adopted configs, legacy mode, and safe
 * mode keep the historical uniform decode (including the documented
 * spurious lightning low-battery and its README workaround), because
 * silently flipping a battery signal on upgrade is a behavior change.
 *
 * Returns undefined when the battery field is missing, non-numeric,
 * or (under the new vendor-polarity policy) not one of the declared
 * 0/1 states — the wrapper should not add or update a Battery
 * sub-service, and an out-of-contract value must never be manufactured
 * into a healthy "OK" reading (PR #67 review F7).
 */
export declare function readBatteryLow(lastData: Record<string, unknown>, batteryField: string | undefined, catalogAdopted?: number): boolean | undefined;
//# sourceMappingURL=batteryFields.d.ts.map