/**
 * Value distribution routing MECHANISM (finding-#4 Stage 3; platform-
 * wired in Stage 4).
 *
 * LIVE as of Stage 4's platform-boundary commit: `platform.ts`'s
 * flag-gated `discoverDevicesV2` builds this routing map at reconcile
 * time and both the polling and realtime paths fan values out through
 * `distributeViaRouting` (via `distributeViaV2Routing`). With the
 * `_sensorMapV2` opted out (non-default) the v1.6.0 `createSensorWrapper` +
 * uniqueId-lookup path still drives everything and this module is
 * dormant.
 *
 * This is the load-bearing wire that makes a row's wrapper actually
 * receive readings. v1.6.0's `distribute` matched AWN payload keys to
 * wrappers by a `MAC-sensorKey` uniqueId built from the built-in AWN
 * vocabulary — a custom `dataPoint` (`my_barn_wind`) would never match
 * and its value was dropped. The row-driven router instead builds its
 * `(mac, dataPoint) → wrapper` map straight from the effective sensor
 * map, so any row (known or custom) that resolved a wrapper receives its
 * value; `coerceValue` handles the non-numeric (timestamp / boolean)
 * fields at the boundary. (Custom rows construct through the restored
 * resolution table as of Stage 4's table-restoration commit.)
 *
 * Unit tests: `tests/unit/sensorMap/routing.test.ts` (mechanism in
 * isolation); lifecycle: `tests/integration/discoverV2.test.ts`.
 */
import type { Logger, PlatformAccessory } from 'homebridge';
import type { AmbientWeatherSensorsPlatform, SensorAccessory } from '../platform.js';
import type { EffectiveSensorMap, EffectiveSensorRow } from './types.js';
export interface RoutingEntry {
    wrapper: SensorAccessory;
    row: EffectiveSensorRow;
}
/** Uppercased `${stationMac}|${dataPoint}` — the routing map key. */
export declare function routingKey(stationMac: string, dataPoint: string): string;
/**
 * Build the `(mac, dataPoint) → wrapper` routing map from an effective
 * map. Each enabled configured row is instantiated via
 * `instantiateWrapper`; a constructor (or dispatch) that throws is
 * isolated — the error is logged naming the row and that one wrapper is
 * dropped from the map, so a single bad row can't abort registration of
 * the rest.
 */
export declare function buildWrapperRouting(platform: AmbientWeatherSensorsPlatform, effectiveMap: EffectiveSensorMap, accessoryForUid: (uid: string) => PlatformAccessory | undefined, log?: Logger): Map<string, RoutingEntry>;
/** A station's raw payload — only the fields the router touches. */
export interface StationPayload {
    macAddress: string;
    lastData: Record<string, unknown>;
}
/**
 * Fan a batch of station payloads through the routing map. For every
 * `(mac, dataPoint)` present in both the payload and the map, coerce the
 * raw value (drop the tick on a malformed timestamp / non-numeric) and
 * push it to the wrapper's `setValue`.
 */
export declare function distributeViaRouting(platform: AmbientWeatherSensorsPlatform, routing: Map<string, RoutingEntry>, stations: ReadonlyArray<StationPayload>): void;
//# sourceMappingURL=routing.d.ts.map