MELCloud & MELCloud Home API for Node.js - v60.5.0
    Preparing search index...

    Interface ClassicErrorLogEntry

    One Classic error-log entry: the cross-dialect ErrorLogEntry kept precise — the Classic wire always carries a numeric device id and a message text, so neither loosens to the neutral optionality.

    interface ClassicErrorLogEntry {
        at: string;
        atEpochMs: number | null;
        clearedAt?: string;
        clearedAtEpochMs?: number | null;
        code?: string;
        deviceId: number;
        message: string;
    }

    Hierarchy (View Summary)

    Index
    at: string

    When the error occurred (ISO 8601, as the wire reported it).

    atEpochMs: number | null

    The instant of at normalized to epoch milliseconds — each dialect anchors its own wall-clock discipline at its boundary. Home at is UTC wall clock, so its instant is exact. Classic at is BUILDING-local wall clock anchored in the client's configured timezone (ClassicAPIConfig.timezone, the host's zone when unset): exact only insofar as that timezone is the building's — a building in another zone skews the instant by the zone delta, and the recorded worldwide skew reaches ±14 h, so day-scale reasoning stays safe where sub-hour reasoning does not. null when the wire's at cannot be parsed (such entries are deliberately kept).

    clearedAt?: string

    When the error cleared (Home only, while uncleared it is absent).

    clearedAtEpochMs?: number | null

    The instant of clearedAt normalized to epoch milliseconds — present exactly where clearedAt is (Home, once cleared), anchored in UTC like the Home discipline of atEpochMs; null when the wire's stamp cannot be parsed.

    code?: string

    Wire error code (Home only — the Classic wire has none).

    deviceId: number

    Numeric ID of the device that reported the error.

    message: string

    Error message text (empty or null wire messages are filtered out).