export interface MayaraClientOptions {
    host: string;
    port: number;
    secure?: boolean;
    timeout?: number;
    debug?: (msg: string) => void;
}
export declare class MayaraClient {
    private host;
    private port;
    private secure;
    private timeout;
    private debug;
    constructor(options: MayaraClientOptions);
    request(method: string, path: string, body?: unknown): Promise<unknown>;
    getRadars(): Promise<Record<string, unknown>>;
    getCapabilities(radarId: string): Promise<unknown>;
    getControls(radarId: string): Promise<Record<string, unknown>>;
    setControl(radarId: string, controlId: string, value: unknown): Promise<unknown>;
    setControls(radarId: string, controls: Record<string, unknown>): Promise<unknown>;
    getTargets(radarId: string): Promise<unknown>;
    acquireTarget(radarId: string, bearing: number, distance: number): Promise<Record<string, unknown>>;
    cancelTarget(radarId: string, targetId: number): Promise<unknown>;
    getSpokeStreamUrl(radarId: string): string;
    getTargetStreamUrl(radarId: string): string;
    /**
     * mayara's Signal K v1 stream. Used by DeltaForwarder to relay
     * `notifications.*` and `radars.*` deltas upstream.
     *
     * `?subscribe=none` is deliberate: under Signal K's subscription model the
     * default (`self`) streams own-ship `navigation.*` too, but the plugin must
     * NOT forward nav — mayara only has it because it received it from Signal K
     * in the first place, so re-publishing it would loop it back. Starting from
     * `none` and letting the forwarder subscribe to exactly `radars.*` /
     * `notifications.*` keeps nav (and AIS) out, and stays correct whether mayara
     * treats a later subscribe as additive (SK-compliant) or narrowing.
     */
    getStateStreamUrl(): string;
    close(): void;
}
//# sourceMappingURL=mayara-client.d.ts.map